Most Dynamics 365 partners are pitching AI-first transformations in client meetings while running their businesses much the same way they did three years ago. And clients are beginning to notice.
Confident slide decks. Microsoft case studies. Polished language about the agentic journey ahead. Then the partners return to their own offices, open the same spreadsheets, and run the same time-and-materials projects they have always run.
This is not a credibility problem. It is a structural one. And it has a name.
What Customer Zero actually means
Microsoft’s position on this is unambiguous. At the Companial Global Connect event in January 2026, Cecilia Flombaum, Dynamics 365 Ecosystem Lead at Microsoft, was direct, “Partners need to be their own Customer Zero.” Not as a suggestion. As a prerequisite for operating credibly in the agentic era.
That means something specific. It does not mean issuing Copilot licences to your consultants and ticking the “adoption” box. It means running a real, agentic transformation in your own operations: identifying high-value internal workflows, redesigning them around human-plus-agent delivery models, tracking and monitoring them, and measuring KPI improvements. Build these from scratch where the investment is low, or the outcome creates reusable IP you can monetise externally.
The shallow version of this is everywhere. Partners who have deployed a handful of AI tools, generated some internal productivity metrics, and are now comfortable describing themselves as Customer Zero. This works as a talking point. However, it is not the same thing, and sophisticated clients are developing a feel for the difference.
Why most partners are not doing it
The avoidance is not ignorance. It is down to arithmetic.
A proper internal AI transformation requires real consultant time. Not a part-time project handed to whoever has some downtime between engagements. Actual senior people, pulled from billable work, running a meaningful programme over several months. For a 40-person implementation partner operating at healthy utilisation, that is a six-figure margin hit once you factor in the opportunity cost.
The financial logic of deferral is entirely rational. Every day a senior consultant spends on internal transformation is a day not billed to a client. The P&L feels it immediately. The return arrives later, and in a form that is harder to attribute. So, partners defer. They do the minimum viable version. They tell themselves they will do it properly next quarter, when utilisation eases.
But utilisation never eases. The quarter never arrives.
This is the core of the buy-versus-build decision. Most partners cannot afford to absorb that cost and uncertainty internally when equivalent capability could already exist externally.
The commercial pressure is already here
This is not a future problem. Microsoft’s Flombaum was explicit about this at the Companial event. Customers already expect ERP implementations to cost less and be faster, and agentic ERP is putting direct pressure on partner P&Ls across requirements gathering, data migration, process configuration, and testing – the four phases that have historically anchored partner revenue on every Dynamics 365 engagement.
Microsoft’s AI-First Partner Transformation Playbook puts harder numbers on it. Expectations of 30 to 50 per cent cost reductions are already being factored into large deal RFPs. Partners who have done the internal work understand where agents can absorb that reduction without destroying margin. Partners who have not are walking into those conversations with no practical anchor.
Three paths, two of which are bad
There are only three ways through this for most partners.
The first is to do it properly on your own. Accept the margin hit, ringfence the consultant time, run the internal programme with the same rigour you would apply to a client engagement. This is a viable answer for large global systems integrators with both financial headroom and a clear strategy for turning internal transformation into market-facing IP, but a genuine risk for a 30 to 60-person local implementation partner making things work month to month.
The second is the shallow version. Do enough to say you have done it, keep the consultants billable, move on. The problem is not that it feels dishonest, though it does. The problem is that it produces none of what Customer Zero is supposed to generate: validated delivery models, reusable IP, confidence in outcome-based pricing, and the ability to tell a client what you learned when things did not go as planned. It also leaves margin exposure unchecked because you have not redesigned delivery in a way that can absorb AI-driven price pressure.
The third path, and realistically the most viable for most partners, is to split the task.
Internally, focus only on the workflows where redesigning them creates reusable, monetizable IP you can take to market. For other areas, aim to buy rather than build wherever the investment stacks up. Bring in proven frameworks, tools, and pre-built IP so your consultants remain largely billable while you accelerate your Customer Zero journey.
This is not a compromise. It is a capital allocation decision. Build where differentiation compounds. Buy where capability already exists.
The partners who will get this right
The uncomfortable truth is that Customer Zero was always going to separate the partners genuinely transforming from those narrating a transformation they have not really started. That gap is closing. Clients are asking harder questions. What have you done internally? What did you learn? What would you do differently?
The partners who move fastest will not all be the largest ones. They will be the ones who solved the investment problem in the best possible way, by being disciplined about where they build and pragmatic about where they buy, and who arrive in front of clients with something real to show.
You cannot sell what you don’t have experience with yourself. The market is getting better at spotting the difference.
Ready to see how GYDE365 can support your Customer Zero journey?
Discover how Dynamics 365 partners are using GYDE365 to move beyond AI narrative and into real, operational transformation.
See how you can balance what to build and what to buy, without sacrificing billable utilisation or waiting months for results.