The LeaseApp that puts Wevi back in the driver's seat.

Who is Wevi?

Wevi is a mobility partner. About 80 percent of its work revolves around the car itself: the purchase, maintenance, tires, vehicle inspection, and the vehicle’s entire lifecycle. But the remaining twenty percent is just as crucial. Think of charging stations and the regulations surrounding electrification, the branding and outfitting of company vehicles, and the daily stream of fines, maintenance, and administrative tasks. For the driver, all of that was scattered across different platforms. The challenge was to bring it all together in one place.

The old app had reached its limits.

The previous custom-built app dated back to a time when technology was even more limited. Features were missing, and the underlying infrastructure was fragile. Data exchange took place via CSV files. While these were sent automatically, the process remained error-prone: a single discrepancy in a file would cause the data to become inaccurate. Inquiries and documents were largely handled via email: about 80 to 100 messages a day arrived in a single central inbox, ranging from “Where is my green card?” to “How do I report this damage?” The result was predictable: overflowing inboxes, duplicate work, and unanswered questions.

It turned out that those very years with the old app were actually an advantage. Wevi knew from experience what worked and what didn’t, what drivers actually used, and what was missing. As a result, there was concrete input on the table from the very beginning, rather than a wish list that would have to take shape over time.

The problem lay at the core, not in the inbox.

The real problem ran deeper than a full inbox. Over the years, the digital landscape had become increasingly complex, and the underlying codebase had become unstructured. As a result, every change became a risk rather than an improvement, and Wevi could hardly make any changes on its own without outside help. What they needed wasn’t a quick fix, but a foundation that was manageable again and that they could steer themselves.

Our approach: build together, maintain ownership.

Wevi has a great deal of in-house technical expertise. What they were looking for wasn’t a vendor who simply checks off a list, but a partner who could understand the context in which they work every day: security, GDPR requirements, and the architectural choices that go along with them. That called for genuine collaboration, and that choice shaped our entire way of working. We deliberately chose co-development over a traditional client-supplier model. The reason was clear: Wevi wanted to retain in-house ownership of the data layer (the layer that retrieves and transmits all data) so that they could make changes themselves after delivery. 

So Wevi built that data layer while Cube handled the app, the architecture, and the releases. Mark, Wevi’s developer, visited Cube’s office weekly and brainstormed directly with the development team, ensuring that questions were answered the moment they arose rather than after days of email exchanges. To ensure quality, we shared our guidelines upfront, discussed which solution and functionality would work best along the way, and concluded with a code review. For Wevi, this wasn’t a new app but a step toward digital maturity: moving from a landscape that was becoming constricting on all sides to a structured foundation under their own management.

The solution: two sides of a single platform.

The platform serves not one but two leasing companies. Wevi and ELC (European Lease Company) run on the same foundation but are strictly separated, each with its own brand, data, and settings. It has two types of users: on the outside, the driver with the app on their phone; on the inside, the leasing company’s administrator, who controls what the driver sees and can do from a single management environment. Everything that provides peace of mind on one side offers control on the other.

For Wevi.

The management environment is the heart of the platform, and this is precisely where the greatest benefits are realized. All tasks that used to be handled via separate emails now come together centrally in one place where the work remains visible. Wevi uses it to manage contracts, handle documents, and send push notifications, all the way down to the individual driver level.

Advanced push notifications.

These push notifications aren’t generic messages sent to all users. We built a notification module in which Wevi sets its own filters to reach precisely the group that needs the message. For example, all drivers who are still driving on summer tires and have driven a certain number of kilometers. That group receives a personalized message about changing their tires; the rest are not bothered. Messages can be sent once or recur periodically (weekly or monthly, for example)without anyone having to think about it. And thanks to deep linking, when a driver taps the notification, they’re taken directly to the right place in the app, rather than to the home screen where they’d have to search for it themselves.

The biggest difference lies in what an employee sees as soon as they click on a driver’s profile. Instead of five systems side by side, the entire file is displayed on a single screen: contracts and vehicles, outstanding traffic tickets, claims, expense reports, and documents. It also includes the details that typically complicate support requests, such as whether the invitation was delivered and opened, whether the account was activated, whether push notifications are enabled, and which app version the user is running. This changes the conversation. Take the most common question: “I didn’t receive an invitation.” In the past, this would have triggered a search through email inboxes. Now, the agent opens a single screen and sees all the necessary information.

Roles and Permissions.

