An RFID ROI Model That Survives the CFO: Costs, Benefits and Honest Assumptions

RFID business cases have a credibility problem, and it is self-inflicted. Projects that need approval produce a spreadsheet showing a payback of eleven months and a five-year return that no one believes. Projects that are honest produce a spreadsheet showing a payback of three years and get rejected. The difference is rarely the technology. It is whether the model separates what can be measured from what has been asserted.

ROI is a model, not a number

A single payback figure is the output of dozens of assumptions, and the assumptions are the deliverable.

• Every RFID business case contains at least one number that came from a vendor brochure and was never verified on site.
• Tag cost per unit is easy to state and easy to get wrong, because it excludes application labour, printer consumables and tag loss.
• Benefit estimates are usually stated as a percentage improvement with no baseline. Without a baseline, no improvement can be verified after go-live.
• A model that cannot be audited after deployment teaches the organisation nothing and cannot be reused for the next site.
• The useful output is not the payback number. It is the list of assumptions, ranked by how much the answer depends on them.

The cost side nobody budgets

The capital list is the easy part. The operating list is where projects overrun.

• Tags, inlays and labels, including the loss rate. In apparel retail, tag loss and damage of 1 to 3 % per year is normal.
• Printers, applicators, verifiers and their consumables: ribbons, printheads, cleaning kits.
• Readers, antennas, cabling, mounting hardware, power and network drops.
• Installation labour, including the electrician, the network team and the structural work that RFID vendors exclude.
• Software integration: middleware, connector to the ERP, dashboard, and the reporting that finance will ask for in month two.
• Training, for operators, supervisors and the maintenance team. Budget it per person, not per site.
• Exception handling labour. This is the largest hidden cost and the one most often omitted.
• Maintenance and replacement, spread over the asset life rather than assumed to be zero.
• Project risk: a contingency of 10 to 20 % on hardware and integration is not pessimism, it is experience.

Where the benefit actually comes from

RFID benefits are usually presented as one large number. They should be presented as five small ones, each with its own evidence.

• Labour avoidance: counting, searching, scanning and reconciling hours that disappear or shrink.
• Accuracy improvement: fewer stock-outs, fewer emergency transfers, less safety stock held to compensate for bad data.
• Shrinkage reduction: fewer unexplained losses, because every movement has a time and a reader.
• Throughput: faster receiving and shipping, which matters when the dock is the constraint.
• Working capital: lower inventory because the same service level is achievable with less buffer.
• Revenue protection: fewer cancelled orders and fewer markdowns caused by misplaced stock.

Each of these must be measured against a baseline taken before the project, or it is an assertion rather than a benefit.

Inventory accuracy and its financial value

Accuracy is the benefit everyone claims and few can quantify, so quantify it properly.

• Measure record accuracy today: sample 200 SKUs or locations, count them physically, and compare to the system. The gap is the baseline.
• Estimate the inventory held to compensate for that gap. If accuracy is 92 %, the safety stock is carrying the error, and the carrying cost is typically 15 to 25 % per year.
• Estimate the cost of a stock-out: lost margin, expedited freight, customer service time and, in some channels, contractual penalties.
• Estimate the cost of a cycle count: labour hours per count, frequency, and the disruption to operations.
• Then state the expected improvement conservatively. Moving accuracy from 92 % to 97 % is credible; claiming 99.9 % in year one is not.
• Verify after go-live with the same sampling method. If the method changes, the improvement cannot be proven.

Labour, shrinkage and out-of-stocks

These three are where the money usually is, and where the estimates are usually loosest.

• Labour: measure the actual minutes per process today, with a stopwatch, not with an estimate from a manager.
• Shrinkage: use the finance figure, not the operations figure, and distinguish theft from process loss. RFID helps with process loss far more than with theft.
• Out-of-stocks: count them for a month before the project. The number is usually higher than anyone believes and lower than the vendor assumes.
• Do not double count. Faster receiving and better accuracy both reduce labour, but the same hour cannot be saved twice.
• Apply a realisation factor: most organisations realise 60 to 80 % of the modelled benefit in year one, and the model should say so.
• Include the benefit ramp. A site does not achieve steady-state accuracy in week two.

Building the model

A model that a finance team can audit is worth more than a model that produces a better number.

• Build it in a spreadsheet with one assumption per cell, labelled, sourced and dated.
• Separate capital expenditure, operating expenditure and benefit, and keep them on separate tabs.
• Model five years, not one, because readers and tags have different lives and the replacement cycle matters.
• Include a do-nothing scenario with its own costs: the labour, shrinkage and stock-outs that continue if nothing is done.
• Model per site and per process, then aggregate. A single blended model hides the site that will not pay back.
• Version the model and keep the version used for approval. When the project underperforms, the comparison is the lesson.

Payback, NPV and sensitivity

Three numbers are enough, provided each is presented with its assumptions.

• Simple payback: cumulative benefit equals cumulative cost. Useful for operations, misleading for finance if used alone.
• Net present value over five years at the organisation's cost of capital, with a stated discount rate.
• Sensitivity: vary tag price, labour rate, accuracy improvement and adoption rate one at a time, and show the range.
• Identify the break-even value of the most sensitive assumption. If the case only works when accuracy reaches 99.5 %, say so plainly.
• Show the downside case, not only the base case. A case that survives a 30 % worse benefit is a case worth approving.
• State the non-financial benefits separately: compliance, traceability, customer requirements. They are real, but they should not be used to rescue a failing financial case.

What the model cannot capture

Some of the value is real and cannot be put in the spreadsheet, and pretending otherwise damages credibility.

• Recall and traceability capability is an insurance premium. Its value appears only in the year it is needed.
• Customer mandates are a condition of doing business, not a benefit. Model them as a cost of non-compliance.
• Organisational learning from the first site reduces the cost of the second, and that reduction is real but hard to allocate.
• Data quality improvements compound over years in ways a five-year model understates.
• Employee experience matters for retention, and retention is expensive, but attributing it to RFID is speculative.

Making the case defensible

• State the baseline, the method used to measure it and the date.
• Give every assumption a source: vendor quote, finance report, time study or explicit judgement.
• Present the base case, the downside case and the break-even assumption.
• Commit to post-implementation measurement with the same method, and name who will do it.
• Report the result honestly, including the parts that did not pay.

An RFID business case is not a persuasion document. It is a forecast, and forecasts are judged after the fact. The organisations that build honest models get approval for the projects that work, and learn something from the ones that do not.