Your TMS stays. Your spreadsheet is enough to start — a full plan, in under 30 minutes.

---

The pitch you have heard before — and why this one is different

You have heard this pitch before. A software vendor walks in, shows you a walkthrough with clean data and a simple fleet, and somewhere in the third slide you realize they want you to migrate off the TMS you spent two years getting your dispatchers to use. The next slide is a timeline. The timeline has a "go-live" date. Your stomach drops.

That is not what this is.

Nivio Dispatch was built by a former 100-truck bulk fleet operator — someone who ran the board, knew every driver by name, and understood that the TMS is not just software. It is institutional memory. It is the system your drivers call into. It is where your billing runs. Nobody with any sense rips that out to try a planning tool.

So here is the actual architecture, in plain language: loads come in from where they already live, the Proprietary Algorithm computes the optimal plan in under 5 minutes, and the plan goes back out — as an export file or pushed directly into the TMS your dispatchers already use. Your drivers are still dispatched from the same system. Nothing moves except the quality of the plan.

---

One load sheet — a complete plan before integration is even discussed

Setup: You keep a load sheet in Excel. Every afternoon, your dispatcher is staring at it, trying to hold every driver's hours, location, and customer window in his head at once.

Payoff: That spreadsheet is all Nivio needs to show you your numbers today.

Upload one day of loads. The Proprietary Algorithm runs against your actual data — your lanes, your volumes, your constraints — and returns a planned output you can evaluate before a single integration is discussed. No IT project. No sandbox environment. No vendor onboarding call that turns into a six-week scoping exercise.

This matters for one specific reason: you should never buy a planning tool on modelled figures alone. Run it against your own data first. The ELD connection, the TMS push, the live driver status feed — those come later, once you have seen what the plan looks like with your loads in it.

The integration path, when you are ready:

Starting point	What you supply	What you get back
Excel / CSV	Upload your load sheet	Optimized plan as export
Samsara	Live connection (available today)	Driver HOS and location in the plan
Geotab	Live connection (available today)	Driver HOS and location in the plan
Motive	Live connection (available today)	Driver HOS and location in the plan
McLeod	Available on request	Loads in, plan pushed back out
TMW	Available on request	Loads in, plan pushed back out

Every row in that table is additive. Nothing in your current stack is replaced at any stage.

---

Your TMS holds the loads. Your ELD holds the drivers. Nivio hands the plan back to both.

Setup: Your TMS holds the loads. Your ELD holds the drivers.

Payoff: Nivio reads both, computes the plan, and writes the result back where it came from.

The data path is directional and non-destructive:

1. In: Loads enter Nivio from Excel, CSV, or a live TMS connection. Driver availability and hours-of-service data enter from Samsara, Geotab, or Motive — or from a manual entry at the start, if you are not yet connected.
2. Plan: The Proprietary Algorithm weighs over 50 constraints simultaneously — commodity type, weight limits, permit requirements, equipment rules, HOS, customer time windows, and the operational rules your fleet actually runs by — and returns the optimal load-to-driver assignments in under 5 minutes.
3. Out: The finished plan exports as a file your dispatcher can work from immediately, or it is pushed directly back into your TMS so dispatchers continue working in the system they know.

Your drivers receive their dispatch from the same system they always have. The dispatcher reviews the plan, makes adjustments — because they know the drivers and lanes better than any software will — and the day runs. The Proprietary Algorithm handles the arithmetic. The dispatcher handles the judgment calls.

What does not change: your TMS, your ELD, your dispatch interface, your driver communication process, your billing workflow. What changes: the afternoon your dispatcher used to spend building that plan by hand.

---

Two to three hours, every afternoon — then under thirty minutes

Setup: Every afternoon, from roughly 3 to 7, your dispatcher hand-builds tomorrow's plan — matching every available driver to every load, around hours of service, customer windows, and the commodity rules that your generic TMS does not even know exist.

Payoff: With Nivio, that same plan takes under 30 minutes. The solver returns it in under 5.

The time that remains after the solver runs is not dead time — it is the time your dispatcher spends reviewing the plan and making the calls that require human judgment. A driver who had a hard day. A customer who called and changed the window. A lane your dispatcher knows runs better with a specific driver. That stays exactly where it belongs: with the person who knows the operation.

