Fleet status lived in three places: a driver’s phone, a dispatcher’s spreadsheet and whoever happened to answer the radio. Fuel, idling and stop time were reconstructed after the fact, which meant they were argued about rather than acted on.
The brief was a single source of truth for a moving fleet: what every vehicle is doing right now, and what it did yesterday, on both the driver’s phone and the dispatcher’s screen.
The people generating the data got the best interface. Trip start, stop reasons, fuel events and proof of delivery are a few taps, offline-tolerant, on the handsets drivers already carry.
Running, idle, stopped and no-data as a single status band, with the map, route history and the vehicle card in one view — no tab hunting during an incident.
Tank volume, filling, pouring-off and consumption tracked per vehicle, alongside average driving, stop duration and speed, so cost conversations start from data.
Threshold alerts and an event log feed the reports the operations manager sends upward — generated, not assembled by hand each Monday.
Taken from the client’s own reporting, not our estimates.
Chosen for the next five years of the product, not the first demo.
Thirty minutes with the people who would actually do the work — no discovery deck, no account manager.