How to recover a failed RTLS pilot
Pilots run in a controlled corner with the best tags, readers and network. Rollouts don’t. Here is how to diagnose why a pilot stalled — and the steps that get it moving again.
Why pilots stall
- Accuracy that held in a clean corner collapses in production RF (metal, racking, forklifts)
- No integration to the systems people actually use, so the data is never adopted
- Tag/inlay or anchor density chosen for a demo, not for scale or cost
- No clear KPI or business case, so nobody will fund the rollout
- A vendor optimising for their hardware, not your outcome
The recovery sequence
- Diagnose: a fast, independent read of where accuracy, integration or economics actually broke
- Re-baseline the use case and the KPI that justifies spend
- Fix the physics: site survey, tag-on-material testing, read-zone or anchor redesign
- Wire it into the workflow so the data is used, not just displayed
- Re-pilot against the real environment, then scale through gates
Why independence helps here
When a pilot is failing, the incumbent vendor is rarely the right party to grade their own homework. An independent advisor with no reseller margin can tell you plainly whether to fix, re-scope or change approach — and we can drop in at any stage.
Frequently asked questions
Can a failed RTLS pilot be saved?
Often, yes. Most failures are fixable: RF design, tag selection, integration or scope — not the whole concept. The first step is an honest diagnosis.
How fast is a diagnosis?
Usually a short, fixed-fee review that pinpoints what broke and whether to fix, re-scope or switch approach.
Do we have to change vendor?
Not necessarily. Sometimes the kit is fine and the design or integration isn’t. We recommend what fits, with no reseller margin.
Can you take over a stalled programme?
Yes — you can drop us in at any stage, including rescuing a rollout that has lost momentum.