ERP software is the integrated application that puts finance, procurement, sales, production, warehouse, HR and service on a shared data foundation. From over 1,200 projects and more than 30 years of advisory experience in the DACH Mittelstand we know: project success is not decided by the vendor name but by the target process architecture before the vendor longlist. Pick ERP software before the end-to-end processes are signed off and you buy the vendor template's problems with it — architecture before software, every time.
What Is ERP Software? Definition and Boundary
ERP software (Enterprise Resource Planning software) is the integrated application that maps a company's central business processes onto a shared data foundation — finance, procurement, production, sales, warehouse, HR and service. It is the application layer of an ERP system, which additionally encompasses the database, hardware and integrations. ERP software is the means, not the end.
The SAP guide „What is ERP?" describes this function as the market standard. The boundary against the ERP system matters — the software is the application logic, the system also includes database, hardware and operating model. In the DACH Mittelstand the software choice is regularly the visible tip of an architecture decision that touches the whole system.
Three characteristics make today's ERP software architecture-grade: first, modular construction with independently configurable finance, materials, production, sales and HR; second, open interfaces over REST API, OData and EDI for clean PIM, MES, CRM and e-commerce connections; third, a clear master-data model — without which any later AI application runs aground.
Which Modules Belong in Modern ERP Software?
Modern ERP software has a financial core (general ledger, controlling, fixed assets) and logistical and operational modules (procurement, materials, production, sales, warehouse). HR, service and project follow, plus business intelligence, CRM and platform functions depending on vendor. For the DACH Mittelstand the split between differentiators and commodities matters more than module breadth.
The financial core stays similar across vendors: double-entry bookkeeping, cost centres, cost objects, fixed assets, consolidation. Here ERP software is commodity — every established solution meets the German HGB minimum. The difference appears in the logistical and producing modules, where order processing, production planning (PPS), warehouse logistics and sales must be tailored to the industry.
From our experience in over 1,200 projects across DACH machinery, food, medical devices and trade, what counts is not the longer module list but the methodical separation of differentiators and commodities. The ABPMP BPM CBOK — Enterprise Process Map supplies the foundation: every core process is decomposed into business capabilities, each capability classified as differentiator or commodity. Only then can one judge which 15 to 20 percent the ERP software must reflect perfectly.
Cloud, On-Premise or Hybrid: the Deployment Decision
Three operating models compete. Public cloud offers the shortest time to value and predictable monthly cost but limits customisation. On-premise keeps maximum control but demands in-house IT. Private cloud and hybrid are the most common real models in the DACH Mittelstand. The decision follows the compliance, integration and cost frame — not fashion.
The DSAG Investment Report 2026 provides the most reliable DACH data: 42 percent of DACH SAP customers plan high or medium investments in S/4HANA On-Premises, 22 percent in private cloud, only 6 percent in public cloud. Roughly half plan their S/4HANA move by end-2030. In the DACH Mittelstand on-premise and private cloud remain dominant — contrary to vendor pitches that stage public cloud as standard.
In our projects three factors drive the model choice: regulatory requirements (GDPR, ISO 27001, KRITIS by industry), the customisation depth of the differentiators, and master-data sovereignty. A DACH machinery manufacturer with its own PLM world usually runs more robustly on private cloud or on-premise. A trade company without production control benefits from the shorter time-to-value of a cloud solution.
DACH Mittelstand Vendor Landscape: SAP, Microsoft Dynamics, Sage, Infor, Oracle NetSuite, proAlpha
The DACH-relevant ERP software landscape sorts across few vendors: SAP S/4HANA and SAP Business One for upper Mittelstand, Microsoft Dynamics 365 Business Central and Finance & Operations for IT-savvy Mittelstand, Sage 100 and Sage X3 for classic Mittelstand, proAlpha and abas for production, Infor and Oracle NetSuite for international constellations. The list is not exhaustive but covers 80 percent of DACH projects.
The Gartner Magic Quadrant Cloud ERP 2025 (SAP press release) names SAP, Microsoft Dynamics 365, Oracle, Infor, IFS and Epicor as Leaders for product-centric enterprises. The Microsoft Dynamics 365 Gartner Cloud ERP Leader 2025 blog covers service-centric and finance. In the producing DACH Mittelstand we more often see proAlpha, abas, Infor and SAP Business One than the global mega-solutions.
The Trovarit study „ERP in Practice" 2024/25 with over 1,700 user companies confirms our observation: user satisfaction with the ERP software stays at a good level (school grade 1.80), while satisfaction with vendor service quality is declining. About 50 percent of ERP projects overshoot timeline or budget — the software is rarely the bottleneck, the vendor and implementation-partner management is.
What Does ERP Software Cost in the DACH Mittelstand? TCO Beats Licence Price
Cloud ERP software in the DACH Mittelstand runs at 50 to 150 euro per user per month. On-premise licences are 1,000 to 5,000 euro per user one-off plus 18 to 22 percent maintenance. Implementation costs 10,000 to well over 150,000 euro. Master data, interfaces, customisation and change push TCO over five to seven years to two to three times the licence.
From our practice in over 1,200 projects a simple rule holds: comparing only licence cost compares the wrong line item. Over five to seven years of Total Cost of Ownership the difference comes from four blocks: master-data maintenance, interface development, customisation depth against the vendor standard template, and change-management effort. In our projects these four account for 60 to 70 percent of true project cost.
The analysis of the DSAG Investment Report 2026 (IBsolution) mirrors the same reality: investment decisions follow feasibility, economics and integration, not visions. The Mittelstand-Digital evaluation 2025 (BMWE) confirms that digitalisation funding programmes are effective — provided the company knows its target architecture. A clean TCO calculation over five to seven years — including total cost of ownership — is the only basis on which selection becomes reliable.
What ERP Software Comparisons in the DACH Mittelstand Don't Tell You
Three points that rarely surface in ERP software comparisons and vendor pitches, but regularly decide between project success and double-cost reset projects in the DACH Mittelstand. They follow from over 1,200 Dreher projects and from the consistent application of the ABPMP standard.
1. ERP Software Is an Architecture Decision, Not a Product Pick
The common practice is vendor workshops first, specification later. From the Dreher view the order is reversed. First the target process landscape map, then the capabilities-mapping bridge, then the architecture-validated specification, then the vendor longlist. Pick ERP software before the documented target process landscape and you buy the vendor template's problems with it. The ISO 9001:2015, clause 4.4 (process approach) requires determining processes and their interactions before any operational decision — and the ERP choice is one such operational decision.
2. Master Data Is the AI Breaking Point, Not the Vendor AI Module
The Bitkom AI Study Report 2026 documents that 41 percent of German companies now use AI, a year earlier only 17 percent. From our practice it confirms daily: without data-object owners and measured master-data quality, the AI potential of the ERP software cannot be lifted. The vendor does not solve the data problem — it belongs in the specification.
3. The Hidden Cost Drivers Are Not on the Price List
In over 1,200 projects we counted: master data, interfaces, customisation and change account for 60 to 70 percent of true TCO. In no vendor pitch do they appear with comparable depth. Run an ERP software selection without a five- to seven-year TCO model and you compare licence prices while buying follow-on cost surprises.
Our take
An ERP software selection without a target process architecture, without a capabilities-mapping bridge, and without a TCO calculation over five to seven years is not a selection. It is a vendor meeting with a retrofitted justification. Architecture before software, every time.
Project Example: DACH Kitchen Manufacturer with Six Order Variants
At a southern German kitchen manufacturer with about 2,000 employees we set up the target process landscape map before any vendor longlist. Six order-processing variants ran in parallel, four of them main variants. Only the consolidated target architecture made the ERP software evaluation binding.
The company had grown over decades. Sales, engineering, work preparation and shipping each kept their own view of order processing — four Excel sheets, nobody had seen the end-to-end process on one page. We insisted: no vendor conversations before the target process landscape map and the Lastenheft are in place.
In two two-day workshops with the managing directors we mapped the three process levels and compared the six variants. Four were marked as main variants, and one consolidated target process emerged. From it came an architecture-validated specification. Six months later the ERP selection was complete and vendor-neutrally evaluated. Implementation ran an estimated 25 to 30 percent shorter than comparable projects without this preparation.
How We Select ERP Software: the Dreher Four-Phase Method
In Dreher Consulting's vendor-neutral ERP advisory the ERP software selection runs in four phases: target process landscape map, capabilities mapping, architecture-validated specification, qualified vendor shortlist with measurable criteria. We work vendor-neutrally — the method protects against biased recommendations.
Our vendor-neutral ERP advisory treats ERP software selection as part of enterprise architecture management for the Mittelstand. We follow a robust procedure:
- Target process landscape map — management, core and supporting processes on one page, with a named process owner per core process. Duration: four to eight weeks.
- Capabilities-mapping bridge — every core process is decomposed into business capabilities, each capability classified as differentiator or commodity.
- Architecture-validated specification — not a feature list, but the translation of the target architecture into functional requirements per core process. From it the vendor Pflichtenheft follows.
- Qualified vendor shortlist — three to five vendors are evaluated against the specification and against measurable capabilities criteria. The choice ends in a reasoned decision, not a gut feel.
Validated across 1,200+ projects: a cleanly prepared ERP software selection shortens the later implementation by up to 30 percent. The method dovetails with our ERP selection, ERP implementation and ERP project management.
Frequently Asked Questions on ERP Software
ERP software is the application layer — modules, business logic and UI for finance, procurement, sales, production, warehouse and HR. An ERP system also includes database, cloud or hardware, integrations and operating model. Selecting ERP software is an application decision. Introducing an ERP system is an architecture decision. In the DACH Mittelstand the software choice is regularly negotiated as a proxy for the system decision — and that is the real leverage.
From our experience a serious ERP software selection in the DACH Mittelstand takes three to six months — including target process landscape map and specification. Fast four-week selections only work where documentation and capabilities mapping exist. Implementation follows with three to nine months for the classic Mittelstand and twelve to twenty-four months for complex Mittelstand with several plants or an international footprint. Skipping the preparation extends implementation noticeably.
There is no universally correct ERP software for the DACH Mittelstand — the answer depends on industry, size, growth plan and differentiators. In the producing Mittelstand we frequently see proAlpha, abas, SAP Business One, Microsoft Dynamics 365 Business Central and Infor on the shortlist. In services and trade Microsoft Dynamics 365, Sage 100, Sage X3 and Oracle NetSuite dominate. The right answer emerges from matching the target process architecture against vendor capabilities — not from a top-ten list. Skip the architecture and you buy the vendor template's problems with it.
Next Steps
Before any ERP software selection, ERP migration or S/4HANA transformation, a four- to eight-week clarification step is worthwhile: target process landscape map, capabilities-mapping bridge, architecture-validated specification. Skipping it risks a double-cost reset project after eighteen to twenty-four months.
To deepen these topics, see our vendor-neutral ERP advisory and our specification approach. Case studies are in our Insights; for a 30-minute call with Dr Dreher use the contact page.
30 minutes with Dreher Consulting
A structured clarification of your ERP software selection — target process landscape map, capabilities-mapping bridge and the five-to-seven-year TCO logic, vendor-neutral and drawn from over 1,200 projects in the DACH Mittelstand.
