Ownership cost — total cost of ownership (TCO) — is the sum of all costs of an ERP system across its full lifecycle, typically five years. In the DACH Mittelstand the sticker price of licence plus initial implementation makes up only around 15 percent of the total; the remaining 85 percent hide in seven cost categories rarely quantified in the vendor pitch. From over 1,200 projects at Dreher Consulting we know: whoever fails to model those 85 percent before contract signature is buying software on a half-truth.
What Is Ownership Cost? Definition and the 5-Year TCO Logic
Ownership cost is the broader reading of total cost of ownership: the period-accurate, total cost figure for an asset across its lifecycle. For an ERP system in the DACH Mittelstand we model the standard five-year horizon — five years, because most licence and maintenance contracts renegotiate at that frequency and migration cycles repeat in that window.
The concept of total cost of ownership traces back to Gartner, which established TCO as an evaluation standard in the late 1980s. As a rule of thumb: initial licence and implementation often make up only around 15 percent of total TCO, with around 85 percent falling on running costs across the lifecycle. This 15/85 orientation is established across industries and remains a useful starting point as of June 2026.
Methodologically, the Forrester Total Economic Impact methodology structures the same view across four dimensions — Costs, Benefits, Flexibility, Risk. In DACH contract negotiations managing directors increasingly demand this lens. For software-asset capture, ISO/IEC 19770-3 on IT asset management provides entitlement tags as the machine-readable basis.
Four characteristics distinguish architecture-grade TCO modelling in the Mittelstand from a naive licence-price summary:
- Five-year horizon, period by period. Cashflows per year, not one lump sum — otherwise maintenance indexation is missed.
- Seven hidden cost categories. Data migration, master data cleansing, interfaces, shadow-IT decommissioning, change management, train-the-trainer, contract risks.
- Contract management as a lever. Licence top-up clauses, maintenance indexation and cloud price-adjustment clauses belong in the model, not in the fine print.
- Risk discounts and sensitivity analysis. Best/base/worst case per category — anything else produces pseudo-precision.
Why Ownership Cost Matters in the DACH Mittelstand in 2026
Three drivers act at once: budgets are scrutinised harder, cloud price adjustments hit running costs directly, and AI add-ons push lifetime cost above the original plan. Going into vendor negotiations in 2026 without a five-year TCO is negotiating from the gut.
First, budget discipline. The DSAG Investment Report 2026 documents that 38 percent of DACH SAP customers are raising overall IT budgets in 2026, and 43 percent are raising SAP software spend specifically. Investment decisions now follow economics, feasibility and integration capacity rather than vision. A defensible ownership-cost calculation is the language those tests run in.
Second, the structural view. The Bitkom study on the digitalisation of the economy positions ERP data as the backbone of digitalisation and shows rising economic pressure on tighter budgets. Ignoring this in vendor selection means paying twice in the implementation phase.
Third, the value-contribution question. A pure cost view understates value and risk discount. In our projects, Mittelstand ERP transformations reach positive economics within five years only when TCO and total value of ownership (TVO) are modelled together — the cost view alone misleads.
From our experience across more than 40 TCO analyses at DACH Mittelstand companies — machinery, food, medical devices, retail — the median share of hidden costs lands at around 47 percent of the total. Across 1,200+ projects the pattern is the same: without a properly modelled ownership cost, ERP selection becomes architecture in the dark.
Project Example: DACH Machinery Manufacturer (anonymised, c. 1,800 employees)
At a southern-German machinery manufacturer with around 1,800 employees and two plants we modelled a complete five-year TCO before the ERP selection. The vendor pitch priced licence and implementation — the five-year TCO ended up at 5.4 times the initially communicated sum. The architecture-first preparation made that transparent before contract signature.
The company had grown organically. The managing directors had two offers on the table — both communicated licences and implementation as a total price. We insisted: no signature before the five-year TCO is modelled for both options. From over 1,200 projects we know — this is where the economics are decided, not in the pitch.
In a structured four-week effort we priced seven cost categories per vendor. Data migration from three legacy systems came to 480,000 euros, master-data cleansing to 210,000 euros, interfaces to PLM and shipping to 340,000 euros, change management and train-the-trainer to 290,000 euros over three years. These four items alone exceeded the communicated initial implementation budget. Oracle NetSuite on ERP implementation costs confirms the rule of thumb: services typically cost two to three times the software licence; data migration runs 10 to 15 percent of total TCO.
This led to an architecture-validated Lastenheft — and a contract negotiation in which top-up clauses, maintenance indexation and cloud price-adjustment were explicitly priced. Six months later the selection was complete, vendor-neutrally. The lesson: ownership cost is not the outcome of an ERP rollout. It is its negotiation basis.
Seven Hidden Cost Categories Vendors Don't Price
Seven cost categories almost never appear in DACH vendor pitches — and together they explain why five-year TCO routinely lands at three to six times the initial communicated sum. They follow from 1,200+ projects at Dreher Consulting and more than 40 five-year TCO analyses since 2023.
1. Data migration from heterogeneous legacy systems
From several legacy systems — typically two to four — data structures need to be translated into the target system. In our projects this runs at 8 to 18 percent of total TCO depending on data quality. Vendors systematically underestimate the item because it is not in the licence.
2. Master-data cleansing as methodical preparation
Cleansing of master data is the invisible prerequisite. Duplicate article numbers, inconsistent customer records and patchy supplier data each extend implementation and testing by weeks, sometimes months.
3. Interfaces to third-party systems
PLM, CRM, shipping systems, web shops, payroll, machine controllers — each interface generates development and test costs plus ongoing maintenance effort across the five-year horizon.
4. Shadow-IT decommissioning
In every Mittelstand project across the past 24 months we have found home-grown Excel tools, Access databases and small in-house applications. Switching them off costs energy, politics and training effort — and shows up in no vendor proposal.
5. Change management and acceptance
Acceptance is earned, not decreed. From our experience across 1,200+ projects, change management is the most consistent indicator of schedule and budget adherence.
6. Train-the-trainer methodology
External consultants train once; in-house no one is left fluent. Train-the-trainer costs two to four percent of the implementation budget in year one but keeps the system alive across the full five years.
7. Contract risks: top-ups, maintenance index, cloud price adjustment
The DSAG guidelines for ERP implementation recommend that licence top-up clauses, maintenance indexation and cloud price-adjustment clauses be explicitly negotiated before contract signature and quantified in a TCO model across at least five years. Without those clauses TCO rises sharply in years three and four — we have priced this pattern in several projects.
Our take
Whoever thinks ownership cost is only licence and implementation is pricing 15 percent of the truth. The remaining 85 percent hide in the seven categories above — pricing them is the actual job before any signature. Architecture before software, ownership cost before licence price.
How We Calculate Ownership Cost in the DACH Mittelstand (Methodology)
We model ownership cost in four steps — inventory, seven-category pricing, sensitivity analysis, contract-negotiation bridge. The sequence is not arbitrary: completeness first, then bandwidth, then the contract lever. From our experience any economic case fails otherwise.
In Dreher Consulting's vendor-neutral ERP selection service ownership cost is an integral part of contract management. Four steps:
- Inventory — all cashflows per year. Licences, maintenance, cloud fees, hosting, training, implementation, customising, interfaces, internal project staff. Two to three weeks.
- Seven-category pricing of hidden costs. Data migration, master-data cleansing, interfaces, shadow-IT decommissioning, change management, train-the-trainer, contract risks. Best/base/worst per category.
- Sensitivity analysis across five years. What happens at 5 percent annual maintenance indexation? At 12 percent cloud price adjustment in year three? At a licence top-up for 30 additional users?
- Contract-negotiation bridge. Translating sensitivities into clauses — top-up caps, indexation limits, exit clauses. Negotiation basis instead of gut feel.
Methodological foundation: The scientific basis for period-accurate pricing of lifecycle costs in information systems comes from lifecycle-costing research, among others at the ERCIS in Münster.
The difference to many consulting offers: we recommend vendor-neutrally. Ownership cost is the sober referee between two vendors — not a marketing story. Our gap analysis prices the gaps per core process; the process-owner logic secures organisational accountability; the Pflichtenheft mirrors the vendor response against the ownership-cost assumptions.
Cloud vs On-Premise: Ownership Cost Compared
Cloud ERP and on-premise ERP do not differ in functionality but in cashflow structure. Across five years cloud can be more expensive than on-premise — if cloud price-adjustment clauses are not negotiated. We model both options in parallel; otherwise the selection becomes a belief decision.
The Trovarit „ERP in Practice 2024/25" study evaluates more than 40 ERP systems across over 1,700 DACH companies. User satisfaction remains stable at a school grade of 1.80, with a spread between vendors of over 1.5 grades — service quality under criticism. Both deployment models benefit from a TCO model before signature.
On-premise means high initial investment (licences, hardware, implementation), lower running costs, but migration and modernisation duties every five to seven years. Cloud means low initial investment, high running fees, automatic modernisation — but cloud price adjustments can drive lifetime cost significantly. Hybrid ERP architectures combine both views per module.
From our more than 40 TCO analyses: at smaller DACH Mittelstand companies (under 250 employees) cloud is often cheaper over five years; at mid-to-large Mittelstand companies (250 to 2,000 employees) the picture tips toward on-premise or hybrid once cloud price adjustments above 8 percent per year enter the model. There is no blanket recommendation — the sensitivity analysis decides, not the trend.
Common Mistakes in Ownership-Cost Modelling in the Mittelstand
Five failure patterns recur in Mittelstand economic-case calculations. All five are avoidable if addressed before contract signature. None has its root in the Excel model. They are organisational and methodological.
- Mistake 1: treating the sticker price as the total. Licence plus initial implementation is 15 percent of the truth. Fix: five-year horizon with all seven hidden categories.
- Mistake 2: ignoring maintenance indexation. 5 to 8 percent annual indexation is standard — over five years a substantial sum that must sit inside the model.
- Mistake 3: keeping data migration and interfaces outside the TCO model. Both must be inside the model, otherwise systematic understatement results.
- Mistake 4: ignoring cloud price adjustment as a risk. Cloud ERP contracts contain adjustment clauses. Fix: three scenarios (4 / 8 / 12 percent) in the model — and negotiate the clauses before signature.
- Mistake 5: no sensitivity analysis. A point estimate is not a decision basis. Fix: best/base/worst per category. The Gartner Finance TCO Topic Hub calls sensitivity analysis the methodological minimum.
Our take: The mistakes are rarely technical. They are methodological — and that is exactly the lever of vendor-neutral consulting. Architecture before software, ownership cost before licence price, every time.
Frequently Asked Questions on Ownership Cost
Ownership cost is the sum of all costs of an ERP system across its full lifecycle, typically five years — licence, maintenance, hosting, implementation, data migration, interfaces, training, change management and contract risks. The licence price is just one of many components. As a rule of thumb, licence and initial implementation typically make up around 15 percent of total TCO; the remaining 85 percent fall on running costs and hidden categories.
From our experience in the Mittelstand the five-year horizon is the most robust standard. Five years because most licence and maintenance contracts renegotiate at that frequency, because cloud price-adjustment clauses bite repeatedly in that window, and because most ERP modernisation cycles repeat after five to seven years. Longer horizons (seven or ten years) are possible but increase uncertainty disproportionately.
Seven recur in our projects: data migration from heterogeneous legacy systems, master-data cleansing, interfaces to third-party systems, shadow-IT decommissioning, change management and acceptance, train-the-trainer methodology, and contract risks from top-up clauses, maintenance indexation and cloud price adjustment. Together these seven categories explain why five-year TCO routinely reaches three to six times the initially communicated sum.
It depends on company size, the cloud price-adjustment rate and the modernisation cycle. From our more than 40 TCO analyses: at smaller DACH Mittelstand companies under 250 employees cloud is often cheaper over five years; at mid-to-large Mittelstand companies between 250 and 2,000 employees the picture tips toward on-premise or hybrid as soon as cloud price adjustments above 8 percent per year enter the model. There is no blanket recommendation — the sensitivity analysis decides.
Tightly. DSAG guidelines for ERP implementation recommend that licence top-up clauses, maintenance indexation and cloud price-adjustment clauses be explicitly negotiated before contract signature and quantified in a TCO model across at least five years. Without those clauses TCO jumps in years three and four. In our practice ownership-cost modelling is therefore not the outcome but the negotiation basis of the selection.
Next Steps
Before any ERP selection, migration or major digitalisation decision, a four-to-six-week ownership-cost modelling step pays off. Whoever skips it risks the five-year TCO landing at three to six times the initially communicated sum — without that becoming transparent before signature.
To deepen these topics, see our vendor-neutral ERP selection and our digitalisation services. We work vendor-neutrally — drawing on over 30 years of experience and more than 1,200 projects across the DACH Mittelstand.
We also recommend the wiki entries on utility value analysis, the process landscape map, the continuous improvement process and make-to-order. A first conversation is available via the contact page.
30 minutes with Dreher Consulting
A structured ownership-cost pre-clarification of your ERP decision — the five-year horizon, the seven hidden cost categories and the contract-negotiation bridge, vendor-neutral and drawn from over 1,200 projects in the DACH Mittelstand.
