ERP cost and effort — realistic, not optimistic.

1. Five cost types of an ERP project

Anyone who looks only at software licences typically sees 20–35 % of the real total cost of an ERP project. Five blocks should be calculated in full:

• Software / subscription. Licences, user subscriptions, edition differences, additional modules, add-ons.
• Implementation. Partner services for conception, customising, interfaces, migration, testing, go-live support.
• Internal effort. Hours from your own business, IT and management staff — most frequently underestimated.
• Operations. Recurring licences, hosting/cloud, internal or external application support, maintenance.
• Follow-up costs. Further development, change requests, rollouts to additional entities/countries, release upgrades.

2. Typical orders of magnitude

Every calculation is individual — the ranges below are reference points for a typical mid-market rollout in a single entity, without deep manufacturing:

For manufacturing companies, multi-entity rollouts or strongly industry-specific requirements, implementation and internal effort typically lie significantly above these ranges.

3. Internal effort — the often overlooked block

The most important cost item is systematically underestimated in many calculations because it is not on any invoice. Internal effort arises mainly for:

• Project management (full-time or nearly full-time across the project duration)
• Process owners in finance, procurement, sales, logistics, production
• Key users for testing, data migration and acceptance
• IT involvement for integrations, identity, infrastructure, data migration
• Executive management for steering, decisions, escalations

A sound rule of thumb: internal effort = 30–60 % of external partner effort, and in group-like structures even more. Anyone who does not plan for this block will finance it silently through delayed milestones and overload in the team.

4. 5-year TCO view

Software decisions are not a single number but a total-cost-of-ownership view over at least five years. For cloud ERP, the cost distribution is fundamentally different from a classic on-premise implementation:

• Cloud ERP: high recurring subscription share, relatively low one-off investment.
• On-premise / private: higher initial investment (licences, infrastructure), lower subscription share.
• Hybrid models: often useful in group structures, but the calculation becomes more complex.

For the decision, the year-1 price matters less than the 5-year overall picture under realistic assumptions about user growth, edition changes and follow-up projects.

5. Typical calculation pitfalls

• List price vs. actual quoted price. Real quotes often deviate significantly from public price lists — in both directions.
• Edition changes. What starts today in a favourable edition can force edition upgrades as scope grows. Relevant question: "From when does the chosen edition no longer suffice?"
• User types. Full users vs. light / team members — the real mix drives the price more than the total headcount.
• Change requests. Everything not in the requirements specification is later calculated as a change request. A good requirements spec reduces CRs considerably.
• Integrations. Interfaces are more often a budget topic than modules. They deserve their own line in the calculation.
• Rollouts to additional entities. Often mentioned only at the reference date but not accounted for in effort.

---

Note: This profile does not replace an individual quote calculation. Realistic budget figures only emerge on the basis of a requirements specification and concrete quotes, not from benchmarks.