AI for Business

Anthropic Adds Spending Reports as Companies Seek Proof of AI's Value

Anthropic has introduced a set of reporting tools aimed at showing enterprise customers exactly what their AI spending is producing, following financial results that underline the business appeal...

Share:

Anthropic has introduced a set of reporting tools aimed at showing enterprise customers exactly what their AI spending is producing, following financial results that underline the business appeal of its Claude Code coding tool.

The company posted an operating profit in the second quarter and reported 900% net revenue retention, meaning spending from the same customers in Q3 2025 grew nine times by Q3 2026.

The new reports draw on internal analytics and employee surveys, letting managers review a team's work over a chosen period, what it produced, what it cost and where workflows broke down. Anthropic says the data won't be used for model training by default, and the reports include recommendations for improving results. The company is also creating pooled group budgets so teams can manage token spending more easily.

The tools respond to a question large customers keep asking: what return are they getting on AI? Research from Jellyfish, which studied agentic coding use among 276,000 customers, found Claude Code and other Anthropic-model tools remain the most widely used, accounting for nearly a third of proposed code changes submitted for review. Spending on those tools has grown tenfold since the start of the year, now equal to roughly 2% of total engineering cost.

Nicholas Arcolano, Jellyfish's chief scientist, said that growth is spending most finance chiefs didn't plan for, and that companies now need to optimize rather than simply spend. Anthropic leads among enterprise customers, and Jellyfish's Nikolas Albarran noted that switching costs and standardized workflows give it staying power even as rivals release new models.

Source: TechCrunch

Ready to Modernize Your Business?

Get your AI automation roadmap in minutes, not months.

Analyze Your Workflows →