Guide · Retail technology
The store-tech case your CFO will approve.
In-store technology rarely fails in the store. It fails in finance, because the business case claims benefits a CFO cannot defend. The fix is not a better deck. It is claiming the benefits that survive scrutiny, zeroing the ones that do not, and bundling so the numbers actually clear. Here is how the case gets a yes.
This guide, in 6 parts
The case dies because it claims the wrong benefits.
The market is moving. Shelf-edge technology is compounding at double digits and the biggest retailer in the country is fitting it across thousands of stores. None of that helps you when your own case lands in front of finance and stalls.
It stalls for one reason. The case leans on a richer experience, more dwell time, a more modern store, and a CFO cannot bank a number that does not tie to a sale or a saved cost. So the whole thing gets discounted to zero, and the project that would have worked on the floor never gets to the floor.
« In-store technology rarely fails in the store. It fails in finance. »
Claim these. Discount the rest to zero.
Build the case the way finance reads it. Three benefits a CFO can defend, one category to keep out of the model entirely. Decide which is which before you write a single line of the NPV.
Labour you can reallocate
Hours that move from a measurable task to a measurable place. A price change that took an associate the better part of a day collapses to minutes on a mobile app; that time goes to the floor and the customer. Put it in the case as hours redeployed at a known rate, not as a headcount cut you will not make.
On-shelf availability
A live, correct view of what is actually on the shelf turns into sales you were losing to empty pegs and phantom stock. Size it from your own out-of-stock rate against a sober uplift, store by store. This is hard money a CFO can defend, because the lost sale was already on the books as zero.
Price agility
The ability to change every price in the estate in minutes, correctly, with no reprinting and no mismatched tags. Value it as labour removed and as margin protected when a cost or a competitor moves and you can respond the same hour. Keep the claim to execution speed and accuracy, not to a dynamic-pricing fantasy you have no intention of running.
Soft engagement metrics
Dwell time, app taps, a richer in-store experience, a more modern brand feel. They may be real, but finance cannot bank a number it cannot tie to a sale or a saved cost, so it discounts them to zero, and rightly. Put them in the narrative if you must; keep them out of the NPV. A case that leans on them is a case that has already lost the room.
Bundle, so one install underwrites three benefits.
A single capability rarely pays back alone. A shelf-label rollout, costed on its own, has to carry the entire return on one benefit line, and it usually cannot clear the hurdle. This is why single-tag pilots stall in finance, not on the floor.
The move is to bundle. Put the shelf-edge platform, the live availability view, and the picking or in-store commerce that rides on the same hardware and the same install into one case. The cost is largely shared, but now it is spread across three benefit lines at once: labour, availability and price execution. The same infrastructure that paid back slowly on one benefit pays back fast on three.
That is what flips the NPV. Not a bolder claim on a single number, but the same floor of cost underwriting several returns together. The kit that makes those benefits real, the shelf-edge platform, the live data, the picking and in-store commerce, is what we build in the connected floor.
« Not a bigger claim on one benefit. The same install underwriting three. »
The payback window that earns a yes.
Finance does not approve a return. It approves a return inside a window it can live with. For in-store retail technology, that window is roughly 12 to 24 months, staged store by store. It is short enough to sit inside the planning horizon, and it is credible because the benefits start the moment the kit is live, not at the end of a five-year curve.
A five-year payback reads as an act of faith and gets deferred. Stage it instead: prove the number in the first stores, let the early returns fund the next wave, and the case expands on its own evidence rather than on a promise. Bain puts most of these deployments at a positive return inside a year once they are scoped on real efficiency; a 12-to-24-month estate-wide window is the honest, approvable version of that.
The case, in five lines.
A store-technology business case is ready for finance when it can tick all five. Until then, it is a wish, and finance will treat it as one.
- A measurable problem, named in money: lost sales to out-of-stocks, hours lost to price changes, margin lost to slow response.
- Only hard benefits in the NPV: labour reallocated, availability recovered, price execution. Soft metrics live in the narrative, never the model.
- A bundle that earns its keep on the floor, not a single tag pilot that has to carry the whole return alone.
- A payback window finance can sign: roughly 12 to 24 months, staged store by store, not a five-year act of faith.
- A named owner and a go-live plan, so the case is a deployment leadership can approve, not a slide it can defer.
Frequently asked.
Why do store-technology business cases keep getting rejected by finance?
Because most of them claim the wrong benefits. The case leans on dwell time, app engagement and a more modern store feel, none of which a CFO can tie to a sale or a saved cost, so the whole thing gets discounted to zero. The cases that pass are built only on benefits finance can defend: labour you can reallocate at a known rate, on-shelf availability you can size from your own out-of-stock data, and price-execution speed and accuracy. Claim those, zero the soft metrics, and the model survives the room.
What benefits should we actually put in the NPV?
Three. Labour reallocation, valued as hours moved from a measurable task to a measurable place at a known rate, not a headcount cut you will not make. On-shelf availability, sized from your real out-of-stock rate against a sober uplift, store by store, because the lost sale was already booked as zero. And price agility, valued as labour removed and margin protected when you can change every price correctly in minutes. Leave soft engagement metrics in the narrative; they do not belong in the model.
A single project does not pay back. How do we make the numbers work?
You bundle. One capability, a shelf-label rollout on its own, has to carry the entire return and usually cannot, which is why single-tag pilots stall in finance. Put the shelf-edge platform, the live availability view, and the picking or in-store commerce that rides on the same hardware and the same install into one case, and the shared cost spreads across several benefit lines at once. That is the move that flips the NPV: not a bigger claim on one benefit, but the same infrastructure underwriting three.
What payback period will a CFO actually approve?
For in-store retail technology, a window of roughly 12 to 24 months, staged store by store, is the one that earns a yes. It is short enough to sit inside the planning horizon and credible because the benefits, labour and availability, start the moment the kit is live. A five-year payback reads as an act of faith and gets deferred. Stage the rollout so the early stores prove the number before the estate commits, and the case funds its own expansion.
Is the shrink and theft number part of the case?
Treat it as secondary, and cite it carefully. US retailers lost an estimated 45 billion dollars to shoplifting, per the NRF Impact of Retail Theft and Violence 2024 report, but the NRF retired its long-running annual shrink series in 2024, so the figure is softer than it looks and easy for a sceptical CFO to pull apart. Some store technology does help on availability and loss, but build the case on labour, availability and price execution, where the money is defensible, and let theft sit in the narrative, not the NPV.
You can write much of this yourself. The benefit lines, the rates and the out-of-stock numbers belong to your own operators and finance team, and they should own them.
Bring us in when the case has to become a system that actually ships and holds across the floor, and when you need the bundle scoped so the NPV clears the first time. Which capabilities to join, and where each one pays back, is its own map; we keep ours private, but if you are weighing what to put in one case and what to stage, that is the conversation. See how we think about it in the Hub Map.
Have a case that keeps stalling in finance?
No deck, no gate. A working session on your real floor, your real numbers and the bundle that would clear, with the operators who would build it.