CFO — evaluatie van RTLS, RFID en IoT.
For a CFO, an RTLS, RFID or IoT programme is one capital-allocation decision among many — competing with M&A, capacity expansion, system upgrades and working-capital projects.
The right framing isn't "is the technology good?" — it's "is this the best use of constrained capital, with risk-adjusted return that exceeds hurdle rate?" This insight covers how we think about that question with CFO clients.
De onderliggende vraag van de CFO
Not "what does the technology do?" — but "what business outcome does this capital purchase change, by how much, with what risk,
over what period?" RTLS programmes that fail at the CFO level usually fail because they were framed as technology investments rather than capital allocation decisions.
The right pitch to a CFO is a business-outcome model with 5-year cash flows, a sensitivity analysis, and a comparison against the next-best use of the same capital.
Capex versus opex — de structurele constructie
Most RTLS programmes can be structured either way. Capex: client owns the hardware, capitalises and depreciates over 5–7 years; lower TCO at steady state but locks capital, slower expansion.
Opex / RTLS-as-a-service: subscription model; higher 5-year cash spend but cleaner cash-flow, faster scale-out, no capitalised asset.
The right structure depends on the company's cost of capital, balance-sheet strategy and growth profile. A growth-stage CFO usually prefers opex; a mature CFO with abundant capital and depreciation-friendly tax position prefers capex.
5-jaar TCO is de analyse-eenheid
Vendor quotes are typically year-1 capex. The CFO should require a 5-year TCO model covering hardware, software, integration, support, tag replacement and change orders. See /templates/tco-model for our spreadsheet.
Most vendor business cases collapse when extended to 5 years — the year-1 capex is competitive but years 2–5 reveal lock-in pricing, tag replacement cycles and change-order economics that change the math.
Risico-gecorrigeerde ROI
RTLS programmes have characteristic risk profiles. Technology risk: does the radio actually deliver accuracy in this environment? Mitigated by pilot validation.
Vendor risk: is the vendor financially stable and the platform on a healthy roadmap? Mitigated by independent reference checking.
Adoption risk: will operators actually use the system to drive the KPI? The biggest risk and the least visible at procurement. Integration risk: does the data actually flow into systems that drive operational change? Mitigated by integration architecture in stage 1.
We weight each risk against the probability-weighted ROI to produce a risk-adjusted number that a CFO can compare directly against other capital allocation decisions.
Terugbetalingstijd — en wat het je niet vertelt
Typical RTLS payback periods range from 6 months (high-volume retail item-level) to 36 months (clinical workflow). Short payback doesn't always indicate the best programme — a high-payback programme can still be sub-optimal if it doesn't compound or if it has high adoption risk.
We model NPV at the company's cost of capital alongside payback period, and we add a strategic-option-value layer (does this deployment unlock further capability later?).
Hoe we omgaan met CFO s
CFO engagements typically include a structured business-case review (often in the diagnostic phase of programme rescue or stage 1 of /method) followed by a 5-year TCO and ROI model.
We provide a one-page CFO summary for steering committees and detailed model for finance teams. References on request — see /for-cfo for the dedicated CFO persona page.
Veelgestelde vragen
Wat is een typische RTLS ROI?
Wide range, depending on use case. Retail item-level: 6–12 month payback, 4–8× 5-year ROI. Healthcare workflow: 18–36 month payback, 2–4× 5-year ROI. Manufacturing WIP: 12–24 month payback, 3–6× 5-year ROI. We model specific to the client environment in stage 1.
Hoe houden we rekening met zachte voordelen (personeelstevredenheid, merk?
We modelleren doorgaans harde cashflowvoordelen als het primaire geval en zachte voordelen als opwaartse scenario's.
Harde uitkeringen zouden het drempel vanzelf moeten overwinnen; Zachte voordelen worden het strategische optie-waarde-argument voor goedkeuring door de raad van bestuur.
Moeten we zelf financieren of een financieringspartner gebruiken?
Het hangt af van de kapitaalkosten en de balansstrategie. Verschillende leveranciers bieden financiering of RTLS -as-a-service opties aan die van capex opex; We modelleren beide tijdens fase 1.
Wat is het juiste drempel voor een RTLS-programma?
Meestal is de WACC van het bedrijf plus een risicopremie voor technologische en adoptieonzekerheid (vaak +3–5%). We passen ons aan op basis van het specifieke risicoprofiel van het programma.
Hoe behandelen we programma's die meerdere business units beslaan?
Toewijzing is vaak de doorslaggevende politieke vraag. We ontwerpen BU-allocatiemodellen op basis van uitkeringstoewijzing bij scoping; Multi-BU-programma's werken het beste wanneer elke BU een meetbare KPI aan het programma heeft gekoppeld.
Laatst bijgewerkt: