Many businesses operate successfully at lower scale with “good enough” systems. Spreadsheets bridge gaps. Teams know the workarounds. Customer expectations are manageable. At £30m, this can be a rational approach.
At £90m, the same approach becomes fragile.
ERP and WMS decisions at mid-market scale are rarely just technology decisions. They are operating model decisions. They determine how the business will plan, control inventory, manage productivity and sustain service as complexity increases.
Why systems become unavoidable as complexity rises
As a business grows, several things happen. Inventory locations increase. Order profiles fragment across channels. Customer requirements become less forgiving. Volume peaks become more severe. Without robust system discipline, accuracy drift and planning instability grow quickly.
At this stage, the cost is not only operational. It becomes commercial: service penalties, lost customers, excess working capital, and leadership distraction.
Why implementations fail to deliver benefit
Many ERP/WMS projects fail not because the software is wrong, but because the programme is led as an IT milestone rather than an operational transformation.
When processes are not redesigned, the system embeds inefficiency. When operational ownership is weak, adoption falters and workarounds multiply. When go-live is treated as “completion”, the stabilisation period is neglected and performance dips persist.
In practice, the difference between success and failure is leadership and governance.
What successful programmes do differently
Successful mid-market implementations are operationally led. They define the desired operating model first: how inventory will be controlled, how work will be planned, how performance will be measured, how exceptions will be handled, and what discipline is required.
Only then do they configure the system to support that model.
They also plan explicitly for the performance dip: additional management presence, clear issue escalation, realistic ramp-up, and stabilisation routines. This reduces the risk of service disruption and helps teams adopt the new way of working.
A structured programme approach matters because systems programmes involve many moving parts and stakeholders. Project-led governance de-risks delivery by sequencing changes, protecting peak periods, and ensuring operational readiness—not just technical readiness.
Support
If systems change is on the horizon, the most useful question is often not “which system”, but “what operating model are we trying to achieve?” A short discussion can help clarify readiness, governance and risk—before the business commits significant time and cost.