ERP deployment & implementation
ERP
Guides
Manufacturing SMEs

How to build the internal business case for a new ERP

August 21, 2026

|

Alex Barroux

How to build the internal business case for a new ERP

The people who know the company needs a new enterprise resource planning (ERP) system are rarely the people who approve the budget. Unfortunately, while operations sees stock corrections that arrive too late or quality records split across paper and spreadsheets, leadership sees cost and the risk of a large software project that could hamper the business.

To the people living with the reality of paper and spreadsheets, or a legacy ERP that takes time and effort from the team more than it helps bring efficiencies, the case for change feels obvious. But an ERP represents a big investment (time and money), so to make the case, the business must show:

  • What the current operating model costs
  • The risk(s) if nothing changes (ideally also quantified in terms of potential cost)
  • Which of these costs will be concretely removed on day one of ERP implementation

In other words, your internal ERP business case has to turn operational frustration into a decision finance, leadership, IT (if you have an IT team), operations, and users can understand. Here’s how.

Start with the business trigger

The best internal ERP cases start with the event, trend, or constraint that makes the timing critical.

Sometimes the trigger is growth. Order volume is rising, the team is hiring, product lines are expanding, and the informal system that worked at 10-15 people starts to crack as the employee count explodes to 25-50.

Sometimes the trigger is external pressure. For example, a major customer that asks for better traceability or a retailer that expects tighter delivery promises. Another common pressure is certification or compliance requirements that forces the company to prove what happened across purchasing, production, quality, inventory, and shipment.

Sometimes the trigger is strategic. The company wants to open a new factory, launch a new channel, bring subcontracted production in-house, or prepare for fundraising. The current system may still function today, but it cannot support the next stage without adding more manual coordination.

Whatever your trigger is, it should sit at the center of the case. Because if the reason for changing ERP is only "the system is frustrating," the project sounds optional. If the reason is "our next growth stage depends on operational visibility we do not have," the conversation changes.

For manufacturers, the signs of a critical trigger are usually easy to recognize:

  • Stock is close enough for accounting, but not reliable enough for daily decisions on the factory floor.
  • Production planning depends on one person rebuilding it by hand with context compiled manually on a weekly basis.
  • Quality, traceability, or batch records exist, but they are hard to use quickly.
  • Sales cannot answer delivery questions without asking operations.
  • Finance sees margin problems after the decision window has closed.
  • Managers trust the spreadsheet more than the existing ERP (if there is one).
  • New hires learn the process through people, not through a clear system.

Those signs show that the company has outgrown its current way of coordinating work. For a deeper timing test, the Bonx article on when ERP becomes a legitimate growth question covers the size, growth, and operational signals that usually make the ERP conversation serious.

Map who needs to be bought in, and how

An ERP business case is not one argument, but rather one decision seen from several angles:

  • Operations needs the new system to remove manual work, expose constraints earlier, and support the way work actually moves through the factory. If the business case ignores planners, buyers, operators, production managers, quality teams, or logistics, adoption will become a problem later.
  • Finance needs credible numbers. Not every benefit has to be perfectly precise, but finance does need to know which savings are real cash savings, which gains are capacity, which risks are being reduced, and which assumptions are estimates.
  • Leadership needs to understand why the project matters now. The case should connect ERP implementation to growth, customer promises, margin control, resilience, or operational risk.
  • IT needs to know what the ERP will own, what it will connect to, which tools stay in place, and where the security, data, and integration boundaries sit.
  • Users need a reason to believe the new ERP will make work easier. They have probably seen systems that create more clicking, more reporting, and more after-the-fact updates. If the business case cannot explain what gets easier for them, leadership should question whether the promised value will ever appear.

Many internal ERP projects drift because the case is too finance-led or too operations-led. If finance owns the whole ERP selection process, the factory can feel like a downstream data source.

That distinction matters when the ERP project is operational rather than financial. Bonx has written separately about why manufacturers should separate manufacturing ERP from finance ERP, because a factory system should not become a giant finance replatforming exercise by accident.

Quantify the cost of the current system

Once the trigger and stakeholders are clear, the case needs numbers. That does not, however, mean fake precision; ERP return on investment (ROI) models become unconvincing when they try to quantify every possible benefit. Better to start with a few fleshed out and very concrete costs.

For example, quantifying the cost of manual work can be an effective place to start. Count the hours spent on purely manual tasks like duplicate data entry, spreadsheet updates, production reporting, stock checks, supplier follow-up, quality record reconstruction, and reconciliation between operations and finance.

