Taxi Dispatch Software for Small Fleets
Last updated
The Short Answer
A taxi firm running 5 to 30 vehicles needs five things from dispatch software: fast phone-booking entry, auto-dispatch by zone, a driver app that survives poor signal, card payments that reconcile themselves, and document-expiry alerts. Everything else — multi-branch management, published APIs, deep telephony integration — is built for operations ten times the size and is the main reason enterprise platforms cost what they do.
Most dispatch software is written about as though every buyer runs 200 cars across four branches. The majority of UK taxi firms do not. If you run somewhere between five and thirty vehicles, your requirements are genuinely different, and the biggest risk in the buying process is being sold something scaled for somebody else.
The five things that actually matter at this size
These are the ones used hundreds of times a day. Get them right and the rest is detail.
- Phone booking speed. At your size, most work still arrives by telephone. If a controller cannot take a repeat booking in under twenty seconds, nothing else about the software will make up for it.
- Auto-dispatch by zone. The point is not sophistication, it is that a booking finds a driver without anyone deciding. Draw zones once, and jobs offer themselves to the longest-waiting driver in the pickup area and cascade outward if nobody takes them.
- A driver app that copes with bad signal. Your drivers go through tunnels, multi-storey car parks and rural notspots. An app that loses state when it loses signal creates work for the office every single day.
- Payments that reconcile themselves. Card, cash and account work all landing in one ledger, so the week adds up without a Sunday spent on it.
- Document-expiry alerts. Badges, MOTs, insurance and plates, alerting before the date. This is the one that protects your licence rather than your margin.
What you can safely ignore
Not because these are bad features — they are excellent, and firms that need them should buy them. They are simply built for a different scale of operation, and they are where a large part of an enterprise price goes.
| Feature | Who it is genuinely for | At 5–30 vehicles |
|---|---|---|
| Multi-branch and multi-fleet management | Operators running several licensed offices | You have one office |
| Published API and custom integrations | Firms with in-house developers or bespoke systems | Nothing to integrate with yet |
| Deep telephony / PBX integration | Call centres taking hundreds of calls an hour | Caller ID is enough |
| Contractual SLAs with penalties | Firms whose contracts require them downstream | Useful, rarely worth the premium |
| Dedicated account manager | Large accounts with complex change requests | You want someone who answers the phone |
The economics at your size
Two numbers decide whether dispatch software pays for itself in a small fleet, and neither of them is the subscription.
Controller hours
If auto-dispatch handles the bookings that used to be allocated by hand, a controller gets time back every shift. At small-fleet scale that rarely means employing fewer people — it usually means the person who was allocating jobs can answer the phone faster, chase account work, or go home on time. It is a quality-of-life return before it is a financial one.
The bookings you never see
The slower leak is the regular passenger who books elsewhere at 11pm because booking with you means a phone call. A booking app and a booking website do not transform a small firm overnight, but they stop that drift, and they cost nothing per booking once they exist.
Set against that, a platform at £100 to £220 a month is two or three airport runs. That is the comparison worth making — not the subscription against zero, but the subscription against the controller hours and the late-night bookings it is meant to recover. If it does not clear that bar at your size, do not buy it. The full breakdown of what dispatch software costs covers the models and the fees that only appear on the invoice.
What to be careful about
- Per-vehicle pricing as you grow. It is often the cheapest option at three or four cars and the most expensive at thirty. Price any quote at 150% of your current fleet before you sign.
- Separate app build fees. A branded passenger app quoted as a one-off build is a real cost that does not appear in the monthly figure.
- Minimum terms. At your size, flexibility is worth more than a small discount. A rolling contract you can leave is worth paying slightly more for.
- Migration effort. The work is not the software, it is rebuilding your tariffs and importing your passenger list. Ask who does that and whether it is charged.
A realistic timeline
- Week 1. Export your data from whatever you use now, even if that is a spreadsheet and a whiteboard. De-duplicate the passenger list while you are in there.
- Week 1–2. Build your zones and tariffs, then price fifty real jobs from last month and compare against what you actually charged.
- Week 2. Get the driver app onto every phone and make one practice job a condition of the next shift.
- Week 3. Go live on a Tuesday or Wednesday morning. Never a Friday.
The step-by-step migration guide covers each of those in detail, and the 24-point checklist covers what to test before you commit.
Cabica starts at £100/month for up to 10 drivers, with no setup fee.
See the PlansFrequently Asked Questions
- Is dispatch software worth it for a small taxi firm?
- For most firms over about five vehicles, yes — mainly because auto-dispatch returns controller time every shift and a booking app stops the slow drift of regulars to national apps. Below five vehicles the case is weaker and depends on how much of your work is already scheduled or account-based.
- How much should a 10-car taxi firm pay for dispatch software?
- Published entry pricing at that size runs from roughly £30 to £150 a month depending on the model. Watch for separate branded-app build fees and per-SMS charges, which can add more than the subscription itself.
- Do I need a passenger app for a small fleet?
- Not on day one. Most small firms take the bulk of their work by phone and should prioritise fast booking entry and reliable dispatch first. An app matters as a defensive measure — it keeps regulars who would otherwise book with a national platform — so it is worth having before you feel you need it.
- Can I run dispatch software without an office?
- Yes, if the console runs in a browser. Cloud-based systems need no server and no in-cab hardware, so a controller can work from anywhere with a laptop and a connection. That is a genuine change from older on-premise systems, which tied dispatch to one machine in one room.
Written By
Gulfam
Chief Executive Officer, Cabica
Gulfam leads Cabica, the dispatch and booking platform used by independent taxi and private-hire operators. He works on pricing, product direction and the operator conversations that shape both.