Most ERP implementations that disappoint don't fail because the software was wrong. They fail because the business treated it as a software decision in the first place.
An ERP system touches finance, inventory, procurement, sales and operations at once, and for regional groups it often spans several countries, currencies and tax regimes. That makes it one of the few technology decisions that genuinely reshapes how a business runs. It is exactly why it can't be handed entirely to IT, or to whichever vendor gave the best demo.
The real question isn't "which system?"
Before comparing platforms, the more useful questions are usually about the business itself: Where does information currently get stuck? Which decisions are delayed because the numbers aren't trusted? Which manual processes are quietly absorbing hours every week? A system chosen to answer those questions will look very different from one chosen off a feature checklist.
Configuration is a business decision, not an IT task
The way an ERP is configured encodes decisions about how the business actually wants to operate: the chart of accounts, approval workflows, inventory valuation, reporting structure and, for groups, how entities in different countries consolidate. Getting this right requires someone in the room who understands both the finance and operations side of the business, not just the technical side of the software.
Adoption is where most value is won or lost
A perfectly configured system that people route around is worth less than a simpler one people actually use. The businesses that get real value from ERP treat rollout as a change-management exercise as much as a technical one, with training, clear ownership and a realistic timeline for people to adjust.
Before you speak to any ERP vendor, be able to answer:
- Which three management decisions are hardest to make today, and what information is missing?
- How should the chart of accounts, branches, cost centres and product lines be structured for reporting?
- Who inside the business will own the system after go-live?
- Which processes need to be fixed first, so you don't automate a broken one?
What this means in practice
Before starting an ERP conversation, it's worth being able to answer one question: what decision is currently hard to make because of missing visibility? That answer, not the software category, should set the direction. Technology should follow the business problem, not the other way around.