Quoting went back to spreadsheets. Scheduling went back to the whiteboard. Critical knowledge stayed in three people’s heads. Here’s what actually happened — and it isn’t resistance to change.
The symptom every high-mix shop knows
Somewhere in your building there’s an ERP that cost real money. And around it, your team has quietly rebuilt the old world:
The “Master Spreadsheet” for quoting. The whiteboard for production scheduling. That one person who just knows how the operation actually runs.
Nobody went back to spreadsheets because they love spreadsheets. They went back because the ERP doesn’t support your special cases. Because the scheduling module couldn’t handle a day where three jobs changed priority before lunch. Because the software assumed every order follows the same path — and yours never do.
The vendor calls that a training problem.
It’s not. It’s a design problem.
The “fully configurable” promise
ERP vendors keep telling you: “our platform is fully configurable to your workflow.”
They have no idea what your workflow actually looks like.
You run high-mix, low-volume. Every order is different. Every BOM shifts. Every job is a puzzle, not a process. And “configurable” turns out to mean some visual tweaks — while the workflow stays theirs: full of required steps you don’t need, missing the ones you do.
Mass production is one product, one BOM, one process — repeated a million times. That’s what this software was built for. Handing it to a custom manufacturer is like handing a tailor a cookie cutter.
You didn’t fail the software. The software was never built for the way you work.
Wrong tool, wrong result
Every manufacturer already knows this principle — on the floor.
A metal file for a precision part? Madness. You’ll get there eventually — burning hours, missing tolerances, one wrong move from ruining the part.
A 5-axis CNC for a simple bracket? Waste. The job gets done, but you’re paying for complexity you don’t need — training, configuration, maintenance, all for a bracket.
Your operational software works exactly the same way:
Spreadsheets seem cheap — until you count the hours re-keying data, chasing the right version, and catching errors after the job has already shipped.
Enterprise ERP seems safe — until your team ignores half of it and builds workarounds in Excel anyway. You’re running an office on software built for Boeing.
Wrong tool, wrong result. So why is this normal in the office when it would be madness on the floor?
Workarounds hold — until they don’t
Here’s the dangerous part. The spreadsheet-and-whiteboard system works. Resourceful people made it work. It holds together.
Until you grow.
Bigger jobs, more orders, new hires who don’t carry the operation in their heads — and the fragile workarounds simply can’t keep up with the throughput. The knowledge in three people’s heads becomes a risk you can measure in job ads and sleepless nights.
The problem was never that your business is too complex. The problem is forcing it into a rigid system that was never built for how you actually work.
What fitting software looks like
Software built for high-mix, low-volume doesn’t start from a template and ask you to configure it. It starts from how you actually quote, schedule, and produce — and builds around that.
The fields you need are there. The ones you don’t are gone. The steps match your routing, not a “best practice” imported from a factory that runs the same widget all day. Three jobs change priority before lunch? The schedule moves with them.
That’s the difference between software your team fights every morning and a tool they actually use — because it fits the work they’re already doing.
Find out what the fight is costing you
Every workaround has a price — hours, errors, delays, knowledge risk. In our free Operations Efficiency Map session, we walk your order lifecycle stage by stage and put numbers on exactly that. One hour, your figures, no obligation.
Or see the alternative in practice: how a system built around one manufacturer’s actual process cut production delays by 30% ￫