SSD Nodes Learn Hosting plans →
Guides Matt ConnorBy Matt Connor

Claude Team vs Enterprise: which to buy

Team or Enterprise for Claude? Compare seat minimums, billing terms, SSO and SCIM, data controls, and where Claude Code fits, with two worked examples.

Team or Enterprise: the short answer

Choosing between Claude Team and Enterprise comes down to seat count and control. Team is the plan for a small company: it starts at two members, stops at 150 seats, and gives you a fixed price per seat with usage included. Enterprise is the plan for an organization that has an identity provider and a security review: it adds SCIM provisioning and audit logs, along with custom data retention controls and customer-managed encryption keys, and it charges a seat fee plus every token of usage at API rates.

Most companies under 20 people never seriously weigh Enterprise, because its minimum is 20 paid seats and they would be paying for seats nobody sits in. Everything below is written for the companies where the choice is a real one.

What does each plan cost?

Team publishes its prices. Two seat types exist, and you can mix them on one plan.

ChartClaude Team list price per seat per month, US dollars, November 2026
The data behind this chart
[
  {
    "plan": "Standard seat",
    "with_annual_commitment_usd": 20,
    "without_commitment_usd": 25
  },
  {
    "plan": "Premium seat",
    "with_annual_commitment_usd": 100,
    "without_commitment_usd": 125
  }
]

A standard seat is 20 dollars per member per month on an annual commitment, or 25 billed monthly. A premium seat is 100 dollars per member per month on an annual commitment, or 125 billed monthly. The annual commitment is a fifth off either way. Both figures are list prices as of November 2026 and both include usage, up to a per-member limit.

Enterprise prices differently, and this is the part buyers misread. The seat fee covers access to the platform and includes no usage at all. Every token spent in the Claude apps and in Claude Code is billed separately at standard API rates, or at 1.1 times those rates for Opus 4.6, Sonnet 4.6 and later models if you turn on US-only inference. As of November 2026 the pricing page lists the Enterprise seat at 20 dollars per seat per month, billed annually, on that basis. Anthropic's billing documentation says self-serve and sales-assisted usage-based plans use the same seat pricing. What the sales-assisted path adds is invoicing, dedicated customer success management and billing in currencies other than US dollars; older seat-based contracts have a different billing structure.

How many seats do you need to qualify?

Team requires a minimum of two members and supports up to 150 seats. Enterprise requires 20 seats when you buy it self-serve, and 50 seats through the sales-assisted path.

Those minimums decide the question for a lot of companies before any feature comparison starts. The minimum is a number of seats you pay for, not a headcount, so a five-person startup can still buy Enterprise, but the audit log it wants then costs 20 seat fees on an annual term, fifteen of them for nobody. A 200-person company can stay on Team for up to 150 licensed users, because the ceiling applies to purchased seats, not total company headcount. Between 20 and 150 seats you have a real decision to make.

Billing mechanics: annual commitments and mid-term changes

Adding a Team seat mid-term is prorated and charged immediately. Upgrading someone from standard to premium is a reassignment, not a new purchase: if the plan already owns a premium seat nobody holds, you assign it and pay nothing extra. Only when every premium seat is taken do you buy another, and that upgrade is prorated and charged immediately for the price difference. That makes growth cheap and easy.

Shrinking is not symmetric. Removing a member does not trigger an immediate credit or refund, so an annual commitment sized for the headcount you hope to have is money you do not get back if hiring slows. Buy annual for the people who are already employed.

On Enterprise the seat fee behaves like a subscription and the usage does not. Enterprise seats are billed annually, and on a self-serve plan seats cannot be removed during the term; reductions take effect at renewal. Usage is billed against what people actually consume. Self-serve plans buy usage upfront as prepaid credits shared across the organization, and usage stops when those credits run out until more are bought. Sales-assisted plans are invoiced monthly in arrears. Either way your bill moves with the work, which is good when a project pauses and uncomfortable when a deadline arrives.

Admin, SSO and SCIM: where the real line sits

Team already includes single sign-on, just-in-time provisioning, and central billing with spending caps. That surprises people who expect SSO to be the Enterprise upsell. It is not. Domain capture and role-based permissioning are less clear: as of November 2026 Anthropic's Team help article lists both for Team, while the comparison table on its pricing page marks both as Enterprise only, so confirm them with Anthropic before you count on them.

What Team does not have is SCIM (system for cross-domain identity management), the protocol your identity provider uses to create and delete accounts on its own. Without SCIM, removing a member and freeing their seat is manual; with JIT provisioning, unassigning someone from the identity provider's app blocks login but leaves their membership and seat in place until an admin removes them. At 12 people that is a calendar reminder. At 300 people with monthly turnover it is a recurring cleanup task, even when login access has already ended.

Enterprise adds the rest of the compliance surface: audit logs, a Compliance API that reads activity logs and conversation content programmatically, an Analytics API for adoption metrics, customer-managed encryption keys, a US-only inference option, and a HIPAA-ready configuration.

Data controls: training and retention are two different questions

