What this is actually for
You think you know your territory. Then you put it on a map and the data disagrees with you.
What we built for ourselves
We joined our own vehicles, CRM, disposal sites, accounts and field touchpoints on geography, then layered on free public parcel, imagery and code-violation data.
It showed us where our business actually was, versus where we'd always said it was. Those were different places.
Route optimisation runs on the same box — cuOpt and OSRM against our real dispatch history.
What you get
- —A real-territory audit: where you work versus where you think you work
- —Demand signals from public parcel, imagery and violation data — before the phone rings
- —Scored opportunity routed into the CRM you already use, not a new tool to log into
- —Route optimisation, where dispatch is in scope
- —The conversion feedback loop, shipped as part of the engagement
Hear how it got built
We recorded the build of each of these, including the parts that didn't work.
- Episode 9 — The Map That Showed Us Our Own Businessrecording
- Episode 6 — Door Hangers Before The Truckrecording
Episodes publish as they're cut. Nothing here is a teaser for something that doesn't exist — the systems are already running.
What this doesn't do
It produces scored leads, not customers. And accuracy decays unless conversion outcomes get fed back in — which is why the loop is contractual, not optional. On routing we quote our own backtested ceiling of about 37%, not a best-case number.
What it runs on
Built on NVIDIA hardware and software we own and operate, not a reseller relationship.
Where it's going next: The routing half is our stated on-ramp to autonomous dispatch. Dispatch now, DRIVE later.
A member of the NVIDIA Inception program
Fifteen minutes, no deck.
Bring one specific problem in one sentence. We'll tell you whether it's worth building, roughly what it takes, and sometimes that the answer is don't build it.
Start hereTwo steps before we talk — it takes about five minutes.