The Role of the ERP Business Case
The ERP business case is not the approval document. It is the leadership contract.
Let’s explore how C-suite teams can align investment, delivery reality and value before committing to change.
ERP investment decisions often look like technology decisions: Which platform to choose, what to include and how much it will cost. But the more difficult questions sit underneath. What is preventing the organisation from performing as it needs to? What is it prepared to change? And who will remain accountable once the programme moves from approval into delivery?
A credible ERP business case should therefore do more than secure funding. It should help leaders agree the value they expect, the risks they are prepared to take, the capacity the organisation needs and the trade-offs they may have to make. If it cannot guide those conversations before approval, it is unlikely to protect the investment afterwards.
Start by tackling the constraints
Starting with features can lead the discussion towards a solution before there is agreement on the problem. A stronger case begins with what is holding the business back, whether that is fragmented data, weak controls, slow decision-making, inconsistent processes, operational exposure or an inability to support the organisation’s strategy.
This matters because an ERP cannot deliver value by itself. Technology can support greater standardisation, visibility and control, but the benefits only emerge when processes, accountabilities and behaviours change too. The case should explain not only what the organisation will buy, but what will work differently and why that difference matters.
For the C-suite, this creates a useful test: Is the investment addressing a significant business constraint, or simply improving the technology without resolving the underlying operating problem?
Turn the ERP business case into a decision matrix
Large investment cases can give a false sense of certainty. A single return figure may look convincing, but often relies on assumptions about adoption, productivity, data quality, organisational capacity and when the benefits will be achieved.
A useful business case separates evidence from assumptions and ambition. It shows which benefits can be measured, which outcomes are strategically important but harder to quantify, and which variables have the greatest impact on the recommendation. It should also show the downside: what happens if adoption is slower, more data remediation is needed or internal capacity is lower than expected?
This doesn’t need to slow the decision down. Instead, it gives leaders greater clarity on what must be true for the preferred option to remain credible, what can be phased or reversed, and which commitments will be difficult to undo. A realistic range is more useful than false precision.
Make the full organisational cost visible
Software and implementation are only part of the investment. The full view should also include data, integration, testing, business change, subject-matter expertise, backfill, training, transition, support and the effort needed to embed new ways of working.
This is often where the business case becomes more uncomfortable, but also more valuable. People may have been named without their time being properly funded. Operational leaders may be expected to manage design, testing and adoption alongside business-as-usual demands. The need for change may be recognised, whilst the capacity needed to deliver it is treated as free.
Making these assumptions visible enables the executive team to choose deliberately between scope, pace, cost and operational risk. Leaving them implicit does not remove the trade-off. It simply moves it into delivery, where it will usually be more expensive and difficult to resolve.
Compare credible routes… Including the choice not to act
A strong case considers credible alternatives rather than presenting one platform as inevitable. The options might include upgrading, replacing, modernising in phases or addressing specific process and control weaknesses first. Agreeing the decision criteria before assessing these routes helps prevent the preferred answer from quietly shaping the test.
The cost of delay should also be part of the discussion, but not as a scare tactic. Leaders need a balanced view of what continued fragmentation, manual effort, weak controls or platform exposure means for the business. The question is not only: ‘What will the programme cost?’ It is also, ‘Which risks and constraints are we choosing to carry if we delay it?’
Align executives around different, legitimate concerns
Executive alignment does not mean removing disagreement. The CIO may be most concerned with architecture, resilience and service continuity. The CFO will focus on affordability, controls, assumptions and accountability for benefits. Operational leaders need to judge whether the organisation can absorb the change whilst continuing to perform.
A credible business case brings these perspectives together rather than smoothing them into a general statement of support. It should record the important trade-offs, who has the authority to resolve them and what they mean for scope, pace, cost, readiness and adoption.
This is where the business case becomes a leadership contract. Approval is not simply permission to spend. It is an agreement about what the organisation will change, what leaders will resource and which outcomes they will own.
Keep the business case alive after approval
The assumptions made at the start will change. Costs will become clearer, design choices will affect benefits, new dependencies will emerge and organisational capacity may shift. A business case that is filed away after approval cannot help leaders respond to any of this.
Instead, use it as an active governance tool. At each major decision point, review whether the evidence still supports the investment, whether benefit owners remain accountable and whether changes to scope or pace affect the value case. Benefits should inform design and prioritisation throughout delivery, rather than being rediscovered after go-live.
This supports a more realistic approach to benefits realisation. Go-live is a technical milestone, not the point at which value automatically appears. People need to adopt new processes, leaders need to reinforce new accountabilities, and the organisation needs enough capacity to stabilise and improve. The business case should reflect this reality rather than treating the change as complete when the system is switched on.
Five questions the investment committee should press
- What specific business constraint are we paying to remove?
- Which benefits depend on process, behaviour or operating-model change rather than technology?
- Which assumptions drive the cost and value range, and what would change the recommendation?
- What organisational capacity has been funded, not merely named?
- Who owns each benefit after approval, and how will governance respond if the evidence changes?
The decision is bigger than funding
The strongest ERP business cases do not remove uncertainty. They make the most important uncertainties visible, connect them to clear accountability and give leaders a practical way to govern the choices ahead.
This is what makes the case valuable at C-suite level. It turns a technology proposal into a controlled business decision, grounded in the organisation’s strategy, operating reality and ability to sustain change.
Bring clarity to your next ERP decision. Speak to Nine Feet Tall about building an investment case that connects strategy, delivery and lasting value: ninefeettall.com/contact