Failed Projects, Contract Traps and Official Sources

Why ERP projects run over time and budget, the contract terms that cost the most later, privacy and data risks, and where to get official help.

Most expensive ERP problems are set up before go-live: a vague scope, a fixed-price quote with a long list of exclusions, a contract that auto-renews at a higher price, or no plan for getting your data out. These guides describe the common patterns generically and show what to do instead.

Start with why ERP projects fail and how to avoid it. Then read about budget overruns and how much contingency to hold, contract traps and the unfair contract terms law, planning your exit and data export, SLAs, uptime and support levels, and privacy, data breaches and where your data is stored. The disputes and official sources guide lists the regulators and free services that help small businesses with software disputes.

This site gives general information, not legal or tax advice. For a large contract, a dispute or a data breach, get advice from a lawyer, tax agent or the relevant regulator.

Failed Projects, Contract Traps and Official Sources

Guides in this topic

Failed Projects, Contract Traps and Official Sources

Why ERP projects fail and how Australian SMEs can avoid it

The recurring patterns behind failed or troubled ERP projects, the warning signs at each stage, and the practical controls that small and mid-sized businesses can put in place.

5 min read