Nivio Dispatch is not a replacement. It is a planning layer that sits on top of what you already run — and you can start this afternoon, before a single integration is touched.
Here is exactly how it works.
Loads go in. The plan comes back out. Nothing gets replaced.
Nivio plans your entire bulk fleet shift — every load, every driver, in under 5 minutes — on top of the TMS you already run. Every empty mile it removes is diesel and parts you never pay for. Over 50 rules are weighed, so the plan that comes out is one your dispatcher can actually run.
That is the product. Everything below is proof.
How it works: in from your system, back out to the same one
This is the design, not a workaround.
Loads come into Nivio from an Excel export or directly from your TMS. The Proprietary Algorithm works through over 50 constraints — hours of service, time windows, commodity types, weight grades, permit requirements, and the equipment rules your fleet actually operates under — and returns an optimized assignment of every load to every driver.
Then the plan goes back out. Export it as a file. Push it into your TMS. Your dispatchers work from the same system they worked from yesterday. Nothing moves except the quality of the plan.
Drivers are still dispatched from your existing system. That is not a feature we added late. It is the architecture.
You are connected today, if you want to be
Nivio connects directly to Samsara, Geotab, and Motive right now. If you run McLeod or TMW, those integrations are available on request.
But the integration is not the starting point. It is the endpoint of a process that begins with a spreadsheet.
Start from the spreadsheet you already keep
No integration is required to see your numbers. Upload one day of loads from Excel. The constraint solver runs. You get a plan back, and you get a picture of what your current dispatch is costing you.
The TMS connection and the ELD connection come later — after you have already seen what the tool does on your own data. That is the sequence: numbers first, integration second.
This matters because the standard objection to new software is not the price. It is the setup cost and the risk of unsettling a system that, however hard-won, is running. Nivio removes both. You do not commit to an integration to find out whether it is worth it.
What removing empty miles is worth
At 60,000 miles per truck per year and a conservative 6% mileage reduction — well below the 12–16% Nivio typically produces — the fuel and maintenance math is straightforward.
At $5.00 per gallon diesel and 4.5 MPG, removing 3,600 miles per truck per year saves roughly $4,000 in fuel and $720 in maintenance. That is $4,720 per truck per year (modelled) on fuel and maintenance alone, before any revenue or capacity effect is counted.
At $60 per truck per month, Nivio costs $720 per truck per year. The modelled return is 6.6 times cost, with a payback period of roughly 56 days.
For a 75-truck fleet, that is roughly $354,000 per year (modelled) in fuel and maintenance against a $54,000 annual cost for the software. A measured outcome on one 75-truck sand fleet came in at $599,000 per year — but that is a real customer result on their specific lanes and loads. Your number starts with your data, and you can run it on the calculator at niviolab.com before you talk to anyone.
For fleets that want it: one API call, over 50 constraints
If your team wants to call the solver directly, the API is open. One call. Over 50 constraints available. You can pass the load list and driver pool from whatever system you run and get the optimized assignment back in the same format.
Most fleets do not start here. But the option is there from day one, without a custom build request.
The afternoon you get back
Every afternoon, from around 3 to 7, your dispatcher hand-builds tomorrow's plan. Matching every available driver to every load, around hours of service, time windows, and customer rules. That takes 2 to 3 hours a day.
With Nivio, the solver returns a plan in under 5 minutes. Your dispatcher spends the remaining time on adjustments — the calls, the exceptions, the driver knowledge that no software will ever replace. Total planning time: under 30 minutes.
They keep control of the board. They stop doing the arithmetic.
See what it looks like on your loads — upload a day of data and get your plan back today.
FAQ
Does Nivio replace my TMS? No. Nivio is additive. Loads come in from your TMS or from Excel, the Proprietary Algorithm builds the optimized plan, and the plan goes back out as an export or a push into your existing system. Your dispatchers continue working from the same tools they use today. Nothing gets replaced.
Do I need to complete an integration before I can see results? No. You can upload one day of loads from a spreadsheet and get a plan back immediately. TMS and ELD integrations are available — Samsara, Geotab, and Motive are connected today; McLeod and TMW on request — but they are not required to start. The integration comes after you have already seen your numbers.
Where does the $4,720 per truck per year figure come from? It is a modelled estimate based on 60,000 miles per truck per year, a 6% mileage reduction, $5.00 per gallon diesel, 4.5 MPG, and $720 per truck per year in maintenance savings. It is not a customer result — it is what the math produces under those stated assumptions. Your own number will depend on your lanes, your loads, and your current empty-mile rate.
See what it looks like on your fleet
Send one day of your actual dispatch. We run it through Nivio and send back a head-to-head comparison within 24 hours, free.
Get your number →