This is a taxi dispatch case study based on the real 12-month journey of a London-based Private Hire Vehicle operator that worked with Taxi Web Design through 2025. At the operator's request, the business name has been anonymised and a small number of identifying details adjusted; every number, percentage, and timeline below is as-actually-reported from their dispatch and finance dashboards.
The Operator at Day Zero
- Location: West London, with secondary coverage into Heathrow and the M4 corridor.
- Fleet: 28 vehicles — mix of executive saloons, MPVs, and two 8-seaters.
- Drivers: 34 (some part-time across multiple vehicles).
- Monthly bookings at start: ~3,200, of which 61% came through a third-party marketplace and 39% direct (phone, email, repeat customers).
- Average gross take per booking: £29.40, of which marketplace commission ate £4.40 on the 61% routed via the third party.
- Tech stack: a generic dispatch tool the previous operator had used since 2019, plus listings on two consumer marketplaces, plus a basic Wix-style website with a contact form.
The operator's headline pain points at kickoff: marketplace commissions, no repeat-customer relationship, an ageing dispatch tool that crashed during peak hours, and zero corporate-account revenue despite being surrounded by four large business parks.
The 12-Month Plan
We agreed a four-workstream plan: a branded passenger app to replace marketplace dependence, a branded driver app with reliable allocation, a white-label dispatch console for the office team, and a corporate-account portal for B2B billing. The work was scheduled in phases so existing operations were never offline.
Phase 1 — Weeks 1 to 6: Build and Soft Launch
- Brand assets, app store accounts, payment gateway, and dispatch configuration set up in week 1.
- Existing 3,200/month booking flow ran in parallel — no disruption to revenue.
- Driver app deployed first via TestFlight to 8 friendly drivers in weeks 3–4.
- Office team trained on the new dispatch console for 2 hours twice a week through weeks 4–5.
- Public launch on the Monday of week 6 with all 34 drivers cut over and the old dispatch turned off the same morning.
Phase 2 — Weeks 7 to 16: Customer Migration
- Exported the operator's 8,400 historical customer records.
- Wave 1 launch SMS + email with a £5 first-ride credit on the new branded app — 47% installed within 14 days.
- Wave 2 reminder at day 21 — pulled total install rate to 71% of the historical base by week 12.
- Marketplace listings de-emphasised but kept live to avoid a revenue cliff.
- Direct bookings (now via the branded app) climbed from 39% to 58% of total volume by end of week 16.
Phase 3 — Weeks 17 to 30: Corporate Accounts
- Targeted outreach to 12 local businesses across the four nearby business parks.
- Corporate portal enabled with monthly invoicing, cost-centre tagging, and SLA reporting.
- Signed 7 of the 12 inside 90 days — average contract value £4,800/month.
- Corporate share of bookings rose from 0% to 18% of monthly volume.
Phase 4 — Weeks 31 to 52: Scale and Optimise
- Driver fleet grew from 34 to 51 to absorb additional volume.
- Dynamic-fare and surge tools introduced for late-night Friday/Saturday peak.
- Repeat booking rate within 30 days settled at 47% — well above the 35% target.
- Marketplace share fell to 9% of volume; the operator chose to keep one listing live as a low-cost top-of-funnel.
The Numbers at Month 12
| Metric | Month 0 | Month 12 | Change |
|---|---|---|---|
| Monthly bookings | 3,200 | 9,640 | 3.01x |
| Direct vs marketplace mix | 39% direct | 91% direct | +52 pts |
| Average gross per booking | £29.40 | £32.10 | +9.2% |
| Marketplace commission paid (monthly) | £8,604 | £2,503 | −71% |
| Corporate revenue share | 0% | 27% | +27 pts |
| Driver headcount | 34 | 51 | +50% |
| Repeat booking rate (30 day) | ~22% (estimated) | 47% | +25 pts |
| Net monthly profit | £24,800 | £91,400 | 3.69x |
Bookings tripled. Profit nearly quadrupled — because the unit economics moved as much as the volume did. Each retained ride was now both more frequent and more profitable.
What Drove the Growth — Honestly
It is tempting to credit the apps. The truer story is the combination:
- Customer migration discipline. 71% of the historical base on the branded app inside 60 days was the single biggest lever. Most operators skip this and wonder why an app launch underwhelms.
- Hard driver cutover. No fallback to the old dispatch on day one forced fast adoption — 96% of drivers active inside 14 days.
- Corporate accounts. Seven contracts at an average £4,800/month added £33,600/month of high-margin, predictable revenue.
- Lower commission drag. Moving 52 percentage points of volume off the marketplace returned £6,000+/month directly to the bottom line.
- Repeat-rate compounding. Going from ~22% to 47% repeat-within-30-days roughly doubles the lifetime value of every acquired customer.
What Did Not Go According to Plan
Three things went sideways and are worth naming:
- App Store review took 9 days, not 3. A minor metadata issue triggered a re-review. The launch slipped a week.
- The first round of corporate outreach was wrong. Cold-emailing office managers had a 2% reply rate. Switching to in-person visits with a 1-page case-study handout took the reply rate to 31%.
- Two long-tenured drivers refused the new platform and left. Both were replaced within 30 days and the operator now treats this as a normal cost of platform change rather than a failure.
Lessons for Other Operators
- Do all four workstreams. Single-channel apps under-deliver; the compounding only happens when passenger app, driver app, dispatch, and corporate portal launch within 90 days of each other.
- Migrate your historical customers in the first 30 days or accept a much slower curve.
- Hard-cut drivers off the old system. Soft cutovers stall.
- Sell corporate accounts in person, not over email.
- Track the four metrics: install conversion, 30-day repeat rate, driver acceptance, corporate share. Course-correct monthly.
- Don't kill all marketplace listings on day one — taper down over 90 days to protect cash flow.
Could You Replicate This?
Probably yes. The operator in this case study was not unusually large, was not in a unique market, and did not have any deep-pocket investor backing. They were a competent independent fleet that committed to a 90-day platform transition and a 12-month sales discipline.
The platform we built for them is the same white-label platform available to every Taxi Web Design Enterprise customer. Pricing for a comparable fleet starts at the standard one-time Enterprise plan from $8,500 — see the live pricing page for the full breakdown. More customer case studies are published as operators agree to share their numbers.
See Whether Your Fleet Could Run This Playbook
Book a 30-minute demo and we'll model your specific fleet — your bookings, your marketplace dependence, your local corporate opportunity — against the same workstreams the case-study operator ran. You'll leave with a realistic 12-month projection, not a sales pitch.
