🔍 Read the full analysis: The Trade-Offs Of Switching From Claude After Meta And Microsoft Pulled Back on ThorstenMeyerAI.com
Get office and shipping supplies delivered free — and shop member deals
- Fast, free delivery on millions of items
- Access to Prime Big Deal Days deals on October 6–7
- Prime Video, Amazon Music and more included
TL;DR
The Information reported on Oct. 5 that Meta roughly halved employee use of Claude Code and Microsoft cut its projected internal spending on Anthropic technology by more than a third. The reported shifts concern internal use, not a broad end to Claude access or customer-facing services, and are attributed to cost controls and in-house alternatives rather than a reported quality failure.
Meta and Microsoft are steering some employees away from Anthropic’s Claude tools and toward their own or other existing products, according to a report by The Information on Oct. 5. The reported changes concern the companies’ internal use, not a decision to end Claude access for customers, and show how large buyers can shift work when costs rise and alternatives are available.
Meta reportedly reduced the number of employees using Claude Code from about 60,000 earlier this year to about 30,000. The report says the company has directed staff toward its internal coding tools, MetaCode, which has more than 30,000 users, and Muse Code, with more than 6,000. Those figures describe reported internal usage; they do not establish how much coding work has moved or compare the tools’ performance.
Microsoft had reportedly projected more than $1 billion a year in internal Anthropic spending, covering Claude Code, Claude models in Copilot and Claude Mythos. It has cut that projection by more than a third, according to the report, while steering employees toward GitHub Copilot and OpenAI models. Microsoft is also reported to continue using Anthropic models for some customer-facing Copilot features, with customer spending on Claude through Microsoft platforms growing.
The source material attributes the internal pullback to rising token costs, tighter spending controls and competing in-house or partner tools. It does not report that either company said Claude performed worse. A further detail in the report says some Microsoft team budgets fell from roughly $100,000 per month to roughly $10,000; that figure is attributed to a single account and should not be treated as a company-wide budget change.
Meta and Microsoft pulled back from Claude. Here’s what switching actually costs.
The Information reports both companies steering their own employees away from Claude. Read as a verdict on Claude, it misleads. Read as a demonstration of switching — and who can afford it — it’s the most useful enterprise-AI signal this month.
Staff steered to GitHub Copilot and OpenAI models; stricter token budgets. One unconfirmed report: some team budgets ~$100k → ~$10k/month.
Microsoft reportedly still spends heavily on Claude for customer-facing Copilot — and that spending is reported to be growing.
Reported drivers: rising token costs and owned alternatives. Neither company is reported to have called Claude worse.
Meta builds coding tools; Microsoft owns Copilot and backs OpenAI. This is ordinary vertical integration.
Keep a second vendor live on real work.
A few hundred tasks with pass criteria.
Logic, prompts, tools in your layer.
Tokens are the cheap half.
Know what you’d rebuild.
On the evidence reported, Meta and Microsoft didn’t reject Claude. They brought spending in-house where they could and kept buying where they couldn’t — Microsoft remains a large Anthropic customer for the products it sells. The signal is the mechanism: the most sophisticated buyers treat models as interchangeable suppliers behind a layer they control.Meta could halve its Claude usage because it had built somewhere else to go. Build somewhere else to go.
Why Internal AI Budgets Are Shifting
The reported decisions show that large organizations can treat AI models and coding assistants as workloads to route among suppliers, rather than making a single permanent choice. When a company already has alternatives deployed, it can shift employee use in response to price, budgets or strategy without necessarily ending another provider’s role elsewhere.
That flexibility is not free for most buyers. Moving a workflow can require new evaluations, prompt and tool changes, adjustments to integrations, and time for employees to learn a different system. It can also affect output quality and the amount of human review required. Those costs are harder to see on an invoice than token charges, but they can shape whether a switch saves money overall.
Meta and Microsoft have substantial engineering resources and existing products to route work toward. Their reported choices are not direct evidence that a smaller company can make the same move at comparable cost or speed. For buyers, the practical question is not only which model is cheaper, but whether the full workflow—including accepted output, rework and review—remains cost-effective after a change.
As an affiliate, we earn on qualifying purchases.
The Alternatives Behind the Shift
Both companies have reasons to favor alternatives they own, build or already distribute. Meta develops its own models and coding tools. Microsoft owns GitHub Copilot and is a major backer of OpenAI. That makes the reported move different from a buyer with no substitute: internal adoption can support products and platforms that also serve the companies’ broader strategies.
The report’s scope matters. It describes decisions about employees’ use and internal spending, while also saying Microsoft continues to use Anthropic models in customer-facing Copilot features. The information provided does not establish that either company has terminated its relationship with Anthropic or that customers have lost access to Claude through Microsoft services.
The reported figures also measure different things: employee counts, a spending projection, and tool user totals. They do not provide a common measure of workload, productivity or quality. The numbers can indicate a change in internal direction, but they cannot alone show whether the alternatives perform better or deliver greater value.
As an affiliate, we earn on qualifying purchases.
What the Report Does Not Establish
The report, as summarized in the source material, does not provide a detailed account from Meta, Microsoft or Anthropic explaining the changes. It is not clear how much internal work has shifted, whether the reported user counts refer to active users or access, or how those counts were measured. The specific timing and implementation of the changes are also not fully laid out.
There is no reported head-to-head evaluation showing how Claude compares with MetaCode, Muse Code, GitHub Copilot or OpenAI models on the companies’ tasks. Nor is there a full cost breakdown covering engineering time, employee productivity, review, rework and infrastructure. The reported budget cut from one Microsoft account may not reflect other teams. The available information therefore supports a report of internal cost and tool changes, not a general verdict on model quality or Claude’s customer demand.
As an affiliate, we earn on qualifying purchases.
How Companies Measure the Switch
The next useful evidence would be clearer reporting from the companies on the scale and duration of the changes, the reasons for them, and whether Anthropic tools remain part of internal or customer-facing systems. Comparable information on costs and performance would help separate budget decisions from changes in output quality.
For other organizations, the reported moves put attention on preparation rather than an immediate choice to leave any particular provider. Buyers can test more than one model on representative tasks, retain their evaluation results, and track not only token spending but also accepted output, review time and rework. Whether Meta and Microsoft’s reported savings outweigh the costs of moving work is not established by the figures provided.
As an affiliate, we earn on qualifying purchases.
Key Questions
Have Meta and Microsoft stopped using Claude?
The report describes reduced internal use and a lower spending projection, not a complete end to Claude access. It also says Microsoft continues to use Anthropic models for some customer-facing Copilot features.
Why are the companies reportedly shifting employees?
The reported reasons are rising token costs, tighter spending controls and the availability of other tools. The source material does not report either company saying Claude performed worse.
How much did Meta’s reported Claude Code use change?
The Information reported that Meta’s employee count using Claude Code fell from about 60,000 earlier this year to about 30,000. The source does not specify whether those figures represent active users or access.
Does the report show that switching models saves money?
No overall savings calculation is provided. Moving tools can involve engineering, evaluation, retraining, review and rework costs, so the reported spending changes alone do not establish the net financial effect.
What should other companies take from the report?
The reported moves show the value of having alternatives ready, but Meta and Microsoft have tools and engineering capacity that many buyers lack. Testing models on real tasks and measuring total workflow costs can help organizations judge a change on evidence rather than token prices alone.
Source: ThorstenMeyerAI.com
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
