This is the story of a project that went well — not because everything was easy, but because we scoped it honestly and built it methodically. It is also a good example of what it actually looks like to replace a tangle of workarounds with something that works.
The situation
A regional trucking operator reached out to us. They were managing their entire business across five separate tools: a spreadsheet for dispatch, WhatsApp groups for driver communication, a standalone invoicing tool, a manual GPS tracker, and email for client updates.
Nothing talked to anything else. A dispatcher would check the spreadsheet, send a WhatsApp message to the driver, manually enter the trip into the invoicing tool, and then send a separate email to the client. Every step was manual. Every step could go wrong. And because nothing was connected, there was no single view of what was actually happening in the business at any moment.
The operator was not struggling because they lacked good tools. They were struggling because they had too many tools and no system connecting them.
How we scoped it
We spent the first two weeks doing nothing but mapping. We followed dispatchers through their actual day. We asked drivers what information they needed and when. We asked clients what they wanted to know and how they currently found out.
By the end of week two we had a clear picture: three types of users (operations team, drivers, clients), five core workflows (dispatch, tracking, proof of delivery, invoicing, client communication), and a list of thirty-odd things that currently required manual intervention.
We presented a scope that covered the twenty most impactful items and explicitly excluded the ten that would add complexity without significant benefit. The client appreciated the honesty. We signed off on a 14-week build.
What we built
- A web portal for operations — dispatch dashboard, fleet overview, trip assignment, invoicing
- A mobile app for drivers — job assignments, navigation integration, proof of delivery with photo capture
- A client portal — live shipment tracking, document downloads, billing history
- Automated invoicing triggered on delivery confirmation
- WhatsApp notification integration for clients who preferred it over the portal
How the 14 weeks broke down
What actually went wrong
Two things caught us. First, the GPS data. The operator's existing tracker exported in a proprietary format that we had not seen before. We had scoped a standard integration and had to build a custom parser mid-project. It cost us about four days.
Second, driver onboarding. We had assumed drivers would adapt quickly to the mobile app. The reality was that several of the older drivers were uncomfortable with smartphones generally. We ran two in-person sessions and redesigned a few key flows to be more forgiving of input errors. That added another week.
Neither of these was catastrophic. Both were things we should have caught in scoping. We flagged them early, adjusted the plan, and still hit the 14-week deadline — but only because we had built buffer into the schedule for exactly this kind of discovery.
The result
Thirty days after go-live, all five legacy tools were retired. Dispatch time per job dropped. Clients stopped calling in for shipment updates. Invoicing that used to take two days now happens automatically. The operator can see the entire business on one screen for the first time.
More than anything, what worked was the scoping process. We did not try to build everything. We built the right things, in the right order, with a clear understanding of what the users actually needed.