Shopfloor Matters
Implementation

How to build an MES business case leadership will sign

You know your factory runs on paper and Excel. Your leadership hasn't approved the fix. How to build a business case around business impact, risk and the cost of doing nothing.

Illustration: The MES business case

You know your factory runs on paper and Excel. You know that's a problem. Yet you're struggling to get leadership to invest.

I hear this constantly. And I know how it feels. It's infuriating.

The good news is that it's usually not the idea that's being rejected. It's the way it's being presented.

What's really blocking it

When I dig into stalled business cases, the same things come up:

  • "We don't have the data to prove the ROI."
  • "Our executives don't understand the urgency."
  • "The investment looks too big."
  • "We tried something similar and it didn't work."

And underneath all of them, one thing: fear. Fear of overrun, overspend and failure. Nobody wants to be the executive who green-lit the project that went wrong. I get it. Their job is on the line.

So your business case has to deal with that fear directly.

Speak business, not features

Leadership doesn't need technical specifications. It needs business impact.

Start with the pain points that keep your leadership awake at night, and put money on them:

  • Quality: what do scrap, rework and customer complaints cost per year?
  • Downtime: what's an hour of lost production on your bottleneck worth in revenue?
  • Labour: how many hours a week go on manual data entry, chasing information and building reports?
  • Delivery: what has late or incomplete delivery cost in penalties, lost orders or lost customers?
  • Inventory: how much working capital is tied up in buffers you hold because you don't trust the data?

Then connect those numbers directly to what the system will change.

The structure that gets approved

Business cases get approved faster when they clearly show:

  1. Current-state costs. What the problems cost today, in money.
  2. Future-state benefits. What will improve, by how much, and when.
  3. Realistic implementation costs and timeline. Including your internal people, not just licences and services.
  4. How the risk is managed. Phases, milestones, measures and decision points.

That fourth point is the one most people miss. It's the one that deals with the fear.

Reframe the risk

The best business cases I've seen reframe the conversation completely.

Transformation as risk mitigation. The bigger risk isn't the investment. It's the quality escape, the failed audit, the experienced operator retiring with all the knowledge in their head.

Phased delivery. Start with one line or one site. Prove the value. Let the results fund the next phase.

The cost of doing nothing. Your competitors are moving. Customers are getting less patient with quality issues and late deliveries. Every year you delay has a cost, and it's usually bigger than people assume.

Use the 1% question

I always ask: what would a 1% improvement in OEE be worth to your business?

Work it out. For most manufacturers it's a very significant number. Then compare it with the improvements the research reports. Deloitte's 2025 survey found average improvements of 10% to 20% in production output among large manufacturers investing in smart manufacturing. I pull together more of the research in What the research says about smart factory ROI.

Use outside research to make the conversation credible. Use your own numbers to make it real.

Don't promise everything on day one

Don't promise transformation overnight. Set milestones. Show quick wins. Build momentum.

I've seen companies pay for their MES in months rather than years, and that's on tangible benefits alone: less scrap, more uptime, more throughput. The intangibles, like happier customers and less firefighting, come on top.

Your leadership doesn't need perfection. It needs confidence that you understand the risks and have a plan to manage them.

What's holding back your next strategic investment: the numbers, or the nerves?

Matt Barber
Written by

Matt Barber

VP & General Manager for MES at Infor. Started as an MES developer, then ran projects, solution design and product. Writes about the smart factory, shopfloor AI and the MES/MOM foundations underneath them.

Keep reading

The newsletter

Get the next one in your inbox

New articles on shopfloor AI, smart factory strategy and the MES/MOM lessons I wish someone had told me before my first implementation.

Prefer LinkedIn? Follow me there →

  • Vendor-neutral, practical guidance
  • Written from real implementations, not brochures
  • Shopfloor AI, smart manufacturing and MES/MOM
  • No hype, no buzzword bingo