Claude Code for teams: seats, admin, and what it really costs

What a seat costs

• Team plans require a minimum of two members and support up to 150 seats.
• Both seat types carry Claude Code. Anything you read saying it is premium-only is out of date.
• The allowance is shared across Claude chat, Claude Code, and Cowork, on a five-hour session window and a weekly window.
• Extended 1M context for Opus is included on both Team seat tiers, where a Pro subscriber needs usage credits for it.

Seats against individual subscriptions, on the numbers

Anthropic publishes seat prices and publishes allowance multipliers, but never divides one by the other. Doing it yourself demolishes the usual "you pay more per head for governance" claim.

Read the pattern rather than the rows. Every monthly plan on the ladder, individual or team, is priced at exactly 0.050 units of Pro allowance per dollar. Annual team billing lifts that to 0.063, which is better than annual Pro. So the governance you get with a seat is close to free, and on annual billing it is better than free.

The other place seats lose is at the bottom. A light user who barely codes pays $25 a month for a Standard seat where $20 of Pro, or nothing at all, would have done. Provision by actual usage, not by headcount.

What a seat buys beyond allowance

The headcount where it flips

Below about five people, individual subscriptions still win on simplicity: no procurement, and each person picks the tier they need including Max 20x. The overhead of five expense claims is real but small.

Between five and ten it depends on two things: how much your finance function hates recurring personal expenses, and whether anyone has left recently with their subscription still live.

Above ten, seats win regardless, because the administrative cost and the security exposure grow with headcount while the per-seat economics stay flat. With annual billing they are not even a premium.

Budgeting for a team of agent users

The mistake is budgeting an average. Agent usage across a team is heavily skewed: a few engineers use ten times what the median does, and they are usually the ones producing the most.

Anthropic gives a usable outside number. Across enterprise deployments, Claude Code averages about $13 per developer per active day and $150 to $250 per developer per month in token terms, staying below $30 per active day for 90 percent of users, as of August 2026. Its own guidance is to budget more for a coding seat than a chat seat, because each Claude Code turn carries file contents, tool calls, and multi-step reasoning.

That is about $110 per engineer per month, weighted heavily toward a minority. On annual team billing the same shape comes to roughly $900. Budgeting a flat $25 each and being surprised is the standard failure, and it usually ends in capping exactly the people who benefit most.

Seeing and capping the spend

Which controls you get depends entirely on how your organization authenticates, and mixed organizations get mixed reporting. Each developer is metered according to the method they signed in with.

• Usage inside the seat allowance is not metered in dollars. The spend report covers usage-credit spend and only appears once an admin turns usage credits on. Until then you can see adoption, not cost.
• Usage credits are the spend control. The seat allowance is the default ceiling; turning on credits lets members continue past it at standard API rates, with limits set at organization, group, or individual member level.
• A member without billing access who runs /usage-credits sends a request to your admins rather than spending anything.
• The adoption dashboard is separate from spend: daily active users, sessions, and contribution metrics, with CSV export.
• On Enterprise, the Analytics API returns per-user usage and cost across Claude surfaces. A Primary Owner creates a key with the read:analytics scope.
• OpenTelemetry export works on every setup and is the only option that streams per-user token and cost metrics into your own observability stack in near real time.

If you are on the Console instead of seats

API organizations get a workspace called "Claude Code" created automatically on first authentication. You cannot create API keys in it; it exists so Claude Code spend is isolated and cappable. Set both a workspace spend limit and a workspace rate limit, so Claude Code cannot crowd out your production traffic.

The per-user figure drops as the team grows because fewer people use Claude Code concurrently in a larger organization. These limits apply at the organization level, so an individual can temporarily exceed their calculated share when others are idle.

Rules worth setting on day one

1. One account per person, always. Sharing halves everyone allowance, because windows are per member, and it destroys the audit trail.
2. Default the team to Sonnet. Opus by default across ten engineers is an expensive convention to unwind later, and opusplan gives you Opus judgement at Sonnet execution cost.
3. Agree on a committed CLAUDE.md. Keep it under 200 lines and move workflow-specific instructions into skills. It is the cheapest quality lever a team has and it stops ten people re-teaching the same conventions.
4. Decide about autonomous runs explicitly. Who may leave an agent unattended, in which repos, with what permissions. Agent teams use roughly seven times the tokens of a standard session.
5. Turn on usage credits with a low org cap first. A cap you can raise beats a blocked engineer at 4pm on a Thursday, and the spend report only exists once credits are on.
6. Review spend monthly, per person. Not to police it, but because the outlier is usually a fixable workflow, most often an uncleared session or an Opus default.

Questions people ask

Keep reading