Claude Team vs Enterprise: what forces the upgrade

For most UK organisations of between five and 150 people, Claude Team is the right plan, and the case for Claude Enterprise rests on a shorter list than most comparisons suggest. Enterprise is genuinely forced by specific needs: audit logs, SCIM provisioning, custom data retention controls, the Compliance and Analytics APIs, customer-managed encryption keys, US-only inference, a HIPAA agreement, more than 150 seats, or a preference for its usage-based billing model, where the seat fee covers access and consumption is billed at API rates. Single sign-on, domain capture, role-based permissioning and spend controls no longer force the upgrade: as of 2026 they are Team plan features.

This guide is written for the IT, finance or operations lead who has to choose one. Every product fact below was checked against Anthropic's published pricing page and Help Center articles in July 2026, and the sources are listed at the end. Both plans change often enough that the details should be rechecked before signature. Anthropic publishes US dollar prices, and its plan documentation notes that pricing, currency and tax handling vary by region.

What does the Claude Team plan include in 2026?

The Team plan covers organisations of 5 to 150 people and now carries most of the controls that used to be Enterprise selling points. On the identity side, Team includes single sign-on with domain capture, just-in-time provisioning, and role-based permissioning. On the financial side, admins can set spending caps at both organisation and individual user level, and billing and access are managed centrally. Team also includes enterprise search across connected sources, workplace connectors for Google Drive, Gmail, Google Calendar, GitHub, Microsoft 365 and Slack, and access to Claude Code and Claude Cowork alongside the chat product. Anthropic does not train its models on Team data by default.

Organisation-wide skill management is also available on Team: an owner can upload an approved skill once and provision it to every member, which used to be assumed Enterprise territory. Anthropic's Help Center states this is available to both Team and Enterprise plans.

Usage works on a per-member allowance. Standard seats carry 1.25 times the Pro plan's usage per five-hour session with a weekly limit; Premium seats carry 6.25 times Pro usage for power users, and organisations can mix the two seat types. Limits are per member, so one person exhausting their allowance does not slow anyone else down, and weekly limits reset at a fixed time assigned to the account. When someone does hit their limit, the organisation can enable usage credits, prepaid at standard API rates, so they keep working rather than waiting for the reset. Published US pricing is $20 per Standard seat per month billed annually ($25 monthly) and $100 per Premium seat per month billed annually ($125 monthly).

What does Claude Enterprise add over Team?

Everything in Team, plus the evidence and control layer: audit logs that capture user actions, system events and data access; SCIM for automated provisioning and de-provisioning from your identity provider; custom data retention controls with a 30-day minimum; a Compliance API for programmatic access to activity logs and chat content; an Analytics API for adoption metrics; customer-managed encryption keys; a US-only inference option; and, for eligible organisations, a HIPAA-ready configuration with a Business Associate Agreement. Anthropic's pricing page additionally lists network-level access control and IP allowlisting under Enterprise.

The other difference is economic. Enterprise uses a single seat type at a published $20 per seat per month, billed annually, and that fee covers access only. All usage across Claude, Claude Code and Cowork is billed separately at standard API rates, with no per-seat usage limits and no included token allowance; admins control cost with organisation-level and per-user spend limits. Enterprise is sold two ways: self-serve online from 20 seats (US dollars only, usage credits purchased upfront), or sales-assisted from 50 seats, which adds invoicing, multiple currencies, usage billed monthly in arrears, and non-standard contractual terms.

