InnerWeb
Skip to main content

Regional implementation partner: recommendations for integrators

An integrator, engineer or salesperson with industrial contacts can deploy the InnerWeb safety system together with the producer in their region. Below are the questions and agreements worth closing before the first meeting with a plant: division of roles, how the pilot runs, billing and the costs the end client will see.

3-6 months
length of the pilot at a plant
Source: price list
1,650 PLN
monthly pilot maintenance (net)
Source: price list
21,000 PLN
sample implementation for two sites (net)
Source: illustrative calculation

Who this role is for

An implementation partner is a company or person who knows industrial plants in their region and can guide the client from the first conversation to the working system. In the InnerWeb model the partner can be an integrator, engineer or salesperson with industrial contacts. They deploy the technology together with the producer, who supplies the product, hardware, training and support.

InnerWeb is a software producer, not a device manufacturer. Industrial beacons have an industrial design, a CE declaration and ATEX construction for zones 2/22, while the remaining hardware is purchased and integrated. InnerWeb does not manufacture or replace access control readers, so the partner's role is not to replace them, but to connect the system to the client's existing environment.

Recommendation 1: define what the partner does and what the producer does

At the start, list the tasks in a table of roles. The producer supplies the software, instance, licences, hardware, training and support. The partner manages the relationship with the client, assesses the local conditions of the plant and coordinates work on site. Disputed tasks, such as training administrators or configuring integration with existing systems, should be agreed in writing before the first offer.

The reasoning is practical: the client sees one contact person, but responsibility must be divided. When the training role is not assigned, in the second week of the rollout nobody knows who is to train the coordinators of external companies.

Two-site implementation: one-off and in stages

Two-site implementation: one-off and in stagesBefore and after chart: the total for implementing two sites is 21,000 PLN net both one-off and in stages.0500010,00015,00020,00025,000PLN netOne-off: Implementation of 2 sites: 21,000 PLN net21,000One-offIn stages: First site + extension: 21,000 PLN net21,000In stages
Source: Illustrative calculation: 13,000 PLN (1 site) + 8,000 PLN (extension) = 21,000 PLN net

Recommendation 2: know the model: conversation, pilot, implementation, maintenance

The model for an industrial plant has four steps: a conversation, a pilot lasting from 3 to 6 months, a full implementation with a one-off cost, and maintenance on a subscription. The partner should describe this sequence to the client in the same way as the producer, so the client does not hear two different versions.

The pilot has specific costs that must be explained. Maintaining the pilot at 1,650 PLN net per month covers the server, instance, licences for 10 users, SLA, 100 BLE beacons and 3 mobile devices, and access to 12 modules, and the pilot can run for several months without additional costs.

Recommendation 3: prepare the client for the payment structure

The implementation is billed by a separate order, independently of the maintenance agreement, and payment is split 50% at ordering and 50% after go-live. Licences come from the software producer. The integrator must understand this, because the client will ask who issues which invoice and for what.

Agree with the producer the extent of the partner's involvement in billing and how it looks on the order documents. Record these rules before the first offer reaches the client: changing the structure after an offer is submitted undermines trust.

First 12 months in three sample configurations

First 12 months in three sample configurationsBar chart: 37,000 PLN, 52,200 PLN and 72,600 PLN net for the first 12 months.020,00040,00060,00080,000PLN net1 site, 10 users: 37,000 PLN net37,0001 site, 10 users2 sites, 10 users: 52,200 PLN net52,2002 sites, 10 users2 sites, 50 licences: 72,600 PLN net72,6002 sites, 50 licences
Source: Illustrative calculation: implementation plus 12 months of maintenance, indicative ranges from 2025-2026 rollouts

Recommendation 4: know the sample costs and ranges

The partner should know the order of magnitude of costs so as not to promise too much or too little. In the sample quote the implementation for one site is 13,000 PLN net, and for two sites 21,000 PLN net. Extending to a second site after the pilot costs 8,000 PLN, which gives the same total sum.

The full cost of the first 12 months in the sample scenarios is 37,000 PLN net for one site and 10 users, 52,200 PLN net for two sites and 10 users, and 72,600 PLN net for two sites with 50 licences. These are indicative ranges from 2025-2026 rollouts; the quote is individual.

Recommendation 5: plan the sequence: pilot first, then the second site

The best sequence for a partner is a pilot at one site, followed by an extension. The pilot costs less, gives the client data from their own plant and lets the partner learn the local requirements before a full implementation is signed.

Because extending after the pilot does not increase the total implementation sum, the client does not lose anything by phasing the work. This is an argument the integrator should have ready in the conversation with procurement.

Recommendation 6: agree how to tell the client about limitations

Tell the client what the system does not do: it does not replace the access control system or the readers, it complements them. Do not promise geolocation without hardware: four modules (employee geolocation, tool geolocation, inactivity detection, traffic analytics) require additional hardware, while seven others run under the same licence with no extra licence fee.

Keep communication compliant: the partner makes no legal promises, such as a guarantee of compliance. They say that the system supports meeting a requirement and provides evidence for an audit.

Video

Frequently asked questions

Does the partner sell access control readers?

Not under this model. InnerWeb does not manufacture or replace readers; it integrates with the client's existing access control system.

Who supplies the hardware and training?

The producer. In the partner model the producer supplies the product, hardware, training and support, while the partner manages the relationship and the implementation in the region.

Does every pilot end in an implementation?

In InnerWeb's rollouts to date, 100% of pilots moved on to implementation. This is not, however, a promise for the next plant.

Become an implementation partner in your region

If you know industrial plants in your region, let's talk about deploying the InnerWeb system together. Book a meeting with our team.

Let's talk