Odoo

Seven signs an ERP project is about to fail

Failed ERP projects rarely collapse suddenly. They drift for months while everyone is individually busy and collectively stuck.

Pandoratech·28 September 2026

Scope that lives in an inbox

If the answer to "is that included?" requires searching email, the scope is not written down. A change that nobody priced is a change that will be argued about, usually at the worst moment. A written scope with an explicit exclusions list is uncomfortable to produce and saves the project.

No single owner on the client side

An ERP touches finance, sales, operations and HR, and every one of them has an opinion. Without one named person who can decide between conflicting preferences, decisions get deferred to a meeting that keeps not happening. This is the most common cause of slipped timelines, and it is not something the vendor can fix.

Data and testing left until last

Data cleanup and user testing are the two tasks most often deferred, and the two that most reliably extend a project when deferred. Both surface problems that change configuration decisions, which is precisely why they need to happen while there is still time to act on what they reveal.

Related services

Frequently asked questions

Can a failing implementation be rescued?

Usually, yes. It starts with an audit that establishes what is actually configured versus what was assumed, which becomes the documentation the project never had. Pandoratech takes on systems implemented by other partners after that audit.

How long should an implementation take?

Pre-configured industry editions go live in one day. Custom implementations run 45 to 90 days depending on modules, users and integrations. A project materially past that range without a scope change is worth reviewing.