What Anthropic's $13 per developer per active day figure for Claude Code covers, and the three ways a company is billed

A finance lead asks what Claude Code will cost per developer, and a search returns one number: $13 a day. The number is Anthropic's own, from its documentation on managing costs, read on 4 October 2026. Before it goes into a budget, read the whole sentence it came from, because the sentence says what kind of number it is, and the page beside it says why your team will produce a different one.
Claude Code is Anthropic's coding tool. A developer types a request in a terminal, the text window where commands are typed, and an AI model reads files, runs commands and edits code. Every part of that work is counted in tokens, pieces of text the model reads or writes, which Anthropic's pricing page puts at 4 characters or 0.75 of an English word each. What a company pays for Claude Code is the cost of the tokens its developers' sessions use, or the seats that include an allowance of them.
The three figures, as Anthropic states them
Anthropic's cost documentation gives three figures in one paragraph, all of them Anthropic's own statements about its own product across what it calls enterprise deployments:
- An average of $13 per developer per active day.
- $150 to $250 per developer per month.
- Costs below $30 per active day for 90 percent of users.
The same paragraph says per-developer costs "vary widely" with model selection, codebase size and usage patterns such as running several instances at once or automation. Anthropic's advice follows in the next sentence: start with a small pilot group and use the tracking tools to establish a baseline before a wider rollout.
So the $13 is an average across other companies' deployments, and it describes those deployments. Two things the page leaves open, by our reading on 4 October 2026: the meaning of "active day", and the number of active days a month behind the $150 to $250 monthly figure. The plain reading of an active day is a day on which the developer used Claude Code, and a pilot should count those days itself.
One more sentence from the same page belongs in any budget conversation: "Budget more for a coding seat than a chat seat." Anthropic's reason is what each turn contains. A Claude Code turn carries file contents, tool calls, which are actions such as reading a file or running a command, and multi-step reasoning, so "one debugging session can consume more than a day of chat". The page on what Claude Code costs per developer sets out everything Anthropic names as moving the figure.
The three ways a company is billed
Whether the $13 figure even arrives as dollars depends on how the company gets Claude Code. Anthropic's documentation names three setups, and says which controls an organisation has depends on the setup.
A Claude for Teams or Enterprise plan. Each member has a seat, a paid place on the plan, and each seat has an allowance: an amount of usage included in the price. Anthropic's documentation says the allowance resets on a rolling five-hour window and a weekly window, is shared with Claude chat and Cowork, and is sized by the seat tier, Standard or Premium. Then the sentence that changes the budget: usage inside the allowance "isn't metered in dollars". Dollar figures appear only for usage credits, which are paid usage a member draws on after the allowance runs out, once an administrator has turned them on.
The Claude Console. This is Anthropic's web console for API accounts, where usage "is billed per token to your organization". Anthropic's documentation says a workspace called Claude Code, a named section of the account, is created automatically the first time Claude Code signs in, and that it provides central cost tracking for all Claude Code usage in the organisation. Every token is metered at Anthropic's list prices, which on 4 October 2026 put Claude Sonnet 5.5 at $2 per million input tokens and $10 per million output tokens, Claude Opus 5.5 at $4 and $20, and Claude Haiku 4.5 at $1 and $5.
A cloud provider. On Amazon Bedrock, Google Cloud's Agent Platform or Microsoft Foundry, Claude Code "is billed per token to your cloud account", and spend controls are in the cloud provider's billing console. Anthropic's pricing page says Amazon Bedrock and Google Cloud have independent regional pricing and refers readers to each provider's own page. Anthropic's documentation also says Claude Code does not send metrics from a cloud back to Anthropic, so its dashboards show nothing for this usage.
If an organisation mixes sign-in methods, Anthropic's rule is one sentence: each developer is metered according to the method they authenticated with. The page on subscription seats or pay per token compares the three setups in one table and says which we recommend for which situation.
Where the figure comes from on each setup
The screen that shows spend differs by setup, by Anthropic's documentation read on 4 October 2026. On a Teams or Enterprise plan, the spend report in organisation analytics shows estimated usage-credit spend per user and per model, updated daily, and appears once usage credits are on. On the Claude Console, the usage page is the place Anthropic names for authoritative billing, and the dashboard at platform.claude.com/claude-code shows daily costs and a table of each member's spend this month. On a cloud provider, the cloud billing console is the record. The page on where to see Claude Code spend lists every screen and how often each updates.
How to produce your own figure
Anthropic's advice is to pilot first. The steps below use the tracking tools Anthropic names; the group size and the length are Reveneau's recommendation, because the documentation gives none.
- Choose the setup before the pilot, because the numbers come from different screens in each.
- Pick developers who work on the codebases the wider team will work on, since codebase size is one of Anthropic's three named sources of variation.
- Run the pilot across at least one full weekly allowance window on a subscription plan, so the weekly limit has been seen once.
- Count active days as well as dollars. Anthropic's analytics dashboard and the Console dashboard's Activity chart both show daily active users. Divide each developer's spend by their active days.
- Read the model mix. The spend report breaks spend down per model, and Anthropic names Opus left as the default model, with long sessions that were never cleared, as the usual causes of unexpectedly high spend.
- Reconcile against the invoice before multiplying anything out.
An invented example, on Anthropic's figures only, makes the arithmetic plain. If 8 developers spend $1,040 in a month across 80 active days, the cost per active day is $13, the same as Anthropic's average. If the same group had 40 active days, it is $26, still under Anthropic's $30 figure for 90 percent of users, with half the use. The result is your own baseline, with Anthropic's $13 and $30 as reference points beside it.
Reveneau is an AI software development consultancy. All of its code is written by AI, and every change must pass an eval suite, a set of automated tests written from the specification, before release, so token use is a running cost of every Reveneau build. Reveneau is independent of Anthropic, and every figure in this post is Anthropic's own statement about its own product, read on 4 October 2026. The guide to Claude Code costs for teams covers the caps, the limit messages and the settings an administrator can enforce, for the person who approves the spend.
Anthropic's $13 is a fact about Anthropic's customers. Your pilot produces the fact about yours.
Sources
- Anthropic, Manage costs effectively (code.claude.com), read 4 October 2026: the three figures, the sources of variation, the pilot advice, the coding seat sentence, the three setups, the seat allowance, the Claude Code workspace, the spend report, and the
/usageestimate. - Anthropic, Track team usage with analytics (code.claude.com), read 4 October 2026: the analytics dashboard, the Console dashboard and its note that spend figures are estimates.
- Anthropic, Pricing (platform.claude.com), read 4 October 2026: the token estimate, the per-model list prices, and cloud provider pricing.