On both Team and Enterprise, your prompts and outputs are not used to train models by default. That is the commercial terms, and it is the same answer on either plan. Nobody needs to upgrade for it.

Retention is separate. "We do not train on it" and "we do not keep it" are different promises, and treating them as one is the most common mistake in an AI vendor review. Custom data retention controls are an Enterprise feature. A written retention period alone does not force Enterprise: Team supports manual chat deletion, with backend deletion within 30 days, and incognito chats are automatically deleted within 30 days unless flagged as a Usage Policy violation. Whether those options satisfy your policy depends on its requirements; configurable organization-wide retention controls require Enterprise, bringing the 20-seat self-serve minimum into the decision. Legal and Usage Policy exceptions can extend retention on either plan.

Is usage pooled across the team?

No. Usage limits on Team apply per member, not to the organization as a whole. A light user's unused capacity does not transfer to a heavy one, so buying extra seats is not a way to buy extra capacity for one person.

What you can do is turn on usage credits. When a member reaches their included limit, credits let them keep working, billed at standard API rates. On Team, owners pre-purchase credits and set a spending limit for the organization as a whole. Limits for each individual are not guaranteed: Anthropic states that spend limits for individual members aren't available to every Team organization. Where they are, the Usage page shows "Spend limits by user"; where it shows "Spend by org member" instead, the organization-wide cap is the spending control you have. Current Enterprise plans work differently: there are no per-seat usage limits to run past, so usage credits do not apply, and admins set spend limits for the organization or for each user instead. Caps by seat tier exist only on legacy seat-based Enterprise contracts that still have standard and premium seats. You can also disable credits completely, in which case work stops at the included limit and no unplanned bill appears.

Team also includes separate monthly API credits: 20 dollars per standard seat and 100 dollars per premium seat, pooled across the organization up to 500 dollars a month. An owner must claim them by linking a Console organization, and new subscribers become eligible after seven days. These credits do not cover interactive Claude Code or extra usage in the Claude apps.

Because overage bills at API rates, the shape of the work drives the number. Long context and long outputs cost far more than short questions, and input and output tokens are priced differently.

Do Claude Code seats come along?

Yes, on both plans, as of November 2026. Claude Code is included with every Team seat, standard and premium alike. It is included with the single Enterprise seat that new and self-serve Enterprise plans use, with one exception covered below. Included means different things on each plan, though, because a Team seat bundles usage while an Enterprise seat bills every token at API rates, a split worked through in what a Claude Code seat costs against paying per token.

There are two exceptions. The first is older Enterprise contracts, which separated seat types. On those, a member needs a Chat + Claude Code seat under usage-based billing, or a premium seat under seat-based billing, until the contract renews and moves everyone to the single Enterprise seat. The second is organizations with the HIPAA-ready configuration, and it is not limited to older contracts: Anthropic provisions them with separate Chat and Chat + Claude Code seats, they are not eligible for the single Enterprise seat, and a Chat seat does not include Claude Code. If your organization signed before the change or runs the HIPAA-ready configuration, check the seat type each person holds in organization settings, because a plain chat seat will not run Claude Code and the error looks like a licensing problem rather than a plan problem.

HIPAA-ready chat alone does not bring Claude Code under your BAA. Covering local Claude Code requires the separate HIPAA configuration applied by the Primary Owner, available to organizations with an Anthropic account team, or qualified zero data retention coverage. IDE extensions remain outside the BAA.

Premium seats exist mostly because of Claude Code. As of November 2026 a standard Team seat carries about 1.25 times the per-session usage of a Pro subscription, while a premium seat carries about 6.25 times, and each seat type also has a weekly limit that applies across all models. A coding agent reads and writes far more text than a chat window, so premium seats belong to the engineers and everyone else stays on standard. For a sense of what heavy agent use actually consumes, see what Claude Code costs in practice.

Enterprise vs Claude Code: this is not a choice

This pairing shows up in search constantly, so here it is plainly. Claude Code is a product: a coding agent that runs in your terminal and in your IDE. Enterprise is a plan: the administration and billing tier an organization buys. They sit at different layers, so they are not alternatives.

You pick a plan first, and Claude Code then runs under whatever seat you hold. It runs under Pro, under Max, under Ultra, under a Team seat, under an Enterprise seat, or billed straight to an API account with no subscription at all. A developer weighing Max at 100 dollars or Ultra at 200 dollars against a premium Team seat is comparing two real options, as long as there is a second person to put on the plan, because Team needs at least two members and is not sold for individual use. "Enterprise or Claude Code" is comparing a plan to a product, and there is no answer to give.

Worked example: a five-person startup

ChartFive-person startup, total Team seat spend per month, US dollars
The data behind this chart
[
  {
    "label": "5 standard seats",
    "with_annual_commitment_usd": 100,
    "without_commitment_usd": 125
  },
  {
    "label": "3 standard, 2 premium",
    "with_annual_commitment_usd": 260,
    "without_commitment_usd": 325
  },
  {
    "label": "5 premium seats",
    "with_annual_commitment_usd": 500,
    "without_commitment_usd": 625
  }
]

