Plan comparison

Claude Team vs Claude Enterprise: price, limits, and when to switch

Claude Team costs $20 per standard seat per month billed annually and fits teams of 2 to 150 people. Claude Enterprise adds SCIM, audit logs, and custom data retention, and bills usage on top of a $20 seat. If you are under 150 people and no one is asking for audit logs, start on Team.

Last updated October 13, 2026

Quick answers

The seven questions people ask, answered in one sentence each

What is the difference between Claude Team and Claude Enterprise?

Claude Team is a shared workspace for 2 to 150 people with usage limits built into each seat, and Claude Enterprise adds SCIM, audit logs, custom data retention and a HIPAA-ready offering while billing usage separately at API rates.

How much does Claude Team cost per seat?

Claude Team costs $25 per standard seat per month billed monthly or $20 billed annually, and $125 per premium seat per month billed monthly or $100 billed annually (US pricing, before tax).

How much does Claude Enterprise cost?

Claude Enterprise lists at $20 per seat per month billed annually, plus usage billed separately at standard API rates, so the monthly total depends on what your team consumes.

How many seats does Claude Team need?

Claude Team requires at least 2 members and supports up to 150 seats.

Does Claude Team include single sign-on?

Yes, SSO is included on Claude Team, so SSO alone is not a reason to move to Enterprise.

When do you need Claude Enterprise instead of Team?

Move to Claude Enterprise when one of four things is true: you handle client-confidential or regulated data, you need SCIM to manage identity at scale, you have more than 150 people, or your usage is heavy and uneven.

What happens when someone hits their usage limit on Claude Team?

With usage credits off, the member waits for the limit to reset; with credits on, the member keeps working and the extra usage is billed at standard API rates.

Prices are Anthropic's US list prices before tax, checked October 13, 2026 on claude.com/pricing.

Prefer to watch?

The short version

Team is the workspace. Enterprise is the control layer.

Claude Team gives a group of 2 to 150 people a shared workspace: all Claude features including Claude Code and Cowork, SSO, central billing, and spend caps, at a per-seat price. Claude Enterprise includes everything in Team and adds the controls a security or compliance team asks for once real data is involved: role-based access, SCIM, audit logs, custom data retention, network controls, and a HIPAA-ready offering with a BAA. Enterprise also changes the billing model, from a seat with usage limits to a $20 seat fee plus usage at API rates.

The most common myth

“We need Enterprise for SSO.” You do not. SSO is on the Team plan. The real Enterprise dividing lines are the depth of identity management and logging: SCIM, role-based access, audit logs, custom data retention, and regulated-data readiness.

Side by side

The full comparison

Grouped by what costs what, what both plans share, and what Enterprise adds. Click any row to open Anthropic's own page for that detail. For how the Enterprise controls work in a rollout, see our governance guide.

Price & seats

Claude Team
Claude Enterprise
Standard seat: $25 per seat per month billed monthly, or $20 billed annually. Premium seat: $125 per month billed monthly, or $100 billed annually.
$20 per seat per month, billed annually. Usage is billed on top at standard API rates.
2 members.
20 seats on a self-serve plan, 50 seats on a sales-assisted plan.
150 seats. Past that, Anthropic points teams to Enterprise.
No published cap.
Each member has their own usage limits, not pooled across the team. Prepaid usage credits let members keep working past the limit, billed at standard API rates.
Usage-based plans have no plan or seat-level usage limits. Each person's usage is metered and billed at standard API rates.

What both plans include

Claude Team
Claude Enterprise
All Claude features, including Claude Code and Cowork. A standard seat includes 1.25x the Pro per-session allowance, a premium seat 6.25x.
Everything in Team.
Yes, with admin controls for remote and local connectors.
Yes.
Spending caps at the organization and individual user level.
Spend limits at the organization and individual user level.
No model training on your content by default.
No model training on your content by default.

What Enterprise adds

Claude Team
Claude Enterprise
Marked No on Team in Anthropic's pricing comparison.
Role-based access with fine-grained permissioning.
Not included.
SCIM provisioning to sync users from your identity provider.
Not included.
Exportable audit logs covering user actions, system events, and data access.
Compliance API not included. Analytics API not listed on Team.
Compliance API for observability and monitoring, plus an Analytics API for engagement and adoption metrics.
Not listed on Team.
Customer-managed encryption keys and US-only inference, per Anthropic's Enterprise plan article. US-only inference is priced at 1.1x for input and output tokens.
Not listed on Team.
Network-level access control and IP allowlisting.
HIPAA-ready offering not included.
HIPAA-ready configuration, with a BAA you can accept from organization settings, plus Claude Security (beta).

After the plan

Picking the plan is the easy part. On most teams we meet, three people use it well, the rest draft emails with it, and five never logged in. That is not a plan problem.

The fix is how the team is taught and what gets built. The adoption framework shows how we measure it, and The Custom Program is how we teach and build it with your team.

The cost question

How your Claude bill behaves

On Team the bill is seats times price until someone hits a usage limit, and what happens next depends on one setting: usage credits. On Enterprise the bill has a usage line that moves with consumption.

Team seats are a fixed price

A standard seat is $25 per month billed monthly or $20 billed annually, and a premium seat is $125 or $100. Seats times price is the base bill.

