InnerWeb
Skip to main content

Logistics hub: rollout by an authorised partner and three contracts

The operator of a logistics hub wanted one partner who issues invoices for implementation and maintenance, but did not want the right to use the software to depend on the fate of the integrator. The answer was a model of three contracts: a licence with the manufacturer, and a maintenance and implementation contract with the partner.

3
contracts in the partner model
Source: InnerWeb partner model
99.5%
availability in the maintenance agreement
Source: partner agreement draft

Starting point: one company to talk to about invoices

The operator of a large logistics hub had a simple purchasing requirement: one entity should be responsible for installing, configuring and later maintaining the system, one entity it talks to and pays. The purchasing department did not want to juggle several suppliers, and the IT department wanted a single path for reporting faults.

On the software manufacturer's side the situation looked different. InnerWeb is the software manufacturer and does not carry out implementations in every region with its own staff. The partner model assumes that an authorised partner (integrator, engineer, salesperson) implements the technology in its region, while the manufacturer supplies the product, hardware, training and implementation support.

Two perspectives collided and the contracts had to be put in order. The client wanted one invoicing party, the manufacturer wanted to keep a direct licence relationship, and the partner wanted a clear scope of responsibility.

Problem: what happens to the licence when the work with the integrator ends

The most common concern of the legal department sounds like this: if the licence is part of the integrator's package, what happens to the system when the integrator's contract expires or the company changes its business profile. A contract that puts everything into one document ties the client to a single contractor for the entire period of using the system.

A second concern was liability. When licences, implementation and service sit in one agreement, it is hard to decide who is responsible for a configuration error and who for a product defect. During an internal audit such blurring makes it harder to name the person and the date.

  • the risk of depending on one integrator for the entire period of using the software
  • no separation of responsibility for the product and for the implementation
  • uncertainty about who invoices the licences during the pilot and who after the permanent contract is signed
  • the need for one reporting number and one SLA for the operator of the facility

Maximum repair time by fault category

Maximum repair time by fault categoryHorizontal bar chart: repair in category A within 8 hours, B within 24 hours, C within 168 hours050100150200hoursCategory ACategory A: 8 hours8Category BCategory B: 24 hours24Category CCategory C: 168 hours168
Source: Sample SLA from the partner agreement draft (category B: 1 day, category C: 7 days)

Solution: three contracts instead of one

The partner model consists of three contracts: licence, maintenance and implementation. The client signs the first one directly with the software manufacturer, the other two with the authorised partner. This way the software rights are separated from responsibility for implementation and maintenance.

The licence is granted to the client directly by the manufacturer under a separate licence agreement and does not depend on how long the cooperation with the partner lasts. If the client changes the integrator, the system keeps working and the new partner takes over maintenance.

Licence agreement with the manufacturer

It sets out the client's rights to use the system, the scope of the licence and the guarantee of operational continuity. It contains no payments to the manufacturer, because settlements go through the partner according to the rules described below.

Maintenance agreement with the partner

It sets response and repair times, availability (for example 99.5% per month) and a monthly subscription with a choice of licence package and optional modules. It is the document that the IT department and the facility manager read every day.

Implementation agreement with the partner

It covers installation, configuration and training. It is settled as a one-off payment, and its scope matches what the partner actually delivers at the facility: network, server, data import, roles, maps and go-live.

SLA and invoicing: figures from the contract draft

The SLA parameters (availability, response and repair times) are set in the maintenance agreement, for example availability of 99.5% per month. Faults are usually split into categories by weight, and each category is assigned a response time and a repair time, so the operator's IT department knows what to expect after reporting a fault.

The parties set the SLA settlement rules in the maintenance agreement, which is clear for purchasing: one document, one reporting number and one escalation path.

Invoicing is split by stage. The authorised partner carries out installation, implementation and maintenance and invoices all of it. During the pilot the partner also invoices the licences, and under the permanent contract the licences come from the manufacturer. The client therefore sees one payment stream during the pilot and a structured split after it ends.

What it costs: indicative ranges

A typical implementation costs from PLN 12,600 to PLN 34,000 net as a one-off payment, depending on scope. Licence packages in the flexible variant cost PLN 80 net per active user per month with a minimum of 10 users, and the fixed package of 50 licences costs PLN 2,500 net per month, or 100 licences PLN 4,000 net per month. These are indicative ranges from rollouts in 2025-2026; each quote is individual.

Prices in the manufacturer's offer are without the integrator's mark-up. The mark-up is added on the partner's side, so the client compares the partner's offers against the manufacturer's price list as a reference point.

Conclusions for the operator and for the partner

Splitting the contracts did not increase the number of contacts on the operator's side, because the partner remained the first line. It did change the legal certainty: the licence does not expire together with the integrator's contract.

For the partner the model means a clear scope: it is responsible for implementation and maintenance, not for developing the software. For the manufacturer it means keeping the licence relationship with the end user without having to run implementations in every region.

Video

Frequently asked questions

Does the licence expire when the client changes the partner?

No. The licence is granted by the manufacturer under a separate agreement and does not depend on how long the cooperation with the partner lasts. A new partner can take over maintenance.

Who invoices the licences during the pilot?

During the pilot the partner invoices the licences. Under the permanent contract the licences come from the manufacturer.

Where are the SLA parameters set?

In the maintenance agreement with the partner: availability, response and repair times are set in the contract, for example availability of 99.5% per month.

Let's talk about the partner model

If you plan a rollout through a partner, we will show you the draft of the three contracts and sample SLA terms. Book a conversation or a demo.

Let's talk