Starting point: a 34,000 PLN offer and the controller's question
The logistics centre was collecting offers for a system covering a site map, a training module, permits and supervision of lone work. The InnerWeb offer came to 34,000 PLN net for implementation in seven items. The finance controller asked the question that is asked for every investment: exactly when does the money leave, and what does the company hold in its hand at each payment?
The arrangement described here is an implementation scenario prepared in the offer, not a closed project. It does show how to approach instalments when the decision maker is responsible for cash flow. For the controller, the rhythm of payments matters more than the final amount.
Three instalments: how the 34,000 PLN was divided
The payment was divided into three parts tied to stages: one third at the order, one third after stage I and one third after go-live. At 34,000 PLN this gives about 11,333 PLN per instalment (11,333, 11,333 and 11,334 PLN net, so that the total adds up).
The three-stage variant has an acceptance after each stage. Stage I is a working training module and an instance with the map. Stage II is an accepted test permit. Stage III is the production go-live. Each acceptance therefore has a verifiable criterion that the controller can see on screen, not only read in a protocol.
- instalment 1: about 11,333 PLN net at the order
- instalment 2: about 11,333 PLN net after stage I (training module and instance with the map)
- instalment 3: about 11,334 PLN net after the production go-live
Three implementation instalments, net
What the controller gained at the purchase decision stage
The first gain is lower risk at signing. At the order the plant pays one third instead of a half, so the exposure before the first proof of operation is smaller than in the alternative two-stage schedule, in which 50% is paid at the order and 50% after go-live at the end of month 2.
The second gain is a clear narrative for the board. The controller presents three payment dates and the three events that trigger them. The board sees that money follows the result, not the passage of time. The third gain is the option to stop the project after stage I if the acceptance goes badly: the plant then loses two instalments less than in a model with payment up front.
For completeness, the controller also noted that the two-stage schedule has its advantages: it is simpler to manage, has fewer acceptance documents and closes faster administratively. The choice depends on whether the company prefers simplicity or cash caution.
Budget for the first 12 months across three subscription scenarios
Implementation is only part of the first-year cost. The offer shows five subscription scenarios for a logistics site: 10 users at 2,000 PLN, 50 licences at 3,700 PLN, 50 licences with a dialer and transmitters at 4,700 PLN, 100 licences at 5,200 PLN, and 100 licences with options at 6,200 PLN net per month. The first 12-month budget in three selected scenarios comes to 58,000, 78,400 and 90,400 PLN net.
Each of these budgets can be reproduced: 34,000 PLN plus 12 times 2,000 PLN gives 58,000 PLN; 34,000 PLN plus 12 times 3,700 PLN gives 78,400 PLN; 34,000 PLN plus 12 times 4,700 PLN gives 90,400 PLN. The controller therefore received a table showing that the implementation is fixed and only the subscription changes, depending on the number of users and options.
- scenario A: 10 users, subscription 2,000 PLN, 12-month budget 58,000 PLN
- scenario B: 50 licences, subscription 3,700 PLN, 12-month budget 78,400 PLN
- scenario C: 50 licences with a dialer and transmitters, subscription 4,700 PLN, 12-month budget 90,400 PLN
First 12-month budget by subscription scenario
How to synchronise instalments with acceptances in the contract
For each instalment, record the event that triggers it, the person who confirms it, and the deadline for acceptance. A good wording is that an instalment becomes due after the stage acceptance protocol is signed, and that acceptance takes place within an agreed time from the notice of readiness.
Also separate acceptance from minor remarks. Non-critical remarks should not block a payment, but they should have a deadline for removal. This way the instalment does not depend on small details, and the supplier is motivated to close everything.
Conclusions for the finance department
Instalments tied to stages change the risk profile, not the price. The amount of 34,000 PLN stays the same, but the distribution over time and the link to the result give the controller an argument in the talk with the board. Add 23% VAT to the net amounts. The ranges are indicative and require an individual quotation.
Division of the implementation into three instalments
| Parameter | Value |
|---|---|
| Implementation in 7 items | 34 000 PLN net |
| Number of instalments | 3 tied to stages |
| Subscription, scenario A | 2 000 PLN net/month |
Result: 3 instalments of about 11,333 PLN; 12-month budget 58,000 PLN net
Note: Sample calculation. Indicative ranges from 2025-2026 deployments; individual pricing. Net amounts, excluding 23% VAT.
Video
Frequently asked questions
Do three instalments change the implementation price?
No. The total stays at 34,000 PLN net. What changes is the distribution of payments over time and their link to stage acceptance.
What is accepted at stage I?
A working training module and an instance with the map. Stage II is an accepted test permit, and stage III is the production go-live.
Is a two-stage schedule possible?
Yes. The two-stage variant assumes 50% at the order and 50% after go-live, with acceptance at the end of month 2. It is simpler, but the upfront payment is larger.
Do the amounts include VAT?
No. All amounts are net, and 23% VAT is added separately. The ranges are indicative and the pricing is individual.
Let's arrange the instalments to your schedule
We will show a split of the implementation into instalments tied to acceptances for your plant. Book a call.
Let's talk