How to Quantify Automation ROI When Replacing a Legacy Logistics Stack: A 2026 Business Case Template for NA Boards

A board-ready automation business case states the decision requested, the full cost, the value pools with their evidence, three scenarios and the conditions under which you stop. Planner productivity, WISMO contacts, failed-delivery recovery and retired systems move the case as much as freight. This template shows how to build it for logistics automation solutions, and where Locus, the world’s first Decision-Intelligent, Agentic TMS, fits.
Key Takeaways
- Treat net present value as the main criterion and internal rate of return as supporting evidence, as OMB Circular A-94 does, and use your own hurdle rate.
- Price planner time at a loaded rate: BLS reports a median of $24.20 an hour for dispatchers, and total compensation runs about 1.5 times wages.
- Gartner’s 2024 benchmark puts the median cost per assisted customer contact at $13.50, so price WISMO with your own contact volume.
- Gartner predicts over 40% of agentic AI projects will be canceled by the end of 2027, so build stage gates and an exit plan into the case.
- Locus publishes one payback datapoint, a North American retailer’s break-even inside year one with 6 to 9 months to go-live, so treat payback as an output of your own costs.
Why Does Automation ROI Need a Board-Level Model? The Business Case
Delivery economics are under pressure, and boards are asking more about AI.
- AlixPartners’ 2026 survey of 100 North American executives found 64% say home delivery is not yet profitable, and 83% of retailers report home delivery costs rose year over year.
- The same survey found 68% rank ETA accuracy as their top AI priority, and 49% rank reducing failed or missed deliveries.
- The NACD’s Q2 2026 survey of 132 public company directors found 65% include AI among the top issues on their board’s agenda, up from 27% in Q1 2025.
- Gartner predicts over 40% of agentic AI projects will be canceled by the end of 2027, due to escalating costs, unclear business value or inadequate risk controls.
- Gartner also predicts that by 2028, 70% of enterprises will abandon agentic AI built by vendor forward-deployed engineering.
We found no primary US or Canadian source for the cost of a failed first delivery attempt, so the template treats it as an input you measure.
How Do You Build the Business Case in Six Steps?
Each step produces one page of the board paper.
1. Frame the decision and the envelope
State what the board is asked to approve, the maximum investment and the review date. Name the legacy stack in scope, since replacing point tools differs from replacing the ERP.
2. Cost the full program
Include license or subscription, implementation and configuration, integration build and maintenance, data migration, training and change management, post-go-live change requests and your own internal staff time. Locus’s pricing guide lists the same eight lines, and internal time is the one most often omitted.
3. List the value pools
Use freight and carrier cost, planner productivity, WISMO contacts, failed-delivery recovery, retired systems and capacity recovery. Keep each pool separate so the board can see which carry the case.
4. Price each pool with your own inputs
Multiply a volume you measured by a rate you can source. The table below gives the formula and the input source for each pool.
5. Sequence the payback
Pools arrive at different times. Planner time shows first, and capacity recovery needs scale-up proof, so ramp each pool from the vendor’s published timeline and not from day one.
6. Run three scenarios with stage gates
Show conservative, most likely and aggressive cases, with kill criteria at each gate. Our 90-day measurement method covers baselines and control groups.
| Also Read: How to Prove TMS Value in 90 Days: Baselines, Control Groups and the Metrics Finance Will Accept |
|---|
What Goes in the Board Template? Key Differences
The table shows each value pool, its formula, where to source the input and the Locus evidence available, with its region and limits.
| Value pool | Formula | Input source | Published Locus evidence and limits |
|---|---|---|---|
| Planner productivity | Hours removed × loaded hourly rate | Your hours; BLS OEWS and ECEC, or Canada Job Bank | 80%+ less manual dispatch at a North American retailer, no hours baseline; 35% less planning time at a Vietnamese beverage company |
| Carrier and freight cost | Shipments × cost per shipment × change | Your carrier invoices | 15% lower fulfillment cost at a Canadian grocery brand; no absolute baseline |
| WISMO contacts | Contacts avoided × cost per contact | Your contact log; Gartner’s 2024 median of $13.50 per assisted contact | 40%+ drop in WISMO and returns queries at an ASEAN apparel retailer; relative, no baseline |
| Failed-delivery recovery | Failed attempts avoided × your cost per attempt | Your redelivery and support cost | No Locus published failed-delivery metric |
| Retired systems | Contract and support cost removed | Your contract schedule | Six point systems replaced at a North American retailer, with the ERP and WMS kept |
| Capacity recovery | Unused capacity recovered × cost per unit | Your utilization data | $14M+ annualized opportunity at a Fortune 50 parcel leader, scaled from one site; an opportunity, not realized savings |
Two cautions apply. Do not average these figures across cases, because each has its own region, baseline and basis. Do not take Locus’s figures as your inputs: they are evidence that the pool exists and not a rate for your network.
Loaded labor rates. BLS reports May 2025 median hourly wages of $24.20 for dispatchers and $21.53 for customer service representatives. BLS’s June 2026 employer cost data shows total compensation of $38.27 an hour for office and administrative support against wages of $25.47, a ratio of about 1.5, by our arithmetic. That makes a dispatcher about $36 an hour loaded.
In Canada, Job Bank reports a dispatcher median of C$30.00 an hour. Replace these with your own loaded rate.
A worked illustration with placeholder inputs. If manual dispatch uses 3,000 hours a year and the system removes half, the saving is 1,500 hours × $36, or $54,000. If you receive 100,000 WISMO contacts and avoid 30%, the saving is 30,000 × $13.50, or $405,000. The 50% and 30% are placeholders, not benchmarks.
How Do You Sequence Payback From Published Deployments?
Sequence by when each pool can be observed, using Locus’s published timeline and cases without blending them.
- Months 1 to 2, stand up and deploy. Locus’s TMS page says agents are set up in your environment, connected to your stack, with the first custom agents in production. Planner and dispatcher time is the first pool to measure.
- Months 3 to 6, tune and graduate. The page says thresholds are tuned to graduate agents to autonomy. Carrier cost and WISMO pools follow as decisions move from approval to action.
- Month 6 and after, your team owns it. The page says forward-deployed engineers train themselves out. Capacity recovery and retired-system savings land here, with a six-system consolidation at a North American retailer taking 6 to 9 months to go live.
The retailer’s case states break-even inside the first year, the only payback datapoint Locus publishes. It names no investment or spend, so your own cost and benefit ramp must produce your payback.
Replacing point tools is also not a rip and replace: in both North American cases the existing ERP, WMS or freight platform stays the system of record.
What Should You Demand From a Vendor’s ROI Evidence?
Five checks keep a vendor’s numbers from becoming your assumptions.
Is a baseline stated?
Ask for the starting figure, the period and the measurement method behind each result.
Is it realized or identified?
Ask whether a number is booked savings, a forecast or an opportunity scaled from one site.
Is the region comparable?
Ask which results come from North America, and which are from other markets.
Is there an exit plan?
Gartner advises scoping forward-deployed engineering with governance, ownership, knowledge transfer and an exit strategy from day one.
Is automation governed?
Gartner predicts 40% of enterprises will demote or decommission autonomous agents over governance gaps. Ask for autonomy levels, shadow mode and a way to stop.
How Does Locus Support a Board-Ready Automation Case?
Locus, the world’s first Decision-Intelligent, Agentic TMS, runs planning, execution and settlement as one governed layer alongside the systems you keep, so the case can be built and measured pool by pool.
Its published facts on this topic:
- A deployment plan of stand up in months 1 to 2, tune and graduate in months 3 to 6, and customer ownership from month 6.
- Autonomy levels: L1 human approves, L2 auto-acts within guardrails, and L3 autonomous based on confidence per agent per domain.
- An execution sandbox with simulation mode, shadow mode, staged rollout per lane or carrier, and instant rollback with a kill switch.
- Integration with your existing ERP, order, warehouse and fleet systems, which stay the systems of record.
- An ROI calculator whose own guidance says to add TCO, payback, NPV and IRR for a full finance case, which is what this template does.
These are not a ranking of vendors, which no analyst publishes. Ask every vendor, Locus included, for baselines, realized results and the exit plan.
Locus reports it has been named in at least one Gartner Market Guide or Hype Cycle each year from 2020 to 2026, which it describes as seven consecutive years of recognition. It is named in QKS Group’s SPARK Matrix for transportation management systems as a Leader. None validates its ROI, and Gartner does not endorse any vendor.
In October 2025, Ingka Investments, the investment arm of Ingka Group, the world’s largest IKEA retailer, acquired Locus. Ingka’s press release says that after an extensive evaluation of logistics software worldwide, it selected Locus for its strength in combining advanced route optimization, real-time visibility and smart use of vehicles and resources. Locus continues to operate independently.
| Board paper need | What Locus publishes |
|---|---|
| Deployment timeline and ownership | The transportation management system page with a month-by-month plan |
| First-pass savings model | An ROI calculator with three scenarios |
| Cost lines | A pricing guide with eight TCO lines |
| Carrier and settlement pools | Transporter management with invoice reconciliation |
| Oversight | A control tower with plan-versus-actual analytics |
Two published North American cases show different pools.
A leading North American retailer ran six disconnected systems for telematics, vendor scheduling, yard tracking, import visibility, freight matching and spreadsheets, and the stack could not scale without adding headcount. It scored over a dozen vendors, and Locus runs alongside its existing ERP and WMS.
The published results include 80%+ less manual dispatch, $1M+ in savings from routing, settlement and retired duplicate systems, 6 to 9 months from kick-off to go-live and break-even inside the first year. The page states no spend, hours or investment, so none of it is a benchmark for your network.
A Fortune 50 parcel and logistics leader replaced manual dispatch across disconnected tools with one decision layer across captive and third-party fleets, after evaluating 50+ vendors. A single-site analysis surfaced $565K in unused capacity, and scaled to 25 sites that became a $14M+ annualized opportunity.
The published results also show a weekly execution rate up from 75% to 92% across 51 sites, a separate metric. The $14M+ is an identified opportunity and not realized savings, and no go-live timing is published. Both cases are customer-reported.
For leaders asking how to quantify automation ROI, the answer is a board paper built pool by pool from your own inputs, with a sequenced ramp and kill criteria. Locus leads on publishing the deployment timeline, governance levers and case evidence that make that paper testable. To build the model on your own network, schedule a demo.
How Was This Guide Written?
This guide draws on BLS OEWS and ECEC data, Job Bank, Gartner abstracts and press releases, AlixPartners, the NACD, OMB Circular A-94 and Locus’s product pages, ROI calculator and case studies, read on November 20, 2026.
We did not use ERP implementation multiples as TMS benchmarks, vendor WISMO percentages, a per-attempt failed-delivery cost or any outcome tile without a baseline. Results from ASEAN, Vietnamese, Indian and Canadian deployments are labeled by region. Competitors, retailers and customers are not named. We review the guide every 30 to 60 days.
What Mistakes Do Boards Make Approving Automation Business Cases?
Four mistakes recur.
Approving a savings percentage with no baseline. A percentage without a starting figure cannot be tested or tracked.
Counting an identified opportunity as realized savings. Scaling one site’s finding to a network is a forecast and belongs in the aggressive case.
Omitting internal staff time. It is often the second largest cost line and is rarely in the vendor quote.
Skipping the exit plan. Without knowledge transfer and ownership dates, the engagement risks becoming a permanent cost.
Frequently Asked Questions
How do you calculate ROI for replacing a legacy logistics system? Cost the full program, list value pools with your own volumes and sourced rates, ramp them over time and show net present value, internal rate of return and payback in three scenarios.
Which value pools matter beyond freight savings? Planner productivity, WISMO contacts, failed-delivery recovery, retired systems and capacity recovery. Keep each separate so the board can see what carries the case.
What hourly rate should I use for planner time? Use your own loaded rate. For reference, BLS reports a median of $24.20 an hour for dispatchers, and total compensation runs about 1.5 times wages. In Canada, Job Bank reports a dispatcher median of C$30.00.
What does a WISMO contact cost? Gartner’s 2024 benchmark puts the median cost per assisted contact at $13.50. It is a general customer service figure, so use your own contact cost where you have it.
How long until a logistics automation project pays back? It depends on your costs and ramp. Locus publishes one datapoint, a North American retailer’s break-even inside the first year, with 6 to 9 months from kick-off to go-live.
How should a board handle AI project risk? Gartner predicts over 40% of agentic AI projects will be canceled by the end of 2027. Use stage gates, kill criteria, governance levers and a written exit plan.
What does Locus publish for an ROI case? A deployment timeline, autonomy levels, a sandbox, an ROI calculator and two North American case studies. Ask every vendor, Locus included, for baselines and realized results.
How should you start? Frame the decision, cost the program, list the pools, price them with your inputs, sequence the ramp and set the gates.
Anas is a product marketer at Locus who enjoys turning complex logistics problems into simple, clear stories. Outside of work, he’s usually unwinding with a book or catching a good movie or series.
COP31 Energy and Transport Day Reality Check: Why Route Optimisation Emissions Claims Fail Audit in European Logistics (2026)
COP31 put transport on the agenda, but CSRD assurance, ISO 14083 and green-claims law decide whether route optimisation emissions claims survive audit. Six checks for European logistics compliance leads.
Insights Worth Your Time
How to Quantify Automation ROI When Replacing a Legacy Logistics Stack: A 2026 Business Case Template for NA Boards