When a CFO or owner is asked to approve dispatch software spend, the conversation usually stalls on the same question: how do we know if it's working? The vendor showed you an ROI projection. It was probably a big number with a short payback period. What they didn't show you is which specific metrics will change, by how much, and how you'll know the change was caused by the software rather than a favorable load market or a better quarter of driver retention.
The core question is simple: what does this do to our cost per loaded mile? Everything else is downstream from that. Here are the four metrics that tell the real story — and one thing to be genuinely skeptical of in any ROI projection you receive.
The 4 metrics that actually matter for dispatch ROI
1. Loaded-mile percentage (before vs. after)
This is the efficiency metric. If dispatch optimization is working, your loaded-mile percentage goes up. Full stop. Every other positive metric in the stack — lower fuel cost, lower maintenance, higher revenue per driver day — is downstream of this number moving in the right direction.
Measure it daily. Track it as a 30-day rolling average so individual outlier days don't obscure the trend. Compare it to the same period the prior year if seasonality affects your loads. If loaded-mile % isn't moving up within 60 days of implementation, the software either isn't deployed correctly or isn't working. Don't let a vendor tell you it takes six months to see results in this metric. The algorithm either finds better plans or it doesn't, and you'll know relatively quickly.
2. Fuel cost per total mile (before vs. after)
Your total fuel spend isn't the right number to watch — it fluctuates with diesel prices, which move for reasons entirely outside your control. Fuel cost per total mile controls for that. If you're driving fewer empty miles, fuel cost per total mile falls regardless of what diesel does at the pump. This metric is also useful for surfacing whether the improvement is real or a fuel-price artifact.
For a bulk fleet running 90 trucks, a 23% reduction in deadhead miles typically translates to a $0.043–$0.052 reduction in fuel cost per total mile (based on fleet economics at current diesel pricing, mid-2026). At scale, that's a meaningful number.
3. Revenue per driver per day (before vs. after)
This is the output metric. Loaded-mile % tells you about efficiency. Revenue per driver per day tells you whether that efficiency is translating to actual throughput — more loads completed, more tons moved, more billable miles per shift. A good plan doesn't just reduce empty miles; it sequences loads so drivers can complete more loads per shift within their HOS window.
On a well-optimized 60-truck fleet, revenue per driver per day typically improves $87–$143 versus a manually planned baseline (based on Nivio Dispatch fleet analyses, bulk petroleum and frac sand operations). Across a 60-truck fleet over 250 operating days, that range is $1.3M–$2.1M in additional revenue capacity — without adding trucks or drivers.
4. Dispatcher planning hours vs. exception management hours
This one surprises some finance teams, but it matters. The value of recovering 2.5 dispatcher hours per day isn't just the labor savings (though at $28–$42/hour all-in, it adds up). It's what those hours get redirected toward. A dispatcher who isn't rebuilding the board from scratch every afternoon has time to manage customer relationships, catch exception situations before they become expensive, and handle the day's problems proactively instead of reactively.
Track this by asking your dispatcher to log their afternoon time for two weeks before and after. The shift should be visible and measurable.
The sample ROI: a 60-truck bulk fleet
| Metric | Baseline (manual) | Optimized | Annual impact |
|---|---|---|---|
| Loaded-mile % | 42.3% | 51.1% | +8.8 pts |
| Fuel cost per total mile | $0.491/mi | $0.443/mi | –$0.048/mi |
| Fuel savings (60 trucks) | — | — | ~$342,000/yr |
| Maintenance cost per truck/yr | $17,820 | $14,940 | –$2,880/truck |
| Maintenance savings (60 trucks) | — | — | ~$172,800/yr |
| Revenue per driver per day | baseline | +$113/driver/day | +$1.69M capacity |
| Dispatcher planning time | 3.4 hrs/day | 29 min/day | ~$18,900/yr recovered |
| Total hard savings (fuel + maint.) | — | — | ~$514,800/yr |
At $514,800 in annual hard savings, the payback period on a typical dispatch optimization platform is 2.4 months. The revenue capacity improvement is additional and harder to guarantee — it depends on load availability and market conditions — so a conservative CFO should anchor on the fuel and maintenance savings, which are structural.
What to be skeptical of
The question isn't whether optimization saves money. Every fleet analysis shows it does. The question is whether the number is big enough to justify the change management.
Be skeptical of:
- Generic "up to X%" claims without fleet-specific data. "Up to 30% fuel savings" is technically true — for some fleet, at some point, under some conditions. Ask for the analysis run against your specific loads, your specific lanes, your commodity type.
- ROI projections based on industry averages. A frac sand fleet in the Permian Basin and a refined fuel fleet in the Southeast have different economics, different load densities, different HOS patterns. An average doesn't tell you what your fleet will do.
- Payback period calculations that include revenue upside. Fuel and maintenance savings are structural and predictable. Revenue upside is real but depends on load availability you don't control. A credible ROI projection separates the two.
Send one day of completed loads — the actual loads your trucks ran, with drivers, times, and miles. Nivio runs the Proprietary Algorithm against that data and returns a fleet-specific projection within 24 hours: your current loaded-mile %, what an optimized plan for that same day would have looked like, and what the annual savings differential implies at your fleet size. No generic benchmarks. Your data, your lanes, your fleet.
The takeaway
A CFO evaluating dispatch optimization software should anchor on four metrics: loaded-mile percentage, fuel cost per total mile, revenue per driver per day, and dispatcher time allocation. For a 60-truck bulk fleet, structural savings (fuel plus maintenance) typically run $490,000–$560,000 per year, with a payback period under three months. Any projection not built from your actual loads and lanes should be treated as directional, not definitive — and Nivio will build you a fleet-specific analysis from one day of data before you make any commitment.
Get a fleet-specific ROI projection
Send one day of completed loads. You'll have your fleet-specific analysis back in 24 hours — your loaded-mile %, what an optimized plan would have recovered, and what the annualized savings look like for your operation.
Request your analysis →