What the cost of an additional plant consists of
We divide the cost of an extension into six items: licences and infrastructure, the map and location structure, transmitters and their installation, roles and permissions, integrations with existing systems, and training and go-live for staff. We give prices only as indicative ranges from 2025-2026 implementations. An individual quote is prepared, because it depends on floor area, the number of buildings and the existing systems. This page does not give amounts, only the share of work that can be compared between plants.
Licences and infrastructure follow from the instance model. Each client gets an isolated instance with its own database and its own mail system, running in Docker containers, including on the client's server. If the group chooses a separate instance per plant, this item repeats for every plant. A shared environment moves it into a single group-level item.
- Shrinks: preparing templates, checklists, risks and the role layout.
- Shrinks partly: configuring the structure, because names and levels are already known.
- Does not shrink: the map, georeferencing and transmitter installation.
- Depends on the plant: integrations with existing access control, time and attendance, HR and ERP systems.
Which items shrink and which stay the same
Items based on a pattern shrink. The structure of a plant has fixed levels: plot, view, building, line and location. Once the first plant has names, typical risks and checklists defined, the next one copies them and adjusts them. The same BHP checklist can be run at many sites, so preparing it is not repeated.
Items tied to geometry and physical installation do not shrink. The map of a given plant, its georeferencing and the placement of transmitters are created from scratch. As a rough guide, one transmitter is placed per 100-200 m2 inside a building and about one every 100 m along plant roads, so the number of transmitters grows in proportion to the floor area of the new plant.
Sample client-side work: first plant and an additional plant
- First plant
- Additional plant
Cost on the client side: the time of people
For the plant director the time of their own staff matters as much as the vendor's price: the BHP manager, security, IT and the administrator. At the first plant they spend it defining the structure, roles and way of working. At later plants that time shrinks, because answers to the basic questions already exist.
That is why the calculation below counts person-days on the client side rather than money. This lets each group apply its own rate. It is more honest than a price without context, because it shows where the difference comes from.
How to reduce the cost of an extension
The biggest impact comes from the order of actions. First the group standard, then the other plants: the reverse order means correcting structures that are already live. The second factor is avoiding hardware replacement. InnerWeb does not produce or replace readers. It only receives events from the existing access control system, so the next plant does not need to invest in a new access system.
It is also worth planning go-lives in series. Two plants with a similar structure, launched one after the other, use the same implementation team and the same materials. Past implementations show a 100 percent conversion of pilots into deployments across 20 implementations and pilots, which for a group means the pilot at the first plant is a reliable basis for planning the next ones.
Client-side work: first plant and additional plants
| Parameter | Value |
|---|---|
| Structure and map, first plant | 14 person-days |
| Roles and training, first plant | 12 person-days |
| Integrations, first plant | 14 person-days |
| Structure and map, additional plant | 10 person-days |
| Roles and training, additional plant | 6 person-days |
| Integrations, additional plant | 8 person-days |
Result: First plant: 40 person-days. Each additional plant: 24 person-days, which is 16 fewer. For three plants the total client effort is 88 person-days instead of 120 with a full repeat of the effort.
Note: Sample calculation: the person-day figures are planning assumptions, not results of a specific plant. Indicative ranges from 2025-2026 implementations; individual quote.
Video
Frequently asked questions
Is an additional plant cheaper than the first one?
Some items shrink because they reuse the template: templates, roles and checklists. The map, georeferencing and transmitters are built from scratch, so the total does not drop to zero.
Do we need to buy new access control readers?
No. InnerWeb does not produce readers and does not replace existing ones. It only receives check-in events from the plant's access control system.
Where can I find the exact price?
The quote is individual and depends on floor area, the number of buildings and integrations. We share indicative ranges from 2025-2026 implementations after a conversation about the scope.
Want to estimate the extension for your group?
We will go through the cost items with you and prepare indicative ranges for your plants.
Let's talk