Pricing

How SmartX HUB Pricing Works

We do not publish a price list, and it is worth explaining why rather than leaving you to assume the worst. SmartX HUB pricing is scoped per deployment because the same platform serves a two-hundred-asset pilot in one building and a fifty-thousand-asset rollout across a dozen sites. Any single published figure would be wrong for almost everyone reading it, and misleading for the rest.

What we can do is show you exactly which variables move the number, and the three commercial shapes most projects take. Read this page and you should be able to estimate your own order of magnitude before you ever speak to us.

Eight variables, all explained Three commercial models Cloud or on-premise
What Moves the Number

Eight Variables Behind Every Quote

These are the questions we work through with you, and they are also the questions to work through internally before asking any vendor what an RTLS or asset tracking system costs. Two of them — technology and site count — typically account for most of the variation between one project and another.

1. Number of sites

Each physical location needs its own site survey, its own infrastructure and its own commissioning. Software scales cleanly across sites; the field work does not. This is why two sites rarely cost twice one site, and why ten sites cost considerably less per site than the first one did.

2. Assets and people tracked

The tagged population drives tag volume directly and platform tier indirectly. Worth separating early: assets that only need zone-level presence are far cheaper to cover than the handful that genuinely require sub-metre accuracy. Most projects overspend by applying one accuracy standard to everything.

3. Modules in scope

You license the capability families you actually use, not the whole catalogue. Tracking, maintenance, supply chain execution, sensors and worker safety are scoped separately, and because they share one record you can add a family later without a migration. See the full feature list.

4. Location technology

The single largest lever. Passive RFID at chokepoints, beacons for zone presence, and UWB or Bluetooth AoA for precision sit at very different points on the cost curve, mostly because of anchor density. Compare technologies before fixing a budget.

5. Hardware and infrastructure

Tags, readers, anchors, gateways, mobile devices, and the unglamorous items that catch budgets out: cabling, power, network drops and mounting in areas that were never designed for it. Identification is built on open GS1 EPC standards, so tags and readers can be sourced competitively rather than only from us.

6. Integrations

Connecting to an ERP, WMS, TMS or industrial control system is effort on both sides of the wire. The platform exposes a documented REST surface and outbound webhooks, so the cost usually sits in mapping your fields and in the availability of your own systems team rather than in building connectors.

7. Cloud or on-premise

This shifts cost between categories rather than simply raising or lowering it. Cloud is predominantly subscription; on-premise moves spend into your own servers, your own operations effort and a different licence shape. Choose it for data residency, latency or policy — not to save money, because it usually does not.

8. Implementation and support

Site survey, configuration, tagging, integration, training and the support model afterwards. Tagging is the item most often underestimated, because someone has to physically attach and register every tag — and on a large fleet that is a project in itself, not an afternoon.

The honest summary

Software is the predictable part of the budget. Accuracy requirements and site count are what actually decide whether a project is modest or major, because both drive infrastructure and field labour. If a number matters more than a feature, start the conversation from the accuracy each process genuinely needs rather than from the accuracy that demonstrates best.

Commercial Models

Three Shapes a Project Usually Takes

These are stages rather than packages. Almost every enterprise rollout we run started life as a pilot, and the pilot exists to replace assumptions with measurements before anyone commits real money. Nothing is thrown away moving from one to the next — the configuration, the tags and the integrations carry forward.

Stage one

Pilot / Proof of Concept

One area, one asset class, one question you cannot answer today. Time-boxed, with a defined success measure agreed before it starts.

Typically includes
  • Limited tag population and a single zone or chokepoint
  • Baseline measurement before and after
  • Tag survival tested in your real process
  • No integration work unless it is the thing being proven
You leave with

Measured figures for the variables in the section above, which is what makes the next quote accurate instead of defensive.

Stage two

Site Deployment

One facility running in production, with the processes it actually depends on. This is where the system stops being a trial and starts being infrastructure.

Typically includes
  • Full site survey and coverage validation before go-live
  • Complete tagging of the asset or worker population in scope
  • Roles, rules, dashboards and notification routing configured
  • First integration, usually to the enterprise resource planner
You leave with

A working reference site and a repeatable template, which is what makes site three cheaper than site two.

Stage three

Enterprise Rollout

Multiple sites on one platform, governed centrally, with local variation handled by configuration rather than by separate installations.

Typically includes
  • Phased site schedule with a standard deployment template
  • Central governance with multi-tenant or multi-site isolation
  • Single sign-on, enterprise security review and audit retention
  • Deployment model chosen per policy: cloud, private cloud or on-premise
You leave with

