Most private transfer companies start on a spreadsheet and a group chat. That works for the first ten bookings a week. It stops working long before the first hundred, and by then the cost of switching systems is a lot higher than the cost of planning for it early.
This is a short map of the three systems that actually matter, in the order they tend to break.
1. The booking engine
The booking engine is the first thing a passenger touches, and the first thing that breaks trust if it gets the price or the vehicle class wrong. Three things it needs to get right from day one:
- Real-time pricing that accounts for distance, vehicle class and zone, not a flat rate copied from a competitor.
- Availability that reflects the actual fleet, not a calendar someone forgot to update.
- A white-label surface, if the plan is to sell the service under a fleet's own brand rather than a generic marketplace.
A booking engine that shows a price and then changes it after confirmation is worse than no booking engine at all. It converts a pricing bug into a trust problem.
Where that price has to come from so it covers real cost is worked through in how to price a transfer without losing money, and why a contact form is no substitute for a booking engine, in a contact form answered tomorrow can't compete with a live price.
2. Dispatch
Dispatch is where most home-grown systems fail first, because it looks simple until a driver cancels five minutes before pickup. The dispatch logic needs to answer one question reliably: given this booking, which available driver is the right one to assign, right now?
A dispatch pool with cascading levels (assign to the closest driver first, widen the search if nobody accepts, escalate to a human if the pool is exhausted) is the pattern that scales. A single WhatsApp group is not.
What "auditable" means here
Every automatic assignment should leave a trail: which drivers were offered the ride, in what order, who accepted, and when. Without that trail, a dispute between a driver and a passenger has no evidence behind it.
The four signals that tell you a home-grown dispatch has run out of road are in when a fleet outgrows WhatsApp and spreadsheets. And when the cascade runs out inside your own fleet, the next level is handing the job to another operator rather than losing it.
3. Compliance
This is the one that gets skipped until it's urgent. Depending on the jurisdiction, a VTC or private-hire operation needs to keep records that regulators can audit: driver licensing, vehicle registration, and — in markets like Spain — the specific paperwork tied to VTC authorizations.
| System | Fails silently when... | Cost of failure |
|---|---|---|
| Booking | Price shown ≠ price charged | Refunds, chargebacks, churn |
| Dispatch | No driver accepts and nobody notices | A no-show passenger |
| Compliance | Records aren't kept in an auditable form | Fines, suspended authorization |
If your current stack is a mix of a booking form, a phone tree and a folder of PDFs, none of these three systems talk to each other, and that gap is exactly where bookings get lost and audits get failed.
Exactly which records have to be kept in Spain, and for how long, is in the VTC licence: what the law requires and what records to keep.
What to do next
Run a pricing test in your head: pick your three most common routes, and check whether the price a passenger sees today matches what you actually charge. If it doesn't, start there — it's the fastest fix with the clearest payoff.
And if you'd rather see it before deciding anything, the demo just below runs on a fleet with sample data, no signup and no card.
