With proprietary ERP systems, license models per seat, module, or transaction dominate. On paper that looks plannable. With growth it often becomes more expensive than calculated: new sites, employees, tenants, or modules drive ongoing cost. For mid-market companies, what counts is therefore not the list price of the first installation, but the total cost of ownership (TCO) over several years.

Why the list price misleads

The initial license is only one building block. Typical cost blocks across the lifecycle:

• One-time introduction: consulting, migration, training, change
• Ongoing licenses and maintenance contracts
• Module and user expansions as you grow
• Customizations and interfaces over years
• Internal or external operations, hosting, monitoring

Whoever compares only year 1 often underestimates years 3 to 7. Especially when the company grows and the ERP becomes a bottleneck in the cost structure. An ERP that grows with you must not punish growth.

Which license levers drive the bill

Three models are common:

1. Per user or seat. Every new role, every site, and every seasonal peak raises the base. Shadow use and named-user quotas create friction between business and IT.
2. Per module. Core processes are cheap. Industry-specific or advanced functions are bought later. The vendor roadmap then steers your budget indirectly.
3. Per transaction or volume. Scales with business success. Fine when transparent. Risky when thresholds and tiers are unclear.

Lock-in levers in the same contracts: minimum terms, expensive module upgrades, restricted export rights, fees for extra environments (test, staging). Before signing, align with vendor lock-in and exit strategy.

How to compare TCO usefully

Calculate over five to seven years and set scenarios side by side: stable user growth, a new site, an additional process area. Ask:

• What does +50 users cost in three years?
• What does another module cost that you do not need today but might need tomorrow?
• What costs arise on termination and data handover?
• Which internal capacity do operations and releases bind?

Include maintenance, support tiers, and mandatory upgrades in the table. A low entry price with steep escalation is often more expensive than a higher but linear path.

What open source changes in the cost structure

With open source ERP, the user license disappears. Budget flows into processes, integration, and operations. That shifts the calculation; it does not eliminate it: hosting, support, and further development remain. The advantage is controllability: you decide where the money goes, instead of buying user quotas.

What still matters is the license model (for example AGPL), documentation of customizations, and switchability of operations and support. Whoever only buys the “open source” label but hosts and extends exclusively with the manufacturer has only relocated the cost trap. Deeper reading: open source ERP.

Nuclos is licensed under the GNU AGPL 3.0. There are no license costs per user. Investment flows into mapping your processes, integration, and operations. That fits mid-market projects that do not want to fund growth through seat licenses.

What leadership should decide concretely

For mid-market companies, license costs are a strategic question, not a pure IT line item. Before signing, clarify which growth scenario you consider realistic in five years, and run exactly that scenario through the numbers. ERP for the mid-market provides the frame for comparison. Whoever checks TCO, exit, and lock-in together makes the decision with open eyes, not with the cheapest offer of year one.