Claude Enterprise vs Team vs Pro: Which Plan Fits

Pick Pro for one person, and Max for one person who uses Claude all day. Pick Team when two to 150 people need to share projects and connectors under single sign-on. Pick Enterprise when someone asks for SCIM, audit logs, custom roles, a retention period or the Compliance API, or when you would rather pay for usage than have per-seat usage limits. Most organisations can answer with one question: does your security review need anything on the Enterprise-only list below? If not, Team is enough.

This piece is about choosing. What Team includes and how to set it up is in Claude Team plan; how to configure the controls once you have them is in Claude enterprise security.

The four paid plans in one line each

• Pro: one person, more usage than Free, with Claude Code and Cowork. Your privacy settings are your own.
• Max: one person, in two tiers with five or 20 times Pro’s usage, plus higher output limits and priority access at busy times.
• Team: an organisation of two to 150 seats, Standard and Premium, with shared projects, admin-managed connectors, single sign-on, central billing and no training on your content by default.
• Enterprise: everything in Team, plus SCIM, custom roles, audit logs, custom data retention, the Compliance API and other controls for security and compliance teams.

Prices are left out; they change, and the plan page has the current ones. What does not change often is which features sit on which plan, and that is what decides the fit.

Size: where Team ends and Enterprise begins

Team needs at least two members and stops at 150 seats. Anthropic’s page on the Enterprise plan↗ (opens in a new tab) gives a minimum of 20 seats bought online and 50 through the sales team. So between 20 and 150 people, both plans are open to you and size does not decide; the rest of this page does. Above 150, Enterprise is the route.

Identity: SSO on both, SCIM on one

Both organisation plans have single sign-on with domain capture, and both can create accounts the first time someone signs in through your identity provider, called just-in-time provisioning. The difference is leaving. Anthropic’s page on JIT and SCIM provisioning↗ (opens in a new tab) says SCIM is for Enterprise and Console organisations only, and not for Team. Without SCIM, removing someone from your identity provider does not remove their Claude seat; an admin does that by hand.

Roles differ the same way. Team has the built-in roles: User, Admin, Owner and Primary Owner. Enterprise adds custom roles assigned to groups, so you can give finance one set of features and engineering another. If you have more than a handful of distinct groups, that alone can decide it.

Audit and compliance: the usual deciding line

These are Enterprise only, and they are the most common reason an organisation moves up:

• Audit logs. Anthropic’s page on accessing audit logs↗ (opens in a new tab) lists them for Enterprise organisations only: Owners export the last 180 days of sign-ins, membership, SSO and project events.
• The Compliance API, for pulling activity, chats and files into your own tools continuously.
• Custom data retention controls, instead of the default periods.
• IP allowlisting, customer-managed encryption keys and US-only inference.
• A HIPAA-ready configuration for eligible organisations.

Data use for training is not on this list, because it does not separate Team from Enterprise. Both are commercial plans, and Anthropic does not use their inputs and outputs to train models by default. On Pro and Max it is a setting each person chooses, which is one reason a company should not run on a pile of personal Pro accounts.

Usage: limits per seat, or pay for what you use

This is where the plans behave most differently day to day.

• Pro sets the baseline, with limits per session that reset every five hours and a weekly cap.
• Max multiplies it for one person. Anthropic’s page on the Max plan↗ (opens in a new tab) offers five or 20 times Pro’s usage.
• Team gives each Standard seat 1.25 times Pro’s per-session usage and each Premium seat 6.25 times. Limits apply per member, not as a shared pool, and you can mix seat types.
• Enterprise, on the current usage-based plan, splits the two: the seat pays for access, and all usage across Claude, Claude Code and Cowork is billed separately at API rates, with no plan or seat-level usage limit.

So the question is how uneven your use is. If a few people are heavy and most are light, Team with a handful of Premium seats keeps the bill predictable. If use is heavy and hard to forecast, or you are tired of people hitting limits mid-task, Enterprise’s usage billing removes the limit and moves the risk to the invoice. Set spending caps either way.

Context window is not a plan decision. Anthropic’s plans page describes it as up to 1M tokens, varying by model, from Free upward, so choose the model for long documents rather than the plan.

Claude Code and Cowork on each plan

Claude Code and Cowork are on all four paid plans, so neither decides the choice on its own. The details do. Computer use, where Claude operates other apps on your computer, is on Pro and Max only; Anthropic’s page on computer use in Cowork↗ (opens in a new tab) says Team and Enterprise do not have it yet. On Enterprise, Cowork’s cloud sessions start switched off and an Owner grants them to groups, while on Team they are on by default. If a pilot group needs computer use now, their own Max seats are the only documented route.

Enterprise vs Max, and Enterprise vs Pro

These comparisons come up because people start from their own subscription. Max and Pro are for one person, and they are not a cheaper Enterprise. They have no organisation, no single sign-on, no shared projects under admin control, no audit logs and no central billing, and training on content is each person’s own choice. If the question is “I need more usage”, Max answers it. If the question is “my company needs Claude”, the answer is Team or Enterprise, whatever the usage.

A short decision guide

1. Is it one person? Pro, or Max if they hit Pro’s limits often.
2. More than 150 people? Enterprise.
3. Does your security questionnaire ask for SCIM deprovisioning, audit logs, a retention period, the Compliance API, IP allowlisting or HIPAA? Enterprise.
4. More than a few groups that need different features? Enterprise, for custom roles.
5. Is usage heavy and hard to predict? Consider Enterprise’s usage billing; otherwise Team with some Premium seats.
6. None of the above? Team. You can move up later; it is harder to explain why you paid for controls nobody configured.

Record the choice, not just the invoice

Six months on, someone will ask why you chose Team over Enterprise, and the reasons will be gone. On a fenbs board, the Decisions page keeps each decision with the person who made it and why, since the decider is always a person, never the assistant. The follow-up work, such as turning on single sign-on or reviewing seats, becomes tasks with a plan and a test status. Whichever plan you choose, Claude connects to the board as a custom connector where your plan and admin allow it, and every change it makes is recorded in History under its own name.