Claude Team vs. Enterprise: which plan does your company need?

For Claude, powered by Anthropic, choose Team if you have 2 to 150 users, want a flat bill with usage included up to per-seat limits, and single sign-on is enough identity control. Choose Enterprise if you need SCIM, audit logs, the Compliance API, custom data retention, role-based access, IP allowlisting or a HIPAA BAA, or more than 150 users. Enterprise seats are $20 a month, but every token is billed on top.

What is actually different between Team and Enterprise?

Both plans include the same core product: chat on web, desktop and mobile, Claude Code, Cowork, Claude in Chrome, Claude for Microsoft 365, connectors, Skills, projects, Research and enterprise search. Both offer SSO, domain verification, usage analytics, organization-wide skills deployment, admin controls for connectors, and no model training on your content by default. The differences are in governance, billing and support.

How does billing work on each plan?

Team works like a phone plan with a data cap. Each named user gets a seat with limits that reset on a five-hour session window and weekly. A Standard seat gives 1.25 times the Pro per-session allowance; a Premium seat gives 6.25 times. Limits are per person and cannot be shared, so one heavy user hitting a cap does not affect anyone else. Owners can enable usage credits, prepaid and billed at API rates, so people can keep working past their limit under an organization spend cap. Team also includes monthly API credits for building on the Claude Platform: $20 per Standard seat and $100 per Premium seat, pooled and capped at $500 a month. They expire monthly and do not cover interactive Claude Code.

Enterprise works like a utility. The seat buys access only. Every token in chat, Claude Code and Cowork is billed at standard API rates, with no included allowance and no per-seat cap. On self-serve Enterprise you buy credits up front, and when the shared balance reaches zero, usage stops for the whole organization until someone with billing rights buys more. On sales-assisted Enterprise, usage is invoiced monthly in arrears. Either way, admins set spend limits for the organization, groups and individual users.

Which plan costs less for your company?

Take a 60-person company with 10 heavy users on annual billing. On Team, 50 Standard seats and 10 Premium seats cost $2,000 a month, or $24,000 a year, with usage included up to the limits. On Enterprise, 60 seats cost $14,400 a year, leaving $9,600 a year before Enterprise costs more. That is $800 a month of usage across 60 people, about $13.33 per person per month. If average usage stays under that, Enterprise costs less in dollars and also gives you the governance features. If heavy Claude Code users push the average well above it, Team is cheaper but caps those users.

Usage averages in the table are assumptions for illustration, not forecasts. Run a 30-day pilot, read actual spend per person from the Usage page, and redo the math with your own numbers. Anthropic notes that Claude Code and Cowork consume tokens at a much higher rate than chat, so the share of engineers and agent users matters more than headcount.

When is Team the right answer?

• You have fewer than 150 users and do not expect to pass that within the year.
• Finance wants a fixed monthly number, and a user hitting a weekly cap is acceptable.
• Your identity provider can manage access through SSO and you add and remove people by hand without trouble.
• No regulator, customer contract or auditor requires you to export chat logs, set retention or show an audit trail.
• You will not process protected health information.
• A small engineering group wants Claude Code, and Premium seats cover them.

What signals mean you need Enterprise?

• Security asks for automated joiner and leaver handling. That is SCIM, and Team does not have it.
• Legal needs a retention schedule or a legal-hold export. Custom retention and the Compliance API are Enterprise only.
• You need to bring employees' existing personal Claude accounts on your domain into the company organization.
• Different departments need different access, for example Claude Code for engineering only. That needs groups and custom roles.
• Access must come only from corporate networks, which calls for IP allowlisting.
• You will handle PHI, or a customer contract requires a BAA.
• You need US-only inference or customer-managed encryption keys.
• You are approaching 150 seats.

How much admin work does each plan take?

Team is light to run. An Owner connects SSO, turns on just-in-time provisioning so people get an account at first sign-in, assigns Standard or Premium seats, and decides whether to enable usage credits with an auto-reload amount and a monthly organization cap. Removing a leaver is a manual step, which is fine at 30 people and error-prone at 140.

Enterprise asks more of IT but gives more back. SCIM syncs groups from your identity provider, up to 1,000 groups per organization, though Claude reads direct memberships only and ignores nested groups. Custom roles attached to groups decide who sees Claude Code, Cowork and other surfaces, but they apply only to members whose organization role is set to Custom; anyone left on the built-in User role keeps everything enabled. Spend limits stack in a set order: an individual limit always overrides a group limit, a setting decides whether the higher or lower group limit wins for people in several groups, and the organization limit is the hard ceiling. Pooled group budgets, in beta, give a department one shared monthly amount and email billing admins at 50, 75, 95 and 100 percent. Budget a few days of admin design for this before go-live, not after.

Self-serve or sales-assisted Enterprise?

How do you move from Team to Enterprise?

Upgrade the existing Team organization instead of creating a new one. Anthropic says the upgrade keeps chat history, projects, shared content, memberships and roles; a new organization starts from scratch. Self-serve upgrades begin at claude.ai/upgrade, need the 20-seat minimum, ask you to set a per-user spend limit and starting usage balance, and cannot be reversed. Raise any Team spend limit before go-live, because when an organization limit is hit, everyone loses access at once. After the switch, check capabilities: Skills, code execution and file creation, Claude Design, Slides, Docs and Claude in Chrome are off by default on Enterprise. Existing skills are not deleted and come back when you turn the setting on. For a sales-assisted move, schedule go-live for the next business morning, since users lose access during provisioning.

What mistakes do companies make choosing a plan?

• Reading the two $20 prices as equal. The Team Standard seat includes usage; the Enterprise seat includes none.
• Running self-serve Enterprise without auto-reload or monitoring. A zero credit balance stops the whole company, not just the heavy user.
• Giving everyone Claude Code on day one. Anthropic recommends rolling high-intensity surfaces out in waves.
• Assuming Team API credits carry over. Enterprise is not eligible for the monthly API credits.
• Turning on domain capture before SSO is enforced and provisioning works. It is a one-way setting, and people outside your identity provider get locked out.