What the Proprietary Algorithm removes is the arithmetic — the hours of hold-every-variable-in-your-head manual matching that should never have been a human job in the first place. The dispatcher does not lose the board. They get the board back, cleared of the grind.

For a 50-truck bulk fleet, that recovered time compounds fast. A dispatcher spending 2 to 3 hours daily on manual planning is giving up roughly 500 hours a year to a task a constraint solver can do in under 5 minutes. That is not a workflow problem — it is a tool problem.

---

A 50-truck fleet, the arithmetic done for you — and the net impact you keep

Setup: You want a number before you talk to anyone.

Payoff: Here is the calculation, built with inputs you can verify and math you can reproduce.

All figures below are modelled estimates based on conservative assumptions: 60,000 miles per truck per year, a 6% mileage reduction, diesel at $5.00/gallon, and $0.20/mile in maintenance. These are not customer results — they are a pre-data estimate for planning purposes. Once you upload a day of loads, the numbers sharpen to your actual fleet.

50-truck fleet — modelled annual impact:

Input	Per truck	50-truck fleet
Miles removed	3,600 mi/yr	180,000 mi/yr
Fuel saved (at 4.5 MPG, $5.00/gal)	$4,000/yr	$200,000/yr
Maintenance saved (at $0.20/mi)	$720/yr	$36,000/yr
Fuel + maintenance combined	$4,720/yr	$236,000/yr
Nivio cost	$720/yr	$36,000/yr
Net impact	$4,000/yr	$200,000/yr

Modelled return: approximately 6.6× cost. Modelled payback: approximately 56 days from go-live. Both figures are modelled from the assumptions above — not a customer result.

---

Already connected. Fifty-plus constraints. One API call.

For technical buyers and fleet operators with engineering resources: Nivio Dispatch exposes a single API call with over 50 constraint parameters — commodity type, weight, permit class, equipment rules, HOS, time windows, driver preferences, and the operational rules specific to bulk operations. The same Proprietary Algorithm that runs the product is available via that call. The plan comes back in the same format whether it originates from the UI, an Excel upload, or a direct API call.

This is not a separate enterprise tier. It is the same solver, available to any fleet that wants to call it directly.

Integrations live today: Samsara, Geotab, Motive. McLeod and TMW available on request. Everything else connects via the API or CSV.

---

Start with the spreadsheet you already keep

Upload one day of loads. The Proprietary Algorithm runs against your actual data and returns a complete plan — before any integration, before any IT conversation, before any commitment.

Talk to the founder about what that looks like for your fleet.

---

FAQ

Does Nivio Dispatch replace our current TMS? No. Nivio Dispatch sits alongside your existing TMS. Loads come in from your TMS or a spreadsheet, the Proprietary Algorithm builds the plan, and the finished plan is pushed back into the same TMS your dispatchers already use. Nothing in your current stack is removed or replaced at any stage.

How long does it take to see a plan with our own data? Upload one day of loads from Excel or CSV and the Proprietary Algorithm returns a complete planned output in under 5 minutes. No integration, no IT project, and no onboarding call is required before you see a plan built from your actual lanes, volumes, and constraints.

Which ELD and TMS platforms does Nivio connect to today? Live connections are available today for Samsara, Geotab, and Motive. McLeod and TMW connections are available on request. Any platform not listed connects via the API or a standard CSV export — no custom development is required on your side to get started.

What constraints does the Proprietary Algorithm actually handle? The solver weighs over 50 constraints simultaneously: commodity type, weight limits, permit requirements, equipment rules, hours-of-service, customer time windows, and the operational rules specific to your fleet. Generic dispatch tools ignore bulk-specific rules; those constraints are built into the core of the solver.

What does Nivio Dispatch cost for a 50-truck fleet? The modelled cost is $720 per truck per year, totalling $36,000 annually for a 50-truck fleet. Against modelled fuel and maintenance savings of $236,000 per year, that produces a modelled net impact of $200,000 and a modelled payback of approximately 56 days from go-live. All figures are modelled, not measured customer results.