Most companies start an ERP project the same way. They reach out to a few vendors, sit through some demos, pick the one that feels right, sign a contract, and hand the project over to an implementation partner. Then they wait for the transformation to begin.
That handoff is where things start to go wrong, usually quietly, and usually before anyone notices.
The implementation partner shows up with a methodology, a project plan, and a team. What they do not show up with is a deep understanding of how your business actually runs today, which of your processes are broken, where your data cannot be trusted, and whether your internal team has the capacity and the clarity to carry a project of this size alongside everything else they are already doing. They are not hiding this. It is simply not what they are hired to do. They are hired to implement the software. The assumption built into every implementation engagement is that your organization has already done the preparation work. Most organizations have not.
Phase 0 exists because of that gap.
It is the work that happens before the vendor is selected, before the contract is signed, before the implementation clock starts. It is a structured diagnostic engagement, usually four to six weeks, where an independent advisor works with your leadership team to answer questions the implementation partner will never ask you.
Not because they are incompetent. Because it is not their job.
What actually happens during Phase 0
The work is not glamorous. It does not involve software demos or feature comparisons. It involves sitting with the people who actually run your operations and asking them to walk you through what they do every day, step by step, and then asking them why it works that way.
What comes out of those conversations is almost always surprising, even to the people who have been running the business for years. You find processes that exist only because of a workaround someone built three years ago after a different system failed. You find data that lives in spreadsheets because the current system never handled it properly. You find entire operational areas where nobody has a clear owner, where two departments have different versions of the same number, where a vendor or a customer relationship runs entirely through one person's memory and nowhere else.
None of this is unique to struggling businesses. I have seen it in companies that are profitable, growing, and well-managed by every visible measure. The operational complexity of a mid-market manufacturing or distribution business almost always outpaces the documentation that exists to describe it. That is not a failure. It is just the reality of a business that has been solving problems and moving forward without stopping to write everything down.
Phase 0 stops to write it down.
The output is a documented picture of how the business operates today, where the gaps are, what is at risk if those gaps are carried into a new system, and what needs to be resolved before an implementation can be set up to succeed. It is the map of your broken processes, built honestly, before anyone starts selling you the solution.
Why this matters more than which software you pick
Here is the thing most CEOs do not realize when they start an ERP project. The software is rarely the reason it fails. The research on this is consistent. Gartner, Panorama Consulting, and others who track ERP outcomes year over year will tell you the same thing: the majority of ERP project failures trace back to poor preparation, unclear requirements, underestimated complexity, and organizational unreadiness, not to a bad choice of software.
You can pick the right vendor and still fail if you walk into implementation carrying unresolved process problems, dirty data, a team that does not have the bandwidth, and leadership that has not aligned on what the project is actually supposed to change.
Phase 0 does not guarantee success. Nothing does. But it removes the most predictable causes of failure before the most expensive part of the project begins.
The question I get asked most often
When I describe Phase 0 to a business leader for the first time, the most common response is some version of: "Can't we just do this during implementation? Won't the partner help us figure this out as we go?"
The honest answer is that some of it will surface during implementation. It always does. But surfacing a broken process six months into a project, after the design decisions have already been made, costs significantly more to fix than surfacing it before the project starts. You are not just fixing the process at that point. You are redesigning configuration, retraining people, potentially delaying go-live, and absorbing the cost of work that has to be redone.
The implementation clock is expensive. Every week on it costs money. Phase 0 is about making sure you are not spending that time discovering things you could have known in advance.
What it is not
Phase 0 is not a vendor evaluation. It is not a feature checklist. It is not a way to delay making a decision. It is a way to make a better decision, faster, with less risk, because you actually understand what you are walking into before you commit.
If you are a mid-market business leader who is thinking about an ERP project in the next twelve to eighteen months, the most useful thing you can do right now is not to schedule vendor demos. It is to get honest about the state of your own operations first.
That is what Phase 0 is for.
Let's Talk About Where You Stand
This is a focused working conversation not a sales call. You will gain clarity on where you truly stand in your ERP journey, what is actually driving the urgency for change, and whether Phase 0 is the right next move for your business right now. If it is not the right fit, you will hear that clearly and directly.