Separate price from total ownership cost
A proximity marketing budget needs to account for far more than the unit price of beacons or NFC tags. The hardware itself is often the smallest line item over a three-year operational window. The meaningful costs sit in site preparation, calibration, integration, ongoing maintenance and the staff time required to keep the system running reliably.
Separate your budget into distinct phases: a pilot phase, an initial deployment phase and a recurring operations phase. Each has a different cost profile. A pilot might run for four to eight weeks in a single zone, using a small number of devices and a limited content set. The initial deployment scales that across the venue. Operations cover everything from battery replacements to content updates over the system's working life.
Resist the temptation to build a single lump-sum figure. When costs are aggregated, it becomes difficult to see which phase is over or under-resourced, and harder to make informed decisions about scaling or pausing the project. Itemise by phase, then by category within each phase.
Core cost categories
Across all phases, the main categories to budget for are:
- Hardware procurement: beacons, NFC tags, QR code materials, mounting fixtures and any gateway or reader devices required by your chosen architecture.
- Site preparation and installation: physical surveys, access equipment, fixing materials, cabling where needed and the labour to install devices at height or in awkward locations.
- Calibration and testing: the often-underestimated time required to tune transmit power, advertising intervals and zone boundaries in the actual physical environment rather than on paper.
- Software and platform fees: recurring charges for the management platform, content delivery and analytics. (The detailed evaluation of these platforms sits outside this site's scope, but the budget line must be included.)
- Integration work: connecting the proximity system to existing content management workflows, ticketing systems or other operational tools.
- Content creation: writing, designing and formatting the notifications, pages or audio that visitors or customers actually receive.
- Ongoing operations: battery monitoring and replacement, device health checks, inventory management, content updates and periodic recalibration.
- Staff time: the hours your own team spends on project management, testing, sign-off and day-to-day oversight.
Some of these are one-off costs. Others recur monthly or annually. A budget that only accounts for the upfront spend will look deceptively affordable.
Scale, support and risk drivers
The shape of your budget changes significantly depending on the use case. A retail environment with fixed shop fittings has different constraints from a museum with rotating exhibitions, and both differ from a multi-day event where infrastructure is temporary.
Retail environments
In a retail setting, beacons are typically mounted above fixture height, often on ceilings or high walls. Budget for access equipment — scaffolding towers, cherry pickers or at least tall ladders — and for installation to happen outside trading hours. If the store is part of a chain, factor in the cost of replicating the deployment across multiple sites, including travel and coordination time.
NFC tags on product displays or shelves are cheaper per unit but require physical contact from the customer's phone. Budget for replacement tags: in high-traffic areas, adhesive-backed tags can be dislodged or damaged. QR codes printed on shelf edges or point-of-sale materials have a negligible unit cost but require reprinting whenever the target URL changes, unless you use dynamic QR codes that redirect server-side.
Museums and heritage venues
Museum budgets need to accommodate changing exhibitions. If beacons are fixed to gallery walls, budget for the labour to relocate or reconfigure them when an exhibition changes. Some venues use temporary mounting solutions — magnetic brackets, clamp fittings or freestanding plinths — to reduce this cost, but these carry their own price premium over simple screw-fixings.
Content creation costs in museums tend to be higher per trigger point than in retail. A product promotion might need a single paragraph and an image. A museum exhibit might require an audio script, recording, editing and accessibility alternatives. Budget for content production as a separate workstream, not an afterthought.
Events and temporary venues
Event deployments have a compressed timeline and a hard end date. Budget for rapid installation and, critically, rapid removal. Devices hired for the event duration avoid a capital outlay but carry hire fees and the logistical cost of shipping and returns. If purchasing devices for repeated event use, budget for secure storage, pre-event testing and the labour to pack, transport and redeploy each time.
Temporary venues also introduce environmental uncertainty. You may not know the exact wall materials, ceiling height or RF environment until you arrive on site. Build a contingency into the installation and calibration budget — typically an allowance for additional time on site.
Pilot phase budgeting
A well-structured pilot is the most cost-effective way to avoid a much larger mistake. Budget the pilot as a self-contained project with its own objectives, success criteria and review point. Include enough devices to test realistic conditions — a single beacon in an empty room tells you very little. Include the cost of observing real visitor behaviour during the pilot, not just technical logs.
Set a clear decision gate at the end of the pilot: what specific outcomes would trigger a full deployment, and what outcomes would trigger a pause or pivot? This makes the pilot budget easier to justify internally because it is explicitly framed as a learning exercise, not a half-hearted rollout.
Evidence required before scaling
Underestimating calibration time
Calibration cannot be done accurately from a floor plan. RSSI values behave differently in every physical space due to wall materials, racking, stock density and the number of people present. Budget for on-site calibration with the actual devices in the actual environment, and expect to revisit it after the first week of live operation. A common mistake is to assume that a single calibration session is sufficient. In environments where stock levels or furniture layouts change, recalibration becomes a recurring task.
Ignoring battery replacement logistics
Beacon batteries deplete predictably in theory but unevenly in practice. Devices mounted at height, behind fixtures or in secure areas take longer to service than those at arm's reach. Budget not just for the replacement cells but for the access equipment and staff time required to reach every device. If your asset register (covered elsewhere in this cluster) shows that twenty percent of your beacons require a ladder and a second person to swap a battery, that directly affects your maintenance cost.
Forgetting content update cycles
A proximity system that broadcasts the same message for months loses effectiveness. Budget for regular content reviews and updates. In retail, this might align with promotional cycles. In museums, it might align with exhibition changes. In either case, someone needs to write, approve and deploy the updated content. If that responsibility is unclear at the budgeting stage, it often goes undone after launch.
Overlooking integration costs
If your proximity triggers need to pull data from another system — stock levels, ticketing status, loyalty points — budget for the integration work. Even straightforward API connections require development time, testing and error handling. Changes to the upstream system can break the integration, so budget for ongoing maintenance of those connections, not just the initial build.
Not accounting for consent and privacy compliance
Under current UK data protection guidance, location-based marketing requires a lawful basis for processing, typically consent. Building a compliant consent flow — clear opt-in, easy opt-out, transparent privacy information — has a development and content cost. If your budget assumes a simple push notification with no consent layer, you will either face compliance risk or an unplanned development sprint to add one.
Key checks before finalising a budget
- Have you separated pilot, deployment and operations costs rather than aggregating them?
- Does the operations budget cover at least two full battery replacement cycles?
- Have you included calibration time for the actual environment, not just an idealised estimate?
- Is content creation funded as a distinct workstream with a realistic per-trigger cost?
- Does the budget include access equipment and out-of-hours installation where needed?
- Have you confirmed whether integration work is included in platform fees or quoted separately?
- Is there a contingency allowance for site conditions you cannot verify in advance?
- Does the consent and privacy mechanism have a dedicated budget line?
- Have you identified who owns content updates after launch, and is their time funded?
- Is there a clear decision gate at the end of the pilot with defined criteria?
A budget that addresses these points will not prevent every surprise, but it will prevent the most common and most expensive ones. The next step — understanding whether that spend is delivering value — is covered in the neighbouring guide to measuring return on investment.
