← VuduVationsThe Intelligence Bureau
VuduIntelConsulting-AI Intelligence
← Edition No. 9
Big Four

EY and PwC each paid Microsoft to supply the AI engineers they do not have.

Two of the Big Four locked billion-dollar Microsoft alliances in the same week, buying the execution muscle their advisory practices were never built to hold.

VuduVations Intelligence Bureau · May 21, 2026 · 2 min read
Own vs RentThe Repricing
Share

In a single week in late May, two of the largest advisory firms in the world made the same admission through their checkbooks. On May 21, EY and Microsoft announced a global AI program worth more than one billion dollars over five years, pairing Microsoft's forward deployed engineers with EY advisers to push clients past pilots and into full deployment across finance, tax, risk, human resources, and supply chain. Three days earlier, PwC and Microsoft launched a commercial engineering motion aimed at the same goal: moving companies from experimenting with AI to running it at scale.

Read the two announcements together and the pattern is hard to miss. The Big Four built their AI practices on advice: which models to adopt, which governance to install, which vendors to trust. That is a real business, but it is not the same thing as building and running the systems. When the market started paying for execution rather than opinion, the advisory firms did not suddenly grow an engineering bench overnight. They rented one. PwC's own AI and engineering leader, Matt Hobbs, has put the stakes plainly in public: execution, done consistently and at scale, is becoming the thing that separates the winners. The alliances are the response to that sentence.

The uncomfortable question sits one layer down. When Microsoft's engineers are the ones in the client account doing the work, who actually owns the relationship, and who owns the margin. A firm that advises keeps the client. A firm that resells someone else's engineers becomes a channel. EY framed its deal as helping clients move beyond experimentation to scaled execution, and that framing is accurate. The mechanism underneath it is that the scaling is being done by the platform, not by the firm whose name is on the invoice.

None of this is a failure of nerve. It is a rational move by firms that needed delivery capacity faster than they could grow it. But renting the engine is a different business than owning it, and the difference shows up in the margin line the moment the platform decides to raise its price or go direct to the customer.

A firm that rents its engineers has bought speed today and handed away leverage tomorrow. The platform can always raise the rent.
VuduVations Intelligence Bureau
The VuduVations Read
The incumbents just told the market, in public, that they do not own the thing the market is now paying for. They are renting execution from a platform and billing the client for the privilege. The one position that does not get repriced when the vendor renegotiates is an outcome the client owns and can run on its own. MCOS delivers that as Consulting-as-Code: a client-owned, source-cited, model-portable procedure that keeps running after the alliance ends and the engineers roll off. Own the outcome, not the borrowed bench.
Share
Sources
EY and Microsoft announce global AI initiative, Microsoft Source
Microsoft and EY to spend $1 billion helping clients adopt AI, Bloomberg
PwC and Microsoft commercial engineering for AI solutions, PwC
Firms in this story: EY · PwC · Microsoft← Back to Edition No. 9