Why Kenyan fleet operators are losing margin on the road, and what actually fixes it
There’s a conversation happening in every fleet office in Nairobi right now. It goes like this:
“Where’s the Eastleigh drop?” “Still with the driver. He’s coming from Karen.” “Karen? The Karen drop was supposed to be after Eastleigh.” “Traffic on Mombasa Road. He had to swing back.”
By the end of the day, that truck has covered 140 kilometers to make eleven drops that, sequenced properly along the Thika–CBD–Industrial Area corridor, should have taken 70. The driver is on overtime. Two clients have called to complain. One of them won’t be a client next quarter.
It’s not just about knowing where your trucks are; proper sequencing shows you the best routes, giving fleet managers confidence in their decisions.
The frustration nobody puts on a slide.
Most logistics software in this market sells the same thing: a moving dot on a map. GPS tracking. ETA notifications. A dashboard. It’s useful, the way a thermometer is useful. It tells you the temperature. It doesn’t lower the fever.
The actual pain for a distribution fleet running B2B routes across Nairobi, Mombasa, Kisumu, or Eldoret, not knowing. It’s the gap between what the route looked like on the dispatcher’s whiteboard at 6 am and what it actually became by 2 pm.
Drivers doubling back across town, one delayed drop cascading into five, fuel burning on the same stretch of road three times in one day.
Every one of those kilometers is a margin left by the business. Every late drop is a B2B relationship getting thinner.
Understanding what route sequencing actually does helps fleet managers see its value and consider adopting it to cut costs and improve efficiency.
Route optimization, done properly, for African road realities, solves a specific problem: given fifteen drops, three trucks, and the actual traffic patterns of a Tuesday afternoon in Nairobi, what’s the sequence that gets every package delivered with the least backtracking?
The answer is rarely the one a human dispatcher draws by hand. Not because dispatchers aren’t smart, they’re often the best logistics minds in the building, but because the math gets unwieldy past about eight stops, and impossible when traffic, time windows, vehicle capacity, and delivery priorities all interact.
Software that sequences drops along corridors doesn’t replace the dispatcher. It hands them a starting plan that already accounts for the city’s geometry and lets them adjust from there.
The results show up in three places:
Fuel savings from optimized routes directly impact margins, making this the first benefit CFOs notice when routes are sequenced properly.
Driver hours. Sequenced routes finish earlier. Overtime drops. The same fleet handles more drops without adding trucks.
Client retention. B2B clients don’t need their delivery to arrive at 10:00 sharp. They need it to arrive when you said it would, in the order you said it would, every week. Sequencing makes that promise keepable.
Why does generic global software keep missing
Route optimization tools built for Amsterdam or Atlanta make assumptions that don’t hold here: they expect addresses to be reliably geocoded, assume road conditions match the map, and believe “the corridor” refers to a single signed route rather than three parallel options that drivers choose between depending on the time of day.
A tool built for African distribution routes has to start from a different set of assumptions, about how drivers actually navigate, what cash-on-delivery does to route timing, how a closed bridge in Industrial Area reroutes half the fleet, and how a B2B client’s loading bay availability dictates arrival windows.
This is the difference between software that works in a demo and software that survives a Wednesday.
The honest case for changing systems
The case for upgrading isn’t “digitise or die.” Most fleets here have already digitised something. The case is narrower and more useful:
If your dispatcher is sequencing routes by hand or in a spreadsheet, you are leaving fuel and hours on the table every single day. Not as a percentage you can argue about, as a number you could calculate if you wanted to, and might not want to.
The real is: question for decision-makers we adopt route optimisation? It’s what is the cost of not using route optimization now, and how long can they afford to ignore it?
What to do next
If your fleet’s route planning feels inefficient, the next step is simple: compare last month’s total kilometres and drops to an optimized sequence to see the difference.
We can run that analysis on your fleet data in a 30-minute call. No demo theatre, no slide deck, just your numbers.