Dispatch time cut by 60%.

The business had grown from a handful of vehicles to a mid-sized fleet over three years. The systems hadn't grown with it. Dispatch ran on a shared Excel sheet that three people edited simultaneously. Job assignments went out on WhatsApp. When a driver didn't see a message, the job didn't happen.

The operations manager was spending the first two hours of every day reconciling what had actually happened the day before. Customer complaints were increasing. The business was turning away work because the operations team couldn't manage the volume they already had.

The MD knew the system was the bottleneck. The question was what to do about it. The off-the-shelf logistics platforms they'd evaluated were either too simple, too expensive, or built for a different kind of operation.

We started with a scoping session that mapped the actual dispatch process end to end, not the idealised version, but what really happened, including the workarounds. That session surfaced three constraints the client hadn't mentioned: drivers used low-end Android phones with unreliable data, jobs sometimes had to be split between vehicles mid-route, and the billing system was manual and disconnected from operations.

The platform we built addressed all three. A progressive web app for drivers that worked offline and synced when connectivity was available. A dispatch console that let controllers assign, reassign, and split jobs without losing history. An export function that fed directly into the billing process.

We shipped in eight weeks. The first week in production, dispatch time dropped by 60%. The operations manager got her mornings back.