Limits are per person

Team usage limits apply to each member, not to the team as a whole, so one heavy user hitting a limit does not slow anyone else down. Weekly limits reset at a fixed time assigned to each account.

At the limit with credits off

The member sees a message with the reset time (for example, “You've reached your weekly limit. It resets [day] at [time].”) and waits. The bill does not move.

At the limit with credits on

An Owner turns on usage credits and pre-purchases them. Members then keep working, and the extra usage is billed at standard API rates against those credits.

At a spend limit

Use stops for Claude, Cowork, and Claude Code until the next billing period or until an Owner raises the limit. One request can slightly overshoot the limit, because the check happens before each request.

Enterprise adds a usage line

The $20 seat fee is billed annually at the start of the cycle, and usage is billed separately at API rates: prepaid in credits on a self-serve plan, billed monthly in arrears on a sales-assisted plan. Admins can set spend limits per user and for the whole organization.

Our recommendation

Set an organization spend limit and a per-user spend limit before you turn usage credits on. Both are admin settings on Team and Enterprise, and they turn an open-ended bill into a number you chose. The governance guide covers what happens at a limit and how to cap a runaway agent.

When to choose Enterprise

The four triggers that mean you've outgrown Team

If one of these is true, Enterprise is the right call. If none of them are, Team covers you today.

You handle client-confidential or regulated data

Audit logs, custom data retention, and a HIPAA-ready offering with a BAA are Enterprise features, and customer-managed keys and US-only inference are in Anthropic's Enterprise plan article. If a client contract or a regulator asks for any of them, move to Enterprise.

You need to manage identity at scale

SCIM provisioning to add and remove users automatically from your identity provider is Enterprise-only. SSO itself is included on Team, so SSO alone is not a reason to upgrade.

You're over 150 people

Team caps at 150 seats. Past that, Enterprise is the path.

Your usage is heavy and uneven

Team seats carry per-person usage limits, and credits above them bill at API rates. Usage-based Enterprise plans have no seat-level limits and bill usage at API rates, which can fit heavy or spiky Claude Code use better, with org and per-user spend limits to keep it controlled.

When to stay on Team

Team is the right starting point when…

You're under 150 people and want a bill you can forecast

A seat price is easier to forecast than a seat fee plus usage. Team seats run $20 to $125 per month depending on seat type and billing, and a spend limit caps what credits can add on top.

You want a shared workspace and admin basics, fast

SSO, central billing and administration, and spend caps are all on Team, without an enterprise procurement cycle.

You don't yet have a hard compliance requirement

If nobody is asking for audit logs, a BAA, or custom retention yet, Team covers the workspace and you can move to Enterprise when a real requirement appears.

If you'll move up later

Starting on Team and moving to Enterprise

Plenty of teams start on Team and move to Enterprise when a compliance requirement, a merger, or headcount forces it. For a single organization, Anthropic documents a direct Team-to-Enterprise migration path, so this is a supported, normal motion rather than a rebuild. It is still not fully automatic, so build your Projects and Skills to be portable from day one and nothing has to be re-done. If a move is clearly coming, the question is timing, not whether to over-build on Team.

This is exactly the kind of decision we set up correctly at the start of a rollout, so the workspace you build in month one still holds after you migrate.

Two entities or a pending merger

Running or merging two companies

A common case: two separate companies, often with a merger on the horizon, deciding how to set up Claude across both. The instinct is to wait and stand up one big account. Usually the cleaner move is the opposite.

Default now

Keep each company on its own account

While the companies are still separate legal and operating entities, a separate account each is the cleanest start: separate billing, separate admin ownership, separate verified domains, and data kept apart until legal close. Team covers this for most teams under 150 people, at lower commitment than Enterprise. Start there unless one company independently needs Enterprise-only controls today.

At close

Consolidate onto the surviving entity

Before close, decide the future system of record: surviving domain, identity provider, billing entity, retention policy, and which Projects move, get rebuilt, or are archived. That decision, not the license tier, is what keeps you out of a messy knowledge base later. Then consolidate at close.

Anthropic does support joining multiple organizations under a single parent organization - built for exactly this shape, where entities share an email domain or need data separation. Identity settings (your identity provider and SCIM) are managed at the parent level, while roles and seat tiers map per child company.

The caveat that matters

Joining organizations consolidates identity, SSO, and provisioning - it does not automatically combine everything. Billing, invoicing, and usage tracking stay at the individual-company level even under a parent. So treat combining two environments as a planned migration, not a one-click merge: upgrading a single company from Team to Enterprise is straightforward, but bringing two separate accounts together is a project worth scoping. Don't assume two large Enterprise environments will later fold into one without work.

Choose the plan, then get the team using it.

The plan is the container. What makes Claude stick is the workflows you build, the governance you install, and whether the team still uses it 60 days later. The 90-Day Rollout installs all three end-to-end and ends with a measurable adoption story.

Plan details verified against Anthropic's published pages on October 13, 2026. Anthropic updates plans and pricing regularly, so confirm the latest terms on Anthropic's own pages before you buy: claude.com/pricing, the Team plan article, the Enterprise plan article, the Enterprise billing article, and the usage credits article. Elevate Online is not affiliated with, endorsed by, or sponsored by Anthropic. Back to all resources →