The Cost Conversation We Had Before We Built Anything
Three weeks before we shipped the first version of Volta, a rideshare driver messaged me. She'd pulled up to a rapid charger in Croydon, plugged in for 20 minutes, and walked away with a £47 bill. The charging itself was £12. The idle fee, parking surcharge, and network markup accounted for the rest. She had no idea until the receipt hit her phone. That conversation changed how we thought about the entire app.
The Price Surprise Nobody Wanted
EV drivers face a fragmented landscape. Forty-plus networks operate across the UK, each with its own pricing model, idle fee structure, and terms. Shell Recharge charges differently to InstaVolt. BP Pulse has a different fee schedule to Instavolt again. Parking, taxes, and network surcharges stack on top. Most drivers don't see the full picture until they're standing next to a charger, committed to using it, or worse, they see it on a receipt after the fact.
The rideshare driver wasn't an outlier. She was our target customer. And she made the problem impossible to ignore. If Volta was going to matter, we couldn't just show a map of chargers. We had to show the actual cost.
That meant doing the hard work upfront: aggregating pricing from every network, standardising it, and displaying it clearly. Not just the kilowatt-hour price. The idle fee. The parking. The tax. The lot. Before the driver even arrives.
Why We Refused the Shortcut
Early on, someone suggested we simplify the problem. 'Show per-kWh and call it done,' they said. 'Most users only care about charging price anyway.'
We pushed back hard. The rideshare driver wasn't an edge case; she was proof that drivers make decisions based on complete information, not partial information. A commuter choosing between three chargers on a journey doesn't just weigh kilowatt-hour rates. A fleet manager doesn't approve a charging location based on one number. A homeowner considering whether to list their own charger on the community marketplace needs to understand what they'll actually earn after parking, network fees, and transaction costs.
Leaving cost information out would have made Volta faster to build. It would have made the app feel lighter. But it would have been useless in the real world.
Total cost became non-negotiable because we'd already heard from the people who would use Volta. They needed it.
The Practical Work of Honesty
Building true total cost into the map required us to think differently about the data we collected and how we displayed it. Every network has its own pricing structure, and they update it. Some charge idle fees in 5-minute increments. Others use 1-minute. Some parking charges are bundled, others separate. Some networks apply VAT differently.
We had to aggregate all of that and present it in a way that made sense to a driver checking their phone at a motorway junction. The journey planner added another layer: when you're plotting a route, the cost changes based on your vehicle, your driving pattern, and where you decide to stop. The premium features that help drivers optimise their journey account for that variability.
The community charging marketplace added complexity again. A homeowner listing a charger doesn't see the same cost structure as a rapid charger network. We had to build a way for private charger hosts to set their own pricing, see their earnings clearly, and understand what they'd actually make after Volta's costs.
Fleet managers needed a different view again. Consolidated billing, cost-centre reporting, policy controls. They needed to see total cost per journey, across all their drivers, across all networks, standardised in one place.
None of that works if the underlying number - the true total cost - is incomplete or hidden.
What Changed When We Committed
Once we committed to showing true total cost, it rippled through every decision. The map design, the search filters, the receipt history, the way we export expense data. The feature set clarified itself around that single commitment.
When a fleet manager exports a report, they're not guessing. When a commuter checks a route, they're not surprised. When a homeowner lists a charger, they know what price they're setting and why. When that rideshare driver (if she ever uses us) stops at a charger, she sees the full number before she plugs in.
That clarity has made it easier to talk to customers, easier to build features that matter, and easier to explain why Volta exists. We're not just another map. We're the map that shows you the number that actually matters.
The Question That Stays With Us
The rideshare driver's message is still in our Slack. We look at it before product reviews, before we make a call about what to build next. Not because it was a complaint, but because it was a clarity.
She'd done everything right. She'd found a charger, stopped, charged her vehicle, left. And she still got a surprise. In a world where EV drivers are already managing charging stops, route planning, and network differences, we decided surprise had no place in our product.
If you've been building something, how do you decide what's non-negotiable before you ship? What's the one piece of information your customers need to see before they commit to your service?
Ready to try Volta by MRVL?
One tap to download. No sign-up wall.