Comparable numbers across every site, which is the point most groups discover they were missing all along.

What we need in order to quote

Bring what you have. If some of it is a guess, say so — a labelled guess is genuinely more useful than a confident number nobody checked, because it tells us where to put the pilot.

Sites in scope, and roughly the floor area of each
How many assets or people, split by how precisely each group must be located
The processes you want to change, in order of pain
Systems it has to talk to, and who owns them internally
Any constraint on where data may be stored
The environment itself: wash-down, freezing, metal, dust, outdoor exposure

If you would rather build the business case before contacting anyone, the RFID ROI calculator, the CMMS ROI calculator and the returnable packaging ROI calculator all run in your browser with no form to fill in. They will give you the benefit side; this page gives you the cost side.

Tell Us the Scope and We Will Tell You the Number

No obligation, and no discovery call required before you get a figure. If a pilot is the sensible first step, we will say so rather than quoting a rollout you are not ready to run.

FAQ

SmartX HUB Pricing — Common Questions

The questions procurement and project sponsors ask before a first conversation, answered as directly as a scoped model allows.

Why not simply publish prices?
Because the honest answer varies by more than an order of magnitude across the projects we run, and a published figure would mislead most readers in one direction or the other. A single-building pilot and a multi-site rollout share the same software and almost nothing else. What we can commit to is transparency about the drivers, which is what the rest of this page is for, and a quote that separates software, hardware and services so you can see what you are actually paying for.
What drives cost the most?
Accuracy, then site count. Every step up in precision means more infrastructure per square metre, and infrastructure carries both hardware and installation labour. The most effective cost decision available to you is deciding, honestly, which processes need precision and which only need to know the asset is in the right area. Applying the strictest requirement to the entire population is the most common way a budget doubles for no operational gain. Compare technologies sets out the trade-offs.
Is it priced per user?
The licence is scoped around deployment — sites, tracked population and the module families in use — rather than around seat count. The reasoning is practical: a system that charges per login discourages exactly the people who should be using it, and safety information that only supervisors can open is worth less than safety information everyone on the floor can see. Confirm the exact shape in your quote, since scope varies.
Do we have to buy hardware from you?
No. The platform is hardware agnostic, and identification runs on open GS1 EPC standards rather than a proprietary format, so tags and readers can be tendered competitively. Many customers buy hardware through us for the simplicity of one supplier and one point of accountability, and others source it themselves. Either is fine; what matters is that the choice stays yours after the contract is signed, not only before.
Does on-premise cost less than cloud?
Usually not, and it is better to choose it for the right reason. On-premise moves spend out of subscription and into your own servers, storage, backup and the internal time to run them, which frequently lands in the same place or higher once staffing is counted honestly. The good reasons to deploy on site are data residency, network latency and security policy — all legitimate, and all supported. Cost savings are rarely among them.
What gets underestimated most often?
Three things, consistently. Tagging, because someone has to physically attach and register every tag and on a large population that is a project with its own plan. Data preparation, because an asset register that has drifted for years has to be cleaned before it can drive anything. And internal time — the systems owner, the safety lead and the operations manager all need hours in the diary, and projects stall on that far more often than on technology. Budget for all three explicitly.
Can we add modules later without starting again?
Yes, and this is one of the practical arguments for a single platform. Because tracking, maintenance, supply chain, sensors and worker safety all resolve to the same record, adding a capability family is a licensing and configuration exercise rather than a new integration project. The tags, the infrastructure and the identities already in place carry over. See the enterprise platform page for how that architecture works.
Do we have to start with a pilot?
Not always. Organisations that have run this kind of deployment before, and know their loss rates, cycle times and accuracy requirements from evidence rather than from memory, can reasonably go straight to a site deployment. Everyone else benefits from the pilot, because it converts four or five assumptions into measurements — and those measurements are what make the full quote accurate rather than padded with contingency. We will tell you which camp we think you are in.
How do we build the business case?
Start from a baseline you already measure rather than from a benefit we describe. Search time, inventory accuracy, unplanned downtime, container loss and audit preparation effort are the usual candidates, and the strongest cases pick two or three rather than claiming all of them. The RFID, CMMS and returnable packaging calculators model the benefit side in your browser, with no form to complete.
What happens after go-live?
Support and platform updates are part of the ongoing agreement, with the response model set out in your quote rather than assumed here. Worth planning for separately: tag replacement across the fleet's life, infrastructure health checks, and reconfiguration when the operation changes — a new production line or a re-racked warehouse changes zones and rules. Systems that are never revisited quietly stop reflecting the site they are supposed to describe. Talk to us about what fits your operation.