The real cost of a failed ERP implementation
A failed ERP implementation in a mid-market business typically costs between two and five times the original project budget once you account for the extended implementation timeline, the business disruption during go-live, the cost of fixing what was built wrong, and the opportunity cost of the management bandwidth consumed for 12 to 24 months.
For a business with £20m to £100m turnover, that is often a £500k to £3m exposure - not counting the reputational and operational damage of a failed go-live with customers, suppliers, or regulators watching.
The difficult truth is that most ERP failures are visible in advance. The warning signs appear during selection and in the early months of implementation. The problem is not that they are hidden - it is that the people closest to the project have an interest in not escalating them, and the people with authority to act are not looking at the right things.
"We knew the implementation was in trouble at month three. The project team kept saying they would catch up. By month nine we had spent another £800k and were no closer to go-live. We brought in independent oversight eight months too late."
- CFO, manufacturing business, post-SAP B1 implementation
Warning signs during ERP selection
These signals appear during vendor evaluation and procurement. Each one individually is a yellow flag. More than two together is a red one.
The vendor is driving the requirements
If the shortlisted vendor is helping you define what you need, your requirements process is compromised before it has started.
No one is responsible for vendor management
If the selection process has no independent owner - or is run by the vendor's preferred implementation partner - the evaluation has a structural conflict of interest.
The demo covered the standard product only
If you have not seen your specific processes run in the system - not a standard demo - you do not know what you are buying.
TCO was not modelled beyond licence fees
Licence and implementation fees are typically 30 to 50% of the total five-year cost. If no one has modelled training, support, integration, and upgrade costs, the business case is based on incomplete data.
References were not followed up seriously
Vendor-provided references will tell you what the vendor wants you to hear. Independent reference checks - particularly with businesses that had a difficult implementation - tell you what you actually need to know.
The contract has not been reviewed by someone who does this
Standard vendor contracts are written to protect the vendor. If no one has reviewed the contract for acceptance criteria, change order provisions, and go-live milestone definitions, you are exposed.
Warning signs during implementation
These signals appear after contract signature and during delivery. If you are seeing three or more, the project needs independent review now.
The project has already missed its first milestone
Early milestone slippage is the single most reliable predictor of overall project delay. It is not caught up - it compounds.
Scope is growing without formal change control
Undocumented scope additions are being absorbed into the project with no impact assessment on cost or timeline.
Business stakeholders are too busy to engage
If process owners and department heads are not attending workshops, reviewing designs, or signing off requirements, the implementation is being built on assumptions rather than validated requirements.
Data migration has not started
Data migration is consistently the most underestimated phase of an ERP implementation. If it has not started by the halfway point of the project, the go-live date is unrealistic.
Testing is being compressed to meet the go-live date
When the project is behind and the go-live date is fixed, testing is the first thing cut. This is how system failures at go-live happen.
The steering group is not receiving independent status
If the only implementation status the board sees comes from the implementation partner, there is no independent check on whether the picture being presented is accurate.
If you are seeing three or more of these signals during implementation: commission an independent health check now. A two-week assessment by someone with no stake in the current delivery will tell you what the project team cannot.
The most common ERP selection mistakes
Selecting based on the demo, not the fit
ERP demos are designed to show the system at its best in standard scenarios. Most ERP failures begin with a selection decision based on an impressive demo of functionality the business will never use, while the specific edge cases that matter to the business were never tested.
Good selection processes require vendors to demonstrate your processes - not their standard demo paths - in the product. The difference in what you learn is significant.
Choosing the cheapest implementation partner
The implementation partner selection is more consequential than the ERP selection in most mid-market projects. The platform difference between Sage 200, SAP Business One, Epicor, and Infor is much smaller than the delivery capability difference between implementation partners. The partner with the lowest day rate is frequently not the partner with the best delivery record.
No independent challenge during procurement
Mid-market businesses frequently run ERP selections without any independent technology advisory. The result is that the vendor community - which has deep procurement experience and a strong commercial interest in the outcome - is negotiating against a team that has never done this before. The commercial and contractual terms reflect that asymmetry.
Underestimating the internal resource requirement
ERP implementations require significant business-side resource: process owners, data owners, IT resource, and change management capability. Businesses that plan for implementation partner resource but not for the internal commitment required consistently run into engagement gaps that delay delivery and reduce quality.
What independent oversight looks like
Independent ERP oversight is not about auditing the implementation partner or adding governance overhead. It is about ensuring that the business has an independent view of delivery status, that risks are identified and escalated before they become crises, and that commercial and contractual decisions are made with full information.
In practice this means:
- Independent status reporting to the steering group or board - not from the implementation partner, but from someone with no commercial interest in the delivery outcome.
- Regular delivery assurance reviews that look at schedule, scope, data migration, testing, and change readiness - not just RAG status against milestones.
- Commercial and contractual oversight of change orders, acceptance criteria, and milestone claims - particularly important in fixed-price contracts where the commercial incentives of the implementation partner diverge from those of the business.
- Go-live readiness assessment conducted independently of the implementation partner in the four to six weeks before go-live - the point at which unrealistic optimism about readiness is most dangerous.
The cost of independent oversight on a mid-market ERP project is typically 3 to 8% of the total project cost. The cost of not having it, when a project goes wrong, is typically 50 to 200% of the original project budget.
Is your ERP project showing these warning signs?
Assured Velocity provides independent ERP oversight and technology advisory for mid-market organisations. Vendor-neutral, no implementation revenue, no conflicts of interest.