The job arrives by email, the status comes back by phone
In transport, information moves slower than the goods.
Usually not because a system is missing, but because the decisions that matter are made in a conversation that is recorded nowhere.
What usually breaks
- The shipment status lives in the dispatcher's head
The customer calls for an update, the dispatcher calls the driver, then calls back.
More
Three conversations to pass on one date — and no trace at all when, a week later, somebody needs to establish what actually happened.
- Waybills circulate as paper and photographs
A signed waybill comes back as a picture in a messaging app.
More
Billing the customer waits on that photo, and finding it a month later is a separate job.
- Driver settlements calculated by hand
Mileage, allowances, working time and waiting assembled in a spreadsheet at month end.
More
The error surfaces at payroll, and correcting it means reconstructing a whole route from memory.
- Planning rests on one person
Whoever knows the drivers' constraints, the delivery windows and which customer won't accept after three o'clock does the planning.
More
Their absence is an operational risk, not an HR one.
What we do about it
- One register from intake to settlement
The job, its assignment, statuses and documents as a single record.
More
The customer gets an answer without a chain of phone calls, and the history survives after the matter is closed.
- Documents attached from the driver's phone
A scan or photograph of the waybill goes straight onto the job, not into a chat thread.
More
Billing stops waiting on somebody's memory.
- Settlements calculated from data that already exists
Working time, routes and waiting collected as they happen rather than reconstructed at month end.
More
The spreadsheet survives at most as an export, not as the source.
- A mobile app for people in the field
A driver works on a phone, in motion and often on poor signal — a different set of requirements from an office panel.
More
We build in React Native, so one codebase covers iOS and Android.
In depth
Where we start
By counting phone calls. Genuinely: the number of conversations needed to establish one status is the single best indicator of how much can be recovered here — and the easiest to check before any quote.
Then with one process, not the whole company. Usually the waybill flow or driver settlements, because that is where manual work is most countable.
What we don't promise
We don't promise route optimisation that beats an experienced planner. An algorithm handles constraints that can be written down; it handles less well the fact that one particular driver shouldn't be sent to one particular address. We build a tool that suggests and remembers — the decision stays with the person.
Related services
Questions from this industry
We already have a TMS. Does that mean you have nothing to offer?
Quite the opposite — most often we work alongside an existing TMS. What is usually missing isn't the core but the layer around it: the driver's app, the document flow, or the settlements that get done in a spreadsheet anyway.
Will the driver's app work without signal?
It has to, and that is one of the first requirements we settle. Local storage and syncing once the connection returns is not an extra — it is the condition for anyone using it at all.
How long does it take?
A first working version — usually the job register or the driver's app — after a few weeks. The full scope depends on the number of integrations and how many exceptions your process has; that surfaces in the discovery workshop and is then counted rather than guessed.
Got an idea? Let's talk.
The first call is free. We reply within one business day.