What genuinely differs between the choices
When deploying proximity technology—whether that involves mounting Bluetooth beacons, applying NFC tags to exhibits, or commissioning an indoor navigation system—the decision over who physically handles the work separates into two broad paths. Building internal capability means your own operations, facilities or IT staff manage the hardware deployment, calibration and ongoing maintenance. Using an integrator means contracting a specialist firm to handle the site survey, installation, signal tuning and sometimes the long-term monitoring.
This decision is fundamentally about the physical layer: mounting hardware, measuring radio frequency behaviour in your specific building, and maintaining an accurate asset register. It is not about building the mobile application or the content management system, which sit outside this physical infrastructure boundary.
The two approaches are not mutually exclusive. Many deployments use an integrator for the initial RF survey and commissioning, then hand day-to-day hardware management to an internal team. The practical question is where the boundary between those two responsibilities should sit for your specific site, and what risks arise if that boundary is drawn in the wrong place.
Capability, friction and operational burden
When internal capability is the practical choice
For environments with a small hardware footprint and predictable physical layouts, internal teams can often manage deployments effectively. A single-site museum replacing static labels with dynamic QR codes and NFC tags on exhibit plinths, for example, requires minimal RF expertise. The task is largely logistical: printing tags, recording their IDs in a spreadsheet or asset system, and physically affixing them at the correct height and orientation.
Small retail units with a handful of entrance-point beacons also fall into this category if the required accuracy is low—simply detecting that a device has entered the shop, rather than pinpointing its position to a specific bay. In these scenarios, the calibration demands are minimal, and the cost of bringing in an external specialist is rarely justified.
When an integrator is the practical choice
Larger or more complex environments usually demand an integrator. Multi-site retail rollouts, large exhibition halls, and venues requiring precise indoor navigation all involve variables that are difficult to manage without dedicated RF surveying equipment and experience.
Older buildings with thick stone walls, metal-framed partitions, or heavy footfall create significant Bluetooth signal interference. An integrator will conduct an on-site RF survey before any hardware is mounted, identifying dead zones and planning beacon density and transmit power to compensate for attenuation. Without this survey, an internal team risks deploying hardware that either fails to trigger or creates overlapping zones that confuse the positioning engine.
Temporary event spaces also benefit from integrator support. The infrastructure must be installed, calibrated, tested under peak load conditions, and then removed within a tight window. An experienced integrator will have workflows designed for this tempo, whereas an internal team may struggle to balance the deployment with their normal duties.
The hybrid model
The most common arrangement for medium-to-large deployments is a split responsibility. The integrator designs the placement plan, conducts the baseline RSSI measurements, commissions the system, and documents the exact mounting locations and configuration parameters. The internal team then takes ownership of routine tasks: swapping batteries, replacing damaged NFC tags, updating QR code destinations, and keeping the asset register current. This model works well provided the handover is treated as a formal process, not an afterthought.
Fallbacks, lock-in and pilot evidence
Assuming IT networking skills translate directly to BLE deployment
A common mistake is assigning beacon deployment to the IT team on the assumption that managing Wi-Fi access points equates to managing Bluetooth beacons. While there is overlap in understanding radio frequencies, BLE behaves differently. Wi-Fi access points are typically fixed, powered devices with strong signals designed for high bandwidth. Beacons are low-power, battery-constrained devices broadcasting simple packets, and their signal strength (RSSI) fluctuates significantly based on minor environmental changes—such as the number of people standing in a corridor. Internal teams need time to understand these physical nuances before being left to calibrate a system alone.
Accepting a deployment without documented calibration data
If you use an integrator, a key check is whether they provide documented evidence of the calibration process. This should include RSSI readings taken at multiple points within each zone, notes on identified interference sources, and the rationale for the chosen transmit power and advertising interval settings. An integrator that simply mounts the hardware, checks that a phone receives a signal, and leaves is not commissioning the system; they are just installing it. Without baseline data, your internal team will have no reference point when troubleshooting signal drift later.
Failing to secure ownership of the asset register
Who holds the master list of beacon IDs, NFC tag serials, their physical locations, and their configuration parameters? If this data lives only in the integrator’s portal or project files, you have a dependency problem. Before a project is signed off, ensure the asset register—including firmware versions, battery types, and expected replacement intervals—is handed over in a format your operations team can actually use and maintain.
Underestimating ongoing physical maintenance
Whether you build internal capability or use an integrator, the hardware requires physical upkeep. Beacons are sometimes removed by cleaners, dislodged by equipment, or vandalised. NFC tags peel off or scratch. QR codes become defaced. The decision about internal versus external capability must account for who walks the floor to inspect mounts, who monitors battery telemetry, and who procures replacement units. An integrator can design a robust system, but they are rarely on-site often enough to notice a beacon that has been rotated ninety degrees by a passing forklift—something that can entirely alter its detection zone.
Key questions to resolve before deciding
- Does the deployment require a measured RF survey, or is approximate zone detection sufficient?
- Do we have staff available to walk the site at regular intervals for physical hardware checks?
- If an integrator commissions the system, what specific documentation and data do we require at handover?
- Who is responsible for updating the indoor map or zone definitions when the physical layout changes?
- What is the realistic cost in staff time of managing battery replacements and inventory internally, compared to a service contract?
Answering these questions against the specific characteristics of your venue—its construction materials, visitor density, and rate of physical layout changes—will point clearly toward the right balance of internal capability and external expertise.
