Device ROI Logic: From Approval to Payback
The Formula and Its Traps
The textbook line “investment ÷ per-session margin = sessions to payback” gets clamped by two constraints: capacity (how many clients the device can serve daily) and demand (how many clients will actually be routed to it). Estimates ignoring these routinely overstate payback by 50%+.
The Right Steps
- Capacity ceiling: session length × effective hours × scheduling limit = theoretical daily capacity; times realistic utilization (30-50% for new programs) = actual.
- Demand allocation: target population × conversion × program penetration = monthly sessions.
- Per-session contribution: price − consumables − labor share − space share (consumables per the cost entry).
- Payback: total investment (training and warranty included) ÷ (monthly sessions × contribution) = months; then apply a 0.8 stress factor.
What Gets Over- and Under-Estimated
- Overestimated: utilization (new devices ramp 3-6 months), pricing stability (competition compresses).
- Underestimated: consumables and service, retraining after churn, marketing/education cost for new programs.
For Decision Makers
ROI output is not a yes/no — it is a decomposition of operating targets: to pay back in X months, Y sessions at ticket Z per month. Those numbers are the real KPIs once the device arrives.
FAQ
What payback period is reasonable?
12-24 months for core programs; traffic programs may run longer (they contribute clients, not margin). Sub-6-month plans usually mean missing items.
What if the device sits idle?
Compute the “break-even utilization” as an alarm line during planning; idle periods feed bundles, cross-industry partnerships and staff training to consume capacity.