Six things have to be true before AI changes a workflow. Most companies have built two.

The interesting thing about Anthropic’s new enterprise AI services company isn’t the services part. Enterprise software has always needed implementation help: cloud migrations, ERP projects, Salesforce rollouts, the forward-deployed engineering Palantir made famous. What’s new is the target. Anthropic is aiming this venture at mid-sized businesses: the segment with enough operating complexity to benefit from frontier AI, but rarely with enough internal engineering to turn it into working systems.

That target tells you something. The hard part of enterprise AI is no longer buying access to a powerful model. Any company can approve ChatGPT Enterprise, Claude, or Gemini, buy seats, call an API, and produce impressive internal demos. None of that proves the company has actually changed how support tickets move, how invoices close, how compliance reviews happen, or how customers get served. Value shows up when the model has a specific role in a specific workflow, with the right data, permissions, review process, and success metric. That work is what most companies haven’t built. In the last few months, agents have gotten reliable enough at running entire workflows that the distance between companies that have built it and companies that haven’t is starting to compound.

That’s why Anthropic, OpenAI, Blackstone, Hellman & Friedman, and Goldman Sachs are all making moves right now. The implementation layer has become the strategic layer in enterprise AI. There are trillions of dollars in workflow value waiting on whoever figures this out first, and the companies that already understand this are about to pull further ahead.

Here’s what’s inside:

• What’s actually new about the Anthropic deployment company. Why the mid-market target and PE backing signal a shift from model sales to deployment capacity — and what private equity sees that the market doesn’t.

• What “implementation architecture” actually means. The technical and operational work that separates AI experiments from production workflows.

• The risk: services that don’t turn into product. When field work compounds into reusable assets versus when it stays bespoke.

• What this means for startups, buyers, and builders. Where narrow, deep ownership beats generic AI productivity plays — and the specific move each one should make next.

• The implementation architecture audit. A prompt that scores your AI product against the six components, tells you whether you own a workflow or decorate a model, and surfaces the two questions that will end your next enterprise deal.

Let me show you how the pieces connect, and what the next phase of enterprise AI actually requires.