Your business changes. Your ERP does not. That sentence describes the experience of nearly every mid-market manufacturer who has ever implemented an enterprise system.
The ERP was scoped in January. Requirements froze in March. The system went live in December. By then, you had added 2 new product lines, restructured your vendor network, changed your approval hierarchy, and opened a second warehouse. The system that went live was built for a business that no longer exists.
Here is how that plays out, and what it costs.
Stage 1: The workarounds begin
The first sign is small. A new rule needs to be added. "We need founder approval for POs to any vendor we have not used before." The system does not support vendor-specific approval logic. The workaround: the planner manually checks the vendor history and routes the PO by email for approval when needed.
Nobody thinks of this as a system failure. It is "just how we do it."
Within 6 months, the operation has 5 to 10 workarounds. Each one is a process that happens outside the ERP because the ERP cannot accommodate it. Each one is a manual step that someone has to remember. Each one is a point of failure that nobody catches until something goes wrong.
Stage 2: The spreadsheets come back
The workarounds create data gaps. The ERP does not capture the vendor-specific approval. So someone tracks it in a spreadsheet. The ERP does not support the new warehouse's unique inventory logic. So someone maintains a separate inventory sheet for that location.
Six months after go-live, the same spreadsheets you eliminated during implementation have crept back. Not because the ERP failed. Because the business changed and the ERP did not.
You are now running two systems: the ERP (which handles 70% of the operation) and the spreadsheets (which handle the 30% the ERP cannot). The founder's dashboard is based on the ERP data. But 30% of the truth is somewhere else.
Stage 3: The change orders
You call the vendor. "We need these 5 changes." They scope it. $65,000. 12 weeks.
You approve 3 of the 5 (the other 2 are too expensive for now). The changes take 16 weeks instead of 12 because the customization from Phase 1 conflicts with the new changes. The vendor fixes the conflict. Another 3 weeks.
Your annual change order budget is now the size of a full-time employee's salary. And you still have 2 unresolved changes and 10 workarounds.
Stage 4: The trust erosion
The founder opens the dashboard. The numbers do not match what he hears on the floor. The production count shows 4,200 units completed. The dispatch team says they have only 3,800 ready to ship. The gap is the 400 units that were logged as "complete" in the ERP but are actually in rework, which is tracked on a spreadsheet.
The founder stops trusting the dashboard. He goes back to calling the floor for updates. Three phone calls, 20 minutes. For a $15M operation, that is the founder's time being spent on data retrieval instead of decision-making.
Stage 5: The replacement conversation
Two years in. $300K spent. The ERP handles 60% of the operation. Spreadsheets handle 25%. WhatsApp handles 15%. The dashboard is "directionally correct" but not trustworthy for decisions.
Someone says: "Should we look at replacing the ERP?"
And the answer is usually: "With what? It took 18 months to implement this one. Going through that again would be worse."
That is vendor lock-in. Not through a contract. Through the sheer weight of time and money already spent. The sunk cost keeps you in a system that no longer fits.
What the alternative looks like
An ERP that changes when the business changes. Not in weeks. Not through change orders. In minutes, through configuration.
New approval rule? Add a row. New production stage? Add it to the flow. New warehouse with different receiving logic? Add a location-specific configuration. New product line with different component structures? Add a new set of rules.
The ERP is not a fixed system that the business adapts to. It is a living configuration that adapts to the business. When the business changes (and it will, because businesses always change), the system changes with it. Same day. Same cost: zero.
That is the difference between an ERP that works in year one and an ERP that still works in year five.
SimpleGrid adapts when your business does. Rules change in minutes. No change orders. No consultants. No workarounds. No spreadsheets creeping back.