Your ERP implementation is 6 months behind.
And I’m willing to bet it’s not the technology’s fault.I’ve been called into enough derailed ERP projects to know the pattern. The platform — SAP, Oracle, NetSuite, it doesn’t matter — is rarely the problem.
What fails is everything around it.
Here’s what I see again and again:
1. Scope was agreed before anyone really understood the data. The integration requirements looked clean in a demo. They weren’t.
2. The implementation partner optimised for go-live, not for you. Once they hit their milestones, accountability gets thin.
3. The internal team was stretched across their day job and the project. Nobody had the bandwidth to push back when things started slipping.
4. Bolt-on systems were an afterthought. Blackline, Concur, Invoicera — the ERP is only as good as its integrations. If those connections are messy, your data is messy.
5. There was no independent voice in the room. Nobody whose job it was to protect the outcome, not the project plan.
A delayed ERP implementation isn’t just a cost overrun. It’s months of clean data you’ll never get back, and audit and compliance risk that doesn’t disappear when you go live.
If your implementation is off track — or you’re about to start one and you want to get ahead of this — I’m happy to share what I’ve learned the hard way.
What’s been your biggest ERP implementation challenge?
I’m curious what others are experiencing — let’s talk.
Email us at info@saoirseconsultants.com, or call us on +1 214 230 1706
