Why ERP and systems projects stall in a cost-conscious market

Across middle-market companies, the reasons are consistent.

Unclear value makes projects easy to defer

When capital is constrained, projects without clearly defined outcomes are the first to lose support.

ERP initiatives often begin with broad goals – a consolidated chart of accounts, a six-day close, and three retired custom integrations – but lack a specific, measurable impact tied to the business. Without a clear connection to margin improvement, cash flow, or operational efficiency, continued investment becomes difficult to defend.

In this environment, systems projects must be positioned as value drivers, not infrastructure upgrades. Without that clarity, they are easily delayed or deprioritised.

Scope expansion outpaces execution

ERP implementations frequently expand beyond their original intent.

Additional modules, integrations, and customisation requests are layered in over time. While each may seem justified, the cumulative effect is increased complexity, extended timelines, and rising costs. In my experience, scope creep is often a symptom of incomplete current-state work.

Maintaining momentum requires disciplined scope management, focusing on what is necessary to deliver immediate, measurable impact.

Ownership and accountability Are diffused

Systems projects span multiple functions, including finance, operations, IT, and commercial teams.

Without clear ownership, decision-making slows and competing priorities emerge, making progress inconsistent. Delays are rarely caused by a lack of effort; they stem from a lack of alignment and accountability.

Projects that move forward tend to have a single point of ownership with the authority to drive decisions and maintain alignment across functions.

Change management is underestimated

Change management is usually the first line cut to meet the budget, and its absence is the single most common cause of slipped go-lives. 

ERP implementations are not just technology initiatives. They require meaningful changes to how the business operates. Processes shift. Responsibilities evolve. Daily workflows are disrupted. When this impact is underestimated, adoption slows and resistance builds.

In a more constrained market, organisations have less capacity to absorb that disruption. As a result, projects stall as teams struggle to balance execution with ongoing operations.

Sustained progress depends on clear communication, structured training, and alignment across the organisation.

Data and system readiness create friction

Legacy systems, inconsistent data, and fragmented processes often complicate implementation. The workarounds and shadow spreadsheets the legacy system quietly relies on are where future-state gaps hide. Stalled implementations are often traced back to incomplete current-state discovery before vendor selection.

When data is unreliable or incomplete, integration becomes more difficult. Timelines extend as teams work to reconcile issues and establish a usable foundation.

In a cost-conscious environment, these delays are harder to absorb. What might have been manageable in a different cycle becomes a reason to pause or scale back.

Preparation with clean data, defined processes, and clear system architecture reduces this friction and supports execution. Cataloguing every function the current system performs is the highest return-on-investment step before vendor selection.

What keeps projects moving

ERP and systems initiatives that continue to move forward in this environment tend to share a common set of characteristics:

• A clearly defined link between the project and financial or operational outcomes;
• Disciplined scope aligned to immediate business priorities;
• Strong ownership with authority to drive cross-functional decisions;
• Realistic timelines based on execution complexity and organisational capacity;
• Early investment in data readiness and process definition; and
• Change management funded as a line item, not a contingency.

These factors shift the conversation from cost to value, making it easier to sustain momentum under tighter constraints.

Closing thoughts

In every implementation I’ve led, the technology was the easy part. Preparation, ownership, and the people’s work were where projects stalled or succeeded.

When projects stall, it’s rarely due to the technology itself. More often, it reflects unclear priorities, misalignment, or insufficient preparation. Addressing those factors not only keeps initiatives moving, it also ensures the investment delivers the visibility, efficiency, and control required to operate effectively in a more demanding market.

---

Luke Mattorano is an area director with SeatonHill Partners. He brings more than 20 years of experience leading accounting, finance, and operations for middle-market and PE-backed companies. He has served as CFO, director of finance, and operating executive across manufacturing, SaaS, and healthcare sectors.