Local firms don't beat the ride-hail apps by copying them — they beat them with account work, school runs, airport pre-bookings and thirty years of local loyalty. Meridianstacks builds you a private hire booking app, driver app and dispatcher console you own outright — no per-driver licence, no commission per booking. Your matched hub is Lagos (UTC+1) — a 0–1 hour offset, so our engineers share your full working day — and every build is a fixed price in pounds, billed by milestone.
Custom taxi dispatch software in the UK would typically cost £20,000–£120,000 at a local agency, and white-label systems rent you an app with per-driver fees forever. Meridianstacks builds your own private hire booking app, driver app and dispatcher console for 40–70% less — focused single-app dispatch, our Focused tier, runs £8,000–£14,000 — at a fixed price in pounds with full code ownership, milestone billing and no commission on any job.
Established local firms losing walk-up trade to ride-hail apps but holding the work those apps can't do well — accounts, contracts, school runs and pre-booked airport jobs. Give your regulars an app without giving away your margin.
If jobs live on a whiteboard, a radio channel or a WhatsApp group, you already run a dispatch system — it's just in your dispatcher's head. We turn it into a live console without forcing a big-bang switchover.
White-label dispatch systems commonly charge per driver, per month — and sometimes per booking — and you never own the software or the passenger relationship. A custom platform ends the rent and puts your brand on the phone.
Whether you run six cars or a hundred and sixty, if your bread and butter is accounts, schools and airports, this is built for you.
Book now or pre-book days ahead, live driver tracking and ETA, saved addresses, fare quoted before confirming, card or cash, booking history and one-tap rebooking — your brand on your customers' phones, not a marketplace's.
Job offers with pickup and destination, accept or reject, one-tap navigation handoff to Google Maps or Waze, passenger-on-board and clear statuses, shift view and a running earnings summary so end-of-week reconciliation stops being an argument.
A live map of every car, the booking diary for today and the weeks ahead, automatic allocation by zone and availability with manual override — drag a job to a driver when you know something the algorithm doesn't.
Ride-hail apps are built around the one-off street job. Local firms live on repeat work — so the platform is built around it.
| Factor | Your own platform | Ride-hail apps | White-label SaaS |
|---|---|---|---|
| Commission per job | None | Commonly 20%+ | Sometimes |
| Per-driver monthly fee | None | — | Typical |
| Account & school-run work | Built around it | Not their model | Varies |
| Passenger relationship | Yours | Theirs | Shared |
| You own the code & data | Yes | No | No |
Third-party fees vary by platform and city; figures are indicative of common practice at the time of writing.
Let's be straight: Uber is genuinely good at what it does. Near-instant availability in big cities, a polished app, cashless payment and a brand passengers already have on their phones. If your plan is to beat that at its own game, save your money.
But the work that keeps a local firm's lights on is work the ride-hail model isn't built for: the school contract that runs every term-time morning, the account client invoiced monthly, the 4am airport pickup booked last Tuesday, the regular who rings the office and asks for Dave. That work rewards reliability, local knowledge and a fixed price agreed up front — and it's exactly what a dispatch platform of your own digitises and protects.
A 30-minute call to map how jobs flow through your office today. You get a fixed price in pounds, a timeline and the senior engineers building it. Days 1–5.
Booking, allocation, pricing rules, account structures and school-run schedules designed around how your dispatchers actually work. Weeks 1–2.
Console first, then driver app, then passenger app — payments, maps and SMS wired up, progress you can see weekly. Weeks 2–10.
The new system runs alongside your radio or WhatsApp group. Drivers switch shift by shift; nothing is turned off until you say so. Weeks 8–12.
Passenger app in the app stores, console live in the office, existing accounts and schedules migrated, full codebase handed over. By week 16 at most.
Optional retainer for changes, new features and seasonal load — same engineers, same timezone. Ongoing.
Realistic timeline: focused single-app dispatch launches in 6–9 weeks; the full passenger + driver + console build in 10–16 weeks.
| Build | White-label SaaS | Typical UK agency | Meridianstacks |
|---|---|---|---|
| Focused single-app dispatch — passenger booking app + dispatcher console (Focused tier) | Per-driver monthly fees | £20,000–£45,000 | ~£8,000–£14,000 |
| Standard dispatch platform — booking, driver app, console, zones & accounts (Standard tier) | Per-driver + setup fees | £40,000–£85,000 | ~£14,000–£26,000 |
| Full passenger + driver apps (iOS & Android) + dispatcher console (Full tier) | You never own it | £60,000–£120,000 | ~£20,000–£40,000 |
| Ongoing support (monthly) | Rolled into rental | £1,500–£4,000 | ~£600–£1,800 |
Prices published from our Open Price Book (v1.0 · July 2026 · next review October 2026). All prices exclude VAT.
Indicative ranges in pounds (GBP). White-label systems look cheap per month but commonly scale with your driver count forever, and you never own the software. Every Meridianstacks engagement is quoted as one fixed price before work begins and billed by milestone — you pay for delivered, accepted work.
Book a free 30-minute scoping call with a senior engineer, in UK hours. Tell us how jobs flow through your office today — honest answers on features, timeline and cost, no obligation.
Book a free scoping call →