Margin leakage can also be an effective metric to consider. Look for late discoveries:

  • Material cost changes that reached sales too late
  • Urgent purchasing caused by missed shortages
  • Rework that could have been prevented
  • Expedited shipping used to recover a late order
  • … etc.

From those more concrete costs, work on quantifying the risk cost. What happens if a customer asks for traceability faster than the team can reconstruct it? What happens if a key person leaves? What happens if order volume doubles and the current process already depends on fragile manual decisions or time-consuming manual processes?

The existing Bonx guide to building a manufacturing ERP business case that gets approved goes deeper into the ROI model.

For the internal approval process, keep the model believable. That means separating observed numbers from estimates and naming a specific owner of each estimate so that one person can be held accountable. It can also be helpful to show conservative, likely, and ambitious scenarios instead of pretending one estimated figure is certain.

Just as important as modeling the costs and risks is modeling which of these costs will be removed and risks will be avoided by implementing an ERP.

A leadership team can challenge a model and still believe it. What it will not believe is a model that turns every possible benefit into guaranteed savings.

Define success criteria for your ERP

Before the team starts comparing vendors, define what the ERP has to do for the business to be considered a success. It can be helpful to pick three to five operational scenarios where the current setup breaks down. They should ideally be real enough that people in the company recognize them immediately, and fixing the current setup should have a real and quantifiable business impact that would be improved if the process was fixed.

For example:

  • A customer changes an order after production has started, and the team has to manually recalculate stock, purchasing, planning, and delivery impact. Ideally, quantify how much time is lost in the recalculation.
  • Sales needs a reliable delivery promise, but the answer depends on stock, capacity, supplier lead times, and one planner's memory. Include an estimate of amount of customer orders per month that are incorrect because of the inability to calculate this on the fly.
  • A quality issue blocks a batch, and nobody can quickly see which customer orders, shipments, or production steps are affected. How much time was lost or customer orders delayed in the last month due to this kidn of issue?
  • Operators record work on paper, then someone else updates the system later. Calculate time lost to double data entry over a week or month.
  • Purchasing discovers shortages too late because demand, stock, and supplier commitments are not connected. Quantify the resulting production delays.

These scenarios should become the internal standard for ERP evaluation and implementation. If a vendor can show a polished module list but cannot show how it will concretely resolve these problems, the business case is at risk.

By focusing on business problems as success criteria, the buying question becomes more concrete. Which system can prove value quickly on the operational flows that matter most, then keep expanding as the business changes?

Answer the objections before the approval meeting

A good internal ERP business case answers the objections before they are raised.

The first objection is implementation distraction. It is fair. ERP implementation takes time from people who already have work to do, and any case that pretends otherwise will lose credibility.

Answer it by showing the implementation path clearly: which flow goes first, who owns the project internally, which data needs preparation, which decisions leadership has to make, and what the team will leave out of the first scope.

The second objection is previous ERP trauma. If the company has tried ERP before and the project disappointed, the business case has to say what will be different this time. Was the previous implementation too finance-led? Too slow? Too generic? Did users avoid the system because it made work harder? Did the vendor force the company into workflows that never matched the factory?

The third objection is adoption. Teams do not reject systems because they love manual work. They reject systems that make their job slower, more rigid, or that are simply not connected to the reality they can see when doing their job.

The business case should explain which tasks become easier, which duplicate entries disappear, which questions no longer require asking around, and which users will validate the first live flow.

The fourth objection is whether the ROI is too soft. The best answer is to separate benefit types. Hard savings are different from capacity gains. Margin improvement is different from risk reduction.

A planner getting 10 hours back every week may not reduce payroll, but it can mean better scheduling, faster customer answers, fewer shortages, and less management time spent putting the week back together.

The fifth objection is delay. Why now? Why not improve the current system for another year?

Waiting may be reasonable if operations are stable, growth is modest, and current tools still give the team reliable answers. But if the company is already hiring around the system, losing margin to late visibility, or relying on a few people to keep the business coordinated, delay is not neutral. It means the company keeps paying the current cost.

For a broader version of these failure modes, read why ERP implementations fail, especially the sections on long timelines, finance-led projects, and accepting generic ERP workflows as if they were automatically right for the factory.

Show the implementation path

Horror stories abound of ERP projects taking so much time and money that the business doesn’t survive. It is therefore critical to show how how the company will avoid the usual traps: oversized scope, unclear ownership, weak data preparation, vague success criteria, and a go-live that arrives too late to prove anything.