Capability	Claude Team	Claude Enterprise
Seats	5 to 150	From 20 (self-serve) or 50 (sales-assisted); no published ceiling
Published US seat price	Standard $20/month annual ($25 monthly); Premium $100/month annual ($125 monthly)	$20/month annual, access only
Usage model	Per-member allowances (Standard 1.25x Pro, Premium 6.25x Pro), weekly limits, optional usage credits	No per-seat limits; all usage billed at API rates; admin spend limits
SSO, domain capture, JIT provisioning	Included	Included
Role-based permissioning	Included	Included, with finer-grained permissioning per the pricing page
Organisation and per-user spend controls	Included	Included
Enterprise search and workplace connectors	Included	Included
Organisation-wide skill provisioning	Included	Included
Audit logs	Not available	Included
SCIM provisioning	Not available	Included
Custom data retention controls	Not available (chats retained until deleted)	Included, 30-day minimum
Compliance API and Analytics API	Not available	Included
Customer-managed encryption keys	Not available	Included
US-only inference option	Not available	Included
HIPAA-ready configuration with BAA	Not available	Available to eligible organisations
Model training on your data	None by default	None by default
Billing	Monthly or annual, card	Annual only; invoicing and multi-currency on the sales-assisted route

What actually forces the upgrade?

An Enterprise case is strongest when a specific obligation, not a general sense of seriousness, demands one of the controls above. The following situations are the honest forcing functions.

Evidence obligations force audit logs and the Compliance API. If a regulator, a client contract or your internal audit function expects you to show who accessed what and when, Team has no answer; Enterprise's audit logs and programmatic compliance access exist for exactly this. This is the usual reason FCA-regulated financial services firms land on Enterprise.

Retention schedules force custom retention controls. UK GDPR's storage limitation principle, in the ICO's guidance, expects personal data to be kept no longer than necessary, and many firms operate formal retention schedules. On Team, chat data is retained until someone deletes it, and deletion is the only lever; Enterprise lets an owner set an automatic retention period with a 30-day minimum, with changes recorded in the audit logs. If your data protection policy states a retention period, Team cannot currently enforce it for you; the full plan-by-plan retention picture is set out in our guide to whether Claude is GDPR compliant.

Headcount and identity automation force SCIM and, eventually, the seat ceiling. Past roughly a hundred joiners, movers and leavers a year, manual seat administration becomes an audit finding in waiting; SCIM connects provisioning to your identity provider. And past 150 seats, the Team plan simply stops: Anthropic documents a migration path from Team to Enterprise for organisations that outgrow it.

