RTLS for the CFO.
Real-time location, RFID and IoT programmes don't fail in the technology — they fail in the financial case. This is the lens a finance leader uses to evaluate one, control it, and exit cleanly if it isn't paying back.
What you actually pay for
RTLS programme costs land in five buckets and finance teams routinely miss the last two. The visible costs are hardware (tags, anchors, readers, gateways, sensors) and software (location-intelligence platform, licensing, maintenance).
The hidden ones are integration into your existing stack (typically 20–40% of total programme cost), change management and training, and ongoing calibration, drift detection and quarterly audit.
A vendor-led quote usually shows the first two and minimises the rest. A defensible business case prices all five with sensitivities.
Where the payback comes from
Five categories of return: recovered labour time (people stop hunting for things), reduced shrink and rentals (fewer lost or duplicate assets), higher utilisation (you buy or rent less),
lower error and rework cost (cleaner data, fewer mis-picks, fewer line stops), and avoided cost of non-compliance (passed audits, fewer recalls).
Each can be modelled per use case with conservative, expected and aggressive sensitivities. Most well-scoped RTLS programmes pay back inside 12–18 months on the conservative case.
Controls that protect the budget
Three contractual controls turn an RTLS commitment into a manageable risk. A gate-driven engagement (see the TRACIO Programme Method) gives you written go/no-go decisions at each stage.
A vendor-neutral architecture lets you swap suppliers without re-architecting. And an independent advisor (see our independence policy) holds the contract, the SOW and the ROI model — not the vendor whose target depends on the deal closing.
The three numbers your board actually wants
Forget 47-line spreadsheets. Boards approve when three numbers are credible: payback period in months, five-year NPV with a stated discount rate, and worst-case exposure if the programme exits at gate 2.
The TRACIO Programme Method ends every stage with those three numbers refreshed.
Frequently asked questions
How is RTLS TCO typically structured?
Five-year TCO covers hardware (one-time + refresh), software licensing, integration, deployment services, and ongoing operations (calibration, monitoring, drift audits).
Vendor-led quotes usually compress to hardware + licensing only; an independent model includes the four hidden categories that drive 40–60% of real cost.
What payback period is realistic?
Most asset-visibility and inventory-accuracy programmes pay back within 12–18 months on the conservative case.
Safety and compliance programmes are usually justified on risk-avoidance rather than direct payback. We model both for the same architecture so the board sees a complete picture.
Can we structure fees as outcome-based rather than fixed?
Yes, for clearly-measurable use cases (inventory accuracy lift, search-time reduction). For ambiguous outcomes (safety, compliance) we stay on fixed-fee or day-rate, because outcome-based pricing on the wrong KPIs distorts the engagement.
What's the worst-case financial exposure?
With a gate-driven contract, your worst case is the cost of design (typically 6–12 weeks of fees plus the site survey) before exiting at gate 1. Below 5% of the full programme cost. That is the structural protection.
Last updated: