What It Actually Means
The idea is a single source of truth. A sale updates stock, triggers purchasing, posts to the ledger and appears in reporting, without anyone re-entering it anywhere.
Why It Is A Bigger Decision Than It Looks
An ERP is not a tool the business uses. It becomes the way the business runs.
That is what makes it the largest software commitment most companies make, and why the failures are so expensive. Replacing one later is a multi-year undertaking, so the decision has a very long tail.
It also means the implementation is a change programme rather than a software installation, and treating it as the latter is the single most common reason they go wrong.
How They Actually Fail
Rarely because the software cannot do the job. The recurring causes are organisational.
Configuring it to match existing processes. Businesses insist the system work the way they always have, which means heavy customisation, which makes upgrades painful and permanently expensive. The processes were frequently shaped by the limitations of the old system, so they are being preserved for no reason.
Underestimating the data. Years of accumulated records, duplicated, inconsistent, with fields used for things they were not meant for. Cleaning and migrating it is usually the largest single piece of work and it is consistently underestimated.
Nobody senior owning it. Delegated to IT, it becomes a technical project without the authority to change how people work, which is the entire point.
Training treated as an afterthought. Staff who do not understand it revert to spreadsheets alongside it, and the single source of truth immediately stops being one.
Do You Actually Need One
For many small and mid-sized businesses, the honest answer is no.
Good accounting software, a decent stock system and a CRM, properly connected, deliver most of the benefit with far less risk and cost. The connections matter more than the consolidation, and connecting three good tools is a considerably smaller undertaking than replacing all of them.
The genuine trigger is not size. It is when the seams between systems have become the dominant cost: when reconciliation between finance, stock and sales consumes real time, when nobody can produce an accurate operational picture without assembling it by hand, and when the manual re-entry between systems is a permanent tax.
What To Ask
- What specifically are we fixing? If it is “our systems do not talk”, integration may be far cheaper.
- How much customisation is proposed? Every customisation is a permanent cost and an obstacle to upgrading. Adapting the process is usually better than adapting the software.
- Who owns this internally, and do they have authority to change processes? If nobody, stop.
- What is the data migration plan, and has a trial import been run? Ask before agreeing a price.
- What does this cost annually, including support and the partner? The licence is frequently the smaller half.
The Alternative Worth Considering
For businesses whose operation is genuinely distinctive, a middle path exists: keep standard tools for standard functions, and build the operational layer that is actually yours.
That avoids both bending the business to fit a product and paying to customise a large system into something it was not designed to be. It is the reasoning behind an internal operations platform, and it suits businesses whose difference is the thing they would otherwise be configuring away.
More terms are in the glossary.
