Explore reported software failures
A troubled ERP project can disrupt orders, operations, customers, and financial reporting. These reported cases show how problems have affected software investments at different scales. The gallery also includes other enterprise systems that support essential business operations.
Choose a range to explore the cases.
The ranges above are guides. Public reports may cite software fees, implementation spending, business losses, or damages sought in a lawsuit. Those figures are not directly comparable, and a project’s consequences can exceed its original budget. Some accounts describe allegations rather than court-established findings; each case links to its source.
What to look for in these cases
As you read, consider the decisions made before problems appeared:
Was there a clear business reason to replace the existing system?
Did the buyer define and prioritize what the new software needed to accomplish?
Did demonstrations verify important capabilities, exceptions, and controls?
Were the vendor’s responsibilities, scope, and acceptance criteria clear?
Were data, users, integrations, and operations ready for go-live?
A troubled project rarely has just one cause. These questions help you examine risks before committing to a product or implementation plan.
Make the ERP decision before committing to the project
If you are considering replacement, first establish what your current ERP is holding back and whether a new system is worth the cost and disruption. Wayferry’s standalone, fixed-fee ERP Replacement Decision Assessment gives your leadership team a documented recommendation: keep the current ERP, replace it later, prepare before replacing it, or proceed now.
Already decided to proceed?