If you are a VP of IT staring down an ERP initiative, this might sound familiar:
The current system is holding the business back. Finance wants better reporting. Operations wants fewer workarounds. The exec team agrees that something needs to change if growth is the goal. What they do not yet agree on is scope, cost, timing, or how disruptive this will be.
“ERP Phase 0 is where the smartest VPs show their value.”
We’ve helped walk VP of ITs through D365 ERP programs, often after things went sideways. The pattern is consistent. Successful projects do not start with software or partners. They start with clarity, alignment, and control. That work lives in Phase 0.
This guide is written to help you run Phase 0 properly so you can secure executive buy-in, protect your team, and set the project up for success before any implementation contract is signed. But first…
What is ERP Phase 0?
It’s where the compass for your roadmap ahead is built. Your North Star when things get choppy (and they will).
Phase 0 is the diagnostic and pre-planning phase of an ERP program. Some organizations call it readiness assessment, business case development, or pre-planning. The name matters less than the outcome.
Phase 0 is where the business decides what problem it is solving and how it will govern the solution.
Phase 0 typically includes:
- Building the ERP business case and project charter
- Defining scope boundaries and success criteria
- Mapping current and future state business processes
- Documenting real requirements and pain points
- Planning resourcing, governance, and decision ownership
- Identifying risks early, including data, integrations, and change impact
- Defining how partners will be selected and evaluated
What Phase 0 is not:
- Vendor demos or RFPs
- ERP & tool selection
- Configuration or design
- Sales-driven discovery sessions
A successful Phase 0 is introspective for the most part. Where are we? Are we ready? What must be done? If Phase 0 feels uncomfortable, that is usually a sign it is working. It forces decisions that are often deferred until it is too late.
Why ERP Projects Fail When Phase 0 Is Rushed or Skipped
When ERP projects struggle, it is rarely because of the software. It is because the foundation was weak.
Here are the most common Phase 0 failures I see.
1. Lack of executive alignment
Funding gets approved, but leadership is not aligned on what success actually looks like. IT becomes accountable for outcomes it does not control.
2. Vendor led definition
Partners define scope, requirements, and timelines before the business has agreed internally. The project drifts toward what is easy to sell rather than what the business needs.
3. ERP treated as a side job
Subject matter experts are expected to do ERP work on top of their day jobs. No backfill is planned. Burnout starts before build even begins.
These are not go live problems. They are Phase 0 problems.
Here is your 6 Step process to nailing Phase 0:
Step 1: Define the Business Case So You Can Get Approved With Confidence
Your first job in Phase 0 is not to justify technology. It is to frame the business problem.
Executives want clear answers to a few questions:
- Why are we doing this now?
- What business outcomes are we driving?
- What happens if we do nothing?
- What will change for the organization?
Lead with outcomes, not features. Avoid module lists and screenshots. You could even argue that deciding between D365 Finance & Supply Chain Management or D365 Business Central isn’t important yet. Focus on measurable impact such as financial visibility, operational efficiency, risk reduction, or scalability.
The output of this step should be a concise business case that an executive can defend in a board conversation without you in the room. I often hear executives say they are being asked to approve a large investment without a shared understanding of what “right” looks like. One CFO described it this way:
“The hardest part of this project is that the exec team doesn’t know what right looks like. Getting alignment at the executive level is my number one priority.”
CFO, Food & Beverage MFG Company
Phase 0 is where you define that picture clearly enough that everyone can point to the same destination.
Step 2: Establish Scope and Guardrails Before Everyone Wants Their Version
ERP projects fail quietly through scope creep long before they fail loudly through budget overruns.
Phase 0 is where you define boundaries.
That includes:
- What business units are in scope
- What processes are in scope
- What will not be addressed in this phase
Clear guardrails do not limit the business. They protect it.
As a VP of IT, this is also where you earn trust. Saying not now with a clear rationale is far better than saying yes and failing later.
Step 3: Map Business Processes and Real Requirements Before Talking to Vendors
Requirements are about decisions, not wish lists.
In Phase 0, process mapping should focus on:
- Where the business is today
- Where it truly needs to be
- What pain points must be resolved
- Where standardization is acceptable
- Where flexibility is non-negotiable
This work must be business-owned, not vendor-authored. If a partner writes your requirements, you will get a solution optimized for their delivery model.
This is also where strong IT leaders must resist the urge to hand control to vendors.
“Do not let vendors run the show. You need to know what you want and why before a Partner proposes solutions.”
D365 F&SCM Program Manager
Strong requirements give you leverage later. Weak ones hand it away.
Step 4: Build the Real Resourcing and Governance Model
This is where ERP plans become credible or quietly fail. In Phase 0, resourcing must move from assumed to explicit.
The most common mistake? Assigning “Reviewers” instead of “Decision Makers.” You must identify who truly owns the business processes across Finance, Supply Chain, and Operations. These individuals cannot just be invited to meetings; they must have the authority to pull triggers and the capacity for sustained involvement.
Identify Resource Gaps Early
Most organizations do not have deep, end-to-end ERP implementation experience sitting on the bench. That is normal. However, significant risk emerges when internal teams are expected to:
- Design complex “future state” processes
- Audit and challenge aggressive vendor recommendations
- Make high-stakes architecture decisions
…all while seeing D365 ERP for the very first time.
Where Independent D365 Contractors Add Value
This is the “Keystone” moment. Experienced independent D365 contractors fill these critical gaps without adding permanent headcount. They aren’t there to do the work your team can do; they are there to provide the framework your team doesn’t have yet.
Independent contractors bring:
- Pattern Recognition: They’ve seen 10+ D365 programs and know where the “landmines” are buried in your specific industry.
- Neutrality: They provide objective guidance without the pressure of hitting software sales quotas or billable-hour targets.
- Cross-Functional Vision: A D365 Solution Architect understands how a small change in Supply Chain configuration will create a massive reconciliation headache for Finance three months later.
This is exactly why we built the community at d365contractors.com. We give VPs of IT direct access to vetted, independent leaders who have already lived through Phase 0 and know how to tie Finance, Supply Chain, and Operations into a unified, functional system.
Stop the “Side-Job” Death Spiral
If your Subject Matter Experts (SMEs) are expected to contribute without a backfill plan, the project is already at risk.
- Operational Backfill: Their daily responsibilities must be covered by someone else.
- Burnout Prevention: ERP work is mentally taxing. If it’s treated as a “side job,” your best people will leave before UAT begins.
As one VP of IT we spoke to put it:
“If your internal team is doing this as a side job, you are doomed.”
Establish Hard Governance
Strong governance isn’t about bureaucracy; it’s about velocity. You need a clear path to “Yes.”
- Steering Committee: Executive-level authority to resolve budget and priority conflicts.
- Process Owners: The “single throat to choke” for every department.
- Escalation Paths: A defined 24-hour rule for decisions that stall the project.
Step 5: Identify Risks Early So You Are Not Asking for Emergency Budget Later
VPs of IT worry about missing something, and for good reason. Industry research has consistently shown that ERP failures are far more often tied to poor upfront planning and governance than to technology itself, a trend documented in multiple ERP studies by firms such as Panorama Consulting.
Risk discussion is true leadership. Phase 0 should surface risks such as:
- Data quality and migration complexity
- Integration dependencies
- Customization pressure
- Regulatory or compliance constraints
- Change readiness across teams
Executives are far more receptive to risk when it is presented early and tied to mitigation plans. Late surprises damage credibility and trust. Experienced program leaders are consistent on this point. Risks that surface late are rarely new. They are risks that were not discussed early.
As one ERP delivery leader noted:
“You want data migration and risk planning to start during Phase 0, not in parallel with testing.”
D365 F&SCM Delivery Leader
Step 6: Use Phase 0 to Control Partner Selection Instead of Being Sold To
Partner selection should be a consequence of clarity, not a substitute for it.
When Phase 0 is done well, you can:
- Run a focused RFP or RFI
- Compare vendors on an apples to apples basis
- Validate delivery models and references
- Negotiate scope and accountability from a position of strength
When Phase 0 is skipped, the loudest sales team wins. The business pays for it later.
Successful D365 Phase 0 Checklist:
Phase 0 is complete when you have:
- An approved business case
- Aligned executive stakeholders
- Defined scope and success criteria
- Documented business processes and requirements
- A realistic resourcing and governance model
- A visible risk register
- Clear Partner selection criteria
- A board-ready budget narrative
At this point, implementation becomes execution, not discovery.
Thinking about an ERP Project? Start with Phase 0
If you are a VP of IT preparing for a D365 ERP initiative and want to sanity-check your Phase 0 approach before taking it to the executive team, we can help.
At d365contractors.com, we work with IT leaders during the earliest planning stages to validate assumptions, identify resourcing gaps, and bring in independent D365 experts where needed.
Book a call with Ryan to pressure-test your Phase 0 plan before implementation decisions are locked in:
