Independent RTLS consultant — choose, design and deploy without a reseller margin.
An independent RTLS consultant scores technology and vendors against your constraints, designs the architecture into your systems of record, and stays accountable through go-live — without selling hardware or a platform.
What an RTLS consultant does
A good RTLS consultant owns the hard parts of a location programme: validating the use case and the accuracy you genuinely need, choosing the right radio for the physics,
designing an architecture that scales, integrating it cleanly into your WMS, ERP, EMR or MES, and governing the rollout so it ships.
The job is as much about saying “you don’t need that” as recommending what you do — stopping you over-specifying precision or buying infrastructure you’ll never use.
Why independence matters
Most “advice” in this market comes from companies that also sell the hardware or the platform. That is not advice; it is sales.
An independent consultant takes no reseller margin and has no platform to defend, so the recommendation is driven only by your use case, budget and risk.
When to bring one in
- Before an RFP — to write requirements that get comparable, honest vendor bids
- When a pilot stalled or missed its accuracy target and you need a diagnosis
- Before a multi-site rollout, so a single-site success actually scales
- When the board wants a defensible business case and payback, not a vendor deck
What you get from a TRACIO engagement
- A clear recommendation: the right technology, architecture and integration plan
- A gate-governed delivery plan so spend stays tied to evidence
- Vendor-neutral selection with no reseller margin
- Plain-English deliverables your whole buying group can act on
Independent RTLS consulting: architecture before anchors
An RTLS consultant exists to stop locating programmes from starting with a preferred radio and reverse-engineering a use case. The valuable sequence is: operational KPI → locating question → accuracy/update needs → RF and integration architecture → vendor-neutral shortlist → production-load pilot. Anything that skips to a demo map with moving dots is theatre.
What a serious engagement covers. Use-case and KPI framing; technology shortlist (UWB, BLE AoA, Passive RFID, hybrid, occasionally Wi-Fi or GNSS outdoors); RF survey oversight; anchor/locator density challenge; integration patterns to MES/WMS/EMR/CMMS; cybersecurity and OT segmentation notes; pilot success criteria; TCO and rollout phasing. Deliverables should be readable by operations, finance and IT — not only by RF engineers.
Why independence changes the outcome. Resellers optimise for attach rate of their anchors and software seats. Independent advisors optimise for the sparsest stack that still hits the locating KPI. That often means hybrid designs, lower density, or even deciding RTLS is the wrong buy this year compared with Passive RFID portals or process redesign.
When to bring a consultant in. Before RFP; when two vendors disagree on density by 30%+; when a pilot stalled; when IT/OT cannot agree on data ownership; or when the board asks for a risk-adjusted business case. Waiting until after contracts are signed turns consulting into remediation.
How to buy the advice. Time-box discovery; insist on written assumptions and accuracy bands under production load; require a vendor-neutral scoring matrix; and keep the consultant out of hardware margin. Ask them to state what they would not deploy on your site — the refusal list is as informative as the recommendation.
Engagement models and red flags when hiring RTLS advice
Common engagement shapes: fixed-fee discovery and architecture; vendor-neutral selection support; pilot design and assurance; programme rescue; and install PMO without hardware margin. Pick the smallest shape that unblocks the next decision. Avoid open-ended retainers that never produce a tenderable specification.
Red flags: refusal to put accuracy percentiles in writing; density recommendations without a survey; insistence on a single radio for every zone; integration marked “phase 2”; and any fee tied to hardware volume. Green flags: a clear “do not deploy” list, hybrid architectures, and comfort facilitating disagreement between operations, IT and finance.
Ask for anonymised examples of density reductions, pilot gates, and recoveries. You are buying judgment under uncertainty — evidence of that judgment is fair diligence.
How TRACIO-style independence shows up in weekly work
Weekly cadence on a healthy advisory: clarify KPI and locating question; challenge density and radio fit; document decisions; prepare vendor questions; and keep finance/IT/operations aligned on the same accuracy definition. The advisor should be willing to recommend “do nothing this quarter” or “Passive RFID only” when continuous RTLS will not pay back. That willingness is the practical meaning of vendor-neutral locating advice.
Independence test in one question
Ask any RTLS advisor: “Where on our site would you refuse UWB and specify BLE or Passive RFID instead?” Competent independent consultants answer with zone maps and KPI thresholds. If every zone somehow needs their densest radio, keep looking.
Field note
Bring the consultant in before the RFP freezes architecture — after award they can only remediate.
Frequently asked questions
What does an RTLS consultant cost?
It depends on scope. A fixed-fee discovery sprint typically starts in the low thousands of euros; vendor selection and pilot design are larger; full programme delivery is scoped per project. Indicative ranges are on our How we work & fees page.
Do you resell hardware or take vendor commissions?
No. TRACIO is independent. We take no reseller margin and no vendor commissions, so the recommendation is driven only by what fits your use case.
Which technologies do you cover?
UWB, BLE, Passive RFID/UHF RFID, active RFID, GPS/GNSS, LoRa/LPWAN and SLAM — chosen by use case, often combined into a hybrid stack.
How quickly can we get to value?
Most clients start with a discovery sprint in weeks and run a pilot before committing to a larger rollout.
Last updated: