BAT.TAXI: A CRM Built for the Cabbie, Not the Fleet

For licensed London Hackney drivers. UK-only.

"CRM" is one of those words.

Most cabbies have never typed "CRM" into Google. It's marketing-speak — used by dentists, sales managers, insurance brokers, and the kind of person who calls a conversation a "touchpoint". You did the Knowledge; you didn't sit on a webinar about customer relationship management.

And yet — quietly — every cabbie wants what a CRM actually does.

A CRM is a system that remembers your customers. What they last booked. When they last rode with you. How to reach them. Which of them tip well, which of them are always late, which of them you'd happily take to Heathrow at 4 AM and which you'd really rather not. That's it. That's the whole concept.

You probably already keep some of this in your head. A handful in your phone. A few notes scribbled on a fare card. The question this post is about is: why isn't there a real one for cabbies — yours, not the apps'?

There is one now. This post is about it.

Where your customer data actually lives — and who pays who

There's no "taxi driver CRM" built for the cabbie because, for the last fifteen years, the taxi apps have been the de facto CRM for the trade. Every fare you do via an app puts a customer in their database, not yours. Every fare you do via an app pays the app a commission — around 29% on average on the leading UK ride-hail platform per Oxford / Worker Info Exchange research from June 2025, with rates exceeding 50% in some cases — and the app keeps the customer record forever.

That's a CRM. It's just somebody else's.

The Google search results bear it out. Type "taxi driver CRM" and the first page is software built for fleet operators, app platforms, ride-hail businesses — anyone whose customer is the company, not the cabbie. The driver is a user account inside the system. The customer records belong to whoever's holding the data. A driver leaving doesn't take anything with them. The platform reassigns the customer to whoever's next.

That's not a CRM for the cabbie. That's a CRM for the platform — with the cabbie listed as a resource.

The platforms aren't doing anything wrong by their own standards. Their business model depends on owning the customer relationship; they couldn't hand it back to the cabbie without dismantling the value they extract. That's how the modern taxi-app industry has been built since around 2010. And it's why the "taxi driver CRM" search returns nothing actually for the cabbie.

What changes when the cabbie is the customer

