Big Tech Loved Claude. Now It’s Trying to Replace It.

Big Tech Loved Claude. Now It’s Trying to Replace It.

The better Claude gets, the stronger the incentive to replace it.

There is a fascinating problem emerging for Anthropic just as the company prepares for what could become one of the largest IPOs in history.

Some of the companies spending enormous amounts of money on Claude are simultaneously trying to use less of it.

Microsoft has reportedly cut its projected internal spending on Anthropic’s models by more than a third.

Meta has cut the number of employees actively using Claude Code roughly in half.

Palantir and Nvidia have placed restrictions around certain Claude usage.

And Meta is increasingly pushing employees toward AI coding systems it built itself.

At first glance, that sounds terrible for Anthropic.

Look closer, however, and the story is considerably more interesting.

Claude may be becoming so useful that its biggest customers can no longer afford to rent all of that intelligence.

Microsoft Was Heading Toward $1 Billion a Year

According to reporting by The Information, Microsoft had projected that its own employees could spend at least $1 billion annually using Anthropic’s models.

Microsoft has now reduced that projected internal spending level by more than one-third.

Inside parts of Microsoft’s cloud and AI organization, the change has been even more dramatic.

Monthly Claude budgets that reportedly reached roughly $100,000 per employee were reduced to around $10,000.

That sounds almost unbelievable until you understand how AI coding agents work.

A developer isn’t necessarily sending a few prompts every afternoon.

An agent can continuously:

Read enormous codebases.

Search files.

Reason across thousands of lines of code.

Generate code.

Run tests.

Debug failures.

Read the results.

Try again.

And continue doing that for hours.

Every step consumes compute.

At enterprise scale, an incredibly productive AI agent can also become an incredibly efficient way to burn money.

Microsoft Isn’t Abandoning Claude

This distinction is important.

Microsoft is reducing internal employee spending on Anthropic.

It isn’t removing Claude from everything Microsoft sells.

Customer spending on Anthropic models through Microsoft’s products has reportedly continued increasing.

Microsoft also has an investment commitment of up to $5 billion in Anthropic.

So this isn’t necessarily:

Microsoft thinks Claude is bad.

It looks much more like:

Microsoft thinks Claude is expensive enough that its own employees shouldn’t use the most expensive option for every problem.

Employees are being steered toward alternatives including Microsoft’s own GitHub Copilot⁠ and models from OpenAI.

That’s ordinary IT cost optimization—just at extraordinary scale.

Meta’s Numbers Are Even More Interesting

Earlier this year, approximately 60,000 Meta employees were reportedly using Claude Code.

That number has fallen to around:

30,000.

Some of that decline reflects Meta’s workforce reductions.

But reporting indicates that a larger factor is Meta increasingly steering employees toward its own AI development tools.

Meta’s internal MetaCode tool has surpassed 30,000 users.

Another Claude Code competitor, Muse Code, reportedly has more than 6,000 internal users.

Meta isn’t merely negotiating a better Claude contract.

It’s attempting to replace some of the work Claude performs with technology it owns.

And then comes the number that explains why.

Meta Reportedly Spent More Than $105 Million in 28 Days

Despite reducing the number of employees using Claude Code, Meta reportedly spent more than $105 million on Claude Code during one recent 28-day period.

Think about that number.

Not annually.

Not across five years.

Twenty-eight days.

At that scale, building an internal alternative starts looking less like an ambitious AI research project and more like a procurement decision.

Suppose your company pays $30 a month for some SaaS application.

Nobody seriously proposes building a competitor internally.

Now suppose your company is spending hundreds of millions—or potentially billions—on that category.

Suddenly hiring hundreds of engineers and buying thousands of GPUs can make economic sense.

Rent is convenient until you’re renting an entire city.

This Is the Cloud Story Happening Again

We’ve seen versions of this cycle throughout technology.

A company discovers an external product that is dramatically better than what it can build quickly.

So it buys it.

Employees adopt it.

Usage explodes.

The technology becomes operationally important.

The bill explodes.

Then someone asks:

Why are we paying another company this much money for something this strategically important?

At small scale, SaaS wins.

At enormous scale, economics can reverse.

Cloud computing itself created this tension.

For most businesses, building a data center instead of using AWS or Azure would be absurd.

But at sufficient scale, companies start designing their own infrastructure.

AI may follow an even more aggressive version of that pattern because the marginal cost of heavy inference can be substantial.

Anthropic Is Teaching Its Customers What They Need to Build

There’s another strategic problem.

Every month Microsoft or Meta spends heavily on Claude, its engineers learn something.

They learn which AI workflows matter.

