Custom Ops Software for Logistics
Your dispatch desk is a WhatsApp group. And it goes down with the phone.
Loads dispatched in a thread. Driver check-ins in a spreadsheet. Status updates that never reach the system. That is not coordination. That is the Spreadsheet Tax, paid every shift in calls, scrolls, and the senior dispatcher who cannot take a day off.
The 30-Day Pilot Build. Three working modules, live in 30 days. Fixed price. Founder led.
The Spreadsheet Tax
Quiet. Unpriced. Paid every shift in WhatsApp scrolls, customer status calls, and the dispatcher who is the system.
What the Pilot replaces
Three of your highest friction dispatch and driver workflows, rebuilt as custom software the team will actually use.
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 cannot 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. That is not a system. That is a single point of failure.
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. The firm calls it indispensable experience. The market calls it key-person risk.
The 30-Day Pilot Build
Three workflows. 30 days. Fixed price.
The Pilot is a real delivery, not a diagnostic. We pick the three workflow modules costing the most coordination, scope them tightly, and ship working software in 30 days.
01
Fit call
A 20 minute conversation to walk through the dispatch workflow that is breaking. We confirm whether the Pilot shape is the right starting point.
02
Written quote, three modules
We send a written quote listing the three workflow modules we will build in 30 days. Fixed price. No scope drift.
03
Build and deliver
Fifty percent on kickoff. Twenty-eight days of focused build. Fourteen days of live use. Fifty percent on delivery.
Dual Guarantee
Two-sided risk reversal.
Delivery
Miss the 30 day mark for reasons on our side, we continue at no extra charge and give you twenty-five percent off any follow on engagement.
Fitness for purpose
After fourteen days of live use, if the build is not solving the scoped problem, fifty percent refund. You keep the code, the deployment, and the documentation.
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 Pilot 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 Pilot Build ships those three in 30 days. A wider build, replacing more of the WhatsApp and spreadsheet stack, gets scoped after the Pilot is in production.
What happens after the engagement?
You own the code, the deployment, and the documentation. If you want ongoing care, BuildX Assurance is our monthly care plan 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 three modules listed.