Making the Case for ERP Investment Internally: A Guide for Finance and Operations Leaders

13 May, 2026

You know your business needs better systems. The spreadsheets are multiplying. Month-end reporting takes days that it should not. Production planning happens in someone's inbox rather than in the system. Stock discrepancies are a recurring conversation at every management meeting.

You have seen the demos. You understand what a well-implemented ERP can do. But you still have not got sign-off.

This is not an unusual position. For many finance and operations leaders in mid-sized manufacturing and distribution businesses, the internal case for ERP investment is harder to make than it should be. Senior stakeholders are cautious. Boards remember hearing about costly, disruptive implementations that took twice as long as planned. And without a clearly structured case, the conversation stalls.

This guide is designed to help you move past that. We will walk through how to build an internal case that speaks to the people who make the decision, addresses the objections you will face and gives your proposal the credibility it needs to succeed.

Why the internal case is often harder than it should be

Most ERP champions inside a business come from operations, finance or IT. They understand the operational pain. What they sometimes struggle with is translating that pain into the language that boards and senior leadership respond to: risk, return and strategic alignment.

There is also a credibility gap to overcome. ERP projects have a well-publicised history of cost overruns and delays, and those stories linger. A proposal that does not acknowledge this directly will lose credibility before it gains traction.

The good news is that the data tells a more positive story than the headlines suggest. Research consistently shows that organisations which carry out structured ROI analysis before implementation and have been live for more than a year report a strong return. According to figures published by DocuClipper, businesses typically see a return of £1.52 for every £1 invested — an average ROI of 52% — and 83% of organisations that conducted an upfront ROI analysis said the project met or exceeded their expectations.

The problem is not usually the investment itself. It is how the case gets made.

Know your audience before you write a word

The most common mistake when building an internal business case is writing it for yourself rather than for the decision-makers. A document full of system capabilities and integration diagrams may resonate with your IT team but will not move a finance director or managing director.

Before you start, identify who will ultimately approve the investment and what they care most about. In most manufacturing SMEs, that means considering three distinct perspectives.

The finance director or CFO

Finance leadership will be focused on cost, risk and measurable return. They will want to understand total cost of ownership over the medium term, not just the headline licence fee. They will be sceptical of benefit projections that are not grounded in operational evidence. And they will expect to see a credible payback timeline.

The key is to present the cost of inaction alongside the cost of investment. Hidden costs that are easy to overlook include time spent on manual workarounds, reporting delays and the downstream consequences of poor data quality on decisions. These are real costs, even if they are not always visible on the P&L.

The managing director or CEO

Leadership will be thinking about competitive positioning, risk and growth capacity. They want to know whether the business can scale without adding proportional headcount. They want confidence that the organisation's data is reliable. They are also acutely aware that the manufacturing sector is under increasing pressure to digitalise, and that standing still carries its own risks.

UK manufacturing is not immune to these pressures. The UK ERP software market was valued at approximately £4.5 billion in 2024 and is projected to grow at a compound annual growth rate of around 9% through to 2035, driven in large part by manufacturing and distribution sector demand. Businesses that delay investment risk falling further behind competitors who are already gaining operational advantage through better data and more integrated processes.

The operations or production director

If this is not already you, you need them on your side. Operational leadership will be concerned about disruption, adoption and whether the system will actually work for the people on the floor. Credible references from businesses of a similar size and sector are more persuasive here than any feature list.

The five pillars of a credible business case

A strong internal case for ERP investment rests on five elements. Miss any of them and the proposal becomes easier to reject.

1. The current state: quantify the pain

Start by documenting what the status quo is actually costing the business. This is often the most powerful part of the case, because it makes visible costs that have become invisible through familiarity.

Useful areas to quantify include:

Hours spent each week on manual data entry, rekeying between systems or correcting errors
Time taken to produce management accounts, weekly reports or production plans
Stock discrepancies and their commercial impact, including write-offs, emergency purchases or customer service failures
Overtime or additional headcount absorbed by process inefficiency
Decisions delayed or made on incomplete data

The goal is not to be exhaustive but to attach real numbers to problems that previously existed only as frustrations. Even conservative estimates, when multiplied across the working year, tend to produce figures that command attention.

2. The future state: realistic and evidence-based benefits

Present the benefits in operational terms that your audience recognises, backed by evidence wherever possible.

Evidence from published research provides a useful baseline. Among businesses that have implemented ERP, 91% reported optimised inventory levels, 78% reported improved productivity and 62% reported reduced costs in purchasing and inventory control. For a mid-sized manufacturer, even partial gains in these areas translate to meaningful financial impact.

Where possible, benchmark against your own current metrics. A reduction in stock holding days, a faster month-end close or a measurable improvement in on-time delivery are all credible, commercially relevant outcomes.

Be careful not to overclaim. A business case that promises transformation without evidence will be challenged. Modest, well-supported projections are more persuasive than ambitious ones that cannot be substantiated.

