In 2019, when COVID hit, I watched something I had never seen before. Businesses that had ignored their systems for years suddenly panicked. Phones were ringing off the hook at ERP vendors. Everyone wanted cloud, everyone wanted remote access, everyone wanted to place orders and fulfill them without being in the same room. What nobody wanted to talk about was whether they were actually ready for what they were about to start.
Most of them weren't.
I saw implementation after implementation collapse under the weight of that urgency. Companies that had never documented a single process were suddenly trying to migrate years of tribal knowledge into a new system while the world was falling apart around them. The ones who survived did so despite the project, not because of it. The ones who didn't are still recovering.
That experience taught me something I now tell every client before we discuss any system at all. Speed is not a strategy. And the most expensive thing you can do in an ERP project is start too fast.
There is a particular kind of confidence that takes over in boardrooms when an ERP decision finally gets made. After months of deliberation, stakeholder interviews, vendor demos, and budget debates, a decision is reached and the instinct becomes almost physical: move. "Let's just pick a system and figure out the process during implementation." It sounds pragmatic. It sounds decisive. And it is, without question, the highest-risk thing you can do.
I have seen this play out more than once, and the pattern is consistent enough that it deserves to be named plainly.
ERP implementation vendors charge by the hour. That is not a criticism، it is simply how professional services work. But it means that every undocumented business rule your team discovers mid-implementation becomes a change order. Every data quality issue that surfaces during migration becomes a delay. Every approval process that exists only in someone's head becomes a scope discussion. The meter is running for all of it. Industry research consistently shows that ERP projects beginning without process clarity run 40 to 60 percent over budget and 6 to 12 months over schedule. That is not a rounding error. That is a failed project wearing a completion certificate.
What I find interesting and genuinely frustrating is that the pre-work which prevents this outcome is rarely framed correctly. It gets called "overhead." It gets treated as the slow part, the unnecessary part, the part that a confident enough team can compress or skip entirely. This framing is wrong.
Process documentation is not overhead. It is the thing that tells your implementation vendor what to build. Clean, validated data is not overhead. It is the input your new system needs to produce trustworthy output from day one. A formal approval matrix is not a bureaucratic formality. It is the guardrail that prevents margin leakage from accumulating quietly in the background while everyone is focused on go-live. These are not preparation tasks. They are the project.
There is something else worth saying here, because it often gets lost in the urgency of the ERP conversation. This preparation delivers independent value. Documented processes reduce operational key-person risk immediately, regardless of which system you eventually select. When business logic lives only in the memory of two or three people, the organization is perpetually one resignation away from a knowledge crisis. Clean data improves reporting reliability today, not on some future go-live date. Formal controls reduce exposure now, in this quarter, not after a successful cutover.
The recommendation is not to delay indefinitely. Delay is its own risk, and indecision has real costs too. The recommendation is to do the preparation that makes the project succeed، to arrive at implementation with documented processes, validated data, and a clear picture of what the system needs to support. That is not caution. That is the only path that reliably works.
The organizations that treat ERP as a technology project tend to struggle. The ones that treat it as a business transformation, supported by technology, tend to succeed. The difference, almost always, comes down to whether the hard thinking happened before the contract was signed or after the clock started running.
At Metadata Advisory, we help distributors and mid-market businesses build the process foundation that makes ERP investments succeed. If you are evaluating ERP and want an honest assessment of where your organization actually stands, Book an ERP Risk Conversation.