Major ERP overhauls promise modernisations.
But cost, disruption, and internal bandwidth often tell a different story.
A large ERP upgrade is often compared to renovating a house while still living in it
Operations continue.
Deadlines remain.
Customers expect service.
Meanwhile:
- Teams split between project and daily work
- Scope expands as dependencies surface
- Pressure builds internally
The system may modernise.
But the organisation absorbs the strain.
Why Big-Bang Projects
Struggle
The Business Cannot Pause
- Finance close monthly
- Sales pipelines move
- Supply chains operate
There is no clean separation between project and business.
Scope Expands Quietly
- Integration surface
- Custom workflows complicate rollout
- Edge cases multiply
Initial timelines rarely stay fixed.
Cost and Fatigue Accumulate
- Budget increases
- Internal bandwidth tightens
- Key teams become project-heavy
Eventually, operational workarounds return just to keep pace.
A Different Approach Is Emerging
Some organisations are shifting away from the large, all-at-once transformation.
Instead, they:
- Start with one high-impact workflow
- Deliver value quickly
- Stabilise before expanding
- Roll out in controlled phases
Less disruption.
More control.
Clearer cost visibility.
The Strategic Question
Before committing to another large ERP, consider:
Workflow
Which workflow truly needs change first?
Internal Bandwidth
How much internal bandwidth is realistically available?
Outcome
What would a phased rollout look like instead?
Plan A Phased Modernisation
A short discussion to:
- Identify the first workflow to modernise
- Assess internal bandwidth
- Map a realistic phased rollout path
No technical deep dive.
No platform pressure.
Just structured clarity.
