When Does an MES NOT Pay Off? 5 Honest Disqualifiers

TL;DR: An MES is a tool — not a maturity shortcut. If you lack stable processes, clear goals, or organizational readiness, an MES will only scale your existing chaos. We sell MES for a living, and we regularly advise companies against implementation — at least for now. This article shows the 5 clear disqualifiers, a decision framework (now / later / never), and the 4 mistakes that kill MES projects. If you're uncertain after reading this whether MES makes sense for you — that's a good sign. It means you're taking the decision seriously.

Table of contents

1. Why does this article exist — from an MES vendor?
2. What are the 5 clear disqualifiers for MES?
3. When are spreadsheets and manual processes objectively better?
4. Decision framework: Now, later, or never?
5. What are the 4 mistakes that kill MES projects?
6. FAQ

Why does this article exist — from an MES vendor?

The MES industry loves talking about benefits: OEE improvements, real-time visibility, efficiency gains. What rarely gets said: an MES is a tool — not a maturity shortcut. When the fundamentals are missing, your investment becomes an expensive data graveyard.

At SYMESTIC, we regularly advise companies against MES implementation — at least for now. Not because our product wouldn't fit, but because their prerequisites aren't met. This article summarizes what we've learned from hundreds of conversations and 15,000+ machine connections: the patterns that predict whether an MES will succeed or fail.

Why honesty is better for both sides: A failed MES project costs € 50,000–200,000 in direct costs — and far more in lost time, team frustration, and a harder restart next time. We'd rather tell you "not yet" today and start a successful project in 6 months than deliver software that nobody uses.

What are the 5 clear disqualifiers for MES?

The size threshold in detail:

Exception to the size rule: Highly automated small operations with expensive equipment (injection molding, precision machining, CNC centers) can benefit from OEE visibility even with < 10 machines — if hourly downtime costs are significant. In these cases, a production KPI starter package makes more sense than a full MES.

When are spreadsheets and manual processes objectively better?

Excel isn't the enemy. For certain situations, a spreadsheet is genuinely the right choice:

The transition from "Excel is fine" to "Excel is costing us money" is gradual. Many companies sensibly start with Excel and switch when the pain becomes significant enough. That's the right sequence — not the wrong one.

Decision framework: Now, later, or never?

What "start later" typically looks like: A mid-sized metal processing company with 80 employees contacts us. They have 15 machines, 2 shifts, SAP — looks like a perfect fit. But in the initial conversation, we discover: no defined cycle times, no downtime categories, no internal champion, and the production manager who'd be the key user is leaving in 2 months. We advise: "Define cycle times, categorize your top 10 downtime reasons, get the new production manager settled, then call us back in Q3." That's 3 months of foundation work that costs nothing but makes the MES project succeed instead of fail.

What are the 4 mistakes that kill MES projects?

The pattern behind all 4 mistakes: Treating MES as a technology project instead of a production improvement initiative. The technology is 20 % of the work. The other 80 % is: defining goals, changing behaviour, acting on data, and iterating. If the organization isn't ready for the 80 %, the 20 % doesn't matter.

FAQ

Is an MES worth it for small manufacturers with 10–50 employees?
It depends on the manufacturing type, not only on size. A 30-employee injection molding plant with 8 highly automated machines running 3 shifts benefits enormously from OEE visibility — the hourly cost of undetected downtime is high. A 50-employee assembly workshop with manual processes and one-off products does not. The question isn't "how many employees?" but "do you have countable products on machines with measurable cycle times?"

What does a failed MES project actually cost?
Direct costs (licences, integration, consulting): € 50,000–200,000 for mid-sized companies with traditional on-premise MES. But indirect costs are worse: 6–18 months of lost time, team frustration ("we tried that — it didn't work"), and a much harder restart next time because trust is eroded. With Cloud MES, the financial risk is lower (monthly SaaS, no CAPEX), but the organizational risk remains: if nobody uses the data, you've still failed.

Can I start with a pilot to test readiness?
Yes — and it's the recommended approach. A pilot with 5–10 machines shows within 4–8 weeks whether the organization is ready and whether expected benefits are realistic. At SYMESTIC, the 30-day free evaluation serves exactly this purpose: you see real data from real machines before committing. If the pilot reveals that prerequisites are missing, you've learned something valuable at zero cost.

What's the single most common reason MES projects fail?
Lack of accountability for acting on the data. The MES delivers visibility — machine 7 has 23 % more downtime than machine 8, and the top cause is changeover overruns. But if nobody is responsible for investigating and fixing that, you're left with pretty dashboards and no improvement. The fix: assign a specific person (production leader, CI manager) who reviews MES data weekly and owns the improvement actions.

You sell MES — why are you telling people not to buy?
Because a failed MES project is worse than no MES project. It costs money, wastes time, destroys trust in digitalization, and makes the next attempt harder. We'd rather have an honest conversation today and a successful implementation in 6 months than a signed contract that turns into a data graveyard. Our 0 % churn rate in 2024 isn't accidental — it's the result of saying "not yet" to companies that aren't ready.

The key takeaway: The decision for or against MES isn't about "modern vs. outdated." It's about fit. Does the tool match your current situation? Are the prerequisites met? Are there clear goals and willingness to act on results? If you're not sure — start with foundation work. Define cycle times. Categorize downtime reasons. Clean your ERP data. That's 3 months of effort that costs nothing and makes everything that follows — MES or not — more effective.

→ What is MES? · → MES Implementation · → Excel vs. MES · → MES ROI · → MES Costs · → Best MES System