Anthropic Made $16.8B Last Quarter. Why Are Investors Nervous?

From Enterprise AI Weekly, recorded 16 October 2026. Anthropic made $16.8 billion last quarter. It grew 45%, and it turned a profit. And this week, some of its investors started talking about paying less for it. That is the question I want to work through today, and I think the answer is sitting in your AI budget.

Same format as always: one round, five stops. Anthropic’s big quarter as announced. The company that just put Claude on a budget. The price war getting an end date. Meta and Apple being friends again. And Wall Street, where one bank had a great quarter and the other stopped counting. If you own the AI budget, or defend it to a CFO, this one is for you. The math is directional, so check it and tell me where you read the room differently.

Stop one: the car stopped accelerating

On Wednesday Anthropic held its investor day in San Francisco, ahead of what could be the biggest IPO ever. First quarter, $4.7 billion of revenue. Second quarter, $11.6 billion. Third quarter, $16.8 billion, and profitable on an adjusted basis. Credit first, because it is earned: last year Anthropic lost more than $8 billion on an operating basis, and now it is profitable at this scale. Very few companies in history have done that.

So why are some investors now talking about $1.5 trillion instead of $2 trillion? Think of it like a car. From the first quarter to the second, foot to the floor; revenue more than doubled. In July, Anthropic was running at $65 billion a year, a number we used on this show a couple of weeks ago. Now take the third quarter and multiply it by four: about $67 billion. The car is still going very fast, but over the summer it stopped accelerating. My math says the run rate grew about 3% from July to September, and when you pay $2 trillion, you are paying for acceleration. $2 trillion is about 30 times this revenue; $1.5 trillion is closer to 22 times. That is the gap investors are arguing about.

Why did it slow? Here is my read, and challenge me on it. First, the buyers got smarter. Two weeks ago we covered Meta cutting its Claude Code users in half and Microsoft cutting engineers’ AI budgets, both moving work onto their own tools. They are eating their own cooking now, and you will see another big buyer do something similar in stop two. Second, the field caught up. OpenAI keeps shipping, and on Tuesday’s episode GPT-6 Astra came out cheapest per task of the frontier models we compared. Google’s new Gemini 4 Argon topped Claude on a couple of independent benchmarks this week. Microsoft is building its own models, and Meta joined the frontier on Monday. Two years ago Anthropic had the enterprise lane mostly to itself. Today it is a crowded road.

Let me be fair: one quarter is not a trend. Analysts who met the team this week still talk about a run rate as high as $110 billion by year end, and Claude is still the model a lot of us, me included, use every single day. But from my seat, the hyper-growth phase was every company trying everything. This phase is every company asking what it is actually getting for the money. Anthropic’s revenue is our spend, and you can see our behaviour in the vendor’s numbers.

Stop two: Accenture puts Claude on a budget

According to an internal memo reported by 404 Media, from October 1 Accenture centrally funds $29 of Claude per person per month. Above that, the cost has to be charged to a specific project, what Accenture calls a work breakdown structure. The same reporting describes heavy users spending $500 to $1,000 a month, and Accenture’s generative AI strategy lead told TechCrunch that AI was becoming “material to the cost structure.” One memo, one outlet, so it is directional. But honestly, I love this. This is AI FinOps arriving at one of the largest consulting firms in the world: chargeback per project.

The next question writes itself. Which projects earn the average? A cap tells you who spent more. To know whose work came out better, you need cost per task by project, by department, by team if you want to go there. We saw the same shape when Uber capped AI spend per employee after a four-month budget blowout: the cap is the reactive move, and the measurement is what makes it a management tool. The detail I find most interesting is that the $29 is an average, and the super users are allowed to spend more. That is also what measurability is for: enablement, coaching, and finding the people whose $1,000 a month is the best money the firm spends. Hold that thought, because it comes back in stop five.

Stop three: the price war gets an end date

