From Spreadsheets to One System.

A national logistics business came to us running on spreadsheets and email. Jobs lived in a shared sheet that several people edited at once. Updates moved by email threads that grew until nobody could find the latest version. Drivers were briefed by phone. It had worked when the company was small. At national scale, it was quietly leaking. Jobs slipped through. Two people would action the same task while another went untouched. Nobody could see the full picture at any one moment, and the cost of that blindness was growing.

Start by sitting with the operators

We did not begin with a system diagram. We began in the office, next to the people doing the work. We watched how a job came in, who touched it, where it went, and what each person did to keep it moving. We learned the workarounds: the colour codes in the spreadsheet that meant something only to the dispatcher, the second sheet someone kept because the main one could not be trusted, the phone calls that existed only to confirm what the email already said.

This is the part that gets skipped, and it is the part that matters. The team had built a working process through years of muscle memory. Our job was to understand that process deeply enough to design something that felt faster from the first day, a system that built on what they already knew rather than forcing them to relearn everything.

Design around how the team actually works

The platform we built mirrored their real workflow rather than an idealised one. Jobs moved through the same stages the team already recognised, so the screen matched the mental model they had carried for years. The dispatcher saw everything in motion on one view. Drivers got what they needed without a phone call. Where the spreadsheet had relied on memory and trust, the system now held a single version of the truth that updated for everyone at once.

We resisted the urge to add features nobody asked for. Every part of the build earned its place by removing a real friction we had watched happen. That restraint is what made adoption easy. The team did not have to be talked into it, because it made their day lighter immediately.

What changed

The missed jobs that came from two people editing the same cell, or from an update buried in an inbox, largely stopped, because there was one place the work lived and it was always current. Managers could finally see the whole operation without ringing around for status. The spreadsheets were retired. The parallel tracking sheets, the confirmation calls, the long email chains all fell away, because the single system made them unnecessary.

The deeper win was visibility. A business that had been running on hope and individual effort could now see itself clearly, plan with confidence, and grow without the process buckling under the weight.

This is a composite picture, but it reflects the kind of work we do for operations-heavy businesses. The pattern repeats across industries: smart teams outgrow the tools that got them started, and the answer is rarely more spreadsheets. It is one connected system, built around how the people actually work, that gives them back their time and their visibility.