Selecting an integrator for a proximity or indoor-navigation deployment is not the same as hiring a general IT contractor. The work sits at the junction of radio physics, physical-space logistics, mobile software and ongoing hardware maintenance. An integrator who understands networking but not RSSI behaviour, or one who can configure a CMS but has never calibrated beacons around moving crowds, will leave you with a system that looks correct on paper and underperforms on the shop floor or gallery.
This guide covers what distinguishes a capable proximity integrator, which credentials actually matter, the questions that reveal practical experience, and how to structure the working relationship so that handover and long-term maintenance do not become problems after the invoice is paid.
What to Look for in a Proximity Integrator
The first filter is direct, verifiable experience with the specific technologies you intend to deploy. A company that has fitted environmental sensors across a warehouse may have no useful expertise in placing beacons for retail zone detection or museum wayfinding. Ask for deployments that match your environment: same technology, similar physical constraints, comparable visitor density.
Physical-space understanding
Proximity systems fail when integrators treat the venue as a blank canvas. A competent firm will start by asking about building materials, ceiling types, footfall patterns, temporary fixtures and how the space changes seasonally or between events. They should be able to explain, without being prompted, how a glass partition, a metal racking unit or a crowd of two hundred people will alter signal behaviour in your specific rooms.
Calibration and measurement rigour
Any integrator proposing fixed accuracy figures before walking the site is either guessing or quoting a manufacturer's laboratory condition. Look for a firm that describes a calibration process: taking RSSI readings at multiple points, adjusting transmit power and advertising interval, and documenting the resulting distance curves for your exact environment. If they do not mention on-site measurement as a standard step, they are not doing proximity work properly.
Battery and maintenance awareness
Hardware that works on day one but becomes unreliable six months later is a common outcome when integrators treat beacons as fit-and-forget. A serious integrator will discuss battery life estimates in the context of your chosen advertising interval and transmit power, explain how they plan to monitor battery status remotely, and outline a replacement schedule. If maintenance only comes up when you ask, treat it as a warning sign.
Privacy and consent grounding
Under UK GDPR and the Privacy and Electronic Communications Regulations, location-based marketing requires a lawful basis, typically consent. An integrator who glosses over consent flows, suggests tracking MAC addresses without a clear legal basis, or cannot explain data minimisation in plain terms is a liability. You do not need a privacy lawyer on the integration team, but you do need someone who understands where the technology stops and legal obligation begins.
Integrator Certifications and Partnerships
Certifications in this field are uneven. Some carry real weight; others are marketing badges that require little more than a registration fee. Understanding the difference helps you avoid paying a premium for irrelevant credentials.
Manufacturer partnerships
Being an authorised reseller or certified partner of a major beacon or infrastructure vendor means the integrator has access to manufacturer training, pre-release firmware information and direct technical support. This matters when you hit an obscure firmware bug or need a custom firmware build. Ask which manufacturers they partner with, at what tier, and how recently they completed the associated training. A partnership badge from three years ago may reflect a relationship that has gone dormant.
Bluetooth SIG membership
Membership of the Bluetooth Special Interest Group does not guarantee deployment skill, but it does indicate that the firm follows the specification closely and receives updates on standard changes. For large-scale deployments, it is a mild positive signal rather than a deciding factor.
General IoT and networking certifications
Qualifications such as CCNA or IoT-focused credentials show baseline networking competence, which is necessary but not sufficient. They confirm the integrator can handle IP infrastructure, VLANs and network security. They do not confirm the integrator understands proximity-specific challenges like trilateration error, multipath interference or the practical limits of zone-based detection.
What to treat with scepticism
Be wary of proprietary "certified integrator" programmes run by small platform vendors. These often exist to create a captive channel rather than to validate competence. Similarly, awards and "top IoT company" lists from unknown publications carry no evidential weight. Ask instead for reference sites you can contact and, where possible, visit.
Questions to Ask Before Hiring an Integrator
The right questions cut past the pitch and expose how the firm actually works. Below is a practical set, grouped by what they reveal.
Experience and relevance
- Can you name three deployments using the same technology in a similar physical environment?
- What went wrong on those projects, and how did you resolve it?
- Have you worked in a venue with our level of visitor density and movement patterns?
Technical approach
- How do you calibrate beacons in a new environment, and what measurements do you record?
- How do you account for signal attenuation from walls, fixtures and crowds?
- What advertising interval and transmit power do you recommend for our use case, and why?
- How do you handle interference from other Bluetooth devices and Wi-Fi access points on the 2.4 GHz band?
Hardware and maintenance
- How do you estimate battery life for our configuration, and what margin do you build in?
- How will we monitor beacon health and battery status after deployment?
- What is your process for replacing failed or low-battery units?
- Do you maintain an asset register, and in what format is it handed over?
Privacy and compliance
- How does your recommended architecture support consent collection and withdrawal?
- What location data is stored, where, and for how long?
- Can you explain how data minimisation is applied in your default configuration?
Handover and support
- What documentation do you provide at project completion?
- How long is the support period, what does it cover, and what happens afterwards?
- Can our own facilities team replace batteries and reassign beacons using your documentation alone?
How the integrator answers matters as much as the content. Vague assurances, deflection to "our platform handles that" or an inability to describe a specific calibration walk-through suggest limited hands-on experience.
Managing the Integrator Relationship
The deployment is only part of the engagement. How you structure the working relationship determines whether the system remains reliable and whether your own team can take over day-to-day operations.
Define roles and boundaries early
Agree in writing which tasks the integrator owns and which fall to your team. Typical boundaries include: the integrator handles site survey, beacon provisioning, calibration, initial installation and documentation; your facilities or operations team handles routine battery replacement, beacon relocation and basic troubleshooting. If the integrator expects to be called for every battery swap, your ongoing costs will be higher than necessary.
Insist on usable documentation
Documentation that lives only in the integrator's project-management system is not documentation you control. Require a handover package that includes: a beacon asset register with hardware IDs, assigned locations and firmware versions; a placement map showing where each unit is mounted; calibration records with RSSI readings; and a maintenance runbook that a non-specialist can follow. Review a sample of their documentation from a previous project before signing.
Build in verification points
Do not wait until the final walkthrough to discover problems. Agree on intermediate verification milestones: after the site survey, after a small-scale calibration test, and after a partial rollout. At each stage, your team should physically walk the space with a test device and confirm that zones trigger correctly, notifications arrive at the right time, and dead spots are identified before they affect visitors.
Plan for the end of the contract
If the integrator provides a managed platform or a cloud service, understand what happens if you switch providers or bring the system in-house. Ask about data export formats, API access for beacon management, and whether the beacons themselves are locked to a single platform. Proprietary lock-in is not necessarily a deal-breaker, but you should enter it with open eyes and a documented exit path.
Schedule a post-deployment review
Set a review date three to six months after go-live. By then, battery drain patterns, seasonal footfall changes and any calibration drift will have emerged. Use the review to adjust placement, refine zone boundaries and confirm that the maintenance process your team is following matches what the integrator intended. This is also the point at which you can realistically assess whether the integrator's support terms still serve your needs or whether internal capability has caught up.
How to verify certifications and partner badges
A partner badge may show that an organisation has a commercial relationship or has completed a vendor programme; it does not prove that the proposed team has delivered the same architecture in a comparable venue. Verify the badge with the issuing organisation, ask which named staff hold the relevant competence, and request evidence for the exact hardware, software and integration scope.
For Bluetooth products, distinguish an integrator’s membership or partnership status from the qualification status of the product being supplied. Search the Bluetooth Qualified Product database and confirm the listed design and model rather than relying on a logo in a proposal.
