/Herr_Dreher_500x500.jpg)
Why this matters. Most top-10 lists of ERP service providers are written by the very providers being ranked — the useful question is: who advises you without wanting to implement the system themselves afterwards? The DSAG has documented for years the tight supply of experienced S/4HANA consultants — and with the 2026/2027 cutover pressure rising, this scarcity becomes structural.
When this comparison is useful
Comparing ERP service providers only pays off once the role of the partner is clear. Selection advisory, requirements-document guidance, technical implementation and post-go-live operation are four distinct disciplines — the market treats them as a single offer. Anyone starting from that collapsed category is comparing logos, not work.
Four criteria that actually hold
-
Separation of selection and implementation: a partner who advises your selection and then implements it has an interest in the outcome of its own recommendation. That isn't an accusation — it's a structure.
-
Methodology before tooling: ask to see the selection methodology, not the list of vendor partnerships. Without a transparent in-house method, the partner amplifies whichever vendor's framing dominates.
-
Key-person commitments: which named people are contractually assigned to your project, and what happens if they leave? The DSAG reports on S/4HANA consultant scarcity make this question non-optional.
-
Post-go-live model: hourly, retainer, SLA? The operational follow-on costs — not the headline price in the selection proposal — determine the actual lifecycle bill.
Where the choice typically fails
A wholesale company in North Rhine-Westphalia, 280 staff, asked its prospective implementation partner to also lead the vendor selection. The recommendation — with no ill intent — landed on the system the partner knew best. Two years later, when the industry-logistics interfaces turned out more expensive than expected, the unspoken alignment of interests finally became visible.
Across more than 1,200 ERP engagements, the pattern repeats: bundling advisory and implementation in one hand rarely saves money — it just shifts the risk to a later point in the project. An independent consultancy that doesn't implement afterwards has, by definition, a different interest: that the selection holds. The gap in interest sounds small, but in moments of project conflict it determines whose position is actually represented in the room.
What to do next
Before the next provider conversation:
-
Ask one question: where do you earn most of your revenue — selection advisory, licence resale, or implementation?
-
Ask for the last three projects where the selection recommendation was not followed by the firm's own implementation.
-
Confirm in writing which named people remain in the project for how long.
If you want this separation set up cleanly from the start, we can run a structured conversation on independent ERP consulting as the safeguard before the later implementation.
FAQ
An ERP service provider typically implements a specific system and earns its revenue from licence and project work. An independent ERP consultant supports the selection and the requirements document without implementing — and therefore has no commercial stake in any particular outcome.
Whenever the selection decision is strategic and the later implementation commits multiple years and seven-figure investments. In that configuration, separating advisory from implementation typically pays for itself within the first project phase.
Four questions are not negotiable: do you separate selection from implementation? Which named people are contractually committed to the project? What does the post-go-live support model look like? What exit clauses are written into the contract if the delivery date slips?
