Every time a passenger books through Uber, three things happen at once. Uber keeps a quarter to a third of the fare. Uber, not you, owns that customer. And Uber decides what tomorrow's fare will be, while you find out when everyone else does.
For years the obvious answer, your own app, sat firmly out of reach. Building one from scratch runs £150,000 to £500,000 and takes a year and a half, which is fine for a venture-backed startup and absurd for a private hire firm with thirty cars. That maths has changed.
White-label dispatch platforms now let an operator of almost any size put a passenger app in the App Store under their own name, for a tiny fraction of that. Here's what's actually inside one, what it costs, and how the numbers stack up against the aggregators.
What your passengers actually get
A white-label app done properly should feel, to your passenger, exactly like the apps they already use, just with your name on it. They enter pickup and dropoff and see a fare estimate straight away. They pick the vehicle they want, whether that's a saloon, an MPV, an executive car, or wheelchair access, depending on what you run. They confirm, and the job drops into dispatch automatically. A map shows the driver approaching with a live ETA. Mid-trip they can call the driver through a masked number, so neither side ever sees the other's real one, or cancel if plans change. Payment happens on its own when the trip ends, with no cash and no fumbling with a card machine. Then they rate the driver, and that rating feeds your performance dashboard.
Where it really diverges from Uber is loyalty. On Uber, the loyalty relationship belongs to Uber. On your app, it belongs to you. Passengers earn points for every pound they spend, climbing through Bronze, Silver, Gold and Platinum tiers, and they redeem those points against future rides. It's the same trick that keeps people loyal to the local coffee shop instead of Costa, except here every point earned ties the passenger a little tighter to your company rather than someone else's platform.
The money side is where it gets interesting. Card details are tokenised by Stripe and held against the passenger's account in your app. The fare is charged automatically when the trip finishes and lands in your own Stripe merchant account, usually within two business days. GridX takes no commission on the transaction. Card processing runs at roughly 1.5 percent, Stripe's standard European rate. Hold that figure next to the 25 to 30 percent an aggregator takes and the case starts to make itself.
Running the numbers
Let's make it concrete. Say your fleet turns over £25,000 a month in fares.
Push all of that through Uber or Bolt at a 25 percent commission and £6,250 a month walks out the door to the aggregator, leaving you £18,750. Run the same fares through your own app on Stripe's 1.5 percent and your processing cost is about £375, leaving you £24,625. That's a difference of £5,875 every month, or £70,500 a year staying in your business instead of someone else's, from a fleet of this size.
You won't move everyone over on day one, and you don't need to. Shift even 30 percent of your fares from Uber to your own app in the first year and that's still £21,150 kept. The white-label app module runs £99 a month, which is £1,188 a year. The return shows up almost immediately.
What "white-label" really means
White-label means the app wears your branding, not GridX's. It goes into the Apple App Store and Google Play under your developer account, with your company name, say "London Premier Cars" or "ABC Taxis", and your logo as the icon. The colour scheme matches your brand, usually just by handing over your primary and secondary hex colours. The passenger-facing text talks about your company, and the SMS and push notifications come from your name too.
What's shared with other operators is the code underneath, and that's the whole point of white-label software. Every operator on the platform picks up new features, bug fixes and performance improvements automatically, without anyone having to keep a development team on the payroll.
The doubts operators usually raise
The first one is always the same: will passengers really download yet another app? Honestly, that depends entirely on whether you give them a reason. People who already like your service will install it if there's something in it for them, so the launches that work tend to lean on incentives, 20 percent off the first three app bookings, a sign-up loyalty bonus of perhaps 500 points (about £5 off), a banner on your website that says "skip the phone queue, book on the app." Operators who actually promote it see 30 to 50 percent of bookings move across within six months. Operators who quietly list it in the store and hope see very little.
Then there's the worry that your customers are older and would rather call. That's fine, because phone bookings carry on exactly as they always have. The aim was never to force everyone onto the app; it's to give the app-comfortable customers a reason to book direct with you instead of opening Uber. The ones who like to call keep calling, and the dispatcher sees app jobs and phone jobs side by side on the same live screen.
And the inevitable "what happens when someone says the app's broken?" On a white-label platform you have a support relationship with the provider, so the technical fixes are their job. Yours is first-line reassurance, the "I'll look into this and come straight back to you." A well-run platform publishes a status page showing uptime, and when something does break it's fixed centrally and pushed to every operator at once.
What you need before you launch
The shopping list is short. You'll want an Apple Developer account at £99 a year to publish on iOS, a Google Play Developer account with its one-off £25 registration fee, and a Stripe account (free to set up) for payments. You'll need your brand assets, a logo as SVG or high-res PNG plus your primary colour, and a Twilio account for SMS and masked calls, which is free to create and billed on usage.
The platform provider handles the App Store submission and the white-label setup. For most operators the app is live within two to three weeks of handing those over.
The lighter-touch option: a booking widget
Not every operator wants a full app on day one, and a booking widget is the lighter alternative. It's a small piece of JavaScript that drops a booking form straight onto your existing website, so passengers can book without leaving the site or downloading anything.
It suits some businesses better than an app. Airport transfer firms, where people book days ahead from a laptop. Corporate clients booking through a travel portal. Or any operator who wants a digital booking channel running today while the app is still being set up. The two aren't rivals; plenty of operators run both, the widget catching website and desktop bookings and the app looking after repeat mobile customers.
The era of handing a quarter of every fare to an aggregator is ending for operators willing to build their own booking channel. The technology isn't the barrier any more, and it isn't really the cost either, at £99 a month against thousands lost in commission. What's left is inertia, and the operators who move first in their town tend to lock in the repeat custom before anyone nearby has thought to.