ERP Consultants — What Good Looks Like
The software vendor decides at most half of the outcome of an ERP project. The other half — arguably more — depends on the ERP consultants and the implementation partner the buyer selects. The consulting landscape in DACH is unusually fragmented, ranging from the Big-4 firms running multi-hundred-million SAP transformations down to two-person boutiques delivering a Microsoft Dynamics 365 Business Central go-live for a Mid-Market engineering firm in eighteen weeks. Day rates span 1,000 to 3,500 EUR, project sizes span 50,000 to 50,000,000 EUR, and quality varies more than either of those ranges would suggest.
This guide describes the four practical consultant archetypes that mid-market DACH buyers actually shortlist, the criteria worth applying when choosing among them, and the fee models that protect the buyer from cost runaway. It is editorial rather than promotional: we name representative firms in each category but the goal is to help buyers reason about the choice, not to recommend a specific consultancy. Selection mistakes here typically cost more than software-selection mistakes do, because the consultant decision rarely gets revisited after it is made.
Four consultant archetypes
The DACH ERP consulting market splits cleanly into four archetypes. Most buyers eventually shortlist within one of these categories, even if they start by talking to all four:
Big-4 and global advisory
Deloitte, EY, KPMG, PwC, plus Accenture and Capgemini. Multi-thousand-strong DACH practices, full transformation capability (process redesign, change management, data migration, post-go-live support), partner networks across all major vendors. Day rates typically 1,800 to 3,500 EUR. Strongest fit: groups above 1,000 staff with multi-country roll-outs, regulatory complexity, or post-merger system integration. Trade-off: the people who win the engagement are rarely the people who deliver it.
Vendor-anchored implementation specialists
All for One Group (SAP), NTT Data Business Solutions (formerly itelligence, SAP), Cosmo Consult (Microsoft), Sovanta (SAP), msg systems (SAP), FIS GmbH (SAP). Several hundred to several thousand consultants each, deep platform expertise, typically certified at every relevant level. Day rates 1,200 to 2,200 EUR. Strongest fit: mid-market and upper mid-market deployments where the platform decision is already firm and platform depth matters more than vendor neutrality. Trade-off: limited willingness to question the platform choice.
Mid-Market boutiques
50 to 300 consultants, typically privately owned, single-platform or two-platform focus, deep DACH localisation knowledge. Names include 3C Solutions, abilis, Adato, COSMO Consult Mid-Market division, Mehrwerk, audius, GISA, q.beyond ERP solutions. Day rates 1,000 to 1,600 EUR. Strongest fit: Mid-Market mid-market projects where senior consultants stay on the project from day one to go-live, and where the buyer wants to negotiate scope and pace directly with the partner's ownership. Trade-off: bench depth is finite — if a key consultant leaves mid-project, recovery is harder.
Regional and freelance specialists
Single-discipline boutiques and freelance consultants, often two to ten people. Particularly relevant for niche modules (production planning, transport management, finance close), for industry-specific implementations, and for selection advisory. Day rates 700 to 1,500 EUR. Strongest fit: specific work packages within a larger project, selection advisory, post-implementation optimisation. Trade-off: not suitable as primary implementation partner for projects above 250,000 EUR.
Selection criteria for consultants
Eight criteria matter more than the rest in evaluating consultants. Buyers who weight these correctly avoid most of the common consultant selection mistakes.
- Reference customers in the same industry and similar size. Three reference visits to consultancy clients of comparable size and vertical — not the consultancy's flagship reference, but a project from the past eighteen months — reveal more than two days of credentials presentations.
- Named team for the project. Insist on names, CVs and committed allocation percentages for the proposed engagement team. The discount between “people in the proposal” and “people on the project” is the single biggest predictor of project quality. A specialist consultancy that names the same people in proposal and delivery is worth a higher day rate.
- Methodology fit with the buyer's culture. Waterfall versus agile, big-bang versus phased, prescriptive versus collaborative — the methodology that worked for the consultancy's last client may not fit the buyer's decision culture. Test methodology fit in workshops, not in proposals.
- Localisation and regulatory depth. GoBD-compliant audit trails, DATEV interface implementation, ZUGFeRD and XRechnung handling, deutsche payroll and HR compliance — these are decisive for any DACH implementation and rarely the strongest area of global firms.
- Partnership and certification level with the vendor. Top-tier partnerships give access to vendor support, early-access programs and escalation paths. Lower-tier partnerships save day-rate but introduce friction with the vendor.
- Bench depth and replacement risk. What happens if the lead consultant leaves the firm or the project mid-way? Larger firms have more bench depth but slower replacement cycles; boutiques have shallower benches but more direct ownership engagement.
- Pricing transparency and change-order discipline. Fixed-price work packages with named deliverables and clear change-order procedures avoid the “time-and-materials creep” that turns 600,000 EUR projects into 1,400,000 EUR projects.
- Post-go-live support model. Application Management Services (AMS), hypercare windows, response-time SLAs and named operational team are part of the consultant decision, not separable from it.
Fee models — T&M, fixed-price, outcome-based
Three fee models dominate the DACH consulting market, with two further variants gaining traction.
Time and materials (T&M). Day rates charged for actual time worked, plus expenses. Standard for advisory, design, configuration and customisation work where scope cannot be fully fixed up front. Advantages: flexibility, no contingency padding. Disadvantages: cost runaway risk, requires active buyer governance. Used for roughly 60 per cent of mid-market projects, more for advisory phases.
Fixed price for defined work packages. Each work package (e.g. financials configuration, sales process implementation, data migration) priced as a fixed deliverable with acceptance criteria. The implementation is decomposed into ten to twenty such packages. Advantages: cost certainty, forces clarity on scope. Disadvantages: contingency padding (typically 15–25 per cent), formal change-order process for every scope change. Used for 25 to 30 per cent of mid-market projects.
Outcome-based. Fees linked to project outcomes (go-live date, user-adoption metrics, business benefits realised). Rare in pure form because the metrics are hard to define and harder to measure cleanly. More common as a partial bonus structure layered on top of T&M or fixed-price baseline. Used for under 10 per cent of mid-market projects, typically by sophisticated buyers with strong PMO capability.
Variant: capped T&M. Day rates as in T&M, but with a contractual cap per work package. Splits the risk: the consultancy absorbs cost overruns above the cap; the buyer benefits if work completes under the cap. Increasingly common as a middle ground between T&M and fixed price.
Variant: rate-card with named-team commitment. Standard day rates per seniority level, but the consultancy commits to specific named individuals at specific allocation percentages. Protects the buyer from bait-and-switch staffing without paying the contingency premium of fixed price.
Day rates by role and seniority
Indicative day-rate bands for the DACH mid-market in 2026. Rates vary by consultancy category (Big-4 at the top, Mid-Market boutique in the middle, freelancers at the bottom):
| Role | Day rate (EUR) | Typical allocation |
|---|---|---|
| Partner / Director | 2,500–3,500 | 5–15 % steering |
| Project Manager / Engagement Lead | 1,800–2,500 | 40–80 % |
| Senior Consultant / Solution Architect | 1,500–2,200 | 60–100 % |
| Consultant / Functional Lead | 1,100–1,700 | 80–100 % |
| Junior Consultant | 700–1,100 | 80–100 % |
| Developer / Technical Consultant | 900–1,500 | 50–100 % |
| Change Management / Training | 1,200–1,800 | 20–40 % |
Project blended rates typically land between 1,200 and 1,800 EUR per day for Mid-Market projects, 1,600 to 2,400 EUR for upper mid-market, and 2,200 EUR upwards for enterprise transformations. Nearshore (Poland, Czech Republic, Romania) and offshore (India, Vietnam) options can reduce blended rates by 30 to 50 per cent but introduce coordination overhead that often consumes part of the saving.
Common mistakes in consultant selection
Five recurring mistakes account for most consultant-driven project failures.
Mistake 1: choosing the consultancy on day rate alone. A 1,200 EUR consultant who delivers 60 per cent of the value at 80 per cent of the speed is more expensive than a 1,800 EUR consultant who delivers fully. Total project cost is far more sensitive to consultant productivity than to the day rate itself.
Mistake 2: not insisting on named team members. Proposals routinely list senior names that disappear at project start. The discount between “named in proposal” and “actually on the project” can run 40 per cent of effort.
Mistake 3: bundling selection advisory with implementation. Asking the implementation partner to also advise on vendor selection compromises both. Selection advisory should be paid separately to a partner who will not implement, or at least firewalled inside the same firm.
Mistake 4: under-investing in change management. The 10 to 20 per cent of project budget that goes into communication, training and adoption support typically returns more than the equivalent spent on additional configuration.
Mistake 5: not negotiating the post-go-live support model up front. AMS terms negotiated after go-live, when the buyer has no leverage, run materially higher than terms negotiated during the implementation contract. Build the operations model into the implementation contract.
Related Topics
- ERP vendors directory
- ERP implementation playbook
- Requirements document template
- ERP comparison overview
- ERP for the Mid-Market
- Top ERP systems 2026
- Cloud vs on-premises decision matrix
Frequently Asked Questions
How much does a typical mid-market ERP implementation cost in consulting fees?
For a Mittelstand implementation of 50 to 250 staff on a Tier-2 platform (SAP Business One, Microsoft Dynamics 365 Business Central, Sage 100, NetSuite SuiteSuccess), consulting fees typically run 250,000 to 800,000 EUR. Upper mid-market projects (250 to 1,000 staff) usually land between 700,000 and 2,500,000 EUR. Enterprise transformations regularly exceed 10,000,000 EUR. Software licences and infrastructure are additional. The widely-used rule of thumb is two to three EUR of consulting for every EUR of first-year software licence.
Are Big-4 consultancies worth the premium?
For complex multi-country roll-outs, regulatory-heavy environments and post-merger integrations, often yes — the breadth of capability and the global delivery footprint genuinely add value. For straightforward Mittelstand implementations of a Tier-2 platform on a single country, the Big-4 premium rarely pays back. Mid-market buyers regularly find that a specialist Mittelstand boutique delivers better outcomes at 60 to 70 per cent of the Big-4 price.
Should we hire one consultancy for selection and another for implementation?
For projects above 500,000 EUR, yes — the selection advisor has different incentives from the implementation partner, and separating them avoids the conflict of interest where the advisor recommends the platform the advisor implements best. For smaller projects the overhead of running two consultancies often outweighs the benefit, and a single specialist advisor with an arm's-length firewall is usually acceptable.
How do we protect against cost runaway in T&M projects?
Three protections work in practice: (1) work-package-level T&M caps rather than open-ended billing; (2) monthly steering committee with actuals-versus-forecast and a no-surprise rule for variances above 10 per cent; (3) clear change-order procedure with named approval authority. Buyers who run T&M projects without these controls regularly see 40 to 80 per cent overruns; with them, overruns rarely exceed 15 per cent.
What is the right consultant-to-internal-staff ratio?
For most Mittelstand projects, the ratio runs roughly 1:1 to 2:1 (one to two consultants per internal team member). Anything heavier on consultants usually signals that internal capacity is too thin, which becomes a problem at go-live and afterwards. Anything heavier on internal staff suggests the buyer is funding a learning curve that will slow the project. The right answer depends on what the internal team can sustain after go-live, not what looks affordable during the project.
