InnerWeb
Skip to main content

Implementation glossary for procurement: recommendations

Two offers for the same system can differ by tens of percent only because one vendor understands a 'pilot' as 50 transmitters and the other as two weeks of testing. The buyer then compares prices instead of scopes. Below is the list of 16 terms that should be defined in the request for proposal before the answers arrive.

PLN 37,000
cost of the first 12 months for 1 site and 10 users, net
Source: offer, indicative ranges from 2025-2026 deployments; individual pricing applies
16
terms in the implementation and cooperation glossary
Source: scope of the study

Why the definitions must come before the offers

Buyers usually receive answers in different formats. One offer counts licenses per user, another per instance, a third per location. Without common definitions the comparison table is fiction, and negotiations end on the unit price, which says nothing about the total cost.

The best practice is an annex to the request with a short glossary: one sentence of definition per term and one question that the vendor must answer with a number. A vendor who refuses to standardize the terms signals that they want to keep room for interpretation after the contract is signed.

Recommendation 1: define the pilot in numbers

One vendor's pilot covers 50 transmitters and 10 licenses, with no time limit. Another may mean two weeks on delivered hardware without integration. In the request, state the number of users, the number of transmitters, the success criteria and whether the time is limited. Ask for the price of the implementation and the subscription separately, because a pilot implementation and a subscription are settled in different ways.

Licenses: monthly net cost by model

Licenses: monthly net cost by modelHorizontal bar chart: flexible license for 10 users PLN 800, for 30 users PLN 2,400, package of 50 licenses PLN 2,500, package of 100 licenses PLN 4,00001000200030004000PLN/monthFlexible, 10 usersFlexible, 10 users: 800 PLN/month800Flexible, 30 usersFlexible, 30 users: 2400 PLN/month2400Package of 50 licensesPackage of 50 licenses: 2500 PLN/month2500Package of 100 licensesPackage of 100 licenses: 4000 PLN/month4000
Source: Example calculation: PLN 80 per user per month (30 users = PLN 2,400) and fixed packages; indicative ranges from 2025-2026 deployments; individual pricing applies

Recommendation 2: establish who is a license

A flexible license costs PLN 80 net per logged-in user per month, with a minimum of 10 users, which means from PLN 800 per month. A fixed package is 50 licenses for PLN 2,500 net per month or 100 licenses for PLN 4,000 net per month. These are indicative ranges from 2025-2026 deployments; individual pricing applies.

Ask whom the vendor counts as a user. In our model the licenses cover the plant's users and the coordinators of external companies who register their employees. Employees of external companies and guests are not counted. A difference in this definition can change the cost several times over.

Recommendation 3: describe the SLA with three types of events

An SLA without event types is a declaration. In our model there are three types: a strategic failure (response in 12 hours, repair in 8 hours from the start of service), a failure that hinders work (response by the next business day, repair within 1 business day) and support and planned works (up to 7 days). In the request, require the same division from all vendors, as well as the availability of the server part in the calendar month.

Also ask for a description of the measurement method. The SLA parameters (availability, response and repair times) are set in the maintenance agreement, for example availability of 99.5% in the month.

Recommendation 4: require acceptance on an artifact

Implementation takes 3 months in three stages and each one ends with the acceptance of a specific artifact. In the request, ask each vendor for the list of stages and the names of the artifacts. If the offer contains only a 'final acceptance', the entire implementation risk stays with the buyer until the last day.

Recommendation 5: ask about the sales model and the contract

From 3 August 2026 the distribution model applies: the InnerWeb license for the client is granted without amounts, and the commercial contract and invoices are issued by the Authorized Partner. For the procurement department this means the counterparty is the partner, and the software vendor is responsible for the license and maintenance. In the request, separate the commercial side from the technical side and ask who is responsible for what.

Prepare separate items: implementation, licenses, maintenance, instance. The full cost of the first 12 months for one site and 10 users in our example is PLN 37,000 net (implementation PLN 13,000 plus 12 times PLN 2,000). This sum is the reference point for the comparison.

Video

Frequently asked questions

How many terms must the buyer define in the request?

The implementation glossary has 16 terms, but the minimum is: pilot, license, active user, SLA, stage acceptance and instance. The rest may follow from the contract.

Should unit license prices be compared?

Not without a definition of the user. The total cost of the first 12 months, including implementation, licenses and maintenance, matters more.

Who issues the invoice in the distribution model?

From 3 August 2026 the commercial contract and invoices are issued by the Authorized Partner, and the InnerWeb license for the client is granted without amounts.

Prepare the request with a glossary

We will send you a template of the glossary of terms to attach to the request for proposal. We will also help standardize the vendor answers in one table.

Let's talk