Microsoft just created a standalone operating unit called Frontier Company, backed by $2.5 billion and staffed with 6,000 industry and engineering specialists. Their job is to sit inside your organization and help you use the models that already exist.

Two days before that announcement, AWS committed $1 billion to a nearly identical initiative. And in May, both OpenAI and Anthropic launched their own deployment-focused consulting arms.

Four of the five companies that build the AI your organization is evaluating have now started separate businesses dedicated to one problem: the fact that most companies cannot get AI to work in production.

The companies that make the models are now selling the service of helping you use them. That tells you everything about where the real bottleneck sits.

Where Microsoft Is Putting the People

Microsoft’s Commercial Business CEO Judson Althoff described Frontier Company as “the largest, most capable, outcome-driven engineering organization in the industry.” The unit is led by Rodrigo Kede Lima, who previously ran Microsoft’s entire Asia business. Early partners include Unilever, the London Stock Exchange Group, Land O’Lakes, and Accenture.

Microsoft is putting $2.5 billion behind the work of preparing organizations to use its models.

That framing matters. For two years, the dominant narrative in enterprise AI has been about capability. Which model is smarter. Which benchmark score is higher. Which provider has the best reasoning. And while that conversation was happening, the actual failure rate in enterprise AI deployment stayed stubbornly high. Gartner’s latest numbers show 40% of enterprise applications will integrate AI agents by the end of 2026, up from less than 5% in 2025. But a 60% governance gap remains between what organizations deploy and what they can actually manage.

Deployment problems persisted as models improved.

What This Tells You About Your Own AI Effort

If you run a team or lead an organization in the middle of an AI initiative, this announcement deserves a look at your own deployment plan.

Here is what the Frontier Company model tells us about the current state of enterprise AI:

The pilot trap has structural causes: companies need to redesign the process the AI is supposed to fit into. Microsoft is betting $2.5 billion that the fix requires humans sitting inside customer operations, mapping workflows, and rebuilding them around AI. A services company gives Microsoft people to do that work with customers.

That is one data point. Here are three more: four separate AI providers all launched deployment consulting businesses within 90 days of each other. They are responding to the same market signal. Their customers need help closing the last mile. The gap between “we have an AI tool” and “AI is changing how we operate” has gotten wide enough to support billions of dollars in new business.

Even with 6,000 engineers available to build and integrate, your organization still owns the decisions about what AI should do, which tasks to retire, which processes to change, and how to retrain people whose jobs shift.

What the Services Commitment Means for Smaller Teams

Frontier Company probably makes business sense for Microsoft. For its enterprise customers, the revealing decision is the commitment of 6,000 people to help them deploy AI.

If Microsoft, with Azure, Copilot, and the largest enterprise distribution channel in tech, still needs a $2.5 billion services arm to get AI into production at its biggest clients, what does that tell you about the mid-market company trying to do it with a three-person IT team and a SaaS subscription?

I keep coming back to this point with every client I work with: redesigning how your team functions with AI in the loop requires operational work. Budget for that process work alongside the license, while the deployment is still small enough to change.

What This Means This Week

If you are evaluating AI tools right now, evaluate your processes alongside them. Gartner’s 60% governance gap, Microsoft’s $2.5 billion deployment bet, and AWS’s $1 billion matching commitment all point to the operational work required.

Redesign one workflow, staff it properly, measure the result, and then do the next one. That gives your team a concrete way to put its model choice to work.

Microsoft’s $2.5 billion commitment puts resources behind that work.