Which coding tasks benefit most.

Where agents fail.

How employees interact with them.

Which features developers love.

How much productivity they gain.

What latency is acceptable.

What capabilities are worth paying for.

Anthropic isn’t merely selling intelligence.

Its customers are learning what valuable intelligence looks like.

Eventually, the largest customers can take those lessons and ask their own AI teams to reproduce enough of the experience internally.

They don’t necessarily need to build a model better than Claude at everything.

They only need something good enough at the workloads consuming millions of dollars.

That is a much easier target.

Meta Doesn’t Need to Beat Claude

This is the key economic concept.

Suppose Claude performs a particular coding task at 100.

Meta’s internal model performs at 92.

Normally you’d choose Claude.

But suppose Claude costs the company $100 million while the internal system’s incremental cost is dramatically lower.

That eight-point performance difference suddenly has a price.

For the hardest engineering problems, Claude might still win.

For routine coding tasks, internal models might be good enough.

You end up with intelligent model routing:

Simple task → cheaper internal model.

Moderate task → another efficient model.

Extremely difficult task → Claude.

This is already how sophisticated enterprises are beginning to think about AI.

The future may not be one AI model. It may be an AI procurement engine.

Anthropic Itself Is Telling Customers to Think This Way

Interestingly, Anthropic’s own enterprise guidance encourages companies to evaluate AI based on cost per outcome, rather than merely counting tokens.

The company suggests asking whether the model is performing work requiring difficult reasoning or simply processing large quantities of relatively straightforward work.

That’s sensible advice.

It’s also precisely why enormous customers might move routine workloads away from Anthropic’s most expensive models.

If Claude saves a senior engineer three hours solving an extremely difficult problem, paying several dollars—or considerably more—for that work may be trivial.

If thousands of agents repeatedly perform simple transformations that an internal model handles almost as well, the economics are completely different.

Use expensive intelligence where intelligence is expensive to replace.

Then There’s the Data Problem

Cost isn’t the only concern.

Palantir and Nvidia have reportedly imposed restrictions around external AI models because of concerns involving proprietary information and data control.

Reuters reported last month that Palantir sought an irrevocable zero-data-retention commitment from Anthropic.

Nvidia reportedly limits Anthropic models to less-sensitive tasks.

Booz Allen Hamilton reportedly prohibited employees from using Anthropic’s commercial AI for certain proprietary cybersecurity work.

Palantir’s own documentation makes the data path explicit: when Claude Code is used locally with Palantir’s MCP integration, relevant tool outputs are sent to Anthropic and governance depends on the organization’s contract with that provider.

That doesn’t mean Anthropic is stealing corporate data.

It means security teams care deeply about where sensitive information travels.

And the more capable AI agents become, the more information employees want to give them.

Source code.

Architecture.

Credentials.

Customer information.

Internal documentation.

Incident-response data.

Product roadmaps.

Business strategy.

An AI coding assistant can become one of the most information-hungry applications inside a company.

Building Your Own AI Changes the Trust Boundary

If Meta uses Claude to analyze proprietary Meta code, another company sits somewhere in the processing chain.

If Meta uses infrastructure and models it controls itself, the security architecture changes considerably.

That doesn’t automatically make the internal system secure.

Internal systems can be compromised too.

But it reduces the number of organizations that must be trusted.

That’s a fundamental cybersecurity principle:

Every external dependency expands your trust boundary.

For most SMBs, eliminating major AI providers isn’t realistic or necessarily desirable.

For Meta, Microsoft or Nvidia?

The calculation is completely different.

They have the engineers.

They have the data centers.

They have the GPUs.

They have the models.

And increasingly, they have a financial reason to use them.

But Calling This a Claude Collapse Would Be Completely Wrong

This is where the viral framing can become misleading.

Anthropic’s business is growing at an extraordinary rate.

Its annualized revenue run rate exceeded approximately $65 billion by the end of July, according to Reuters, up from $47 billion in May and roughly $9 billion at the end of 2025.

And be careful with that $65 billion number.

It is a run rate, not $65 billion of revenue already collected over the preceding 12 months. It annualizes a recent level of sales.

That’s still extraordinary growth.

Anthropic had valued itself at $965 billion in its May funding round and is now pursuing an IPO that could value it at more than $2 trillion.

So Anthropic isn’t confronting customers abandoning a failed product.

It’s confronting something arguably more complicated:

Customers love the product enough that their bills have become strategically important.

The IPO Makes This Much More Interesting

Anthropic’s IPO prospectus already identifies dependence on major technology companies as a significant business issue.

