Hire the partner type before you hire the radio.
The market mixes independent advisors, systems integrators, vendor professional services, and Location-as-a-Service. They all say “vendor-agnostic.” Only some of them can still say no to a hardware order.
Four partner types buyers actually meet.
Independent locating advisor — paid only by you. No hardware SKU, no twin platform to defend, no reseller margin. Output is requirements, shortlist, architecture, RFP scoreability, gates, and (when asked) delivery oversight or rescue. TRACIO sits here.
RTLS / digital-twin systems integrator (SI) — designs and deploys. Often claims vendor-agnostic evaluation, then implements UWB/BLE/vision stacks, integrations, and managed care. Useful when you already know you need a builder. Incentive still skews toward a billable deployment. Public examples in this category package consulting + implementation + managed tiers and digital-twin simulation as one journey.
Vendor professional services — the OEM’s own PS or a certified partner. Deep on one stack; quiet on where that stack is the wrong physics. Fine after a neutral shortlist; risky as your first advisor.
Location-as-a-Service (LaaS) — bundled hardware, software, install, and run in a subscription. Predictable opex; weaker exit and weaker “you own the architecture” story. Fit when you want a utility, not a programme you can retender.
What “vendor-agnostic” hides.
SI sites and OEM blogs now all use the phrase. The test is economic, not rhetorical:
Who gets paid if UWB loses to portal RFID? If the answer is “we still install something,” you have a builder. If the answer is “we still get paid for being right,” you have an advisor.
Do they publish named logos as proof? Deploy SIs often do. Independent advisors under NDA usually cannot — and should not fake it.
Is digital twin the product? Many SI portfolios lead with twin + simulation. That can be right. It can also pull you into a platform before the locating KPI is proven. Advisors sequence twin after the system of record and the radio fit are honest.
Managed care — whose SLA? SI managed tiers monitor anchors, tags, accuracy drift, and integrations (Essential / Professional / Enterprise patterns are now common). LaaS bundles the same under one vendor. Independent managed care holds your vendors to their SLAs and keeps credentials, maps, and exit packs yours.
Competitive landscape (advisory view).
Deploy SIs with consulting fronts — multi-office RTLS + digital-twin integrators that sell discovery, technology selection, vendor evaluation, implementation, and managed services as one funnel. Strong when you need hands on tools. Weak when you need someone who can kill a deployment.
Regional turnkey locators — European and APAC specialists (often Sewio/Quuppa/partner-led) who select among a shortlist of radios and deliver turnkey. Fast in their geography; less natural as a global, procurement-grade shortlist owner.
Silicon-to-WMS UWB boutiques — deep UWB engineering (sometimes Qorvo-partnered) that owns ranging through integration. Excellent when centimetre UWB is already the decision; not a substitute for a multi-radio business case.
OEM LaaS — hardware + run subscription. Simplifies contracting; concentrates lock-in.
Big-4 / generalist SI IoT practices — programme governance without locating physics depth. Pair them with a locating advisor, or expect the radio choice to arrive pre-decided by a preferred OEM.
When to hire which.
Start with an independent advisor when the RFP is unscoreable, two vendors disagree on physics, a pilot stalled, procurement needs TCO that survives audit, or you must keep exit rights. See also independent RTLS consultant and consulting.
Hire an SI to build after the shortlist and architecture are frozen — or hire the advisor to oversee the SI without taking reseller margin.
Use vendor PS for stack-specific commissioning once the stack is chosen.
Consider LaaS when you want opex simplicity and accept thinner architectural ownership.
Managed care — once locating is production-critical, budget proactive drift control. Prefer a model that monitors business KPIs (muster time, miss-reads, search minutes), not only gateway uptime. TRACIO managed services are built that way.
Questions that expose the incentive.
- If portal RFID beats UWB on this dock, do you still earn deployment margin?
- Will you sign that you take no reseller commission on the shortlist you write?
- Who owns maps, configs, and tag databases if we change SI in year three?
- Is the pilot designed to win a PO — or to fail closed on edge cases?
- Does “managed” mean you hold our vendors to SLA, or that you become the single throat?