Claude Team is Anthropic's per-seat plan for smaller groups. Claude Enterprise adds a seat fee plus metered usage, SCIM, custom retention and audit logs. This guide sets out what each plan includes, what it costs, and how we recommend a South African company runs its first rollout.
Every price and policy below comes from Anthropic's own pages, with a link and the date we checked it.
By Rob MacleanReviewed by Amanda KaburiseLast reviewed
Team is priced per seat, so the bill is known in advance. Enterprise charges a seat fee for access and bills all usage on top, so the bill follows how much people use it.
| Item | Plan | Detail | Source |
|---|---|---|---|
| Standard seat, billed monthly | Team | $25 per member a month | claude.com |
| Standard seat, billed annually | Team | $20 per member a month | claude.com |
| Premium seat, billed monthly | Team | $125 per member a month | claude.com |
| Premium seat, billed annually | Team | $100 per member a month | claude.com |
| Premium seat usage | Team | 5x more usage than a Standard seat | claude.com |
| Seats | Team | Minimum 2, maximum 150; Standard and Premium seats can be mixed | claude.com |
| API credits | Team | Up to $500 a month in pooled API credits | claude.com |
| Payment methods | Team | Credit, debit or prepaid card; no ACH | support.claude.com |
Prices in USD as of , excluding VAT. Check the vendor page before you buy.
| Item | Plan | Detail | Source |
|---|---|---|---|
| Seat fee | Enterprise | $20 per seat a month, billed annually | claude.com |
| Seats | Enterprise | Minimum 20 seats | claude.com |
| Usage | Enterprise | All usage is billed on top at standard API rates; the seat fee includes no token allowance | support.claude.com |
Prices in USD as of , excluding VAT. Check the vendor page before you buy.
The Enterprise seat fee buys access, not usage. Every request is billed at API rates, so a few heavy users can cost more than many light ones. We do not publish a typical monthly figure, because it depends on who uses Claude and for what.
We recommend setting group and per-user spend limits before the pilot starts, then reviewing usage weekly for the first month.
| Item | Plan | Detail | Source |
|---|---|---|---|
| Spend controls | Enterprise | Limits at organisation, group and user level. A user limit overrides a group limit, and no limit anywhere means usage is uncapped. Anthropic recommends starting with group and per-user limits | support.claude.com |
| Older seat-based Enterprise contracts | Enterprise | Seat-based Enterprise (Standard and Premium seats) ends at each customer's next renewal | support.claude.com |
As of . Check the vendor page before you rely on it.
Both plans support single sign-on. The controls that large companies usually ask for first, such as SCIM, custom retention and audit logs, are Enterprise only.
| Item | Plan | Detail | Source |
|---|---|---|---|
| Plan family | Team and Enterprise | Anthropic groups Team and Enterprise as Claude for Work | privacy.claude.com |
| Availability in South Africa | Team and Enterprise | South Africa is a supported country | anthropic.com |
| Billing currency in South Africa | Team and Enterprise | Varies by region; check at checkout | support.claude.com |
| Single sign-on | Team and Enterprise | SSO and domain verification on Team and Enterprise | claude.com |
| Domain capture | Enterprise | Enterprise only | claude.com |
| Just-in-time provisioning | Team and Enterprise | Available on Team and Enterprise | support.claude.com |
| SCIM directory sync | Enterprise | Enterprise only | claude.com |
| Customer-managed encryption keys | Enterprise | Enterprise only | support.claude.com |
| Compliance API and audit logs | Enterprise | Enterprise only | claude.com |
| Audits and certifications | Team and Enterprise | SOC 2 Type 2, ISO/IEC 27001, ISO/IEC 42001 and CSA STAR | trust.anthropic.com |
As of . Check the vendor page before you rely on it.
| Item | Plan | Detail | Source |
|---|---|---|---|
| Training on business data | Team and Enterprise | Not used for training by default; feedback you choose to share and the Development Partner Program are the exceptions | privacy.claude.com |
| Data retention | Enterprise | Custom retention on Enterprise only | support.claude.com |
| Data processing addendum | Team and Enterprise | The customer is the controller and Anthropic the processor; a DPA is part of the Commercial Terms | privacy.claude.com |
As of . Check the vendor page before you rely on it.
Neither Claude Team nor Claude Enterprise stores data in South Africa. Using either plan means sending information outside the country, so treat it as a cross-border transfer from the start.
Enterprise can restrict inference to the US. Data residency in other regions is a different route: Claude through a cloud provider, not a Team or Enterprise setting.
| Item | Plan | Detail | Source |
|---|---|---|---|
| Where data is stored | Team and Enterprise | In the US. Default processing may route through the US, Europe, Asia and Australia | privacy.claude.com |
| US-only inference | Enterprise | Available on usage-based Enterprise, at extra cost | support.claude.com |
| Regional data residency | Team and Enterprise | Available through Amazon Bedrock and Google Cloud Vertex AI, not through Claude Team or Enterprise | claude.com |
As of . Check the vendor page before you rely on it.
These are the questions we would settle with your legal and security teams before a pilot uses personal information. This is a starting point, not legal advice.
The trade-off: usage is billed on top of the seat fee, so set spend limits from the first day.
Each setting below links to the Anthropic page it comes from. The order, pilot size and measures are our recommendations, not Anthropic requirements. Anthropic's own steps are in its SSO setup guide and JIT and SCIM provisioning guide.
We recommend starting with one team and one or two workflows, not a company-wide launch. Pick work with a baseline you can measure, such as drafting proposals or answering internal policy questions. Check the seat rules first, because Team and Enterprise set different minimums.
We recommend this order: verify your domain, set up SSO and test it, then choose how accounts are created. SCIM is Enterprise only; on Team, you invite people or use just-in-time provisioning.
Before you save JIT or SCIM, assign every current Claude user in your identity provider. Anthropic deprovisions users who are not assigned when the setting is saved.
Settle three things before users arrive: which connectors to turn on, how long to keep conversations, and how much usage to allow. We recommend turning on only the connectors the pilot needs. On Enterprise, set a retention period your records policy supports, and start with group and per-user spend limits.
We recommend one live session per team, built around its real work, plus a shared page of approved uses and example prompts. Name one person to answer questions in the first weeks. Tell people plainly what not to put into Claude, and why.
Measure the workflow, not the tool. Before the pilot, record the time per deliverable, the cycle time and the rework rate for the chosen tasks. Measure them again after four to six weeks. Report hours saved as estimated, and treat usage figures as a sign of adoption, not of value.
At the end of the pilot, make one of three decisions: expand on Team, move to Enterprise, or stop. Move to Enterprise when you need SCIM, custom retention or audit logs. Stop, or change the workflow, when the measured gain does not justify the seats.
Seat fee: $20 per seat a month, billed annually. All usage is billed on top at standard API rates; the seat fee includes no token allowance. Seats: Minimum 20 seats. Prices are in US dollars, excluding VAT, as of 30 October 2026. Because usage is metered, we recommend setting spend limits before the pilot starts.
A Standard seat costs $20 per member a month billed annually, or $25 per member a month billed monthly. A Premium seat costs $100 per member a month billed annually, or $125 per member a month billed monthly. Seats: Minimum 2, maximum 150; Standard and Premium seats can be mixed. Prices are in US dollars, excluding VAT.
We have not confirmed the billing currency from a South African account. Billing currency in South Africa: Varies by region; check at checkout. Budget in US dollars until you see the checkout.
No. Where data is stored: In the US. Default processing may route through the US, Europe, Asia and Australia. US-only inference: Available on usage-based Enterprise, at extra cost. Regional data residency: Available through Amazon Bedrock and Google Cloud Vertex AI, not through Claude Team or Enterprise.
Not used for training by default; feedback you choose to share and the Development Partner Program are the exceptions. We recommend telling staff which of these exceptions your company allows.
SCIM directory sync: Enterprise only. Provisioning on Team: Invite-only by default, or just-in-time provisioning, which creates the account at first sign-in. Without SCIM, we recommend a written leaver process so someone removes access promptly.
Check the data processing addendum, your basis for sending personal information outside South Africa, the retention period, which data staff may enter, and the training default. Get your information officer's sign-off before the pilot uses personal information. This is a starting point, not legal advice.
Our AI workflow diagnostic takes about two weeks. It baselines one process, checks data and security feasibility, and ends with a go/no-go decision. It can conclude that you need no AI build at all.
Planning a rollout now? Book a call with Rob and Amanda.
