In Brief: The risk of a wrong ERP decision rarely lies in the software itself — it lies in unclear decision criteria, contracts without exit options, uncontrolled change requests, and a lack of benefit control after go-live.
In Brief: The risk of a wrong ERP decision rarely lies in the software itself — it lies in unclear decision criteria, contracts without exit options, uncontrolled change requests, and a lack of benefit control after go-live. Avoiding an ERP mis-selection takes more than a vendor comparison: it takes an independent party that documents the decision, secures it contractually, and makes its outcome verifiable.
How mid-sized companies secure the most expensive IT decision of a decade — with independent decision assurance from system selection to benefit control after go-live.
Avoiding an ERP mis-purchase takes more than a functional and vendor comparison: it takes an independent party that documents the decision, secures it contractually, and makes its outcome verifiable. We call this methodology ERP decision assurance — it is part of our DAA (Decision Architecture Assessment) approach and is described in full in this article.
Across more than three decades and over 1,200 projects in the DACH SME sector, we have seen a recurring pattern: ERP projects rarely fail because of the software. They fail because of four sources of risk that exist before, during and after selection — unclear decision criteria, contracts without exit options, uncontrolled change requests, and the failure to check whether the business case actually materialised after go-live.

Traditional selection consulting addresses only the first of these — and only up to the point of a recommendation. At the same time its core service is under pressure: market overviews and functional comparisons are now delivered faster and more cheaply by platforms and AI tools. Anyone who genuinely wants to avoid poor decisions has to look for value where no tool can provide it: in sound management decisions, independent risk and implementation assessment, and proven results.
Selection consulting answers the question, "Which system fits?" Risk minimisation — in the sense of decision assurance — answers three further questions: "Can we justify this decision at any time?", "What happens if the project fails?", and "Did the promised benefit materialise?" Selection is therefore one component of risk minimisation — not the other way round.
Implementation partners often offer "free" advice during the selection phase — naturally with the aim of securing a choice within their own portfolio. This is exactly where a significant part of the mis-purchase risk arises for mid-sized businesses: the neutral selection phase is skipped. A consultant who genuinely secures a successful decision does not, as a rule, implement the solution themselves. Only for that reason can they secure the implementation contractually and sign off milestones independently. No implementing system house defines exit criteria against itself.
Platforms and language models are useful in the research phase — we use AI tools consistently in preparing our own analysis. But a platform that also relies on vendor profiles and marketing operates on two sides of the market at once. And a language model is liable for nothing. Avoiding wrong decisions means having an independent third party — paid exclusively by the user — stand behind the decision-making process.
Criteria, weighted alternatives, deliberately rejected options with justification, assumptions and risks — fully documented. In our project practice the dossier is regularly the document that managing directors present to the advisory board, shareholders and financing banks: the ERP decision is then not "IT's opinion" but a transparently derived, well-founded business decision. In family businesses with several shareholder groups, the dossier has repeatedly proven to be the instrument that prevents factions forming — because rejected options are documented with reasons, rather than being informally "dismissed".
Before a contract is signed, criteria are defined whose breach triggers a project stop, restart or vendor change — and these criteria are written into the vendor contract. Our experience in project management shows that the difference between an expensive ERP project and one that threatens the company's existence almost always lies in when problems are identified. Contractually defined checkpoints enforce that honesty at set times — not only once the budget is exhausted.
Licence, maintenance and service terms are negotiated on the basis of market knowledge from over 1,200 projects — with a documented difference between the initial offer and the final agreement. In our experience, initial offers from ERP vendors consistently contain significant room for negotiation, particularly on maintenance rates, price-adjustment clauses and day rates for later change requests — precisely where costs accrue over the project's life and stay invisible in a simple price comparison.
Anyone running a construction project appoints an owner's representative accountable solely to them — not to the general contractor. In an ERP project, the decision consultant takes on that role: milestone acceptance, change-request control, escalation management and enforcement of agreed deadlines. Following the principle of "organisation before IT", this also includes checking whether organisational process changes fit the system — or whether the system is starting to distort the organisation.
Six and twelve months after go-live, the realised benefit is measured against the business case documented in the decision dossier: lead times, inventory coverage, process costs, data quality — depending on the original objectives. Only this step turns a decision into a verifiable result. It is also the component most often missing in consulting practice: after go-live, implementers and traditional selection consultants are already on to the next project.
How big is your ERP decision risk?
In a 30-minute initial consultation we identify together where the greatest decision risks lie in your project — before selection, before signing the contract, or mid-project. Vendor-neutral, with no implementation bias, based on over 1,200 projects in the DACH SME sector.
Book a risk-minimisation consultationVendor-neutral · no implementation bias · no obligation
Wholesale: A trading company faced a contract renewal with its existing vendor — "without alternative", according to internal assessments. The structured decision dossier, setting out genuine alternatives, did not initially change the system decision, but it shifted the negotiating position: only the documented, credible option to switch made the existing vendor willing to concede — on both terms and performance commitments.
Medical technology: In regulated environments, decision documentation is not optional but required — auditors and notified bodies expect to understand the rationale behind system-relevant decisions. The decision dossier became an integral part of the quality-management documentation, sparing the company from reconstructing decision paths under audit pressure.
Food industry: During a rollout, a contractually agreed stage gate was triggered: milestone acceptance revealed that promised industry functionality (batch traceability) was not at the agreed level of maturity. Because the gate carried consequences set out in the contract, the missing components were delivered rather than deferred — go-live was delayed in a controlled way, instead of an unfinished system going live.
Mid-sized companies in the DACH region, for whom the ERP decision is a six- to seven-figure investment and the most far-reaching IT decision of a decade. This is especially true when the advisory board, shareholders, auditors or financing banks expect a transparently documented decision — or simply when the experience isn't there, because the company last selected an ERP system fifteen years ago while the vendor runs such negotiations every week. Our project focus areas are wholesale, medical technology, food, and professional services.
Through an audit-proof, documented decision dossier with genuine alternatives, contractually anchored abort criteria, professional contract negotiation, and an independent party paid exclusively by the user company. Wrong decisions rarely come from the wrong software — but from unclear foundations, poor contracts and a lack of oversight.
It begins before the system decision and only ends after go-live: documented criteria and alternatives, abort thresholds in the vendor contract, negotiated terms with a documented delta, independent milestone acceptances, and the review of realised benefit against the business case.
Our methodology for exactly this end-to-end safeguarding: the independent assurance of the ERP decision across its entire lifecycle — from the decision dossier to the benefit assessment, as part of the DAA™ (Decision Architecture Assessment) approach, by a consultant who does not implement and is paid exclusively by the user.
The complete documentation of criteria, weighted alternatives, rejected options including justification, assumptions and risks — the document with which the decision can be defended at any time to the advisory board, shareholders and banks.
They provide research, but no responsibility: no liability for the recommendation, no moderation of internal conflicts of interest, no negotiation with the vendor, no independent acceptance. The mis-purchase risk lies precisely in this absence of responsibility.
For DACH SMEs with ERP investments in the six- to seven-figure range — especially where shareholder structures, advisory boards or bank financing require documented decisions.
|
|
Talk directly to Dreher's AI Assistant - Click the mic icon and ask out loud or type your question. Get expert answers in seconds, available 24/7.
Ask now by voice