Walk into any mid-market manufacturing plant in North America and you will find one of three things: a partially deployed MES, a fully deployed MES that nobody on the floor actually uses, or a stack of spreadsheets functioning as the MES.
All three exist for the same reason. The category that was supposed to solve this — manufacturing execution systems — has been quietly broken for at least a decade. Here are the five ways. You can tell us we're wrong by scheduling a call.
Reason 01
The category was designed for a buyer who has left the room.
Modern MES products were architected in the early 2000s for global enterprise manufacturers — the kind with twenty plants, a Chief Manufacturing Officer, and a six-figure annual SaaS budget. The products were priced, scoped, and implemented accordingly.
The mid-market manufacturer running three to five plants on a thinner ops team has been quietly inheriting that architecture ever since — paying enterprise prices for enterprise complexity they don't need, in exchange for a feature set that mostly applies to plants ten times their size.
The biggest MES vendors aren't dumb; they know this. They've solved it the way enterprise software always solves it: they make you spend nine months in scoping workshops "right-sizing" the implementation. It is a feature of the business model. It is not a feature of your business.
"We bought the enterprise MES three years ago. We use about 11% of it." Plant manager · 4 plants · mid-market discrete manufacturer
Reason 02
"Best practices" is a license to ignore your plant.
Open the brochure for any major MES product and you will find a section on "best practices." It will explain that the product is built around the way the world's leading manufacturers run their operations. This is true. It is also the problem.
"Best practices" in MES marketing means: the way the vendor's biggest reference customer does it. Which is, in turn, the way that customer's consultancy convinced them to do it during their last implementation. It is a circle of received wisdom that does not survive contact with your floor.
The next time a vendor uses the phrase "best practices," ask them to name the practice, the plant it came from, and what changed when it was applied. If the answer involves a slide deck, walk out.
Your plant has a way it runs samples. A way it handles temporary work instructions. A way it routes maintenance requests at 2am on a Saturday. None of those are wrong. They are the accumulated result of people who actually understand your equipment, your union rules, your customer mix, and your geography. An MES that asks you to throw them out and adopt "best practices" is asking you to throw out the only competitive advantage you actually have.
Reason 03
The eighteen-month implementation is a business model.
The single most quoted number in MES procurement is the implementation timeline. The polite version: twelve to eighteen months. The honest version, after change orders: twenty to thirty.
This is not because shop-floor software is technically harder than other enterprise software. It is because the implementation revenue is, for many MES vendors, more profitable than the license revenue. Every quarter of additional consulting hours is a quarter of additional billing. The incentive is to make the implementation long, complex, and dependent.
The honest sign that you've been caught in this is the moment somebody — internal or external — describes a year-two phase, and what's in it is the kind of basic functionality you assumed would be in year one. The product was sold to you on year-two capabilities. You are paying year-two prices for year-one work.
"Phase two is when we get to the dashboards I thought I was buying in phase one." Operations director · Tier-2 automotive supplier
Reason 04
The roadmap doesn't have your seat at the table.
You ask the vendor for a feature. Maybe it's a small one — a different way of grouping downtime reasons, or a custom permission for floor support. The vendor says: "That's a great suggestion, let's get it into the next roadmap committee."
The roadmap committee meets quarterly. It is staffed by product managers who report to a VP of Product who reports to a CRO whose comp plan is tied to logo growth, not retention satisfaction. Your feature gets prioritized against features requested by customers ten times your size. You will not win.
Most of the time, your request will go into a "considered for future" tier and stay there indefinitely. Occasionally it will resurface in a release-notes email two years later, slightly different from what you asked for, and you will get to email your CSM to ask if the new feature solves what you were originally trying to solve. Half the time, it doesn't.
You are paying a software vendor an annual subscription. You have, in writing, a list of features they have committed to. The list moves. You cannot make the list move. Your competitors, who are running an older version of the same software because they didn't upgrade, have a similar list with slightly different items moving.
Reason 05
Lock-in survives long after the value runs out.
The dark gift of an MES is that it sits at the deepest part of your operational stack. It is wired to the PLCs. It is the source of truth your ERP integration trusts. It has been customized by three generations of consultants. Replacing it feels like replacing the foundation of a building while the building is still operating.
So you don't replace it. You complain about it in private. You build adjacent spreadsheets to cover its gaps. You hire a new operations director whose first three months are spent learning the bespoke customizations that the last consultancy left behind. You consider replacement every two years and decide it's too painful.
This is rational at the level of any given decision and irrational across the lifetime of the asset. A system that you would not buy today, that does not meet the operation as it runs today, that is actively constraining decisions about new equipment and new lines — and that you keep, because changing it is hard.
Lock-in is not an accident of MES architecture. It is the design.
Buy software and the engineers who customize it.
Off-the-shelf MES is one-size-fits-no-one. Pure-custom dev is a blank page. The third option is a product with the engineers attached — pre-built where it should be, customized where it has to be, by people who already know how a plant works.
That's what we built. That's what FactoryView is.