The booking is the record.
Before
The office copied a change into driver messages, passenger updates and accounts, by hand, one at a time.
With Kairo
Kairo keeps those permitted views connected to the same live piece of work.
The software came after the operation.
Louis Herbert built Kairo inside a chauffeur company that already had jobs to run, drivers to brief, passengers to update and accounts to close. The first brief was simple: stop turning one booking into four versions of the truth.Hartley · MAN T2 → WilmslowPickup 14:35Pickup 15:10Flight delayed 35 min
Email14:3515:10still 14:35
Dispatch14:3515:10still 14:35
Driver14:3515:10still 14:35
Invoice14:3515:10still 14:35
Hartley · MAN T2 → WilmslowPickup 14:35Pickup 15:10Flight delayed 35 min
Email14:3515:10still 14:35
Dispatch14:3515:10still 14:35
Driver14:3515:10still 14:35
Invoice14:3515:10still 14:35
One flight delay, one booking. On the left the office retypes the new pickup time into each place it lives and misses the driver. On the right the record changes once and every permitted view moves with it.
One booking had become several versions of the truth.
The office could copy the same booking between email, dispatch, driver messages and accounts.
A client change could reach the office without reaching every person or screen it affected. Missed extras and awkward margins could appear after the journey rather than while the team could still act on them.
Kairo began by keeping the office, driver, passenger and account client connected to the same permitted live record. Account rates, airport work, returns, partner jobs and waiting time became part of the operation rather than another hand-off.
One operation is the first test. It doesn't mean one chauffeur company represents every fleet. Switching starts with an operator's own historic jobs, data and rate cards, so Kairo finds the differences before handover.
Louis Herbert is a working chauffeur operator in Manchester. He built Kairo because the dispatch tools he used day to day kept several versions of one booking. The office had one version, the driver had another, and the invoice sometimes told a third story.
That gap is what Kairo is built to close: one booking, one record, visible to everyone who is permitted to see it, from the first enquiry through to the paid invoice.
Built for pre-booked work, not hail-and-ride.
Kairo is built for pre-booked chauffeur work: airport transfers, as-directed hire, corporate account clients and event transport that are arranged ahead of time. It keeps one live record for each booking as it moves from enquiry through quote, dispatch, driver, passenger, invoice and account billing.
It is not built for high-volume hail-and-ride taxi dispatch, where jobs are accepted and assigned in real time with no advance booking. Operators running that model need a different kind of system.
The product decisions follow the work.
Three decisions that came out of running real jobs, and what each one replaced.Difficult work belongs in the system.
Before
The office handled airport timing, account rates, waiting time and partner work as exceptions.
With Kairo
They are part of the operating model, where the team can see and act on them.
A switch has to work before the old system leaves.
Before
A tidy import is not enough if real quotes, jobs and rate cards do not behave correctly.
With Kairo
Managed Launch runs Kairo beside the current system for a live week before handover.
Run on live work before it is sold.
Kairo runs dispatch, driver workflows, passenger updates, quoting, invoicing and driver pay every day inside the chauffeur company it was built in. That does not make the product finished. It gives every decision a real place to fail before another operator depends on it.
- Tested on
- Live chauffeur work, daily, since day one
- Built in
- Manchester, United Kingdom
- Switching model
- DIY or a parallel Managed Launch
Details, plainly.
- Legal name
- Kairo Engine Ltd
- Company number
- 17127596
- Registered in
- England and Wales
- Registered office
- 61 Lyne View, Hyde, SK14 4ND
- Contact
- admin@kairoengine.com
Bring one historic booking.
We will follow it through dispatch, the driver, passenger updates and accounts, then give you a written view of what switching your operation would involve.