Claude Team vs Claude Enterprise — the moment usage stops being included.
Team is a listed price with usage baked in: $20–$25 a standard seat, $100–$125 premium, minimum two members, and heavy weeks get throttled. Enterprise changes the shape — a quoted seat billed annually plus usage at standard API rates, so heavy weeks get invoiced instead. Enterprise is also the only tier with SCIM, audit logs, data retention controls, a compliance API and a HIPAA-ready offering. Buy Team for price; buy Enterprise for governance.
| Category | Winner | Margin |
|---|---|---|
| Price transparency · can you read it off a page | AClaude Team | Team lists $20/$25 standard and $100/$125 premium; Enterprise is quoted |
| Cost predictability · knowing next month's bill | AClaude Team | Team is seat price only; Enterprise adds token usage at standard API rates on top |
| Behaviour at heavy use · when limits are hit | BClaude Enterprise | Team throttles until the window resets; Enterprise keeps working and bills the usage |
| Minimum commitment · smallest viable purchase | AClaude Team | Two members and a monthly card payment; Enterprise is billed annually |
| User provisioning · adding and removing people | BClaude Enterprise | SCIM on Enterprise against just-in-time provisioning and domain capture on Team |
| Audit trail · who did what | BClaude Enterprise | Audit logs and OpenTelemetry monitoring are Enterprise-only |
| Data retention control · how long prompts persist | BClaude Enterprise | Retention controls are listed as an Enterprise capability |
| Regulated workloads · health and finance | BClaude Enterprise | A HIPAA-ready offering and a compliance API exist only at Enterprise |
| Spend controls · capping runaway usage | ·Both | Team has organisation and user spend controls; Enterprise adds per-user caps against a metered balance |
| Claude Code access · the coding agent | ·Both | Included on Team seats and on Enterprise, alongside chat and Cowork |
| Payment flexibility · how you pay | BClaude Enterprise | Enterprise offers prepaid credits self-serve or invoicing in arrears through sales; Team is card-billed |
| Best overall | ·Depends | See the decision tree below |
If you want a number, not a contract.
- Listed price — $20 a seat annually, $25 monthly, with usage included rather than metered
- Low floor — two members is the whole minimum, and you can start today on a card
- Premium seats — $100 annually or $125 monthly for 6.25x Pro's per-session usage where a few people need it
- Real admin basics — SSO, domain capture, just-in-time provisioning, role-based permissions and spend controls
- Claude Code included — the terminal agent is part of the seat, not an add-on
If governance is the requirement.
- No throttle — usage is billed at standard API rates rather than capped, so heavy weeks finish
- SCIM — provisioning and de-provisioning through your identity provider, not by hand
- Audit — audit logs and OpenTelemetry monitoring for the questions security teams ask
- Retention — data retention controls, listed as an Enterprise capability
- Compliance — SOC 2, ISO 27001, GDPR and CCPA alignment, a compliance API and a HIPAA-ready offering
| Aspect | Claude Team | Claude Enterprise |
|---|---|---|
| Standard seatThe default seat type | $20–$25 / seat $20 per member per month billed annually, $25 billed monthly. Carries 1.25x Pro's usage per session with a weekly limit that applies across all models A wins | Quoted per user Priced per user per month and billed annually. Enterprise now uses a single seat type — organisations still on older standard-and-premium seat structures are on legacy plans |
| Premium seatFor the heaviest users | $100–$125 / seat $100 per member per month billed annually, $125 monthly. 6.25x Pro's usage per session, with separate weekly limits for all models and for Sonnet models specifically | ✗ Single seat type Enterprise replaces seat tiers with metered usage, so a heavy user costs more in tokens rather than requiring a different seat |
| Usage on top of the seatThe structural difference | $0 · included Usage is bundled into the seat as a multiple of the Pro plan. Exceeding it means waiting for the window to reset, not receiving a bill A wins | Billed at API rates Usage charges are separate from seat fees and calculated on actual token consumption at standard API rates. Organisations choosing US-only inference pay 1.1x those rates |
| How you payBilling mechanics | Card, monthly or annual Seats are charged up front for the billing period, and seats added mid-cycle are prorated for the days remaining and charged immediately | Prepaid or in arrears Self-serve Enterprise buys credits up front that deplete with consumption, paid by card or ACH. Sales-assisted Enterprise is billed monthly in arrears on actual consumption, by bank transfer or card for smaller invoices B wins |
| Minimum sizeSmallest viable purchase | 2 members The Team plan requires a minimum of two members, which puts the entry price at $40 a month billed annually A wins | Annual commitment Priced per user per month and billed annually, with the seat count set in the agreement rather than published as a minimum |
| Spend controlsStopping surprises | Org and user level Spend controls are available at both organisation and individual user level, though with usage included the practical limit is the usage window rather than a dollar figure | Caps against a balance Admins set organisation-wide or per-user spending limits. On self-serve plans these work alongside the credit balance; on sales-assisted plans they block usage past the threshold B wins |
| What is included in a seatProduct surface | Chat + Claude Code Claude on web, desktop and mobile, plus Claude Code for delegating coding tasks from the terminal | Chat + Cowork + Code Workforce access to Claude chat, Claude Cowork, Claude Code and company connectors through a managed interface B wins |
| Which is cheaperThe honest answer | Cheaper when usage is steady A fixed $20 seat with usage included beats metered billing for anyone whose consumption sits inside the window most weeks A wins | Cheaper when usage is uneven Paying only for tokens consumed can undercut a flat seat for occasional users, and it removes the throttle for heavy ones. The crossover depends entirely on your own consumption |
| Capability | Claude Team | Claude Enterprise |
|---|---|---|
| Listed price | ✓ $20–$125 a seat | ✗ quoted |
| Usage included in the seat | ✓ 1.25x or 6.25x Pro | ✗ metered at API rates |
| Behaviour past the limit | Throttled until reset | Keeps working, billed |
| Billing period | Monthly or annual | Annual |
| Minimum members | 2 | Set in the agreement |
| Mid-cycle seat proration | ✓ charged immediately | ✓ per agreement |
| Prepaid credit balance | ✗ | ✓ self-serve Enterprise |
| Invoicing in arrears | ✗ | ✓ sales-assisted |
| US-only inference option | ✗ | ✓ at 1.1x standard rates |
| Single sign-on | ✓ SSO and domain capture | ✓ SSO/SAML and domain capture |
| Just-in-time provisioning | ✓ | ✓ via SCIM |
| SCIM provisioning | ✗ | ✓ |
| Role-based access control | ✓ role-based permissioning | ✓ RBAC |
| Audit logs | ✗ | ✓ |
| OpenTelemetry monitoring | ✗ | ✓ |
| Usage analytics and reporting | ~ billing and admin tools | ✓ |
| Data retention controls | ✗ | ✓ Enterprise-only |
| Compliance API | ✗ | ✓ |
| HIPAA-ready offering | ✗ | ✓ |
| SOC 2 and ISO 27001 | ✓ organisation-wide | ✓ stated on the plan |
| Claude Code | ✓ included | ✓ included |
| Claude Cowork | ~ not listed as a seat feature | ✓ listed |
| Company connectors | ~ standard connectors | ✓ managed company connectors |
| Per-user spend caps | ✓ spend controls | ✓ against a metered balance |
Claude Team
A listed price with usage folded in — two members is the whole minimum, and the ceiling is a usage window rather than an invoice.
Strengths
- Published pricing — $20 a seat annually or $25 monthly, with premium seats at $100 and $125
- Usage included — 1.25x Pro per session on standard seats, 6.25x on premium, with no separate token bill
- Small minimum — two members, bought on a card, with no annual commitment required
- Admin basics — SSO, domain capture, just-in-time provisioning, role-based permissions and spend controls
- Mixed seats — buy premium only for the few people who need 6.25x, and standard for everyone else
Weaknesses
- No SCIM, so joiners and leavers are managed by hand or by domain capture rather than from your identity provider
- No audit logs or OpenTelemetry monitoring, which is often the first thing a security review asks for
- No data retention controls and no compliance API
- No HIPAA-ready arrangement, so regulated health data is out of scope
- Heavy weeks stop rather than cost more — throttling is the ceiling
Best for
- Teams of two to a few dozen with steady usage
- Organisations that want a number they can approve without a contract
- Mixed workloads where a few heavy users can take premium seats
- Getting started this week rather than this quarter
Claude Enterprise
A different pricing shape — a quoted annual seat plus metered usage at API rates, and the governance surface that regulated buyers actually need.
Strengths
- No throttle — usage is billed on actual token consumption at standard API rates, so a heavy week finishes
- SCIM — provisioning and de-provisioning driven by your identity provider
- Audit — audit logs plus OpenTelemetry monitoring, with usage analytics and reporting
- Retention and compliance — data retention controls, a compliance API and a HIPAA-ready offering
- Payment options — prepaid credits self-serve, or monthly invoicing in arrears through sales
Weaknesses
- No listed price — every number comes from a quote
- Usage is a second, variable line on top of the seat, so the monthly total moves with consumption
- US-only inference costs 1.1x standard API rates
- Billed annually, so the commitment is longer than a Team card payment
- Older Enterprise agreements using standard and premium seats are legacy structures being phased out
Best for
- Regulated industries needing retention controls or a HIPAA-ready arrangement
- Organisations whose identity provider must own provisioning
- Security reviews that require audit logs and telemetry
- Usage that is uneven enough that a fixed seat would either throttle or waste
Eight-person startup adopting Claude
You want everyone on it next week, nobody has time for procurement, and the finance question is simply what it costs.
Reasoning: Team, without much deliberation. Eight standard seats at $20 billed annually is $160 a month with usage included, the minimum is two members, and you can buy it on a card today. Enterprise would mean a quote, an annual commitment and a second variable line for token usage — all of which buys governance you do not yet need.
Health-tech company touching patient data
Legal will not approve anything without a HIPAA-ready arrangement and a clear answer on how long prompts are retained.
Reasoning: This ends at the plan sheet rather than the price sheet. A HIPAA-ready offering, data retention controls and the compliance API are Enterprise capabilities; Team carries none of them. No amount of seat-price arithmetic changes that, and running regulated data on a Team plan is a compliance problem rather than a cost saving.
Engineers hitting the weekly limit every Thursday
Your heaviest users run Claude Code all day and stop working when the weekly window closes.
Reasoning: First try premium seats — $100 annually for 6.25x Pro's per-session usage is a large step and stays inside a listed price. If they still hit the ceiling, the structural fix is Enterprise, where usage bills at standard API rates instead of stopping. The question to answer honestly is whether you would rather pay for the overflow or lose the hours.
Two hundred employees, most of them occasional users
Everyone should have access, but realistically thirty people will use it daily and the rest a few times a month.
Reasoning: This is where metered billing earns its complexity. Two hundred Team seats at $20 is $48,000 a year whether or not the light users show up. Enterprise charges a quoted seat plus actual token consumption, so the long tail costs close to nothing in usage. Model both against a month of real data before committing — the crossover depends entirely on how light the light users are.
Security review before rollout
Your security team needs to see who accessed what, pipe events into existing monitoring, and manage accounts from the identity provider.
Reasoning: Three specific requirements, and Team meets none of them: audit logs, OpenTelemetry monitoring and SCIM are all Enterprise capabilities. Team offers SSO, domain capture and just-in-time provisioning, which handles sign-in but not lifecycle or evidence. If the review is a gate rather than a formality, this decides the tier before cost enters the conversation.
Finance wants a fixed annual number
The budget is set once a year and variable lines cause problems no matter how small they are.
Reasoning: Team is the fixed-number plan: seats multiplied by twelve, with usage included rather than metered. Enterprise deliberately splits the bill into a seat and a consumption line, which is more accurate and less predictable. If a variable line is genuinely unacceptable, buy the plan that does not have one — and accept that the ceiling arrives as a throttle instead.
Frequently asked.
Common questions about this comparison, with sources where they matter.
Q · 01 What is the real difference between Claude Team and Enterprise? +
$20 a seat annually ($25 monthly) for 1.25x Pro per session, or $100 ($125 monthly) for a premium seat at 6.25x. Enterprise is a quoted seat billed annually plus usage charged on actual token consumption at standard API rates. So Team stops when you hit the limit; Enterprise keeps going and bills you. Everything else — SCIM, audit logs, retention controls, HIPAA — follows from Enterprise being the governed tier.Q · 02 How many seats does Claude Team need? +
$40 a month billed annually or $50 monthly. Seats added mid-cycle are prorated for the days remaining in the billing period and charged immediately. There is no published minimum for Enterprise — the seat count is set in the agreement, and the plan is priced per user per month and billed annually.Q · 03 Are premium seats worth $100? +
Q · 04 Which plan is cheaper? +
$20 seat with usage included is cheaper for anyone whose consumption sits inside the window most weeks. Metered Enterprise billing is cheaper when a large share of your users are occasional — you pay a seat and almost no tokens for them — and it is the only option that does not stop your heaviest users mid-task. Take a month of real usage data before deciding; on a large team with a long tail of light users the difference runs to tens of thousands a year in either direction.