InnerWeb
Skip to main content

Framework agreement and site orders: best practices

When a company has several plants, every amendment to the contract with the software vendor means weeks of negotiation. The solution is a split: the framework agreement governs licenses and maintenance over the years, and each deployment at a new site is a separate order based on the offer. Below are the practices arranged in the order in which the parties usually apply them.

PLN 21,000
two sites in one schedule, net
Source: offer, indicative ranges from 2025-2026 deployments; individual pricing
PLN 8,000
pilot extension to the second site, net
Source: offer, indicative ranges from 2025-2026 deployments; individual pricing

Two kinds of obligations in one project

Deployment is a one-off obligation: configuration, mapping, training, acceptance. Licenses and maintenance are a continuing obligation: access, availability, updates, support. Combining them in one document means every change in the deployment scope reopens the whole contract, including the maintenance prices.

Deployment is settled by an order based on the offer, independently of the maintenance agreement, so launching another site does not require an amendment to the service contract. This structure is the basis of the practices below.

Practice 1: the framework agreement governs what is stable

In the framework agreement, record: the licensing model, the SLA, the update rules, the rules of liability and service access. From 3 August 2026 the distribution model applies: the InnerWeb license for the client is granted without amounts, and the commercial agreement and invoices are issued by the Authorized Partner. The framework should therefore name both sides of the obligations: the producer's license and the partner's commercial terms.

Pilot at two sites: together from the start or in two steps

Pilot at two sites: together from the start or in two stepsComparison of two routes: both cost PLN 21,000 net in total0500010,00015,00020,00025,000PLN netTwo sites from the start: Total: 21,000 PLN net21,000Two sites from the startOne site, then extension: Total: 21,000 PLN net21,000One site, then extension
Source: Offer: PLN 13,000 plus PLN 8,000 extension equals PLN 21,000; indicative ranges from 2025-2026 deployments

Practice 2: a deployment order per site

Each order covers one site or one set of sites and contains the scope, the schedule, the price and the acceptance artifacts. A pilot at one site in the external companies system costs PLN 13,000 net, and a variant with two sites in one schedule PLN 21,000 net. These are indicative ranges from 2025-2026 deployments; individual pricing applies.

Extending the pilot from one site to the second costs PLN 8,000 net, so the total equals the two-site variant from the start. The strategy for the purchaser: start with one site if you are not sure about the second, because you lose nothing on price.

Practice 3: license prices in the framework, not in the order

Put the license price lists into the framework agreement: the elastic license costs PLN 80 net per logged-in user per month with a minimum of 10 users, or a fixed package. Moving from the elastic license to a fixed package happens without an amendment and without interrupting the operation of the system. This clause saves the parties when things grow: the next plant reports its users and does not negotiate rates.

Practice 4: calculate the cost of an extension

The purchaser should know the cost of the next site before signing the framework. For comparison: the full cost of the first 12 months for one site and 10 users is PLN 37,000 net (deployment PLN 13,000 plus 12 x PLN 2,000). For the second site, the PLN 8,000 pilot extension is added, but no new contract is needed.

Practice 5: who signs what

The framework agreement is signed by the person authorized to commit to multi-year obligations, while deployment orders are signed by the plant director or by a person within their limit. Record this in the framework as a table, so that the plant does not wait for headquarters on every order, and headquarters can see all orders in aggregate.

Checklist

Video

Frequently asked questions

Does another site require an amendment to the maintenance agreement?

No. Deployment is settled by an order based on the offer, independently of the maintenance agreement.

Is it worth starting with one site?

Yes, if you are not sure about the second. The extension for PLN 8,000 net gives a total equal to the two-site variant from the start.

Can the elastic license be changed to a fixed package?

Yes. Moving from the elastic license to a fixed package happens without an amendment and without interrupting the operation of the system.

Build a framework for a group of plants

We will present a framework agreement and deployment order scheme for your group of plants. We will show how to calculate the cost of the next site.

Let's talk