InnerWeb
Skip to main content

FAQ: partner programme of the security system

An integrator, installer or sales manager considering a partnership with a software producer asks the same questions: who is party to the licence, who issues the invoices, who trains the people and whose customer it is when the cooperation ends. Below are answers based on the InnerWeb authorized partner model, in the order they come up in the first conversation.

3
agreements in the partner model
Source: InnerWeb partner model
20
producer implementations and pilots
Source: company facts
100%
pilots that moved on to implementation
Source: company facts

Model of cooperation and division of roles

An authorized implementation partner is an integrator, engineer or sales manager who deploys InnerWeb technology in their region. The software producer supplies the product, hardware, training and implementation support, while the partner runs the project at the customer's site, knows the local plants and people, and is responsible for installation and maintenance.

The customer has two ways in: talking directly to the plant, with a 3-6 month pilot followed by full rollout, or implementation through an authorized partner in its region. The partner therefore does not compete with the producer for the same contact, but opens a second path that is often faster because it rests on existing trust.

Do I have to be a manufacturer of hardware or software?

No. InnerWeb is the software producer, and the industrial beacon has an industrial design registration, a CE declaration and an ATEX construction for zones 2/22. The remaining equipment is bought and integrated. The partner does what it does best: design, installation, configuration and customer relations.

Do I have to be an access control installer?

No, but it is a common and natural profile. InnerWeb does not produce or replace access control readers, it integrates with the customer's existing system. A partner who installs that system therefore has access to the same cabinet, the same people and the same work schedule.

Licences and three agreements

The model consists of three agreements: a licence agreement with the producer, a maintenance agreement with the partner and an implementation agreement with the partner. This split separates the rights to the software from responsibility for implementation and maintenance, so each party knows what it is responsible for.

The licence is granted to the customer directly by the producer under a separate licence agreement. It defines the customer's rights to use the system, the scope of the licence and the business continuity guarantee, with no payment to the producer under that agreement. It does not depend on how long the partner cooperation lasts, which answers the question of what happens to the customer after the split.

Who owns the customer relationship?

The customer remains the partner's customer for implementation and maintenance, while under the licence it has an agreement with the producer. If the partner stops providing services, the customer does not lose the right to the system: it may name another authorized partner or contract directly.

Invoices, prices and markup

Installation, implementation and maintenance are delivered by the authorized partner, who invoices all of it. During the pilot the partner also invoices the licences, and under a fixed agreement the licences come from the producer. This split must be described in the offer, so that the customer's procurement department does not receive two invoices for the same item.

Prices in the producer's offer are prices without the integrator markup. The markup is added on the partner's side, so the partner decides its own margin, and the customer sees the final price in the partner's offer. We describe this in detail on the page about licences and partner markup.

Training, support and partner competences

The partner receives implementation training from the producer, access to documentation and support during the first projects. The scope covers configuration of roles and the permissions matrix, work with beacons, integration with customer systems through the REST API and webhooks, and preparation of the implementation acceptance.

Knowledge of the security system and familiarity with the plants in the region are not enough if the partner cannot explain to the customer exactly what it is getting. For that reason the training also covers how to present the product, the acceptance criteria for the pilot and conversations with the heads of safety, security and IT.

Leads, pilots and producer credibility

Referrals from partners turn into a customer meeting faster than inquiries from advertisements. A joint pilot with the partner shortens the path of trust to a new technology, because someone the plant knows recommends the solution and takes part in the rollout.

The producer has 20 implementations and pilots behind it, and all pilots have moved on to implementation. It holds European patent EP 3970095 B1 and the MSWiA licence L-0023/25. The partner can cite these facts in the conversation with the customer as proof that the software is mature, not experimental.

Video

Frequently asked questions

Does the customer lose the system if it stops cooperating with the partner?

No. The licence is granted by the producer under a separate agreement and does not depend on how long the partner cooperation lasts. The customer may name another authorized partner or contract directly.

Who invoices the customer?

The partner invoices implementation, installation and maintenance. During the pilot the partner also invoices the licences, and under a fixed agreement the producer invoices the licences.

Does the producer impose the partner's margin?

No. Prices in the producer's offer are without the integrator markup, and the markup is added on the partner's side.

What does the partner get at the start of the cooperation?

Implementation training, documentation and support during the first projects, including help with role configuration and API integrations.

Let's talk about partnership

Tell us about your region and your customers. We will show the three-agreement model on a concrete example and agree how a joint pilot would look.

Let's talk