3. Total cost of ownership: full transparency

One of the most common reasons business cases fail at approval is that hidden costs emerge later and undermine trust. Present the full cost picture from the outset, including:

Software licensing or subscription costs
Implementation and consultancy fees
Data migration
Internal time commitment during implementation
Training and change management
Ongoing support and annual maintenance

For mid-sized businesses, research suggests that ERP ownership typically represents around 3 to 5% of annual revenue. Presenting this in the context of the business's size and the projected return makes the investment proportional rather than alarming.

Phasing the investment can also make the financial profile more acceptable. A staged approach that begins with core modules and extends functionality over time often reduces upfront cost and allows early wins to fund subsequent phases.

4. Payback and return on investment

Translate the benefits into financial return and present a realistic payback timeline. Most ERP projects in the SME space achieve payback within two to three years, with the average across published research sitting at approximately 2.5 years.

Presenting a simple payback model alongside a three-year total cost of ownership gives decision-makers a clear picture of the financial trajectory. Net present value and internal rate of return calculations add rigour if your finance leadership expects them, but for most SMEs a straightforward cost versus benefit analysis over three years is sufficient.

The key is to be honest about the assumptions underpinning the model and to invite scrutiny rather than avoid it. A business case that acknowledges uncertainty and explains how it has been handled is more credible than one that presents overly precise projections.

5. Risk: address it before they raise it

Every decision-maker in the room will be thinking about risk. Address it directly.

The most common concerns are implementation disruption, user adoption and cost overrun. For each, prepare a specific response:

On disruption: a phased implementation plan, a realistic timeline and a clear description of what will remain operational throughout. Experience from comparable businesses is valuable here.

On adoption: describe your change management approach. Who will champion the system in each department? How will training be delivered? What does the go-live support plan look like?

On cost: explain how the implementation will be scoped and managed, what contingency is built in and how scope creep will be controlled. Choosing an experienced implementation partner with sector-specific knowledge significantly reduces this risk, and that is worth saying explicitly.

Common objections and how to handle them

Even a well-constructed case will face pushback. Prepare for the objections most likely to arise.

"We tried this before and it did not work"

This is the most emotionally loaded objection and needs to be handled with care. Acknowledge the previous experience directly. Then explain what is different this time: the implementation approach, the partner, the scoping methodology or the level of internal preparation. Show that the lessons from the previous attempt have informed the current proposal.

"The timing is not right"

This is often code for either "I am not convinced" or "I do not want the disruption." Dig into which it is. If it is the former, you have a case-building problem to solve. If it is the latter, address the disruption concern directly with a phased plan and a clear description of how day-to-day operations will be protected.

It is also worth noting that there is rarely a perfect time to implement ERP. The question is not whether the timing is ideal but whether the cost of delay is greater than the cost of acting now. For many businesses, the answer is yes.

"Can we not just improve what we have?"

Sometimes the answer is yes, and you should be honest about that. If the current system is fundamentally capable but poorly configured or underused, optimisation may deliver significant gains at lower cost and risk.

But if the current system is creating structural limitations on growth, visibility or operational control, the case for investment becomes stronger. Being willing to acknowledge the nuance here actually builds credibility rather than undermining it.

"What happens if we do nothing?"

This question is less often asked than it should be. The answer is that inaction is not cost-free. The operational costs documented in your current state analysis continue to accumulate. Competitive disadvantage grows as peers invest. And the eventual cost of change only increases as technical debt and workaround complexity compound over time.

Getting the right implementation partner in your corner

One element that can significantly strengthen an internal business case is the involvement of a credible, experienced implementation partner from an early stage.

A specialist partner brings several things that are difficult to replicate internally. They can provide realistic cost and timeline benchmarks drawn from comparable projects. They can help translate operational pain into quantified financial impact. And they can give your senior leadership confidence that the project will be managed by people who have done this before, in businesses like yours.

For manufacturers and distributors, that sector specificity matters. An ERP partner who understands the particular challenges of UK manufacturing, from production planning and stock management to traceability and compliance, can frame the case in terms that resonate with your leadership team.

Organisations that work with a specialist implementation consultant are significantly more likely to report successful ERP outcomes. That is not a coincidence. The right partner does not just implement the system. They help you make the case, plan the change and protect the investment.

A practical next step

If you are at the stage of building an internal case for ERP investment, the most useful thing you can do before committing to a formal proposal is to establish a clear baseline.

That means documenting the current state in operational and financial terms, identifying the specific outcomes that matter most to your decision-makers and having a frank conversation with a specialist who can help you assess whether the investment is right for your business right now.

At HIT Technology, we work with manufacturers and distributors across the UK and Ireland who are at exactly this stage. We offer a free systems evaluation designed to help you understand where your current systems are falling short, what a realistic improvement looks like and what the financial case for change might be.

There is no obligation and no hard sell. Just a practical, experienced conversation that gives you something concrete to take back to your board.

Go back