Reuters’ analysis of the filing found that roughly 16% of Anthropic’s revenue comes through cloud partnerships, while Anthropic depends on many of those same technology companies for the enormous computing infrastructure required to build and operate Claude.

That creates an extraordinary web of relationships.

Amazon can be:

Investor.

Cloud provider.

Distribution channel.

Infrastructure partner.

And potential competitor.

Microsoft can be:

Investor.

Customer.

Distribution channel.

OpenAI partner.

And competitor.

Google can be:

Investor.

Infrastructure provider.

Model competitor.

Meta can be:

Customer.

Model competitor.

Coding-agent competitor.

This isn’t a traditional supply chain.

Everyone is simultaneously buying from, selling to, investing in and competing with everyone else.

Anthropic’s Greatest Customers May Be Its Greatest Long-Term Risk

Imagine you’re Anthropic.

Your ideal customer spends $10 million a year.

Fantastic.

Then $50 million.

Even better.

Then $500 million.

Incredible.

Then $1 billion.

At some point, you’ve created a new problem.

Your customer now has a billion-dollar incentive to eliminate you from part of its cost structure.

The more successful you become inside a hyperscaler, the more economically rational it becomes for that hyperscaler to develop an alternative.

That’s an unusual business paradox:

The customer becomes dangerous precisely because the customer became valuable.

This Won’t Happen the Same Way for Small Businesses

An SMB shouldn’t read this story and conclude:

“We need to build our own AI.”

Absolutely not.

Microsoft and Meta can justify developing internal models because their usage is enormous.

A 100-person law firm cannot.

A medical practice cannot.

A school cannot.

A typical mid-sized business cannot.

For those organizations, renting intelligence from OpenAI, Anthropic, Microsoft, Google or another provider will almost certainly remain vastly cheaper than attempting to create frontier AI infrastructure.

The relevant lesson is different.

Don’t become unnecessarily dependent on one model.

Businesses Need an AI Exit Strategy

We’re currently watching companies build workflows deeply around individual AI vendors.

Claude.

ChatGPT.

Gemini.

Copilot.

That’s convenient.

But imagine your organization builds hundreds of workflows around one provider and then:

Pricing triples.

Terms change.

Retention policies change.

A model is discontinued.

Performance deteriorates.

A regulatory issue blocks its use.

Your industry requires different data handling.

Or another model becomes dramatically better.

Suddenly AI vendor lock-in looks very similar to every other technology lock-in problem.

Businesses should increasingly separate:

The workflow

from

the model performing it.

Where practical, build systems capable of changing models without rebuilding the entire business process.

That’s especially important for MSPs managing AI adoption across multiple customers.

Treat Models Like Infrastructure, Not Religion

There is a strange tendency in AI right now to become tribal.

Claude people.

ChatGPT people.

Gemini people.

That’s fine for consumers.

It’s bad enterprise architecture.

The correct model depends on the workload.

One model might be extraordinary at coding.

Another cheaper for repetitive document processing.

Another better for multimodal analysis.

Another available inside a compliance boundary your organization requires.

Another may become best six months from now.

Businesses shouldn’t ask:

Which AI are we loyal to?

They should ask:

Which model gives us the best combination of capability, cost, security and control for this task?

That’s a very different question.

Anthropic’s Problem May Actually Prove How Valuable AI Has Become

Microsoft cutting Claude spending by a third sounds bearish.

Meta cutting Claude Code users from roughly 60,000 to 30,000 sounds worse.

But Meta reportedly spending more than $105 million in just 28 days on Claude Code tells another story entirely.

Companies don’t spend that kind of money on software nobody values.

The danger for Anthropic isn’t necessarily that Claude doesn’t work.

It’s that Claude works well enough to become an enormous line item.

Once that happens, the CFO notices.

Then procurement notices.

Then the internal AI team notices.

Eventually somebody does the math.

And one of the strangest dynamics of the AI economy begins:

Big Tech rents the best intelligence it can find—until renting becomes expensive enough to justify building its own.

For Anthropic’s potential $2 trillion IPO, that may be one of the most important risks investors have to understand.

Some of the company’s best customers aren’t merely negotiating their bills.

They’re building the replacement.

70% of all cyber attacks target small businesses, I can help protect yours.

#ArtificialIntelligence #Cybersecurity #Anthropic #EnterpriseAI #ManagedIT

Meta reportedly spent $105 MILLION on Claude Code in just 28 days. Now it’s trying to replace it. Microsoft has cut projected internal Claude spending by more than a third too. Claude isn’t necessarily losing—the problem may be that it became so useful that Big Tech decided renting AI was getting too expensive.