Principle: the pilot is the first stage of implementation, not a separate project
A plant that treats the pilot as a separate project asks what to do with it once it ends. A plant that treats it as a stage already has the answer: the instance, the accounts, the beacon network and the configured modules stay, and the implementation extends the scope. The difference comes from the decision made before the pilot, not after it.
In the strategic cooperation model with an industrial plant, after the conversation a pilot lasting 3 to 6 months follows, and then full implementation with a one-off implementation cost and maintenance on a subscription. InnerWeb has a 100% move from pilot to implementation in its projects so far, which shows that the model is predictable.
What stays unchanged: beacons and the instance
The beacons installed during the pilot are battery-powered and stay in their places. In the pilot, 100 beacons across 8 floors are mounted in 2 days without connection to a power supply, so moving to production requires no dismantling and no reinstallation. Expansion means adding more beacons in new areas, not rebuilding the network.
The same applies to the instance. 12 modules are available on the same instance in the pilot, and enabling more does not require extra hardware or reinstalling the beacon network. Production runs on the same instance and the scope expands through configuration.
- battery beacons stay in their installation places
- the instance and accounts remain, the scope of modules changes
- roles and permission settings move over without rebuilding
- pilot data becomes the production history
Monthly licence cost for 50 users: two models (example calculation)
What changes: modules, users, licences
Most changes concern the number of users and the scope of modules. The monthly pilot rate of PLN 1,650 net covers the server, the instance, licences for 10 users, SLA and 100 BLE beacons and 3 mobile devices, and a pilot can last several months without additional costs (indicative ranges from implementations 2025-2026; individual pricing). After the move to production there are more users, and licences are counted differently.
A flexible licence costs indicatively PLN 80 net per logged-in user per month (minimum 10 users), and fixed packages of 50 and 100 licences about PLN 2,500 and PLN 4,000 net per month (indicative ranges from implementations 2025-2026). Licences are counted for plant employees and coordinators of external companies who pre-register people and submit requests; employees of external companies and guests are not counted.
How to choose a licence at the move
The choice between a flexible licence and a fixed package depends on the number of people who actually log in during a month. With a small number the flexible model pays off, with a large fixed number a package does. Example calculation: a flexible licence for 50 users is 50 x PLN 80 = PLN 4,000 net per month, which is the same as the 100-licence package, while the 50-licence package works out cheaper by PLN 1,500.
It is therefore worth counting how many users log in during a typical pilot month, and choosing the model on that basis. The calculation is feasible, because the pilot provides data on the number of logins, not only declarations.
Implementation instalments: what they cover and how to spread payments
The implementation is broken down into items. In one pilot of a work-permit system the work was split into 7 items: analysis and workshops, server and accounts, mapping of the procedure, switching cards, hazards, external companies, testing and launch, with payment in three instalments. After the pilot the scope is similar, but the analysis items are shorter, because the plant already knows the system.
The full cost of the first 12 months for one location and 10 users is, in the example calculation, PLN 13,000 for implementation plus 12 x PLN 2,000, which gives PLN 37,000 net; for two locations and 50 licences it is PLN 72,600 net (indicative ranges from implementations 2025-2026). The amounts are examples, and the price depends on the scope.
Order of actions so that system operation is not interrupted
The move is best planned in four steps. The first is confirming the production scope and the number of users. The second is enabling additional modules on the pilot instance. The third is expanding the beacon network in new areas. The fourth is changing the billing model from pilot to production.
System operation is not interrupted, because each step concerns a different layer: configuration, modules, hardware or billing. The plant does not have to stop patrols or procedures that already work.
- confirming the scope and the number of users
- enabling further modules on the same instance
- adding beacons in new areas, without touching the existing ones
- changing the billing model from pilot to production
- reviewing pilot data as the basis for the production configuration
Pitfalls at the move and how to avoid them
The first pitfall is the lack of decisions on success measures before the pilot. After a few weeks the plant does not know whether the result is good, and extends the pilot endlessly. The second is the assumption that production requires a new beacon network. The third is underestimating the number of users, which changes the choice of licence.
It is also worth agreeing who on the plant side approves the move: the director, OHS or procurement. A pilot without a decision-maker usually ends with a report, not an implementation.
Comparison of licence models for 50 users
| Parameter | Value |
|---|---|
| Flexible licence | 80 PLN net/user/month |
| Number of users | 50 people |
| Package of 50 licences | 2500 PLN net/month |
Result: Flexible: 50 x PLN 80 = PLN 4,000 net per month; package of 50 licences: PLN 2,500, which is PLN 1,500 less per month (PLN 18,000 per year).
Note: Example calculation at indicative rates from implementations 2025-2026; individual pricing.
Video
Frequently asked questions
After the pilot, do the beacons have to be dismantled?
No. The beacons are battery-powered and stay in their places, and expansion means adding more in new areas.
Does the move require stopping patrols?
No. The changes concern different layers: modules, hardware in new areas and billing, so procedures that already work can continue without a break.
Who is counted for licences?
Plant employees and coordinators of external companies who pre-register people and submit requests. Employees of external companies and guests are not counted.
Planning the move from pilot to production?
We will calculate the scope, the licences and the order of actions so that the beacons from the pilot keep working without a break.
Let's talk