Claude Team vs Enterprise: which to buy

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 get to decide, because Enterprise has a seat minimum they cannot meet. Everything below is written for the companies that do have the choice.

What does each plan cost?

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

[
  {
    "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 annually, or 125 monthly. The annual commitment is a fifth off either way. Both figures are list prices as of August 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. As of August 2026 the pricing page lists the self-serve Enterprise seat at 20 dollars per seat per month on that basis. The sales-assisted path publishes no price. You talk to a buying specialist and receive a quote, so any per-seat Enterprise number you find written down somewhere is someone else's contract, not a rate card.

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. A five-person startup cannot buy Enterprise, so the audit log it wants is not available at any price. A 200-person company cannot stay on Team, because 150 seats is a hard ceiling and there is no overflow. 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 also prorated, 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. Usage on seat-based Enterprise plans is billed at the end of each month against what people actually consumed. 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 with domain capture, just-in-time provisioning, role-based permissioning, and central billing with spending caps. That surprises people who expect SSO to be the Enterprise upsell. It is not.

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, deprovisioning is manual, which means an employee who left on Friday keeps a working Claude seat until an admin opens organization settings and removes them. At 12 people that is a calendar reminder. At 300 people with monthly turnover it is an audit finding, because you cannot prove access ended when employment did.

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. If your legal team has written a retention period into policy, that requirement forces Enterprise no matter how few people you have, and the 20-seat self-serve minimum becomes the real constraint on your 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 spending limits for the organization and for each individual. Enterprise adds a limit per seat tier, so standard and premium users can have different ceilings. You can also disable credits completely, in which case work stops at the included limit and no unplanned bill appears.

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 August 2026. Claude Code is included with every Team seat, standard and premium alike. It is included with every seat on new and self-serve Enterprise plans.

The exception 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. If your organization signed before the change, 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.

Premium seats exist mostly because of Claude Code. As of August 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, with a second weekly limit that applies to Sonnet usage on its own. 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 a Team seat, under an Enterprise seat, or billed straight to an API account with no subscription at all. A solo developer weighing Max at 100 or 200 dollars against a Team seat is comparing two real options. "Enterprise or Claude Code" is comparing a plan to a product, and there is no answer to give.

Worked example: a five-person startup

[
  {
    "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 not on the table, because the self-serve minimum is 20 seats. 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 per-person spending cap, not more seats, because limits are per member and extra seats do not pool. That whole shape is covered in Claude Team plans for a small business.

Worked example: a fifty-person engineering org

[
  {
    "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, and you end that month holding a real token figure for your own workload. Compare that figure against a quote. Buy Enterprise when a security or retention requirement forces it, or when headcount is heading past 150 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 will not sell to you yet.
• 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 retention requirements: Enterprise, self-serve.
• Over 150 people: Enterprise. Team has a hard cap and there is no way around it.
• 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 every 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, 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. A company of five cannot buy Enterprise at any price, so the comparison only becomes real above 20 people. Above 150 people the comparison closes again, because Team stops there.

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

Team includes single sign-on with domain capture, plus just-in-time provisioning and role-based permissioning. Enterprise adds SCIM provisioning, which lets your identity provider create and remove Claude accounts automatically. Without SCIM you remove people by hand in organization settings, so the upgrade is about deprovisioning risk rather than about how people log in.

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, and owners can cap spending both for the organization and for each person. Turning credits off stops work at the included limit instead of producing a bill you did not plan for.