In November 2026, a Claude Team seat costs from $20 (Standard, billed annually) to $125 (Premium, billed monthly) excluding tax, and includes usage up to a limit; a Claude Enterprise seat costs $20, and every token is paid on top at API rates. For the same consumption, Enterprise works out about 7 times more expensive for an average user, and up to 30 times for heavy usage like Idun Group's (public rates, before discount; measured from 9 to 17 November 2026). Stay on Team as long as you do not need Enterprise's controls. But Anthropic moves every Enterprise contract to per-token billing at renewal, so measure your usage before you make the move.
How much does Claude cost a company in November 2026?
In November 2026, Claude costs a company $20 to $125 per seat per month on the Team plan, or $20 per seat plus usage at API rates on the Enterprise plan. For an individual, the Pro subscription costs $17 a month billed annually ($20 billed monthly), Max $100 and Ultra $200. Prices exclude tax and come from Anthropic's plans page, read on 18/11/2026; the euro prices are those it shows to a visitor located in France.
| Plan | Who it is for | Price per month, billed annually | Price per month, billed monthly | Usage |
|---|---|---|---|---|
| Free | one person | free | free | included, with limits |
| Pro | one person | $17 (€15) | $20 (€18) | included, with limits |
| Max | one person | — | $100 (€90) | included, more than Pro |
| Ultra (formerly Max 20x) | one person | — | $200 (€180) | included, ten times Pro's weekly usage |
| Team, Standard seat | 2 to 150 seats | $20 (€18) | $25 (€21.04) | included up to a limit |
| Team, Premium seat | 2 to 150 seats | $100 (€90) | $125 (€105.23) | included, five times the Standard limit |
| Enterprise | at least 20 seats | $20, in dollars even in France | — | none: every token is paid at API rates |
Prices excluding tax, taken from Anthropic's plans page on 18/11/2026. The euro prices are the ones Anthropic shows, not a conversion from the dollar.
Free, Pro, Max and Ultra are individual subscriptions, with no central administration and no usage analytics; paid annually, Pro saves €36 over twelve months. For a company, the choice is between Team and Enterprise: a Team Standard seat, at €18 a month billed annually, gives 1.25 times Pro's usage per session.
Each Team seat also comes with monthly API credits, $20 for a Standard seat and $100 for a Premium seat, pooled up to $500 a month; they are for the applications you build, not for chat or Claude Code (Anthropic help centre, read on 18/11/2026). For comparison, ChatGPT Business shows the same seat grid, $20 and $100 a month billed annually, $25 and $125 billed monthly, but up to 200 seats (OpenAI's pricing page, read on 18/11/2026).
How much does a Claude token cost?
At API rates, a million Claude tokens costs from $0.10 for input with Haiku 5.5, on a short request, to $40 for output with Fable 5.2, the most powerful model (API documentation, read on 18/11/2026). These rates pay for all Enterprise usage, and for Team usage beyond the seat's limit. Re-reading context from the cache costs $0.20 per million on Opus 5.5; yet this context makes up 82% of Claude Code's cost at Idun Group (see below).
| Model | Input | Output | Cache write, one hour | Cache read |
|---|---|---|---|---|
| Fable 5.2, the most powerful | $8 | $40 | $16 | $0.20 |
| Opus 5.5 | $4 | $20 | $8 | $0.20 |
| Sonnet 5.5 | $2 | $10 | $4 | $0.10 |
| Haiku 5.5, request of 100,000 tokens or fewer | $0.10 | $0.50 | $0.20 | $0.01 |
Prices per million tokens, excluding tax, from Anthropic's API documentation read on 18/11/2026. A cache read costs one twentieth of the input price on Opus 5.5 and Sonnet 5.5, one fortieth on Fable 5.2 and one tenth on Haiku 5.5; a five-minute cache write, 1.25 times the input price; batch processing, half price.
How much would a Claude Team seat cost if it were paid per token?
At Idun Group, a Claude Team Premium seat consumed in Claude Code the equivalent of about $3,500 a month at public API rates, nearly 30 times the seat price of $100 to $125 a month (two Premium seats measured from 9 to 17 November 2026). Idun Group pays for Team seats, and even on Team, Claude Code's telemetry (OpenTelemetry) reports the tokens each request consumed and their cost at public API rates.
| Team seat | Seat price, per month | Usage at API rates, 9 to 17/11 | Scaled to a month | Ratio to the seat price |
|---|---|---|---|---|
| Premium, member A (8 active days) | $100 to $125 | $1,069 | ≈ $3,560 | 28 to 36 times |
| Premium, member B (7 active days) | $100 to $125 | $1,018 | ≈ $3,390 | 27 to 34 times |
| Standard, member C (5 active days) | $20 to $25 | $196 | ≈ $650 | 26 to 33 times |
Idun Group's measurement on three Team seats (two Premium, one Standard), Claude Code only, from 9 to 17 November 2026: the cost of each request calculated by Claude Code at public API rates, with cache writes counted at one hour; a month counted as thirty days.
On Claude Enterprise, a member this intensive would cost $20 for the seat plus about $3,500 of usage a month, instead of $100 to $125 on Team. And Idun Group's usage is rising: for the whole team, across all subscriptions, the Claude Code equivalent at API rates went from $9,100 in July to $21,000 in October 2026, 2.3 times more in three months.
At Idun Group, 82% of Claude Code's cost at API rates pays for context, meaning the files and the conversation that Claude re-reads with each request: 40% to write them to the cache, 42% to read them back. The answer itself accounts for only 17% (Team seats, measured from 9 to 17 November 2026).
These figures have four limits:
- Three seats and nine days: this is a measurement, not a market average. Read it alongside Anthropic's benchmark and the industrial group's case, below.
- They only cover Claude Code. Claude's chat and Cowork are not included, so the figures are a minimum.
- We are heavy users, because it is our job. Anthropic's average benchmark for Claude Code is much lower: about $13 per developer per active day, $150 to $250 a month (Claude Code documentation, read on 18/11/2026).
- The calculation uses public rates, before discount, and one-hour cache writes, the ones Claude Code uses on a subscription. Through Anthropic's sales team, Enterprise opens up discounts on a spend commitment, and their size is not published; with a five-minute cache, the bill would fall by about 15%, and the ratio would go from about 30 to about 25 times.
How much does a Claude Enterprise user cost per month?
On Claude Enterprise, a user costs $20 for the seat plus their usage at API rates: $170 to $270 a month for the average developer whose benchmark Anthropic publishes, and $20 plus about $3,500 for a seat as intensive as Idun Group's Premium seats. That average developer fits within a Team Standard seat, which absorbed the equivalent of $650 a month in our case. Depending on intensity, moving from the Team seat to per-token billing therefore multiplies the bill by 7 to 30: the more successful adoption is, the more the move costs (Anthropic's benchmark read on 18/11/2026; Idun Group's measurement from 9 to 17/11/2026). The low end of the range does not come from us: Anthropic's benchmark gives 7 to 13 times, and the Anthropic sales rep's estimate for a group with 322 licences, 6.7 times.
| Case | Usage per month, at API rates | On Team, per month | On Enterprise, per month | Gap |
|---|---|---|---|---|
| Average developer, Anthropic's benchmark | $150 to $250 | Standard seat: $20 to $25 | $170 to $270, seat included | 7 to 13 times |
| Heavy Standard seat, Idun Group | ≈ $650 | $20 to $25 | $20 + ≈ $650 | ≈ 30 times |
| Heavy Premium seat, Idun Group | ≈ $3,500 | $100 to $125 | $20 + ≈ $3,500 | ≈ 30 times |
| Industrial group with 322 licences, for the whole group | — | ≈ €12,000 | ≈ €80,000, estimated by Anthropic's sales rep | 6.7 times |
Anthropic's benchmark for Claude Code, read on 18/11/2026; Idun Group's measurement, Claude Code only, from 9 to 17/11/2026, a month counted as thirty days; industrial group met by Idun Group on 27/10/2026; seat prices taken from Anthropic's plans page on 18/11/2026.
Sources: Idun Group's Claude Code telemetry; Claude Code documentation (Anthropic's benchmark); Idun Group's conversations with 151 groups since June 2026; Idun Group meeting of 27/10/2026.
Why do companies stay on Claude Team?
Companies stay on Claude Team because its flat-rate seat costs far less than the same usage paid per token, even if it means working around its limits. Of the 151 groups that have described their tools to Idun Group since June 2026, 55 have deployed Claude or are testing it; of the 11 that specified their plan, seven are on Team, only one on Enterprise, two on individual subscriptions and one pays per token (figures as of 28 October 2026).
Yet Team stops at 150 seats, and companies that go beyond it open a second account rather than move to Enterprise. A software publisher that reached 150 seats opened a second account; its IT manager wants, he says, to "avoid […] us going through Enterprise", and to move non-technical uses to Gemini, already included in its Google Workspace.
A French industrial group, met by Idun Group on 27 October 2026, has 322 Claude licences on Team, in Standard and Premium seats, spread across several accounts since a Team account stops at 150 seats: about €12,000 a month. Anthropic's sales rep put the same consumption on Enterprise at €80,000 a month, 6.7 times more. In mid-October, Anthropic offered it "€1 million of tokens as free credit" to switch. At the estimated rate of €80,000 a month, that million would cover a little over a year: in the second year, the bill would go from €144,000 to €960,000. The group has "not said yes for now". Its IT manager expects the API, 25% of its AI budget today, to account for a little under half of it next year.
Claude Enterprise contracts have been moving to usage-based billing since the November 2025 renewals. Since February 2026, every new contract has the single $20 seat, with no tokens included, and older contracts move to it at renewal; the old flat rate could go up to $200 per user, with tokens at a reduced price (The Register, 16/04/2026). Nothing has been announced for Team to date. The self-serve move from Team to Enterprise is irreversible, and Team's monthly API credits stop with it. Idun Group found no public source on credits offered by Anthropic to move from Claude Team to Enterprise (search of 18/11/2026): to its knowledge, the €1 million offered to the industrial group is the only example.
Team or Enterprise: what changes on the bill?
On Claude Team, the seat, from $20 to $125 a month, includes usage up to a limit; on Claude Enterprise, the $20-a-month seat only gives access, and every token is paid at API rates. Team takes 2 to 150 seats; Enterprise requires at least 20.
| Team | Enterprise | |
|---|---|---|
| Who it is for | 2 to 150 seats | at least 20 seats self-serve, 50 through Anthropic's sales team |
| Seat price, per month | Standard: $20 billed annually, $25 billed monthly; Premium: $100 billed annually, $125 billed monthly | $20, billed annually |
| Products the seat opens | Claude on web, desktop and mobile, Claude Code and Cowork | the same |
| Usage included | an allowance per five-hour session and a weekly limit, specific to each member; Premium gives five times more than Standard | none |
| Beyond that | usage credits, at API rates, if the admin turns them on | everything is already usage-based, with no per-seat limit |
| Spend limits | a monthly limit for the organisation, and per member where the option exists | limits for the organisation, per group and per person |
| Controls | — | SCIM provisioning, audit logs, Compliance API, custom roles, Analytics API |
Anthropic's pages read on 18/11/2026.
Above 150 seats, one Team account is no longer enough: the plan Anthropic provides for that is Enterprise, even if some companies open a second Team account. Between 20 and 150 seats, an Enterprise seat only costs less than a Team Premium seat for a member who consumes less than $80 a month at API rates ($105 against Premium paid monthly), and never less than a Standard seat paid annually, at the same price of $20. Anthropic's benchmark for a developer, $150 to $250 a month, is already above that. So the case for Enterprise rests on its controls, which Team lacks: SCIM provisioning, audit logs, Compliance API. On Team, keep Premium seats for those who often hit the Standard limit: the console's usage analytics show the time spent at the limit.
On Team, Fable 5.2 is reserved for Premium seats, up to half of their weekly quota. Both plans give access to Claude Cowork, Anthropic's office agent, which, like Claude Code, consumes far more tokens than a chat.
What is the Claude bill made of?
The Claude bill has three lines: the seat, usage beyond what the seat includes, and the API for programmatic use.
- The seat. A seat added mid-period is charged immediately, prorated. Removing a member does not lower the bill: their seat stays paid and can be given to someone else. On Team, reducing the number of seats only takes effect at renewal, with no prorated refund.
- Usage beyond the seat. On Team, it takes the form of usage credits at standard API rates, bought in advance, valid for twelve months and non-refundable; they extend chat, Cowork and Claude Code, unlike the monthly API credits, which are reserved for programmatic applications. On Enterprise, all usage is paid at API rates.
- The API. An internal application or an agent that calls Claude is paid per token. Claude Code can also run through an API account, or through Amazon Bedrock, Google Cloud or Microsoft Foundry: it is then billed per token on that account, and its spend does not appear in Claude's console.
Is Claude Code included in the seat?
Yes: Claude Code is included in every Claude Team seat and in the current Enterprise seat, but what it consumes is not always included. On Team, it draws on the same pool as chat and Cowork. On Enterprise, every Claude Code token is paid at API rates: about $13 per developer per active day on average, according to Anthropic (Claude Code documentation, read on 18/11/2026). One debugging session can consume more than a day of chat.
What is Claude's 5-hour limit?
The 5-hour limit is the session over which the usage included in a Claude Team seat renews: it opens with the first message, and the limit resets in full five hours later (Anthropic help centre, read on 18/11/2026). A weekly limit comes on top, renewed on a fixed day and at a fixed time. Chat, Cowork and Claude Code draw from the same pool, and switching models does not restore access. The current Enterprise seat has neither a five-hour session nor a per-seat limit, only spend limits.
What happens when Claude's limit is reached?
When a Claude Team member reaches their limit, they wait for it to reset, unless the admin has turned on usage credits: they then carry on at API rates, up to the spend limit, and a spend limit that is reached only stops those credits. On Claude Enterprise, reaching a spend limit cuts off Claude, Cowork and Claude Code until the next period, or until an admin raises the limit; on self-serve, a credit balance at zero stops usage for the whole organisation.
What commitments come with a Claude Enterprise contract?
The Enterprise contract is billed annually and can be bought in two ways, with the same features and the same seat price. Self-serve: at least 20 seats, payment in dollars only, usage prepaid in credits shared across the whole organisation, and no seat removed before renewal. Through the sales team: at least 50 seats, payment by invoice and in other currencies, usage billed monthly in arrears, and possible discounts on a spend commitment.
What should you negotiate with Anthropic before moving to Claude Enterprise?
Before signing Claude Enterprise, negotiate with Anthropic's sales team what its plans page reserves for that route: tiered discounts on a spend commitment, a trial, and an account manager above certain amounts. For free credits, ask for their amount, their duration, and the expected bill once they run out: for the industrial group, the €1 million would cover a little over a year. Set spend limits per group from day one. And bear in mind that, on self-serve, the move from Team to Enterprise is irreversible.
Why is moving Claude to per-token billing feared?
Moving Claude to per-token billing is feared because the bill then follows usage, and Claude models are among the most expensive per task. Per-token billing means paying for Claude by consumption, every token at API rates, instead of a flat fee per seat that includes usage up to a limit: the Claude Enterprise seat has worked this way since February 2026.
A fintech met by Idun Group on 16 November 2026 sums it up: "as soon as you move to the token side […] it can quickly cost you an arm and a leg". The IT manager of another industrial company, which already pays for everything per token, goes further: for him, the flat rate is "subsidised tokens", and the end of the subsidy "is going to hurt".
The price of a Claude token is falling, but the bill depends mostly on the number of tokens per task. Claude Opus 5.5 costs $4 and $20 per million tokens, against $5 and $25 for Opus 5 (API documentation, read on 18/11/2026). On Artificial Analysis's index, read on 18/11/2026:
- Claude Opus 5.5, at its maximum setting, costs $10.04 per task for a score of 59; GPT-6.2 Astra, $4.00 for a score of 62; Gemini 4 Carbon, $7.76 for 60. Claude Fable 5.2 has the same per-token price as Astra, but produces more than four times as many tokens: $26.54 per task.
- Among coding tools, Claude Code is in the lead: with Fable 5.2, it scores 58.5 points for $15.47 per task; the best configuration of Codex, OpenAI's tool, with GPT-6.2 Astra, scores 53.5 points for $5.12.
According to The Register (3/11/2026), Revolut's 2,000 or so engineers have dropped Claude Code and Codex as their default tools in favour of GLM-5.3, an open model that Revolut runs on 56 Nvidia B200 GPUs. Its inference cost for coding has fallen by about 90%, and Claude Code remains available as an exception. The announced cost, about $0.30 per million tokens, does not count cloud, staff or monitoring (Dealroom, 3/11/2026).
How do you keep Claude's return on investment when every token is paid for?
To keep Claude's return on investment on per-token billing, you need to know which tasks it does, who does them best, and to pool what is repeated. In Idun Group's measurements, 82% of Claude Code's cost at API rates pays for context; when five people each ask Claude to re-read the same repository for the same task, the company pays for that reading five times.
Take a security update for an application, redone every month by several developers. Each of them runs it with their own instructions, and Claude re-reads the repository, looks for the dependencies and checks good practice. A single shared skill, or a routine that opens a pull request every morning, does the same work once. A partner integrator sees the same thing among its clients: "people rarely tell each other which skill they have built for their own use, even though they are doing the same thing as the person next to them". At a consulting and training firm we worked with, the head of AI asked everyone to share their skills, and saw "zero sharing".
The levers, in the order we apply them:
- Measure use cases and tasks, team by team: what Claude does, how often, at what cost.
- Identify who does each task best, and why: their instructions, their skills, their model.
- Pool what is repeated: a shared skill, a routine, an automated task.
- Choose the model and the setting for the task: Haiku or Sonnet for what is simple, Opus or Fable for what deserves it. At the "high" setting, Opus 5.5 costs $3.46 per task instead of $10.04, for a score of 51.8 instead of 59 (Artificial Analysis).
- Set spend limits per group. Since 28 October 2026, an Enterprise group can be given a shared monthly budget, with alerts at 50, 75, 95 and 100%.
Also open Claude Code and Cowork in waves: according to the Claude Enterprise consumption guide, opening them to everyone on day one is the fastest way to create unexpected consumption. A uniform cap is not a good answer either: as Anthropic points out, members at their limit are often the ones who have adopted the tool best. At the same consulting firm, our analysis showed one user who had hit their limit 74 times, and the head of AI was getting requests such as "Please remove the cap".
How do you calculate the cost of Claude per active user?
The cost of Claude per active user is the total cost, seats plus usage billed on top, divided by the number of people who actually use it over the period.
Cost per active user = (seats paid × seat price + usage billed on top) ÷ active users
Fictional example. A company pays for 140 Team seats annually, 110 Standard and 30 Premium: 110 × $20 + 30 × $100 = $5,200 a month. A hundred people use them: Claude costs it $52 per active user. On Enterprise, the 140 seats would cost $2,800; if the 100 active users each consume $200 at API rates, Anthropic's average benchmark for a developer, usage adds $20,000: $22,800 a month, or $228 per active user and 4.4 times the Team bill, before discount. Replace these numbers with yours.
To move from the cost of a seat to what it returns, you then tie usage to use cases and weigh the cost of doing against the cost of inaction.
What is an active user in Claude?
For Anthropic, a member is active on a given day if they have sent at least one message in chat, or opened a Claude Code or Cowork session with tool use (Analytics API documentation, read on 18/11/2026). The console's "Analytics" page, open to owners on the Team and Enterprise plans, compares active members with assigned seats each week, and shows how long the top 10% of spenders stay at their limit. Enterprise adds the Analytics API and, since 28 October 2026, "smart reports", which link each type of work a team does to its spend and its deliverables; Anthropic states that they are not meant for evaluating individuals.
Keep the same definition from one reading to the next, and also look at those who consume very little: they are often people who have not got started. Our article on Copilot reports explains the difference between an active seat and a used seat: the same caution applies here.
What should you check before renewing Claude or moving to per-token billing?
Before renewing, extending or moving Claude to per-token billing, gather six measures in a single document; the first three can be read in Claude's admin console.
- Seats paid, by type. In "Organization settings > Members", the "Tier" column shows each person's seat: Standard or Premium on Team, the Enterprise seat on recent contracts. An Enterprise contract that still shows "Chat" and "Chat + Claude Code", or "Standard" and "Premium", is a legacy plan: it moves to the single seat at the next renewal, and the usage included until now will be paid per token.
- Usage billed on top of the seat, by team, and its spend limits. In "Organization settings > Usage": on Team, are usage credits turned on, and under what monthly limit? On Enterprise, which limits are set, for the organisation, per group or per person? A limit set to unlimited lets consumption be billed with no ceiling.
- Active seats over 30 and over 90 days, and who consumes. In "Analytics", the "How much is Claude costing?" section exports a spend report, one row per person and per model, over 90 days at most. On the usage-based Enterprise seat, it covers all consumption; on legacy seat-based Enterprise contracts, only what exceeds the seat. Note the definition used for an active user.
- What your current usage would cost at API rates, team by team: this is the bill for moving to per-token billing. For Claude Code, its OpenTelemetry data gives it request by request, even on Team; for chat and Cowork, it has to be estimated.
- The cost per active user, calculated as above, over the same period.
- The three use cases that justify a seat, team by team, and the tasks that are repeated from one person to the next.
The sixth measure combines data and interviews; it brings out a task like the security update that several developers redo every month, and tells you where to start pooling, what to cut and who to train. It is about teams: we analyse usage, not individuals. A data or AI manager can send this list as it stands to the leadership that makes the call; what each seat produces, beyond what it costs, is the subject of our page on what your Claude seats return.
To measure actual use of your Claude seats before renewal, Idun Group reads your console's exports and interviews your teams, within 15 days.