Five people, two of them writing code. Enterprise is technically available, but the self-serve minimum is 20 seats, so it would mean paying for fifteen empty seats on an annual term before a single token of usage. Unless a compliance requirement forces it, the only decision left is the seat mix. Three standard seats plus two premium seats cost 260 dollars a month on the annual commitment, or 325 without one.

Start on monthly billing. A five-person company changes shape inside a quarter, and removing a seat from an annual commitment produces no refund. Switch to annual once the headcount holds steady for a few months. If the two engineers hit their premium limit every week, the next step is usage credits with a spending cap, not more seats, because limits are per member and extra seats do not pool. Set that cap per person if your Usage page offers limits by user; not every Team organization gets them, and the rest can cap only the organization as a whole. That whole shape is covered in Claude Team plans for a small business.

Worked example: a fifty-person engineering org

ChartFifty-person org, total Team seat spend per month, US dollars
The data behind this chart
[
  {
    "label": "50 standard seats",
    "with_annual_commitment_usd": "1,000",
    "without_commitment_usd": "1,250"
  },
  {
    "label": "30 standard, 20 premium",
    "with_annual_commitment_usd": "2,600",
    "without_commitment_usd": "3,250"
  },
  {
    "label": "50 premium seats",
    "with_annual_commitment_usd": "5,000",
    "without_commitment_usd": "6,250"
  }
]

Fifty people, twenty of them engineers running coding agents daily. On Team, thirty standard seats and twenty premium seats come to 2,600 dollars a month on the annual commitment. That number is fixed, which is why finance likes it. Putting all fifty on premium would be 5,000, most of it capacity the non-engineers will never touch.

This company clears both Enterprise minimums, so it has a genuine choice. At fifty seats, Enterprise charges a small platform fee per seat and then bills every token at API rates. The seat line becomes predictable and small, and the usage line becomes the whole budget. It lands under the Team figure when usage is light, and well over it when twenty engineers run agents all day.

So measure instead of guessing. Run Team for one billing period with usage credits enabled and a spending cap set, but remember that the overage bill measures only usage beyond included limits, not the full workload Enterprise would bill. Compare the full workload's estimated API cost plus Enterprise seat fees against a quote. Buy Enterprise when a security requirement or a need for configurable retention controls forces it, or when you need more than 150 licensed users and Team runs out, and treat any cost saving as a bonus rather than the reason. The Enterprise seat fee and usage billing page works through that arithmetic in detail.

The decision rule, by company size

  • Under 20 people: Team. Enterprise means paying for 20 seats, so it only makes sense when a compliance requirement forces it.
  • 20 to 150 people with no compliance mandate: Team, unless removing departed members by hand has already become a chore.
  • 20 to 150 people with SCIM, audit log or configurable retention control requirements: Enterprise, self-serve.
  • Over 150 licensed users: Enterprise. A larger company can stay on Team if it needs no more than 150 seats.
  • Any size with heavy, spiky agent usage: price both, because API-rate billing rewards knowing your real consumption.

If you are still deciding between the individual subscriptions and a team plan at all, start with which Claude plan you actually need.

FAQ

Is Claude Enterprise an alternative to Claude Code?

No, and the comparison does not hold. Claude Code is a product, a coding agent that runs in your terminal and IDE. Enterprise is a plan, the administration and billing tier an organization buys. Claude Code is included with every Team seat and with the single seat on current Enterprise plans, so the question to answer is which plan you buy, not which of the two you choose. On older Enterprise contracts, and in HIPAA-ready organizations, which keep separate Chat and Chat + Claude Code seats on any contract, confirm the member holds a seat type that includes Claude Code, because a chat-only seat will not run it.

What is the minimum number of seats for Claude Team and Enterprise?

Team needs two members and supports up to 150 seats. Enterprise needs 20 seats when purchased self-serve, and 50 seats through the sales-assisted path. The minimum is seats you pay for, not people you employ, so a company of five can buy Enterprise only by paying for 20 seats, and for most small companies the comparison only becomes real above 20 people. Above 150 licensed users the comparison closes again, because Team stops there; total company headcount does not determine eligibility.

Does Claude Team include SSO, or do I need Enterprise?

Team includes single sign-on and just-in-time provisioning. Anthropic's Team help article also lists domain capture and role-based permissioning, but its pricing page marks both as Enterprise features, so confirm those two before you rely on them. Enterprise adds SCIM provisioning, which lets your identity provider create and remove Claude accounts automatically. Without SCIM, removing a JIT member and freeing their seat requires manual cleanup, although unassigning them from the identity provider's app blocks login.

Is Claude usage pooled across everyone on the plan?

No. Usage limits on Team apply per member, so unused capacity from a light user does not transfer to a heavy one. When someone reaches their limit, usage credits let them continue at standard API rates. Owners can cap spending for the organization, and for each person only where their Team organization offers per-member limits, which Anthropic says not every Team organization has. Turning credits off stops work at the included limit instead of producing a bill you did not plan for.

Was this article useful?