The total cost of off-the-shelf software: what the sticker price hides
The sticker price is never the final price. Add-on modules, integration, training, support: the method to work out the real cost before you sign.

By Jérôme Knops
Published October 15, 2026 · 4 min read

The pricing page showed €49 per user per month. Fifteen people, that is €735 a month: a reasonable budget, approved in ten minutes. Eight months later, the bill is more than double, and nobody changed plans. The sticker price was only the starting point.
The sticker price is only the license
The figure used to compare two vendors is almost always the same one: an amount per user per month, for the base version. It is the number used to build the budget, and it is also the one that matters least once the software is actually running.
That price covers neither the options discovered necessary later, nor the connection to the company's other tools, nor the time spent training teams, nor support when something breaks on a Friday evening. It covers access to the software. Nothing more.
The modules added one by one
A business management tool sold as "complete" often turns out bare. Advanced invoicing is a module. The reporting a manager actually reads is a module. Automatic export to accounting software, another module. Each one has its own per-user price, each is billed separately, and each looks reasonable on its own.
It is the sum that stops looking reasonable. A building materials distributor adding three modules at €10 to €15 per user per month sees the initial budget climb by 50% to 100% without changing software at all: they have simply finished discovering what the base offer did not cover.
Integration: a cost that comes back every year
Business management software that does not talk to the payroll tool, or to accounting, forces someone to bridge the gap by hand, or requires a technical integration. That integration has a setup cost, often several thousand euros, then a maintenance cost every year: an update on one side breaks the link with the other, and it has to be fixed.
This cost never appears on the pricing page. It shows up on the integrator's invoice a year after signing, when it is too late to turn back.
The full calculation, worked through
Back to the opening example: business management software for fifteen users, sticker price €49 per user per month.
| Line item | First year | Following years |
|---|---|---|
| Base license (15 users) | €8,820 | €8,820 |
| Advanced invoicing module | €2,700 | €2,700 |
| Reporting module | €1,800 | €1,800 |
| Payroll integration setup | €6,000 | €0 |
| Integration maintenance | €1,200 | €1,200 |
| Initial training | €2,000 | €0 |
| Premium support | €3,000 | €3,000 |
| Total | €25,520 | €17,520 |
The price advertised at the start, €8,820 a year, was only a third of the real first-year cost, and half the cost of the following years. None of these line items is an anomaly: each one sits, on its own, in the vendor's price list. What nobody did before signing was add them up.
This calculation repeats for every piece of software in the company. At a distributor with several hundred employees, four such tools cost €190,000 a year altogether, licenses, modules and integrations included.
What changes with an application built for the company
An application built for a company has no separate modules page: what the company needs is built in, from the start. No per-user license either, so no bill that climbs with every hire, as we explained in the article on per-user licensing. Integration with the company's other software, payroll or accounting, is built once, inside the application itself, without depending on a third-party update that breaks the link the following year.
The price works differently too: we cover it in the article on the cost of a custom business application. The question is not "how much is the license", but "how much will the whole thing, modules and integrations included, cost in three years".
When off-the-shelf software is still the right choice
Off-the-shelf software stays relevant for a standard need shared by every company in the same sector: general accounting, for instance, or payroll itself. There, the modules and updates are designed for everyone, and their cost is justified by that shared scale. The problem appears when the same software is used to cover what makes the company specific: that is where modules multiply, and integration becomes permanent.
Total cost of software: the key takeaways
The price on a pricing page describes a license, not a complete management setup. Before signing, list the modules the company will need within the year, the number of integrations to build with tools already in place, and the training and support time that represents.
That calculation takes an hour and avoids an unpleasant surprise a year later. It also allows a fair comparison, on the same basis, between off-the-shelf software and an application built for the company: not on the sticker price, but on what each will actually cost, year after year.

Founder and CTO of Edenio
Jérôme Knops is the founder of Edenio, where he designs and builds custom business applications for construction, supply chain and distribution companies. He runs the scoping meetings, writes the code, and stays the person you talk to once the tool is in production.
See all their articles
Jérôme Knops
