Custom deployment
The routing core is patented and already in production. What gets built for you is everything around it: your scopes of work, your service levels, your customer commitments, and the judgment your dispatchers already carry in their heads.
What's built, and what's yours
A bespoke build usually starts at zero, which is why it takes a year. Ours starts at the center of this diagram. The further out you go, the more of it is specific to you. What never changes is our concentration on routes as the core of success. Routes: that's what we'll always do and what we'll always deliver — Intelligently Automated Streaming Logistics driving your business.
Streaming Logistics — three patents covering live vehicle dispatch, mobile warehousing, and the workflow intelligence on top. It runs today. You are not paying to invent it, and you are not waiting on it.
What each contract actually obligates you to do, priced and sequenced the way you already sell it. The routing model gets your work types, not a generic stop.
Response windows, penalty clauses, priority accounts, the customer who gets called first no matter what the math says. Your SLAs become constraints the engine optimizes against rather than a spreadsheet someone checks afterward.
The outer ring is the hardest and the most valuable. Your dispatchers know which yard is impossible after 4pm and which driver you send to a difficult account. We sit with them, write that down, and encode it. Software that ignores this gets overridden until people stop using it.
Why the timeline holds
Compressing a normal build is expensive and usually bad. You either strip scope or add engineers, and adding engineers to a late project makes it later. That is the trade every development shop is making when it quotes you an aggressive date.
We are not making that trade. Routing, dispatch, and optimization already exist as product. Ninety days is what it takes to understand your operation and configure the platform to it, which is a different kind of work than writing an optimizer from scratch — and a far more predictable one.
What the core already does:
A typical deployment
We map the operation with your people — work types, SLAs, assets, the exceptions nobody documented. This produces the written scope everything else is measured against.
The routing model gets built to that scope. Integrations to the systems you already run. Your data cleaned enough to dispatch on.
The system dispatches alongside your current process. You compare both every morning and we tune against real days, not a demo dataset. No cutover risk.
Your dispatchers run on it. We stay in the room through the first full cycle, then move to ongoing support.
Ninety days is our target for a typical deployment and what most operations should plan around. Integration count, data condition, and how many service lines share a fleet all move it.
What moves the number
Two companies with the same truck count and the same revenue can need deployments that differ by a factor of three. These are the things we look at on the first call.
Your TMS, billing, telematics, customer portals. Each integration is real work, and some vendors make it harder than others.
Address history, asset records, job history. Clean data shortens everything. Messy data is normal and we plan for it.
A single line of work is straightforward. Four lines competing for the same trucks is a harder optimization and a longer configuration.
Simple response windows are easy. Tiered penalties, customer-specific commitments, and contractual exceptions take longer to encode correctly.
Dense metro work, long rural runs, and multi-market operations each behave differently and get configured differently.
Sitting underneath a platform you intend to keep is a different job than becoming the system your dispatchers open first.
Some operators want automated dispatch on day one. Others want their people in control for two quarters. Both are fine, and they scope differently.
The deployment moves at the speed of access to the people who actually know how the operation runs. This is the most common thing that slips a timeline.
How pricing works
We would rather tell you the structure and get the number right than publish a figure that is wrong for your operation in either direction. Here is how an engagement is put together.
Bring the first call whatever you have — route history, contracts, a spreadsheet, a complaint. We can usually tell you inside an hour whether this is worth either of our time.
Thirty minutes, your data, no deck. You will leave knowing what a deployment would involve and roughly what it would cost.
