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.

Häufig gestellte Fragen

What does an ERP consultant cost per day?

Daily rates for ERP consultants in the DACH region range roughly between around 800 euros for junior consultants and 2,800 euros for partner or director level, depending on seniority and specialisation, with the midpoint for experienced senior consultants frequently at about 1,300 to 1,500 euros. Specialists in high-demand platforms such as SAP S/4HANA or Oracle Fusion typically charge a premium of around 20 to 30 percent and thus often fall in the range of 1,600 to 2,800 euros per day. Depending on the contract, travel and incidental expenses are frequently added, so the effective daily price can exceed the pure fee. Specific rates also depend on whether it is a framework-agreement project, a fixed-price project or ad-hoc spot consulting, and since 2025 they have become more negotiable in a rather soft market environment.

How much does consulting cost relative to the ERP licence?

A common rule of thumb says that consulting and implementation costs in the mid-market amount to roughly one to three times the licence sum — for cloud subscriptions measured against the first 24 to 36 months or so — while heavily customised industry or multi-country projects can also reach five to eight times. In many projects, consulting, customising, data migration and training thus form the largest cost block, while the pure licence or subscription fees often account for only about 15 to 25 percent of total costs. Licence costs tend to predominate at smaller companies, whereas consulting costs predominate in larger and more complex ventures. Since this distribution depends heavily on company size, industry and cloud versus on-premises model, the figures should always be calculated for the individual project.

What is the difference between a selection consultant and an implementation partner?

A selection consultant works vendor-neutrally and mainly supports the early project phase with requirements analysis, requirements document, market research, vendor demos and contract negotiation; they typically earn their daily rate and not vendor commissions. An implementation partner, by contrast, is tied to a specific product, usually vendor-certified, and after the system decision takes on customising, interfaces, data migration, training and go-live support. In practice, a two-stage approach often proves successful, with neutral consulting for selection and preparation and a specialised partner for the technical implementation. It is important to recognise potential conflicts of interest, since pure implementation partners naturally have a vendor bias in favour of their own system.

Which ERP consultancy is the best?

There is no universally best ERP consultancy, as the right choice depends on the chosen ERP system, the industry and the respective project phase. Large firms such as the Big 4 (Deloitte, EY, KPMG, PwC) or corporate consultancies bring extensive resources and strategy know-how, while specialised boutiques often offer deeper industry expertise and consistently senior staffing, and vendor partners the deepest product knowledge. For pronounced industry requirements, it is worth looking at industry specialists such as ams.erp in machinery and plant engineering, CSB-System in the food industry, or specialised utility solutions such as SAP S/4HANA Utilities, Schleupen or Wilken in the energy sector. Decisive for project success are less the name than verifiable references from comparable projects, a suitable methodology and the cultural fit with your own team.

Does every ERP project need an external consultant?

Not necessarily, because small companies with manageable standard processes and a lean, configurable cloud solution can sometimes handle an implementation with the vendor and their own key users. However, as soon as complex processes, individual customising, many interfaces, data migration from legacy systems or a re-implementation such as the switch from SAP ECC to S/4HANA come into play, the value of external consulting rises considerably, especially since mainstream maintenance for SAP ECC expires in 2027. Also to be considered is the high internal effort, as a mid-market ERP project typically ties up a project manager heavily for 12 to 18 months and places partial demands on several key users. An experienced consultant can contribute methodology, market knowledge and negotiating strength and help avoid expensive wrong decisions, which is why the costs are usually justified in complex ventures.

How do I find and vet the right ERP consultant?

Sensible vetting criteria are proven industry expertise, relevant vendor certifications — for example with SAP, Microsoft, Oracle or Sage — a methodology that fits the project, such as SAP Activate, Microsoft's Success by Design or FastTrack for Dynamics 365, or agile approaches, as well as two to three solid references from comparable projects, which you should also contact directly. Clarify the fee model early, because time and material shifts the risk to the client, fixed price to the consultant, and in the mid-market a hybrid variant of fixed price for standard phases and T&M for customising frequently dominates. An often underestimated factor is cultural fit, i.e. whether the team communicates directly, responds quickly and senior consultants really do work in day-to-day project business. It has proven effective to hold a short joint workshop with the planned project team before signing the contract in order to test collaboration and fit in practice.