Programme rescue — when RTLS, RFID or IoT isn't delivering.
Most failed enterprise RTLS, RFID and IoT deployments aren't failures of technology — they're failures of scope, vendor selection, integration architecture or success criteria.
Programme rescue is our flagship engagement for clients with a deployment that's stalled, over-budget, under-performing or politically toxic.
Independent diagnosis, root-cause analysis, recovery plan, and (where required) vendor renegotiation and re-delivery. We've rescued deployments at every scale.
When programme rescue is the right engagement
Typical signals: the pilot delivered against vendor metrics but didn't move any business KPI; production rollout has stalled or fragmented across sites; vendor and integrator are pointing fingers at each other;
capex is committed but ROI hasn't materialised; the executive sponsor is losing patience; an audit or steering committee has flagged the programme as red.
If any of these match, programme rescue is the engagement. We have run rescues on UWB, BLE-AoA, RFID, AGV/AMR and hybrid stacks in manufacturing, healthcare, logistics, defence and retail.
The diagnostic — what we look for in week 1
We start with a structured diagnostic across six dimensions. Scope and success criteria: what was the deployment supposed to deliver, and was it ever quantified? Most stalled programmes never had measurable success criteria.
Technology fit: was the chosen radio appropriate for the environment and use case? RF site survey at production load tells us in days. Vendor and integrator performance: independent review of vendor and integrator delivery vs contract; the asymmetric-information traps.
Integration architecture: does the data flow into the systems that drive the business outcome? Most underperforming programmes have broken or absent integration.
Operational fit: do the people on the shop floor or in the ward use the system? Adoption issues are usually scope issues in disguise. Commercial position: what are the contractual options for renegotiation or termination?
Root-cause analysis — the five patterns we see
Five failure modes account for the vast majority of stalled deployments. Scope misalignment: the deployment was scoped against a technology rather than a business outcome — "we want UWB" instead of "we want a 12% reduction in WIP delay".
Wrong radio: vendor sold a technology that doesn't fit the environment (UWB in dense metal without sufficient anchor density; BLE-AoA in heavy multipath; RFID at unstable read accuracy).
Integration gap: data is captured but doesn't flow to WMS/MES/EMR — events don't drive any operational change. Vendor lock-in pricing: year-2 commercial terms make scale-out uneconomic; client is held hostage to extension capex.
Adoption failure: front-line operators don't use the system because workflow change wasn't designed; system reports look right, KPIs don't move. We diagnose which pattern (or combination) applies in week 1.
The recovery plan — built in weeks 2–3
The recovery plan is concrete and time-boxed. Scope correction: redefine success criteria as measurable business KPIs (not technology metrics), with executive sponsor sign-off.
Technical remediation: targeted changes — adding anchors, switching radio in specific zones, fixing integration, swapping tags.
Vendor and integrator action: renegotiate scope, commercials and SLAs based on root-cause findings; in rare cases, recommend replacement. Operational change: workflow design, change management, training for adoption.
Re-baseline: new milestones, new acceptance criteria, new ROI model. The plan is delivered to the executive sponsor and steering committee as a single document with a transparent assumptions log.
Vendor renegotiation — independent and credible
Programme rescue often involves renegotiating with the incumbent vendor or integrator. Our independence (no commissions, no kickbacks — see /about/independence) gives us credibility on both sides.
We've renegotiated commercial terms, scope, SLAs and milestone structures with major RTLS, RFID and AGV/AMR vendors.
Where the relationship is unrecoverable, we recommend vendor replacement and run a structured re-procurement using /templates/rfp-template and /templates/vendor-matrix.
Re-delivery — phase 3 of /method, adapted
Once the recovery plan is signed off, re-delivery follows phase 3 of /method (Production rollout) with two adaptations. Tighter gates: we add additional acceptance gates between the previous failure point and full rollout — usually three to five additional gate reviews.
Independent validation: we validate each gate independently rather than relying on vendor self-reporting. Phased expansion: rollout extends to additional sites only after the rescued site demonstrates business KPI delivery for an agreed period (typically a quarter).
How long, and how much
Diagnostic: 2–3 weeks. Recovery planning: 2–3 weeks. Vendor renegotiation: 4–8 weeks depending on commercial complexity. Re-delivery: 12–36 weeks depending on scope. Total: 5–13 months end-to-end for the typical mid-scale rescue.
Commercials: fixed-fee for diagnosis and planning; time-and-materials or success-based for execution. Most clients recover 5–10× the programme-rescue fee in remediated capex and accelerated ROI.
Why hire us rather than the incumbent vendor
Three reasons. Independence: we're not the vendor that built the problem, so we have no incentive to hide root causes.
We earn fees from clients only — see /about/independence. Pattern recognition: we've seen the same failure modes dozens of times across vendors, industries and geographies.
We diagnose in days what would take a vendor or internal team months. Credibility on both sides: vendors and integrators take us seriously because we're rigorous and fair. Renegotiation goes faster and produces better commercial outcomes.
Frequently asked questions
Will you blame the vendor we already chose?
Not by default. We diagnose root causes objectively, and they often include client-side scope, integration and adoption decisions as well as vendor performance.
Where the vendor is genuinely at fault, we're direct about it — but the most common finding is a mix of issues across the engagement.
Do you take fees from the incumbent vendor for the rescue?
Never. We earn fees from clients only. The incumbent vendor pays nothing to us in any direction. See /about/independence.
What if we want to replace the incumbent vendor?
We run a structured re-procurement using /templates/rfp-template and /templates/vendor-matrix. Most rescues don't end in replacement — but when they do, we manage the transition rigorously.
Can you start with a 1-week diagnostic before committing?
Yes — many engagements start with a paid 1-week diagnostic that produces a brief root-cause report and a recommendation on whether full rescue is needed. Clients then decide whether to proceed.
How do we engage you if our incumbent vendor is in the room?
Politely and transparently. We tell the vendor up front that we're an independent advisor and that we'll be diagnosing root causes objectively. Most vendors prefer this to ambiguity. The rare cases where vendors won't co-operate become input to the recovery plan.
What's the success rate?
We've never had a rescue end in unrecoverable failure post-diagnosis. Most rescued programmes go on to deliver against their original (or revised) ROI within 12–18 months.
We're selective about which engagements we take — we don't accept rescues where the technology fundamentally can't deliver the use case (in those rare cases, we recommend abandoning, which is also a successful diagnosis).
Last updated: