What the Tax Looks Like
It does not show up on the fuel bill.
It shows up in the customer who calls again because no one updated the status, the driver who pulls over to answer a question the app should have answered, and the dispatcher who can't take a real day off.
Dispatch lives in a WhatsApp group
The fleet runs on a thread that scrolls off the screen by lunch. A driver question at 3pm needs someone to scroll back to 9am. One phone going dark and the whole operation loses its dispatch desk.
Driver logs spread across spreadsheets
Hours, mileage, fuel, inspection. Five sheets, four owners, none of them current. The audit becomes an archaeology project.
No single source of truth for what is moving
The customer calls asking where the load is. The dispatcher calls the driver. The driver pulls over to answer. Everyone is doing extra work to answer a question the system should answer.
The senior dispatcher is the integration layer
When they take a Friday off, the fleet slows down because one person was holding the coordination in their head. That is key-person risk, not indispensable experience.
The 30-Day Operations Reset
Five modules. 30 days. Fixed price.
The Reset builds working software. Five modules, two standard and three custom, live in 30 days. We pick the three workflow modules costing the most coordination, scope them tightly, and ship.
01
Fit call
A 20 minute conversation to walk through the dispatch workflow that is breaking. We confirm whether the Reset is the right starting point.
02
Written quote, five modules
We send a written quote listing the five workflow modules we will build in 30 days. Two standard, user authentication and role-based access control, plus three custom. Fixed price. No scope drift.
03
Build and deliver
Twenty-eight days of focused build, then live use with 30-day hypercare. A senior team builds, founders stay accountable.
Completion and On-Time Guarantees
Two-sided risk reversal.
On-time guarantee
Past a two-week grace period, every week we run late costs us 10% off the price, capped at 50%.
Completion guarantee
Nothing deploys until a signed acceptance checklist passes. The codebase is handed over, with documentation, demo videos, and training, per the agreed contract.
Fit Check
Is this the right shape for your fleet?
Straight signal on where the Pilot fits and where it does not. The 20 minute fit call is the next step either way.
If this is you, the Pilot is the right starting point.
- Mid-market fleet operators running dispatch on WhatsApp and spreadsheets
- Last-mile or brokerage teams where status updates do not reach the system
- Operators who want a working driver and dispatcher screen in weeks, not a TMS programme
If this is you, we will say so on the call.
- Full TMS replacement programmes
- Real-time route optimisation for thousands of concurrent vehicles
- Cross-border customs and brokerage automation as the primary scope
FAQ
Frequently asked questions.
Will this replace our TMS or work with it?
It works with it. The Reset targets the gaps your TMS does not cover: dispatch happening in WhatsApp, driver check-ins on paper, status updates that go to phones rather than the system. The TMS stays. The shadow workflow gets replaced.
Our drivers run on WhatsApp. How does adoption actually work?
The software has to feel like WhatsApp, or it loses. We design driver-facing screens for fast input on phones with poor signal, large buttons, and minimum tapping. The dispatcher view replaces the WhatsApp scroll. Adoption is the whole point.
What about peak season disruption?
Cutover phases are scheduled around your peak. We build incrementally, in 30-day milestones, so the team is using new pieces in weeks rather than waiting for a single go-live that risks dispatch.
How do you handle HOS, DOT, or other compliance?
Compliance is designed in from the start. We model hours-of-service rules, driver eligibility, vehicle inspection cycles, and audit logs that meet the standard your safety team works to. They define the rules. We engineer the system that enforces them.
We have tried fleet apps before and they did not stick. Why now?
Most fleet apps are sold to fleet owners and used by dispatchers. The drivers never bought in. We build for the driver first, the dispatcher second, the owner third. If the screen the driver sees is not faster than WhatsApp, we go back and rebuild it.
How quickly can we see impact?
If the right starting point is dispatch, driver check-in, and status, the 30-Day Operations Reset ships those three in 30 days. A wider build, replacing more of the WhatsApp and spreadsheet stack, gets scoped after the Reset is in production.
What happens after the engagement?
The codebase, the deployment, and the documentation are handed over per the agreed contract. If you want ongoing care, BuildXLR8 Assurance is our care plan, custom-priced per build and prepaid annual, for security patches, dependency updates, and monitoring. You are never locked in.
Stop paying the Spreadsheet Tax.
Book a 20 minute fit call. We walk through the workflow that is costing the most coordination, confirm it is a fit, and send a written quote with the five modules listed.