Traditional SaaS, ERP, and MES are losing the workflow
Standard software promises best practices, but manufacturers still fall back to spreadsheets when the system cannot represent how work actually happens.
Key takeaways
- Standard ERP and MES templates often miss the local exceptions that make an operation competitive.
- When software does not fit the workflow, teams rebuild the missing process in Excel, email, calls, and offline trackers.
- The next generation of operations software has to model the real workflow without forcing every company into the same operating playbook.
The standard solution creates the shadow system
Traditional enterprise software usually arrives with a promise: adopt the standard process, reduce customization, and inherit best practices. That sounds efficient until the standard process meets the factory. A buyer needs a supplier workaround. A planner needs a temporary allocation rule. A quality lead needs a hold that blocks one downstream step but not another. A supervisor needs to capture what really happened on the floor before the official record catches up. When the system cannot represent those details, the work does not stop. It moves into Excel, email, calls, Teams messages, and local trackers.
The spreadsheet problem is a signal
The numbers show how persistent this pattern is. Basis Technologies surveyed 200 SAP enterprises across the US, UK, and Germany and found that 59% still rely on Excel spreadsheets to manage SAP change, even though 96% of senior leaders said SAP is critical to day-to-day operations. In S&OP, a 2025 survey of 164 professionals across 54 countries found that 81.1% manage the process in Excel or Google Sheets, while only 6.6% use ERP systems. Spreadsheets are not winning because enterprises love manual work. They are winning because they are flexible enough to hold the exceptions the official system rejected.
ERP and MES failures are often workflow failures
A failed rollout is rarely just a software failure. It is usually a mismatch between the implemented model and the operating reality. ComputerWeekly, citing 2024 Gartner research, reported that by 2027 more than 70% of recently implemented ERP initiatives will fail to fully meet their original business case goals, and as many as 25% will fail catastrophically. The lesson is not that ERP has no value. The lesson is that a central system built around generic assumptions can become brittle when the business depends on local judgment, cross-functional exceptions, and rapid change.
Best practice can erase your advantage
The most dangerous phrase in enterprise software is "this is how the standard template works." If every competitor adopts the same process map, the same approval gates, the same planning categories, and the same operating reports, then the software has quietly flattened the thing that made the company different. Your edge may live in how you sequence constrained resources, how you recover from supplier misses, how quality and production negotiate risk, or how planners interpret demand signals. Treating those behaviors as deviations to be eliminated can destroy strategic advantage in the name of clean implementation.
The future is workflow-native
Modern operations software should not force a choice between rigid standardization and uncontrolled customization. It should model the real workflow as a governed system: the objects that matter, the relationships between them, the rules that must hold, the approvals that require human judgment, and the exceptions agents are allowed to escalate or resolve. That is the path beyond traditional SaaS, ERP, and MES. Not another static module, but a living operating layer that fits the business closely enough that people stop rebuilding the truth offline.