Budget boundaries and commercial assumptions
When budgeting for a proximity system, the hardware — beacons, NFC tags, QR code print runs — tends to dominate early conversations. The software layer, however, usually accounts for the larger share of long-term spend. Understanding what that layer actually contains, and how it is priced, prevents the most common budgeting errors in proximity deployments.
Three distinct software components typically sit behind a beacon, NFC or indoor navigation installation:
- Device management platform. The interface where you register beacons, adjust broadcast settings, monitor battery levels and organise your hardware inventory. Some manufacturers bundle this at no extra charge; others treat it as a paid tier.
- Campaign or content management system (CMS). The tool used to define what happens when a device enters a zone or taps a tag: which notification fires, which web page loads, which audio track plays. In retail this might be offer management; in museums, exhibit-linked content scheduling.
- Analytics module. The reporting layer that aggregates zone entries, dwell times, path data and notification engagement. The depth of this module varies enormously between providers.
These three functions may be delivered by a single platform or assembled from separate products. A museum, for instance, might use one vendor's beacon management console, a separate CMS for exhibit content and a third-party analytics tool that ingests exported data. Each junction introduces a licensing decision.
Pricing Models You Will Encounter
Proximity software is not typically sold with a simple one-off licence. The most common structures include:
- Per-beacon or per-device licensing. A recurring charge tied to the number of registered beacons or active NFC zones. Straightforward to predict at small scale, but it penalises dense deployments where a large number of beacons serve a single floorplan.
- Per-venue or per-site licensing. A flat fee per physical location, often with tiers based on floor area or number of zones. Common in multi-site retail and venue chains.
- Monthly active user (MAU) or interaction-based pricing. Charges tied to the number of unique devices detected or notifications delivered. This model aligns cost with usage but becomes difficult to forecast in footfall-sensitive environments such as event venues.
- Tiered feature gating. A base platform fee with analytics, API access or multi-venue support locked behind higher tiers. The headline price may look manageable until you discover that the reporting you actually need sits two tiers up.
No single model is universally better. The right choice depends on whether your cost driver is hardware count, visitor volume or the number of physical sites. A single museum with two hundred beacons and modest footfall faces a different optimisation problem to a retailer with twenty stores, thirty beacons each and high daily traffic.
Scale, support and risk drivers
Retail: Campaign CMS and Frequency Controls
In a retail proximity deployment, the CMS carries significant functional weight. Store managers need to schedule offers by time of day, restrict notification frequency per visitor and retire campaigns when stock runs out. If the CMS cannot enforce frequency caps or quiet hours natively, you either accept notification fatigue risks or build custom logic elsewhere.
When evaluating retail CMS costs, check specifically whether the following are included in the standard tier or require an upgrade: per-zone scheduling, A/B testing of notification copy, expiry rules tied to campaign dates and role-based access so regional managers can control their own stores without seeing the entire estate.
Museums and Galleries: Content Versioning and Language Support
Museum deployments often involve a relatively high content-to-zone ratio. A single exhibit may need audio in multiple languages, descriptive text, accessibility alternatives and child-friendly versions. The CMS cost question here is less about volume and more about versioning capability and workflow: can curators draft and approve content before it goes live, or does every change require a developer?
Analytics for museums tend to focus on dwell time per exhibit, popular routes and revisit patterns. Verify whether the analytics module treats dwell time as a standard metric or an add-on, and whether path visualisation is available without exporting to a separate business-intelligence tool.
Events: Temporary Licensing and Peak Pricing
Event organisers face a distinct cost structure. The deployment lifespan may be three days, but the software must handle sudden, concentrated load. Some providers offer short-term licences or event-specific packages; others apply standard MAU pricing that can become disproportionate when a three-day conference generates tens of thousands of interactions in a compressed window.
Clarify before contracting whether the platform imposes interaction caps, whether overage charges apply and whether the analytics data remains accessible after the event licence ends. Losing access to post-event reporting because a short-term licence has expired is a recurring problem.
Data Export and Integration Costs
The analytics module is only useful if its output reaches the people who need it. Some platforms include CSV or API export in all tiers; others restrict API access to enterprise plans or charge per data pull. If your operations team relies on pulling location data into an existing dashboard, confirm the export mechanism and any associated costs early. The integration work itself sits outside this article's scope, but the licensing terms that enable or block it are a direct software cost.
Approval evidence and contingency
Mistaking Device Management for Analytics
Many beacon manufacturers provide a free management console that shows which devices are online and their battery levels. This is not an analytics platform. It tells you nothing about visitor behaviour, zone traffic or campaign performance. Assuming the included console covers your reporting needs is one of the most frequent budgeting errors, particularly in first deployments.
Underestimating MAU Sensitivity
If your pricing model ties to active users or interactions, small changes in footfall can produce large cost swings. A venue that typically sees 5,000 monthly visitors but hosts a one-off event drawing 30,000 could face a sudden bill increase. Ask the provider whether MAU tiers are calculated on a rolling monthly basis, whether there is a smoothing mechanism and what happens during predictable spikes.
Ignoring Data Retention Costs
Storing raw location data over months or years has a cost that is not always visible in the headline price. Some platforms limit data retention to thirty or ninety days on standard tiers, charging extra for longer histories. If you need to compare footfall patterns across seasons or satisfy audit requirements, check the retention period and the cost of extending it before committing.
Vendor Lock-In Through Proprietary Formats
If the CMS stores all campaign content and the analytics module keeps all historical data in proprietary formats with no export path, switching providers later means rebuilding from scratch. When reviewing software costs, factor in not just what you pay but what you can take with you. Standard data export formats and documented APIs reduce future transition costs even if they carry a premium at the point of purchase.
Key Questions for a Software Provider
- Which of the three components — device management, CMS, analytics — are included in the quoted price, and which are separate?
- What pricing model applies, and what is the most likely cost driver for a deployment of your scale?
- Are there interaction caps, MAU thresholds or data-retention limits on the proposed tier?
- Can you export campaign content and analytics data in standard formats without an additional fee?
- What happens to historical data if you downgrade or do not renew?
- Is multi-venue or multi-site management included, or does each location require a separate licence?
- Are role-based access controls and approval workflows available for content editors?
Software, CMS and analytics costs are rarely the line item that sinks a proximity project on their own. They are, however, the costs most likely to grow quietly after launch — through tier upgrades triggered by usage, retention extensions demanded by compliance, or integration charges that only become visible when the operations team asks for data the base platform will not release. Scrutinising the licensing structure at procurement stage, rather than after the beacons are already on the wall, is the practical safeguard.
