One record, from the phone call
to the paid invoice.
Most delivery businesses run on four or five systems that each hold a piece of the truth. An order arrives in one, a route lives in another, the driver's day is on paper, and the invoice is typed again from a ticket. Every seam is a place for the numbers to disagree. This is built as one system on purpose.
Draw the areas once. Everything downstream uses them.
Delivery areas are drawn as real shapes on a map — the outline your business actually serves, not a circle around a pin. Assign each one a warehouse, a service day and a colour.
From then on they do the work: a new order tags itself to the area it falls inside, lands on the right day for the right hub, and shows up where the dispatcher expects it. Territory changes are a drawing exercise, not a data-entry project.
Routes on real roads, anchored to real warehouses.
Routes start and end at the hub that actually loads them, and they follow the road network rather than straight lines between pins — because a straight line does not tell a dispatcher whether the 2 p.m. window is reachable.
Multiple warehouses are the normal case, not an upgrade: a business running three depots across a hundred miles sees one operation, with each route belonging to the building it leaves from.
A board you work on, and a map you watch.
A dispatcher does two different jobs, and they want two different screens. One is a working surface — moving stops, swapping crews, fixing the plan. The other is vigilance — watching the day run and noticing the moment it stops going to plan.
The dispatch board
Drag an unscheduled order onto a route. Move a stop from one lane to another. Swap the driver or the truck from a right-click. Every change can be undone — nothing about a working board should be a one-way door.
The live map
Trucks, territories and the stops clearing as the day runs, with alerts when a time window is about to be missed or a truck leaves the area it should be in. The two screens stay in step, so acting on one is visible on the other.
The driver's phone, and nothing to install.
The handheld is a web app. A driver opens a link or scans a QR code, signs in with their own credentials, and works. There is no app store, no install file, no device programme, and no version to chase when you fix something — the next stop already has the fix.
- Their own sign-in. A device that lives in a truck never carries an office login, and a driver only ever sees their own route.
- One question at a time. Arrive, what happened, how much, proof, done — usable with gloves on and in a hurry.
- Proof and reasons. Photo and signature on delivery; when a stop cannot be completed, why is recorded rather than lost.
- Money at the door. Cash, cheque or card against the invoice the delivery just raised, attributed to the driver who took it.
- Alerts that reach the truck. A cancelled stop, a new order, a re-sequenced route or an account put on hold — before the driver is standing at the door.
The delivery is the invoice.
Billing is not a separate evening job. Completing a stop raises the invoice from what was actually delivered, and a payment taken at the door settles against it immediately — so the question "what is owed, and by whom" has one answer at any hour of the day.
Invoices that match reality
Short-delivered means short-billed. What the driver recorded is what the customer is charged, without a second person re-typing it.
Receivables in one place
Who owes what, how old it is, and which accounts are worth a phone call this morning — including the cash a driver is still carrying.
Cost per unit, honestly
Product, labour, fuel and equipment brought together, so the cost of serving a route is a number rather than a feeling.
It proposes. You decide.
There is a real place for automation in this work: spotting that two half-empty routes should be one, that a sequence no longer makes sense after three cancellations, or that an account's pattern has quietly changed.
What we will not build is software that rearranges a dispatcher's day without asking. The default is a proposal with its reasoning attached, waiting for a human yes — and an operator who wants it to act on its own can turn that on deliberately, per company.
Want to see it?
We are still building, and we would rather show it to people who run routes for a living than describe it on a web page.