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

Why Choose Us?

We can drive the change you need to stay ahead of the curve – ask us how.

Newsletter Signup

Frequently Asked Questions

How can Nine Feet Tall help with ERP planning? 

Nine Feet Tall helps organisations develop robust ERP plans that align business goals, technology requirements and change management activities. Our experienced consultants support every stage of the planning process, helping to create the foundations for a successful ERP transformation.

Who should be involved in ERP planning?

Successful ERP planning involves stakeholders from across the organisation, including leadership teams, operational managers, IT teams and end users. Early engagement helps ensure the solution meets both business and technical needs.

When should ERP planning start?

ERP planning should begin before system selection or implementation. Early planning helps organisations understand their requirements, define success measures and establish realistic budgets and timelines.

Why is ERP planning important?

Effective ERP Planning reduces risk, improves stakeholder alignment and creates a clear roadmap for implementation. A strong plan helps organisations avoid costly delays, scope creep and adoption challenges.

What is ERP planning?

ERP planning is the process of defining the objectives, requirements, resources and approach needed for a successful ERP implementation or transformation programme. It helps organisations align people, processes and technology before delivery begins.

What common mistakes should I avoid when using storytelling in business cases?

Avoid overly complex language, neglecting data, or failing to connect emotionally with your audience. Also, steer clear of being too technical for non-experts and ensure your story aligns with the stakeholders’ interests and concerns.

How do I tailor my business case story for different stakeholders?

Tailor your story by understanding each stakeholder’s priorities, adjusting the focus to address their specific interests, using relatable language, and highlighting the most relevant aspects of the investment for their role.

How can storytelling improve my business case for technology investment?

Storytelling enhances your business case by making complex information engaging and memorable, helping decision-makers visualise benefits and creating emotional connections that make your proposal stand out.

Latest Thoughts

11 November 2026

AI in the Charity Boardroom: The Trustee’s Checklist

Read More
05 November 2026

The ERP decision that matters most happens before you commit

Read More
15 October 2026

Conscious AI Summit: People First. AI Second.

Read More
Red and white picnic rug - Retal Digital Readiness
29 September 2026

Growth by Acquisition: Why Retail M&A Success Depends on Digital Readiness

Read More
Orange toy car on a wooden floor - ERP Change Management
22 September 2026

What Is ERP Change Management? A Practical Guide for Business Leaders

Read More
Blue light switch on white wall - Change Capability Maturity
29 July 2026

How Mature Is Your Change Capability?

Read More
3 eggs on a white background - AI Transformation Investment
22 July 2026

Why your AI investment needs Change Management from day one

Read More
Flock of Starling Murmuration - ERP Adoption in Energy and Utilities Sector
09 July 2026

Why ERP User Adoption Matters More Than Implementation

Read More
IT Change - Orange Hot airballoon at dusk
27 May 2026

Preparing for Fast-Paced IT Change

Read More
Owl on blue sky background - digital transformation strategy
14 May 2026

Digital Transformation Leadership: Building Readiness

Read More
Orange clouds over mountain tops - Nine Feet Tall ERP Implementation
13 May 2026

Landmark transformation programme for PA Media Group

Read More
King and Queen Chess Pieces - ERP Leadership
06 May 2026

Stages of ERP Implementation: A Leadership Guide

Read More
13 February 2026

Choose your Perfect Partner: Get Maximum Value from Technology Selection

Read More
05 January 2026

Esther McMorris steps down from Nine Feet Tall

Read More
Orange Theatre Seating
04 June 2026

What Project Assurance Should Actually Do: The Ultimate Checklist

Read More
Old fashioned alarm clock on an orange background
28 October 2026

Change Management Plan for ERP Implementation: A Step-by-Step Guide

Read More
Packing boxes against an orange wall - ERP Upgrade Readiness
22 October 2026

10 Questions Every CIO Should Answer Before an ERP Upgrade

Read More
Bucket and Spade on a sandy beach - retention int he charity sector
08 October 2026

Retaining Talent in the Charity Sector

Read More

How we’ve helped our clients thrive

Case studies