BAT.TAXI is built around a single inversion: the licensed cabbie is the customer. The platform is the agent. (HMRC's own VAT manual VTAXPER77100 already frames the legal relationship this way — "cab firms can act as agents for drivers". We just built software that matches.)

And it's a pre-book only service — minimum one-hour lead time between booking and pickup. That's the structural reason any of the below works: the lead time is what makes it possible for the cabbie to actually be there for the customer, or to arrange a Co Driver who can. Without it, the whole Driver-As-Agent model collapses (a cabbie can't be in two places at once). The model has been manually proven for eighteen months before the platform launched; this isn't a hypothesis.

That sounds abstract. What it means in practice:

• You sign up with your own account. Not a seat in someone else's account.
• Every customer you invite is on your list. Not the firm's list. Not BAT.TAXI's list (we'll come back to that). Yours.
• Every job you do gets logged against your customer. You can see this. You can search it. You can sort it.
• Your data exports. Spreadsheet, CSV, whatever you want — the entire record of every customer, every quote, every booking, every payment, every note you've made.
• And the proof point: cascade deletion. If you ever leave BAT.TAXI, your customer book — every contact, booking history and note — is cascade-deleted from the system, and your passengers are notified. We don't keep your customer book, we don't sell it, we don't poach it. It's irreversible — so export your records first; keeping records for your licensing authority is your responsibility, not ours. Walk out and your customers walk out with you.

That last point is the structural test of whether a system is really yours or really theirs. Every taxi app keeps the customer data when the driver stops using the app — because the data was always theirs. We delete it — because it was always yours. Different category of product.

How the BAT.TAXI dashboard actually works as your CRM

You don't need to know CRM jargon to use it. The dashboard is built around the four things a cabbie actually does — fielding the message, quoting the job, doing the work, and remembering the customer next time.

The message centre is your inbox for every customer interaction. Quote requests, confirmations, follow-ups, the "are you free Friday?" message from a regular. One feed, threaded by customer.

The customer record is what most cabbies have only ever kept in their head. A row per customer. Name. How they came to you (which QR code, which invite). What they've booked. What they've paid. Their preferred pickup. Any notes you've made — "hates small talk", "always has bags", "go via Kingsway not Aldwych at 8am".

The ratings and feedback system is two-way. You rate the customer; the customer rates you — and rates any Co Driver who covers a redirected job for you. Cabbies have been doing the first half informally for decades; this just makes it portable.

The Co Driver redirect is your safety net for when you can't take a job. When a regular messages you while you're on holiday, at a hospital appointment, or simply asleep, the request can be redirected to a trusted Co Driver in your network. The customer is served. The relationship stays yours.

The pause-invites feature is the bit that makes scaling sustainable. When your book is full enough, you turn the inbound invites off. Existing regulars keep messaging you; new sign-ups stop. You're never in the position of having to disappoint someone because word got out.

This is what "CRM for the cabbie" actually means. Not enterprise software with five hundred features you'll never touch. The same handful of things you already do — built into a tool that remembers them properly.

Side-by-side: the taxi apps' CRM vs the cabbie's CRM

A quick comparison. This is the difference that matters.

The last row is what makes every other row true. Whichever party pays for the software is the party the product serves. The taxi apps were paid for by venture capital chasing platform economics; BAT.TAXI is paid for by the cabbie. The products work for whoever's holding the cheque.

Data ownership, GDPR, and what we actually do with the records

Worth being plain about this, because cabbies have heard a lot of vague software-vendor language about "your data" over the years.

Under UK GDPR, when you collect a passenger's contact details to deliver them a quote and a ride, you are the data controller. BAT.TAXI is the data processor — we hold the data on your behalf so the system works. You decide how long it's kept, what notes you put against it, whether a particular customer should be deleted. We don't sell it. We don't profile it. We don't aggregate it into a marketplace pool. We don't share it with other cabbies. None of it goes anywhere except your account.

If a customer ever asks you to delete their data (which is their GDPR right), the system has a one-tap delete. If you ever close your BAT.TAXI account, the same cascade delete fires across your entire list — the technical proof that the data was always yours.

This isn't a marketing claim. It's how the product is built.

Why this matters before driverless arrives

Brief detour, but worth flagging — and the Waymo post covers it in depth.

In a driverless future, the journeys that still need a human cabbie are the ones with a relationship attached. The wheelchair regular. The hospital regular. The 4 AM Heathrow regular. The post-night-shift nurse you've picked up for two years. Those aren't relationships an algorithm can build — but they are relationships an algorithm can steal, if you don't have them on a list that's yours.

A CRM that's actually yours — yours when you join, yours when you leave — is the prep for that change. Without it, the asset that survives Waymo doesn't belong to you.

What it costs

Same two options as the rest of the BAT.TAXI platform. The CRM features above are the full BAT.TAXI platform — they're not a separate "CRM add-on".

• Platform Only: £4.99/month or £39.99/year. UK rollout cities + international. Digital only.
• Driver Pack (London-only soft launch): £99 first year (marketing pack + platform included free); £39.99/year from Year 2. Includes everything in Platform Only plus the physical in-cab marketing materials and the Airport Pricing dashboard feature. (Read about the Driver Pack.)

For context, the taxi apps take around 29% in commission on average per fare on the leading UK ride-hail platform (Oxford / Worker Info Exchange, June 2025) — with some fares attracting over 50%. That's the bill you pay for the apps to hold your customer database. BAT.TAXI is the bill you pay to have your own database — £4.99 a month, flat. No matter how many fares.

FAQ

What's a CRM in plain English? A system that remembers your customers. What they've booked, when, what they paid, how to reach them. Not specific to taxi work — every business that has repeat customers uses one. Most cabbies have been doing the same thing in their head and their phone for years; BAT.TAXI is the proper version of that.

Do I need to be technical to use it? No. If you can use WhatsApp and a calendar, you can use the BAT.TAXI dashboard. There's an info button on every function for when you want a quick explainer.

Can I export my customer list? Yes. Anytime. CSV or spreadsheet. The full record of every customer, every booking, every payment.

What happens to the data if I cancel BAT.TAXI? We cascade-delete your customer book from the BAT.TAXI system. Every contact, every booking history, every note — gone, and unrecoverable. We keep none of your customer book, so please ensure you've exported all your records using the download feature in your driver app before deleting — keeping them is your responsibility, not ours.

What about GDPR? You're the data controller. We're the processor. We don't sell, profile, aggregate, or share the data with anyone — including other cabbies. Each customer has a one-tap delete right that you can action from the dashboard, or that we'll handle if the customer contacts us directly.

Can I add notes to a customer record? Yes. Private to you. "Always has a suitcase", "prefers the Cromwell Road route", "place suitcase in the front" — whatever you'd write on a fare card. They're yours, not visible to the customer.

How is this different from just keeping customers in WhatsApp? WhatsApp is your inbox. BAT.TAXI is your inbox plus a proper booking record (TfL-compliant for pre-booked work), plus a customer profile with history and notes, plus the Co Driver fallback, plus airport quoting, plus invite QR codes, plus the pause feature, plus the ratings system, plus the cascade-delete promise. WhatsApp on its own can't generate a booking record TfL would accept.

Is there a free trial? The Platform Only tier is £4.99 month-to-month — cancel any time. That's the trial equivalent. You can be live the same day you sign up, and walk away after 30 days having spent under a fiver if it isn't for you.

What if a customer asks to be removed entirely? One-tap delete in the dashboard. They're gone from your list, and from our system. No retention period. GDPR compliant.

Ready to own your customers — properly, in a system built for you? Sign up as a cabbie →

Already a BAT.TAXI cabbie? Sign in →