Claude Team vs Enterprise (2026): Pricing, Seats & GDPR
Claude Team vs Enterprise: What is the difference?
Claude Team fits teams of 2–150: roughly US$20 per standard seat monthly (annual billing), with a GDPR DPA and SSO included. Claude Enterprise adds SCIM provisioning, audit logs, retention controls and a Compliance API — self-serve from 20 seats or via a custom sales-assisted quote.
- Claude Team: 2–150 users, ~US$20/standard seat/month annual (~US$25 monthly), premium 5×-usage seats ~US$100.
- Claude Enterprise: self-serve from 20 seats (~US$20/seat + usage billed at API rates) or a custom sales-assisted quote.
- Both plans include a GDPR DPA; neither guarantees EU data residency — EU-only runs via AWS Bedrock or Vertex AI.
- Most teams start on Team; Enterprise pays off once SCIM, audit logs or formal procurement become mandatory.
Claude Team vs Enterprise: Which Plan Does Your Business Need?
Claude Team is the right plan for teams of 2–150 users at roughly US$20 per seat per month (annual billing) — it includes a GDPR DPA, SSO and central admin. Claude Enterprise is the right plan once you need SCIM, audit logs, retention controls or formal procurement — as self-serve from 20 seats or via a custom quote.
Claude Team vs Enterprise at a Glance
| Feature | Claude Team | Claude Enterprise |
|---|---|---|
| Price per user | ~US$20/seat/month (annual; ~US$25 monthly) | Self-serve from ~US$20/seat (usage billed separately at API rates); sales-assisted: custom quote |
| Seat minimum | 2 users (up to 150) | 20 seats self-serve; negotiated for sales-assisted |
| Premium seats (5× usage) | Yes — ~US$100/seat, mixable with standard seats | Individually configured (sales-assisted) |
| DPA (Art. 28 GDPR) | Yes | Yes |
| SSO/SAML | Yes | Yes |
| SCIM provisioning | No | Yes |
| Audit logs | No | Yes |
| Retention controls | No | Yes |
| Compliance API | No | Yes |
| Custom system prompts | Limited | Full (organisation level) |
| API priority access | No | Yes |
| Dedicated account team | No | Yes (sales-assisted) |
| Zero Data Retention | No | Optional |
| Data location | US (default) | US (default) — EU-only only via AWS Bedrock or Vertex AI |
Both plans include a GDPR-compliant Data Processing Agreement and store data in the US by default. No direct Claude plan guarantees EU data residency — the deciding factors between the two plans are governance and procurement, not data location.
When Claude Team Is the Better Choice
Claude Team is Anthropic’s self-serve business plan. It is usually the right choice when:
- Your team has 2–150 users with standard productivity workloads
- You want a GDPR DPA without negotiating a custom contract
- SSO and central user management are enough for your IT setup
- You can start small — the former 5-seat minimum is gone, so pilot teams of 2–5 are fine
- You are a startup or SME testing AI adoption before a company-wide rollout
A standard seat at ~US$20 covers everyday use; premium seats at ~US$100 with roughly 5× the usage suit heavy users such as analysts or developers, and both seat types can be mixed in one workspace. See the full Claude Team plan guide for feature details and the DPA.
When Claude Enterprise Is the Better Choice
Claude Enterprise is Anthropic’s highest commercial tier. It is the better choice when:
- You need SCIM provisioning to manage seats through your identity provider
- Your compliance programme requires audit logs (Art. 5(2) GDPR accountability)
- You need retention controls or Zero Data Retention for sensitive workflows
- You want custom system prompts enforced at organisation level
- Formal procurement matters: quotes, invoicing, volume discounts, AWS Marketplace
- You are rolling out to 20+ seats in a regulated sector (finance, health, legal)
The full Claude Enterprise guide covers the contract structure and governance features in depth.
Claude Team vs Enterprise Pricing
Pricing is the first comparison question — and the two plans work differently.
Claude Team pricing
- Standard seat: ~US$20 per user per month on annual billing; ~US$25 on monthly billing
- Premium seat: ~US$100 per user per month, with roughly 5× the usage of a standard seat
- Seat range: 2–150 users; standard and premium seats can be mixed
- Billing: credit card, self-serve, no quote needed
Claude Enterprise pricing
Enterprise is sold in two variants (as of November 2026):
- Self-serve: minimum 20 seats on annual billing, starting at ~US$20 per seat per month — but usage is billed separately at standard API rates, so heavy workloads push the effective per-seat cost up
- Sales-assisted: custom quote with invoicing, staggered volume discounts, onboarding support and optional procurement via the AWS Marketplace
What that means for your budget
For a 10-person team, Team costs roughly US$2,400 per year. The same headcount on Enterprise self-serve is not even possible — the 20-seat floor exceeds it. The comparison only becomes relevant from ~20 seats upward, and from there the usage-based billing structure of Enterprise is the key variable to model before you commit.
Worked examples at standard-seat pricing (annual billing, as of November 2026):
| Team size | Claude Team (annual) | Claude Enterprise self-serve (floor) |
|---|---|---|
| 5 users | ~US$1,200/year | Not available — below 20-seat minimum |
| 10 users | ~US$2,400/year | Not available — below 20-seat minimum |
| 20 users | ~US$4,800/year | ~US$4,800/year + usage billed at API rates |
| 50 users | ~US$12,000/year | ~US$12,000/year + usage billed at API rates |
At 20+ seats the seat fees converge — what separates the tiers is the usage billing and the governance package. Model your heavy-user share before deciding: a workspace with several premium-seat users on Team may cost more than a lean Enterprise deployment, and vice versa.
Admin Controls and Security: Team vs Enterprise
Both plans include SSO, central user management and a shared workspace. The governance gap opens above that:
- SCIM: automated user provisioning is Enterprise-only — relevant once you manage users through Azure AD, Okta or a comparable identity provider
- Audit logs: Enterprise-only; essential for demonstrating accountability under Art. 5(2) GDPR
- Retention controls: Enterprise-only; set how long conversations are kept, or add Zero Data Retention
- Compliance API: Enterprise-only; exports governance data into your own monitoring stack
- Custom system prompts: organisation-level enforcement is fully available on Enterprise, limited on Team
If your security team has asked for any of the first four items, the plan decision has effectively been made for you.
Does Anthropic Train Claude on Your Business Data?
No — on either commercial plan. Anthropic does not train its models on business content from Claude Team or Enterprise: inputs and outputs from commercial workspaces are excluded from model training by default, and employee personal data is not used for training either.
This is the decisive privacy difference between business and consumer use. On consumer accounts (Free and Pro), conversations may be used for training depending on your settings — one of the reasons Free and Pro are not suitable for business data in the first place.
The practical consequence: on both Team and Enterprise, the training question is settled contractually. What still differs is operational control — retention periods and audit evidence exist only on Enterprise, which matters for documented compliance programmes even when training is off the table on both plans.
GDPR Compliance: DPA and Data Residency Compared
DPA availability: both plans include a Data Processing Agreement under Article 28 GDPR, incorporated automatically into Anthropic’s commercial terms. German companies must have this DPA in place before processing personal data — our Anthropic DPA guide explains what to review, and the dedicated Claude DPA page walks through the contract text.
Data location: both plans process and store data in the United States by default, with Standard Contractual Clauses (SCCs) covering the EU–US transfer. That is legally workable for most use cases, but your privacy notice and records of processing must reflect the transfer.
EU data residency: no direct Claude plan guarantees it — not Team, and not Enterprise. If your data protection officer requires EU-only processing, the route is a deployment on AWS Bedrock (eu-central-1, Frankfurt) or Google Vertex AI in EU regions, each under a separate contract with the hyperscaler. The plan tier does not change this — see our Claude EU hosting guide for the deployment paths.
DPIA: for standard productivity use on either plan, a Data Protection Impact Assessment is usually not required. It can become necessary for special-category data (health, biometrics) or large-scale employee monitoring use cases — regardless of which plan you pick.
Claude Enterprise vs ChatGPT Enterprise
Buyers comparing Anthropic plans often shortlist OpenAI’s ChatGPT Enterprise as well. The shape of the comparison:
- Governance: both offer SSO, SCIM, audit logs and admin controls at the enterprise tier
- GDPR: both include a DPA; ChatGPT Enterprise data residency runs through Azure EU regions, while EU-only Claude deployments run through AWS Bedrock or Vertex AI
- Contract strengths: Claude’s larger context window is an advantage for long-document work (contracts, filings); ChatGPT has broader third-party integrations and image generation
- Pricing model: ChatGPT Enterprise is quoted per seat on annual contracts; Claude Enterprise self-serve separates seat fees from usage billed at API rates
- Minimum commitment: ChatGPT Enterprise typically starts around 150 seats in practice; Claude’s self-serve tier is accessible from 20 seats, making it the earlier upgrade path for mid-sized teams
Neither plan removes the SCC analysis for EU–US transfers by default — the deployment path (Azure EU vs AWS Bedrock/Vertex AI) is what changes the transfer picture, not the brand. For a German-law review of the OpenAI alternative, see the ChatGPT Enterprise GDPR guide.
Five-Step Decision Checklist
If you need the decision today, run this sequence:
- Count your seats. Below 20 users, Claude Team is the only viable business plan — Enterprise self-serve does not go lower.
- Ask your IT team about SCIM. If identity-provider provisioning is mandated, you need Enterprise regardless of team size.
- Ask your DPO two questions: is US processing under SCCs acceptable, and are audit logs required by your compliance programme?
- Model usage, not just seats. Estimate your heavy-user share; on Enterprise their consumption is billed at API rates on top of the seat fee.
- Check procurement rules. Credit-card billing rules out Team in companies that require quotes and invoices — Enterprise sales-assisted covers formal purchasing.
The outcome is usually unambiguous: Team for self-serve teams below 20 seats, Enterprise for governance-driven organisations at 20 seats and above.
Upgrading from Claude Team to Enterprise
The upgrade path is straightforward — most organisations grow into Enterprise rather than starting there. Typical triggers:
- Headcount crosses 20 seats and usage-based billing becomes material
- IT mandates SCIM for automated joiner/leaver processes
- Compliance or a customer audit requires audit logs and retention documentation
- Procurement rules out credit-card billing — quotes and invoicing needed
- A regulated use case calls for ZDR or formal contractual assurances
Workspace content and users carry over. If you are between the two tiers, the Claude Business explainer clarifies the naming and the solo-to-team step first.
Review the DPA Before You Roll Out
Whichever plan you choose, the legal groundwork comes first: the DPA must be signed before personal data flows, your privacy documentation must reflect US processing under SCCs, and employee-data use cases should be cleared with your works council where applicable.
Compound Law advises German businesses and startups on GDPR-compliant AI procurement — DPA review, DPIA assessment and deployment structure. Contact us before you connect business data.
For the adjacent decisions: the Claude Team plan guide, the full Claude Enterprise guide and the Anthropic DPA breakdown.