A strong internal case should include:

  1. The business trigger behind the project
  2. The current cost in manual work, margin leakage, risk, and growth drag
  3. The stakeholders involved and what each one needs from the project
  4. The first operational scope
  5. The data, tools, and integrations required for that scope
  6. The internal owner and decision group
  7. The success criteria for go-live
  8. The topics deliberately parked for later

The last point is worth dwelling on, because ERP projects slow down when every single long-tail idea or need becomes part of the first scope. A dashboard that would help later, an integration that is not required for the first live flow, or an edge case that happens twice a year can hold the whole project hostage.

Bonx, the AI-native manufacturing ERP, changes what manufacturers can credibly expect from ERP implementation. Our customers reach a first go-live in 10 weeks on average and a full go-live in four to six months. That means the internal case can be built around a first valuable scope and an initial go-live instead of a distant go-live after a year of workshops. This de-risks the go-live for everyone inovlved.

At Bonx, speed doesn’t mean taking shortcuts. Féroce deployed Bonx in 42 days before a national TV appearance multiplied order volume tenfold, while keeping traceability intact through the surge. Something Added deployed Bonx in two months with a native integration to HP 3D printers, so orders could be grouped automatically, manufacturing orders generated, and jobs assigned to machines based on predefined rules.

For more detail on this kind of implementation path, Bonx has a separate article on what fast manufacturing ERP implementation actually looks like.

The final approval test

The final internal ERP case should lead to a clear decision: approve the project, delay it with intention, or accept the cost of the current operating model.

That last option should be explicit and is important, because ERP implementation is too often judged as if the alternative were free. It is not. The alternative is the current system, with the manual work, hidden costs, growth limits, and risks that come with it.

If the current system can still support the next stage, the project can wait. A company with stable production, trusted stock, clear margin visibility, reliable delivery promises, and low operational complexity may have better things to do than implement a new ERP.

But if the business is already paying through manual coordination, scattered traceability, late decisions, unreliable stock, unclear margin, and too much knowledge sitting in too few heads, the case is no longer speculative. The cost is already there.

A strong internal business case for ERP implementation says: this is what our current operating model costs, this is what the next system has to prove, this is how we will control the first scope, and this is what we risk if we keep pretending the status quo is free.

FAQ on building an internal ERP business case

What should an ERP business case include?

An ERP business case should include the business trigger, the cost of the current system, the stakeholders affected, the first implementation scope, expected benefits, key assumptions, internal effort required, implementation risks, and the decision the company needs to make.

Who should be involved in an ERP business case?

Operations, finance, leadership, IT, and future users should all be involved. Operations should define the work that needs to change. Finance should help make the numbers credible. Leadership should connect the project to company priorities. IT should define system boundaries and integration needs. Users should validate whether the new ERP will actually fit daily work.

How do you justify a new ERP internally?

Justify a new ERP by showing the cost of the current operating model. Count manual work, late decisions, margin leakage, traceability risk, customer-service impact, and growth drag. Then show which first operational scope the ERP should improve and how the company will measure whether it worked.

How do you calculate ROI for ERP implementation?

Start with observable costs: hours spent on manual work, errors, rework, urgent purchasing, expedited shipping, and reporting. Separate hard savings from capacity gains, margin improvement, and risk reduction. Use conservative, likely, and ambitious scenarios instead of pretending one ROI number is certain.

How do you get leadership buy-in for ERP implementation?

Leadership buy-in comes from connecting ERP implementation to business outcomes: growth, margin, customer promises, risk, and operational resilience. The case should show why the project matters now, what the first scope will prove, how internal effort will be managed, and what happens if the company delays.

When should a company replace its ERP?

A company should consider replacing its ERP when the system no longer supports daily decisions, trusted data, growth, traceability, or operational coordination. Common signs include spreadsheet workarounds, unreliable stock, late production visibility, manual reporting, weak adoption, and too much dependence on a few people who know how work really moves.

Share this article

The Bonx blog

You may also like ...

ERP deployment & implementation

Why ERP implementations fail

| Lynn Heidmann

Illustration of a monitor showing a stalled ERP implementation progress bar with a warning triangle in front of it.
Why ERP implementations fail

Contact us

Tired of your ERP working against you?

So were we. That's why we built Bonx, the AI-native manufacturing ERP.

Book a personalized Bonx demo
The two Bonx founders in branded caps, arms folded, in a leafy courtyard.