In the first week of July, the AI deployment market changed shape. Microsoft announced Frontier Company, a new operating business focused on delivering enterprise AI deployments, backed by a $2.5 billion investment and 6,000 industry and engineering experts. Two days earlier, Amazon Web Services had announced a $1 billion internal commitment to its own AI deployment venture, explicitly embracing the forward-deployed engineering model. Anthropic and OpenAI both established FDE groups in May, partnering with private equity firms, banks and consulting firms. And weeks before that, OpenAI launched its Partner Network with a $150 million investment and a target of 300,000 certified consultants by the end of 2026.
Four announcements. One pattern. The platforms that build the models have decided they will also deploy them.
For twenty-five years, the enterprise technology stack ran on a division of labor so stable nobody wrote it down anymore: platforms build, integrators deploy. Microsoft sold licenses; Accenture sold transformation. The boundary was the business model. That boundary just moved — and it moved in one direction.
The tell is in the framing. Microsoft says Frontier Company will work closely with its partner ecosystem, citing robust FDE partnerships with global SIs including Accenture, Capgemini, EY, KPMG and PwC. Its commercial CEO resisted the FDE label entirely, describing instead the largest, most capable, outcome-driven engineering organization in the industry. Both things are said in the same announcement: we will work through our partners, and we are building the biggest deployment force in the market. In dealcraft terms, that is not a contradiction. It is a negotiating position.
I have structured partnerships on both sides of this line — inside a platform running direct and partner motions simultaneously, and advising the partners navigating it. The pattern is always the same: the announcement talks ecosystem; the org chart talks capture. Which one prevails is not decided by the press release. It is decided by the governance and economics nobody reads until there is a dispute.
So here are the questions the partner ecosystem should be asking — the ones that determine whether “partnership” survives contact with a 6,000-person deployment army.
1. Who owns the client relationship — structurally, not rhetorically?
When a platform’s deployment unit and its SI partner both qualify for the same statement of work, someone decides who leads. Is there a deal registration system with teeth? A conflict-of-interest protocol? An escalation path that doesn’t terminate inside the platform’s own sales hierarchy? If the answer to “who arbitrates channel conflict” is the party with the $2.5 billion deployment unit, that is not governance. That is discretion — and discretion always flows toward the balance sheet that funds it.
2. What do the co-sell economics actually pay for?
Every platform-partner agreement now needs its economics stress-tested against a new scenario: the platform competes for the deployment revenue it used to hand you. What is the referral fee when the platform’s own unit takes the work your relationship sourced? Who books the outcome when delivery is blended? Are partner incentives tied to influence, sourcing, or delivery — and who measures which? These are exactly the terms that were left soft when the platform had no delivery arm. They cannot stay soft now. Incentives that are not engineered will invert.
3. Who owns what the deployment creates?
Microsoft’s stated principle is that a customer’s intelligence is protected — data, IP and competitive advantage are not used to commoditize what differentiates them. Good. Now ask the partner-side version of the same question. When a joint deployment produces reusable accelerators, industry templates, workflow IP — who owns them? The platform that hosts, the SI that built, or the client that paid? In my experience, deployment-phase IP is the single most under-negotiated asset class in enterprise partnerships, because at signing it doesn’t exist yet. Eighteen months later it is the whole ballgame.
4. What is the exit, and who priced it?
Partner agreements in this market were written for a world where the platform needed the channel. Terms renegotiate when leverage shifts — and leverage just shifted, publicly, with a number attached. Partners should be modeling their agreements the way an investor models a position: what happens at renewal, what happens if the platform’s unit takes priority allocation of scarce engineering and model capacity, what the contingency is if co-sell becomes compete. A partnership without a priced exit is not a partnership. It is an option the stronger party holds over the weaker one.
The deeper point is one I have argued since writing The New Rules of Partnerships: in the AI era, ecosystems beat individual firms — but only engineered ecosystems. What Microsoft, Amazon, Anthropic and OpenAI are all signaling is that deployment is where AI value is actually realized, and no one intends to leave value realization to someone else’s P&L. The SIs will not exit this market; it is their market. What changes is the architecture. The stable, implicit, handshake-governed platform-SI relationship is being replaced by something that must now be explicitly structured: decision rights, measured incentives, IP allocation, and contingency terms — negotiated before the next master agreement renews, not after the first channel conflict.
The firms that treat last week’s announcements as a press-release event will find out what their partnership was worth when the first deal collides. The firms that treat it as a structuring event will renegotiate from strength while the platforms still need the channel’s coverage.
The announcements are easy. The architecture is hard. That gap is where partnerships are won and lost — before anything breaks, and long before anyone admits it could.
Randy McGraw is the founder of M2 Ventures and author of The New Rules of Partnerships. He has structured more than $2.3B in partnership and JV value across Japan and APAC.