I've watched companies spend $500,000 on an ERP system and get $50,000 worth of value out of it. I've seen the opposite too — lean organizations that squeezed every dollar out of their investment and transformed how they operate. After 30 years of advisory work with companies ranging from mid-market manufacturers to global enterprises like Lockheed Martin and AT&T, I can tell you exactly what separates the two groups.
It's not the software. It was never the software.
The Myth That Keeps Costing You Money
Every ERP sales process is built around the same promise: implement our system, and your problems go away. The demos are clean. The integrations sound seamless. The ROI calculations are compelling. And then you go live, and six months later you're wondering why your team is still running shadow spreadsheets alongside the $400,000 platform you just deployed.
Here's what the vendor never tells you: an ERP system is a mirror. It reflects the quality of your processes, the clarity of your data, and the alignment of your people. If those three things are broken before implementation, the software will faithfully automate your chaos at scale.
I've seen it happen at companies with household names. The platform was best-in-class. The implementation partner was certified. The executive sponsor was committed. And it still failed — because the people strategy was an afterthought.
The Three Places ERP Implementations Actually Break
1. No single owner of the truth. Every ERP lives or dies on data integrity. Who owns the item master? Who governs the chart of accounts? Who has authority to change a vendor record? If the answer to any of those questions is "whoever gets to it first," your system will produce garbage outputs from day one. Before you spend a dollar on software, you need a data governance framework — not a committee, a framework — with named owners and defined processes.
2. Change management is treated as a training problem. Most organizations budget for training. Almost none budget for change management. Those are not the same thing. Training tells people how to use the system. Change management addresses why they don't want to. The finance manager who built her current process over 12 years is not going to adopt a new workflow because she sat through a two-hour webinar. She needs to understand the business case, feel heard during the transition, and see that her expertise was respected in the design. That takes a people strategy, not a training calendar.
3. The implementation partner optimizes for go-live, not adoption. Your implementation partner's success metric is getting you live on time and on budget. Your success metric is actually using the system the way it was designed, two years after go-live. Those goals are not the same, and nobody in the room is going to tell you that. A fractional CIO or independent advisor sitting on your side of the table changes this dynamic entirely — because their incentive is your long-term outcome, not the project milestone.
What Good ERP Advisory Actually Looks Like
When I work with a client on ERP selection or implementation, the first conversations have nothing to do with software. They're about process. Specifically: what are your current processes, which ones are broken by design versus broken by execution, and which ones do you actually want to take into the new system?
Because here's the truth most people don't want to hear: an ERP implementation is your best opportunity to fix broken processes. And it's also your greatest risk of locking those broken processes in permanently at enterprise scale.
The companies that win don't just implement software. They use the implementation as a forcing function for organizational discipline — cleaning data, rationalizing processes, aligning ownership, and building the habits that make the system work after the consultants leave.
Before Your Next ERP Decision, Answer These Questions
If you're evaluating a new system, preparing for an upgrade, or trying to rescue a troubled implementation, start here:
Process clarity: Can you document your current end-to-end processes in plain language? If you can't describe them clearly, you can't configure them correctly.
Data governance: Do you have named owners for every master data domain? If not, you don't have a data problem yet — you have a people problem that will become a data problem the moment you go live.
Change leadership: Who in your organization is responsible for adoption, not just training? Is that person senior enough to make decisions and resolve conflicts? Do they have executive air cover?
Independent representation: Who on your team is evaluating this from your perspective — not the vendor's, not the implementation partner's? If the answer is nobody, that gap is costing you money you can't see yet.
The Bottom Line
ERP selection and implementation is one of the highest-stakes decisions a mid-market company makes. The software matters. The partner matters. But neither of those things matters as much as the organizational readiness you bring to the table — the quality of your processes, your data, and your people strategy.
Get those three things right before you touch the software, and almost any modern ERP will work for you. Get them wrong, and even the best platform in the world won't save you.
I challenge you to audit your current ERP situation honestly. Not the system. The people strategy around it. What you find will tell you exactly where to focus.
To your growth and prosperity.
— Mike Martin | Fractional CIO/CTO | ERP Advisor | Top Down Strategies
Evaluating a new ERP or navigating a troubled implementation? Let's talk — I've seen every failure mode, and I know how to get you out of them.