Because all this information is sensitive, the system uses roles and permissions on two axes. By company: anyone working for ELC sees everything related to ELC and nothing related to Wevi. And by responsibility: those who handle claims see only claims and not the requests assigned to a colleague. This reduces clutter in daily work and keeps the data of both companies neatly separated, in full compliance with the GDPR. If a driver does encounter an issue, an employee can use the “impersonate” function to open the exact same screen the driver sees in read-only mode and without taking over the account. An administrator can switch between Wevi and ELC with a single action, and if something goes wrong with an account, Wevi manages or deletes it itself, without Cube’s intervention.

Under the hood: React Native.

For those who want to understand the technology behind it: the app is built with React Native, allowing iOS and Android to run from a single codebase. This not only eliminates the need for two separate development processes but also keeps both versions in sync. We use Expo for distribution and updates. This allows us to send minor adjustments, such as a text change or an interface improvement, directly to users without them having to first install an update from the App Store or Google Play. A full store update is only required for fundamental changes.

The web app shares a large portion of that same codebase and is now in use as well. This isn’t just convenient for users who prefer to work on a laptop; it also solves a practical problem: files are often stored on the laptop rather than on the phone. Through the web app, users can upload those documents with just a few clicks, without having to go through their mobile device. This same technical choice also makes it possible to offer a specific version of the “My” environment as a web version in the future.

Secure access and data protection from the very first line of code.

The integration with Wevi is handled via a back-office API. Wevi provides and manages the data (users, vehicles, traffic tickets, claims, and passes) from its own systems, and the app retrieves that data and sends information back. The management environment itself is an admin panel with a modular design, allowing new features to be added step by step without having to overhaul the entire system. Because personal data and vehicle documents pass through the platform, secure access and data protection have been built in from the very first line of code, fully compliant with the GDPR.

From Carwise to the new app: how the data migration went.

The transition was no small undertaking. Cube took over the existing platform from another party, and the old backend could no longer be modified. What was possible, however, was to carry over all historical data, so that after logging in, a driver would simply find their own data. For the user, the transition therefore felt mainly like a new app and a new password, not like starting over. Technically, it worked like this: all driver data is stored in Carwise, the system in which Wevi maintains its lease administration. Wevi forwarded those users and their associated data to Fabric, the middle layer between the administration system and the app. We then retrieved all drivers along with their complete data history via the back-office API, and based on that, we set up an account for each user in the admin environment.

The rollout to all drivers.

After that, it was just a matter of sending out invitations. Within that admin environment, we built the functionality to send activation emails to individual drivers, organizations, and umbrella organizations. Drivers activated their accounts themselves, went through a brief onboarding process in the app, and were up and running. No need to fill out forms again or search for contracts: thanks to the syncs we ran, all relevant history was available from the moment they first logged in. Still, the rollout went remarkably smoothly. After an internal testing phase with few surprises, the app was first rolled out to one of Wevi’s major clients, representing about 10% of users. That went so smoothly that within two days, all remaining drivers were invited to join. To make the transition as easy as possible, we built the public website leaseapp.nl alongside the app: the gateway where a driver can see at a glance what the app does, download it immediately, and find answers to frequently asked questions.

The result.

The numbers best illustrate what has changed. Shortly after the rollout, more than half of the potential users had already downloaded the new app, a figure comparable to the total user base the old app had built up over several years. The fact that the migration went smoothly helped: riders simply had to activate their accounts and could immediately access their own history in the app.

Behind the scenes of day-to-day operations, the difference is just as tangible. Whereas previously about 80 to 100 driver inquiries per day were received in a single central inbox, those now come through the portal: a 30% decrease in email volume. A damage report that used to take three days to process due to back-and-forth emails is now completed in a single step. Because the number of support hours spent on errors and bugs remained low, Wevi can focus on further developing the platform.

Equally telling is who is using the app. Adoption spans the entire organization, from those who interact with drivers all day long to colleagues who are nearing retirement. You hardly ever hear from the drivers themselves, and that’s exactly the sign that it’s working: as long as their green card is within reach, there’s no reason to call.

What Wevi has in hand now.

The biggest gain? Wevi went from an app they couldn’t touch to a platform they control themselves. The integration with their own systems is managed in-house, the email chaos has been replaced by a single, organized hub, and the foundation is flexible enough to scale with the business. Whether Wevi eventually adds a third company or starts offering a completely different type of lease asset: the foundation is already in place.