Three narrower forcers: customer-managed encryption keys, for organisations whose security posture requires holding the key material; the US-only inference option, which is a United States processing control rather than a UK residency answer (the residency routes via cloud platforms are covered in our Claude Enterprise UK buyer's guide); and the HIPAA-ready configuration with a Business Associate Agreement, which matters mainly to UK firms serving US healthcare clients.

Finally, the billing model itself can be the reason. Organisations with genuinely heavy users sometimes prefer paying for actual consumption at API rates with no per-seat caps, rather than managing allowances and credits. The same model cuts the other way for budget-holders who value predictability, which is why the decision belongs in a finance conversation, not just an IT one.

What no longer forces the upgrade?

Single sign-on and domain capture, just-in-time provisioning, role-based permissioning, and organisation and per-user spend controls are Team features in 2026, per Anthropic's current Team plan documentation, with single sign-on also confirmed on the pricing page's Team card. One nuance survives: Anthropic's Enterprise pricing card still lists role-based access with finer-grained permissioning as an Enterprise addition, so organisations that need granular role design should confirm the current position before deciding on that basis. Enterprise search, the workplace connectors, enterprise deployment of the desktop app and organisation-wide skill provisioning are also on both plans. Each of these was, at some point, an Enterprise-only argument, and much of the comparison content in circulation still says so. If a proposal justifies the Enterprise premium on single sign-on alone, it is working from an old feature list.

The power-user argument has also weakened. Team's Premium seats carry 6.25 times Pro usage and can be mixed with Standard seats, so a firm with three heavy users and twelve light ones can serve both inside Team rather than moving everyone to usage-based billing.

What this means in practice: the Team plan is no longer the compromise option. It is a governed, centrally administered commercial plan with a no-training default, identity management and cost controls. The upgrade question is narrower and easier to answer than it was a year ago, and it starts with the forcing list above rather than with feature envy.

How much do Claude Team and Enterprise cost in the UK?

Anthropic publishes US dollar prices: Team Standard seats at $20 per member per month billed annually or $25 billed monthly, Team Premium seats at $100 billed annually or $125 monthly, and Enterprise at $20 per seat per month billed annually plus all usage at standard API rates. Anthropic notes that pricing, currency and tax handling vary by region, so UK buyers should confirm the sterling position at checkout or with sales. Two structural points matter for a UK budget. First, invoicing, whether in sterling or any other currency, is only available on the sales-assisted Enterprise route (50-seat minimum); self-serve Enterprise bills in US dollars only, and Team is a card purchase. Second, an Enterprise budget is two numbers, not one: seats plus consumption. Set organisation and per-user spend limits before go-live rather than after the first surprising invoice, a point we make at length in the Enterprise buyer's guide.

For a five-to-twenty-seat UK SME, the realistic comparison is Team's predictable per-seat cost against Enterprise's 20-seat self-serve minimum with variable usage. As a worked example at published US prices, a ten-person firm on annual Standard seats pays $200 per month before tax, and moving its two heaviest users to Premium seats takes that to $360; the equivalent Enterprise entry point is twenty seats at $400 per month before any usage has been consumed. Unless one of the forcing functions applies, the smaller firm rarely gets value from the jump; the governance features it actually needs, from SSO to spend caps, are already in the Team price. Published prices exclude applicable taxes.

How to decide in one meeting

Three questions settle it. First, does any obligation you can name require audit logs, SCIM, enforced retention, the Compliance API, customer-managed keys, US-only inference or a BAA? If yes, Enterprise, and note which obligation, because it will shape the configuration. Second, will you exceed 150 seats within the contract term? If yes, Enterprise, or plan the migration point now. Third, does procurement require invoicing, sterling billing or non-standard terms? If yes, that is the sales-assisted Enterprise route regardless of feature needs. If all three answers are no, buy Team, revisit at renewal, and rely on the documented Team-to-Enterprise migration path if circumstances change; nothing about starting on Team locks you out of upgrading with your data intact.

The AI Consultancy is an Anthropic Consulting Partner and runs this plan assessment, with the retention, identity and rollout configuration that follows it, for UK organisations. If you want the decision made against your actual obligations rather than a feature list, our Claude consulting and Claude implementation services start there, and our enterprise AI consulting service covers the larger deployments. For how the two plans compare against OpenAI's equivalent, see Claude vs ChatGPT Enterprise for UK SMEs.

Sources

• Claude pricing page (claude.com/pricing), accessed July 2026 (Team and Enterprise feature cards, published US seat prices, Enterprise seat-plus-usage model, network-level access control and IP allowlisting, no-training defaults, rolling five-hour usage sessions and usage credits at standard API rates per its FAQ).
• Claude Help Center, "What is the Team plan?", accessed July 2026 (5-seat minimum and 150-seat maximum, SSO and domain capture, just-in-time provisioning, role-based permissioning, spend controls, enterprise search, connectors, Standard 1.25x and Premium 6.25x Pro usage, usage credits, seat pricing, and the note that pricing, currency and tax handling vary by region).
• Claude Help Center, "What is the Enterprise plan?", accessed July 2026 (audit logs, SCIM, custom data retention, Compliance API, Analytics API, customer-managed encryption keys, US-only inference, HIPAA-ready BAA, seat fee covering access only with usage at API rates, self-serve 20-seat and sales-assisted 50-seat minimums, multi-currency and invoicing on sales-assisted, Team-to-Enterprise migration).
• Claude Help Center, "Provision and manage skills for your organization", accessed July 2026 (organisation-wide skill management available on Team and Enterprise plans).
• Anthropic Privacy Center, "Is my data used for model training?" (commercial products version), accessed July 2026 (no training on commercial data by default).
• Information Commissioner's Office, guidance on the storage limitation principle under UK GDPR, accessed July 2026.