A Striking Claim from Anthropic's CFO: Claude Writes More Than 90% of the Company's Code
Originally published in Turkish. Read the original →

In a podcast appearance, Anthropic CFO Krishna Rao said more than 90 percent of the company's code is now produced by Claude. The company's annualized revenue has grown from 9 billion dollars to more than 30 billion dollars, while Claude Code reached the 1 billion dollar revenue band in just six months.
The figure shared by Anthropic CFO Krishna Rao in a podcast appearance clearly shows how quickly AI companies are transforming their own internal processes: more than 90 percent of the code the company writes every day is now produced by Claude. The financial picture that emerged in the same appearance is at least as striking. Anthropic entered 2026 with roughly 9 billion dollars in annualized revenue, and by the end of the first quarter that figure had moved above the 30 billion dollar band.
Rao's remarks matter on two levels. First, the company developing one of the world's most advanced language models trusts its own model as a "production partner." Second, that trust offers a concrete reference point for the maturity of AI-assisted coding tools. We are now talking about a component that has left the experimental stage behind and settled into the backbone of software production.
What Does "90 Percent" Actually Tell Us?
This ratio did not appear overnight. At companies building large models like Anthropic, an enormous amount of infrastructure, experiment, evaluation and deployment code is written every day. A significant share of this work is repetitive, well-structured but unforgiving of errors. The productivity gap created by coding agents shows up most sharply in exactly this kind of environment.
To interpret the number correctly, a critical caveat is needed. "90 percent of the code" does not mean "90 percent of the decisions." Human engineers still make architectural choices, do code review and approve critical merges. Claude, meanwhile, takes on work such as editing files, running tests, debugging and preparing helper scripts. A high number of generated lines is not by itself a measure of productivity; but it clearly changes, at a fundamental level, what human hours are spent on.
Employees' Role Is Shifting to Managing "Agent Fleets"
One of the most interesting details Rao shared is the new way Anthropic's teams work. Inside the company, "agent fleets" are used, in which multiple AI agents take on tasks in parallel. An engineer's job is no longer to write every line themselves; it is to direct a group of agents, check their output and step in when the process gets stuck.
The same transformation is not limited to engineering teams. In areas such as financial reporting, data collection and internal documentation, Claude has also been placed in a kind of "digital coworker" position. A significant share of employees are handing traditionally manual workloads to agents and turning toward decision-making, strategy and oversight. This approach means not only productivity gains but also redrawing job descriptions.
Using Compute Inside First
Anthropic moving in this direction is no surprise. Compute capacity is the scarcest resource for AI companies. Rather than keeping its GPU budget open only to external customers, the company chooses to use a meaningful portion of it in its internal processes. There is a strategic logic behind this decision: current models play a direct role in producing the next generation of models. In other words, Anthropic using Claude in its own development flow also grows the data, testing and experience pool for the next version.
This approach points to a closed loop: a better model produces better code; better code makes faster new experiments possible; faster experiments result in stronger models. Perhaps the most important aspect of Anthropic's claim is that it implies this loop has started working in a measurable way.
The Revenue Picture: From 9 Billion Dollars to the 30 Billion Dollar Band
Anthropic's financial indicators back up its operational speed. According to the data Rao shared, the company started 2026 with annualized revenue at around 9 billion dollars. As the first quarter closed, that figure had moved above 30 billion dollars. A revenue picture that more than tripled in three months clearly shows how aggressive demand is on the enterprise AI side.
A significant component of this growth is Claude Code. Even though only six months have passed since its public launch, the product has reached an annualized revenue level of 1 billion dollars. Enterprise subscriptions are said to have quadrupled since the start of 2026. This picture shows that developer-centric AI tools have become a permanent line item not only for individual users but also in enterprise budgets.
The AI and Employment Question Is Still Open
Looking at the picture only through the lens of productivity would be an incomplete reading. Whether AI-assisted production will replace white-collar jobs or create new fields of work is one of the most debated topics in the industry. One group of economists argues that automation is advancing faster than new jobs are emerging and could put pressure on employment. The other camp argues that productivity gains will create new demand and therefore new roles.
Rao's view is closer to the second camp. He says that as long as there is no weakening on the demand side, companies won't stop hiring because of AI. But Anthropic's own practice implies that, at least in the short term, some job descriptions will change fundamentally. This is a model built not with the goal of "doing the same work with fewer people," but of "getting far more work done with the same people."
A Signal for the Industry
Anthropic's statement also serves as a reference point for other big AI players. There were already early signs that OpenAI, Google and Microsoft had reached similar automation rates internally. Anthropic's difference is that it states this ratio openly in public. This approach creates competitive pressure on one hand, and on the other works as a kind of "use case" for enterprise customers.
An AI company trusting its own model this much is a natural reference for enterprise buyers. The thought "if Anthropic has its own code written by the model, we can hand off part of our internal processes too" becomes an argument that speeds up the sales process. Other companies can be expected to come forward with similar statements in the coming quarters.
The technical side of this signal will follow quickly too. As development processes open up to agents, topics such as release management, environment isolation, observability and audit logging will have to be redesigned. Records of which file an agent changed with which approval, which command it ran and which test it passed form a new visibility layer that replaces classic code review. A model operating at Anthropic's scale shows that mature practices are starting to land on the infrastructure side as well.
The picture Anthropic shared shows that coding agents have long since moved beyond the definition of a "helper tool." Leaving most of the company's daily output to the model is a clear sign of a quiet but rapid transformation in enterprise software culture. Add the revenue jump and the rise of Claude Code, and it points to AI companies moving into a different league, both operationally and commercially, in the period ahead.
Still, the picture raises questions faster than it answers them. How will the quality assurance, oversight and accountability model for systems that work this autonomously take shape? How sustainable a career model is the role of employees reframed as "agent managers"? Anthropic's answer seems clear: the future lies not just in using models, but in working together with them. How far that answer spreads across the industry will be determined by the next few quarters.




