TL;DR
Most systems don’t fail because they stop working. They fail because of everything required to keep them working. The real cost isn’t the system itself, it’s the accumulation of extra tools, manual effort, and hidden risk that builds over time.
A few months ago, I wrote about ERP decision gridlock, why companies stay stuck, why decisions tend to sit at the top, and why inefficiencies get tolerated longer than they should be.
Since then, I’ve had more conversations. Real ones. The kind where people walk you through their day and you can hear the friction in the background.
And what became clear is this:
Most companies aren’t stuck because nothing works. They’re stuck because everything still works just enough.
The System Isn’t Broken, and That’s the Problem
On the surface, operations continue.
Quotes go out.
Orders get processed.
Inventory moves.
From a distance, everything looks intact.
But closer to the work, it’s a different reality. Teams are re-entering data, chasing information across systems, and relying on workarounds just to keep things moving. What started as temporary fixes slowly becomes part of the process itself.
Over time, inefficiency doesn’t feel like inefficiency anymore.
It feels normal.
That’s where the real issue sits—not just in the system, but in the mindset that allows it to continue. Familiarity makes it tolerable. Leadership sees outcomes, not effort. Reports show results, but not the friction behind them.
By the time the problem becomes visible at the top, it’s already been there for a while.
When Moving Forward Doesn’t Solve the Problem
What I didn’t fully appreciate before is what happens when companies try to fix it—but don’t actually change the structure underneath.
I’ve seen companies invest in new systems expecting a clean break from the past.
One company spent between $8,000 and $14,000 to get started. That was just the beginning. Then came data migration, training, and additional tools to fill gaps they didn’t expect.
Before long, they weren’t running one system. They were managing multiple layers just to operate.
The complexity didn’t disappear. It just changed form.
Where Small Decisions Turn Into Bigger Risks
Another company had flexibility built into their system. They could edit historical data, change part numbers, and delete records.
At first, that felt like control.... Until it didn’t.
One of their team members described it in a way that stuck with me. It was like having to press a button every time you wanted your brakes to work. Most of the time, you’ll remember. But when you really need it, that’s when you might not.
That’s the tradeoff.
Flexibility without structure can feel efficient, but it creates gaps in traceability and accountability that only show up when it matters most.
The Layering Effect Nobody Talks About
I’ve also seen companies run into something simpler, but just as telling.
They wanted to centralize their RFQs. A core workflow. Something that should live inside the system.
The answer they got was to purchase a third-party tool.
That’s when things start to feel off.
Because now you’re not solving the problem—you’re layering on top of it.
The same pattern shows up in smaller ways too. A support request that should be simple takes longer than expected and comes back with an added cost. Individually, it’s manageable. But over time, it adds up.
And that’s the part most companies don’t measure.
The Cost That Builds Over Time
None of these situations, on their own, feel like a breaking point.
That’s what makes them easy to accept.
But together, they form a pattern:
- extra tools
- extra steps
- extra cost
- extra risk
It’s not just inefficiency.
It’s accumulation.
And it doesn’t show up all at once.
It builds quietly.
A Different Way to Look at the Decision
Most ERP decisions are framed around cost.
But the companies that gain clarity start asking different questions.
Not “What does this system cost?” But “What does this system require from us?”
-What happens outside of it?
-What depends on manual effort?
-What needs to be added to make it work?
-Where does risk exist if something goes wrong?
That’s where the real picture starts to come into focus.
Seeing It Before It Becomes Obvious
This isn’t about forcing change.
And it’s not about saying every system is wrong.
It’s about understanding that the impact of staying the same doesn’t always show up immediately.
It shows up over time.
In ways that are easy to normalize… until they’re not.
The companies that move forward successfully don’t wait for something to break. They recognize the signals earlier. They question what feels routine. And they look beyond whether something works, to whether it works the way it should.
Because in the end, the story of an ERP isn’t found in whether it runs.
It’s found in what it takes to keep it running.
What I’ve come to appreciate more over time is that most companies aren’t far off, they’re just missing visibility into what’s actually happening beneath the surface. This isn’t about rushing change or forcing a decision. It’s about stepping back and asking better questions about how your operation really runs today. Because once you see that clearly, the path forward tends to become a lot more obvious.
