Why most ERP implementations fail — and how the best contractors avoid it
Most ERP projects in construction fail to deliver ROI. The issue isn’t the software — it’s the implementation model. Here’s what separates success from expensive failure.
Most ERP projects in construction fail to deliver ROI. The issue isn’t the software — it’s the implementation model. Here’s what separates success from expensive failure.
What you’ll learn
Most ERP implementations in construction fail not because of the software, but the model. Learn the four common failure modes and how leading contractors avoid them.
Every year, UK contractors spend millions on ERP implementations that don’t deliver. Projects overrun, adoption stalls, and finance teams end up reverting to spreadsheets within months. The software gets blamed, consultants move on, and the business is left with sunk costs and broken trust in technology investment.
The software is rarely the problem. The implementation model usually is.
Many ERP projects are scoped in a way that looks comprehensive on paper but is unrealistic in practice. The scope is defined by what the software can do, not what the business actually needs. This produces an implementation plan that’s technically correct but commercially undeliverable — because no contractor can dedicate the internal resource required to a full-scope ERP implementation while running live projects.
ERP configuration is a business design exercise. How you structure your chart of accounts, define your project hierarchy, set up your approval workflows — these decisions shape how the business will operate for years. When configuration is delegated to technical teams without sufficient business involvement, the result is a system that works technically but doesn’t reflect how the business actually runs.
We work with construction, engineering and manufacturing businesses to identify technology opportunities and build practical digital roadmaps.
Finance teams are asked to change how they work — often significantly — with limited preparation time and minimal ongoing support. When the system behaves differently from expectations, there’s no one to call. Workarounds develop. The old spreadsheets come back out.
A big-bang go-live — switching everything over at once — concentrates all the risk into a single moment. When problems emerge (and they always do), there’s no fallback. The business is simultaneously dealing with the pressure of live operations and the instability of a new system.
The contractors who successfully implement ERP systems share a consistent approach. They scope to a core that is deliverable in 90–120 days, not a comprehensive vision that takes 18 months. They treat the first phase as a foundation — getting financial management, project accounting, and reporting working reliably — before adding complexity.
They involve senior finance and commercial people in configuration decisions, not just IT. They run parallel operations during go-live, not a hard cutover. And they build in post-go-live support that lasts long enough for the team to genuinely embed the new ways of working.
The implementation partner matters more than most businesses realise when they’re selecting software. A partner who has delivered the same system in the same industry — who knows the common configuration pitfalls, the typical adoption challenges, and the failure modes to avoid — is worth significantly more than a cheaper generalist.
At Rubik, we work exclusively with construction, engineering, and manufacturing businesses. We’ve implemented Sage Intacct across dozens of contractors, and we’ve seen the same failure modes repeat themselves. Our implementation model is built around avoiding them — phased delivery, business-led configuration, structured change management, and ongoing support that doesn’t end at go-live.
Rubik works with industrial businesses to develop digital strategy, identify opportunities for data and technology, and implement the right solutions at the right time.