The buyers are capping the bill, so what are the sellers doing? On Tuesday Google made Gemini 4 Argon generally available at $2 per million tokens in and $10 out, and in the same announcement it published the date that changes. On December 1 it moves to $4 in and $20 out. That is exactly Meta’s price for Muse Wonder and exactly Claude Opus 5.5’s price from Tuesday’s episode. From December, three labs sit at the same frontier price, and the cheap rate is a 46-day window.

Here is why that matters to a CFO, to FP&A, and to every FinOps professional watching. If your 2027 AI plan was built on this month’s rate, your cost per task on Argon doubles on December 1. Same work, double the price. And one detail most people will miss: cached input on Argon is 95% cheaper. If you know your cache hit rate, you can protect a lot of that bill. If you don’t, that is your first homework, because the cache line is where your money is. It all comes back to knowing your own cost per task, cost per turn, cost per merged pull request. There are so many tasks, subtasks and projects to measure before you understand the value of your AI, and every one of them starts with collecting the data.

Stop four: Meta and Apple are friends again

This is the most fun one this week. On Thursday Meta and Apple announced they have been working together to run Meta’s open-weight model, Muse Spark Open, locally on a Mac. It is an 816-billion-parameter model running across two or four Mac Studios with Apple’s new M5 Ultra chips. Meta’s AI chief Alexandr Wang put it best: “We are excited for mommy and daddy to be playing nice again.” After the last few years between those two companies, that is quite a line.

Why do I care for the enterprise? Because it runs locally. The vendor never sees your prompts, and there is no token bill; you pay for hardware instead. That is a new column on the cost comparison we built on Tuesday: price per token, cost per task, and now cost per task on hardware you own. To be clear, there is no Apple Intelligence integration announced; this is about running a model on a Mac. But Meta is serious, and I would keep watching it. It is the same reason customers ask us to run Olakai inside their own walls: once the model is on your hardware, the measurement layer has to be there too.

Stop five: two banks, two very different quarters

Goldman Sachs reported $18.7 billion of revenue against about $16.7 billion expected, with equities revenue up 72%. A blowout. JPMorgan missed on both revenue and profit for the first time in nearly three years. But the part I cannot stop thinking about came on JPMorgan’s call, when an analyst asked about AI. CFO Jeremy Barnum said the AI expense is something like $700 million a year. Then he said the firm is “really trying to move away from quantifying the benefit,” that the benefits “are not observable in our current quarterly earnings,” and that some of them “are going to be offset with token costs.”

So here is the largest bank in the US spending hundreds of millions a year on AI, and the CFO says the return is not visible in the numbers yet, and the token bill is eating part of it. To be fair to him, it is the most honest AI answer I have heard on an earnings call this year. It is also exactly why I want to go deep on JPMorgan on Tuesday. My very first video that went viral, about a year ago, was about what JPMorgan measured, so I cannot wait to see what has changed since last November. What are they actually building, what does it cost, and what would you need to see to call it a return? Those are questions every enterprise AI leader should be asking of their own program.

The one question behind all five stops

Let’s put the room together. Anthropic’s growth slowed, Accenture capped Claude, Google dated its discount, Meta offered a way around the token bill, and JPMorgan’s CFO said the bill eats part of the benefit. Every one of those comes back to the same question: what does each finished piece of AI work cost you, and what did it return?

That is what we build at Olakai, the Enterprise AI System of Record: every AI interaction, every vendor, every model captured and structured, so you can answer that question before your CFO asks it. Accenture’s $29 cap becomes a budget with alerts rather than a memo. Argon’s December 1 price change becomes a forecast you can run against last quarter’s actual tokens, cache hits included. And JPMorgan’s “not observable” becomes cost per finished task by team and by model, side by side with the outcome, which is the page a CFO can defend. The same record sits underneath whether you run coding agents or employee assistants, and whether you read it through our platform, through Kai, or through your own AI over our MCP connector.

One question for the weekend, for the comments: does your company cap AI spend per person yet? And if it does, what is the number? Your AI is an investment, so let’s measure it like one. That was this week’s round. Tell me if you read the room differently, and I’ll see you on Tuesday for JPMorgan.