Claude Team Plan: What You Get, When Enterprise Is Worth It, and a 30-Day Plan to Roll It Out
We added Anthropic’s current prices and plan details: Team is for 2 to 150 people, seats come as Standard or Premium, and single sign-on, usage analytics and spend caps are now part of Team. There is also a comparison with Pro and Max, and a separate guide to Team vs Enterprise.
The Claude Team plan is Anthropic’s plan for companies that want Claude for a group rather than for individuals: one bill, an admin console, business data terms under which your content is not used to train models, and projects and connectors your team can share.
Buying it takes ten minutes. Getting a team to use it takes a plan, and most companies skip that part, which is why so many Team subscriptions end up with a handful of heavy users and a long list of seats nobody opens. Below: what the plan gives you, when Enterprise is worth it instead, and a thirty-day rollout that gets people using it on real work.
What the Team plan gives you
The Team plan is for groups of 2 to 150 people. Every seat gets the full Claude: all models, projects, Claude Code and Cowork, with more usage than a personal Pro plan. On Anthropic’s pricing page on 23 October 2026, a Standard seat cost $20 a month on an annual plan or $25 monthly, and a Premium seat $100 or $125, in US dollars before tax. The usage is included in the seat, which is what makes Team such good value. What you get for it comes down to five things.
| What you get | Why it matters for a company |
|---|---|
| Central billing and seat management | One owner adds and removes people. No expense claims for personal subscriptions, and leavers lose access the day they leave. |
| Single sign-on and spend caps | People sign in with the company account, and an admin can cap spend for the whole organisation or for one person. Usage analytics show who actually uses it. |
| Business data terms | Anthropic does not train its models on content from Team and Enterprise plans. That is usually the line between “we can’t put client work in there” and “we can”. |
| Shared projects | A project holds the context and files for a piece of work. Shared, it means a new colleague starts with the team’s instructions and material instead of from zero. |
| Connectors with admin control | An administrator can switch connectors on for the organisation and keep them read-only, so the approved setup is the default rather than something each person configures. |
If you are unsure about the data question specifically, we have written a direct answer to whether Claude is safe for confidential data.
Standard and Premium seats
A Team plan can mix two kinds of seat. Both include everything; the difference is how much each person can use before they reach their limit.
| Seat | Usage | Give it to |
|---|---|---|
| Standard | More than a personal Pro plan | Most people: writing, analysis, research, everyday work in projects |
| Premium | About five times a Standard seat | The few who work in Claude all day, or build with Claude Code |
Limits are per person and are not pooled, so one heavy user never uses up a colleague’s allowance. Start everyone on Standard and move the people who keep hitting the limit to Premium after the first month. That number comes straight out of the usage analytics.
Team, Pro or Max?
Pro and Max are personal plans. Max is for one person who works in Claude all day and needs much more usage than Pro. Neither gives the company anything: no shared bill, no admin, no single sign-on, and each person decides for themselves what goes in.
| Pro | Max | Team | |
|---|---|---|---|
| Who it is for | One person | One person who uses Claude all day | 2 to 150 people at a company |
| Billing and seats | Personal | Personal | One bill, admin adds and removes people |
| Single sign-on | No | No | Yes |
| Usage analytics and spend caps | No | No | Yes |
| Shared projects and admin-controlled connectors | No | No | Yes |
Three people on Max are three separate accounts that happen to be paid by the same company. As soon as two or more people use Claude for the company’s work, Team is the plan that makes it the company’s tool.
Team or Enterprise?
Start on Team unless you already know you need something only Enterprise has: more than 150 people, HIPAA, SCIM or a compliance API. Enterprise has the same $20 seat, but usage is billed on top at API rates, so for a team that uses Claude every day it costs far more. The full comparison, with a calculator, is in Claude Team vs Enterprise, and what the other plan includes is in our Claude Enterprise guide. If you already have Microsoft 365 and are weighing Claude against Copilot, our guide to Copilot vs Claude covers what each is better at and when to run both.
Why most rollouts stall in week three
The pattern is consistent enough to predict. Week one, everyone logs in and asks it something. Week two, the curious keep going. By week three, usage has collapsed to a handful of people, and a few months later someone asks whether the licences are worth renewing.
Three causes account for almost all of it:
- People test it on the wrong questions. A trivia question gets an unremarkable answer, and the conclusion is drawn from that. Nobody tried it on the report they spend every Monday assembling.
- Nobody knows the rules. Can I paste a client email in? A contract? Payroll data? Without an answer, careful people do nothing, which is the opposite of what you paid for.
- Nothing is connected. Every task starts with copying material in from somewhere else, and that friction quietly decides which tasks are worth trying.
Three things to set up before anyone logs in
Half a day of preparation removes all three causes. Do it before the invitations go out, not after usage has dropped.
1. One page of rules. Which data never goes in, which always may, what needs a human look before it leaves the company, and who to ask. Short enough that people read it:
2. One shared project per team. Put in the context every request would otherwise need: who the team is, who its clients are, the tone it writes in, the templates it uses. This is the difference between Claude giving a generic answer and one that sounds like your company. We cover how in what Claude projects are for.
3. One connector per team, read-only. The tool each team spends the most time digging around in: CRM for sales, the file store for operations, the helpdesk for support. Our guide to Claude connectors has the list and the rollout decisions.
A thirty-day rollout plan
| Week | What happens | Done when |
|---|---|---|
| 1 | Rules published, one shared project and one read-only connector per team. Invitations go out with the rules attached. | Everyone has logged in and knows where the rules are. |
| 2 | A hands-on session per team: each person builds something for their own role, on real work, with the rules set in the room. | Every person has used Claude on one real task, not a test question. |
| 3 | Each team picks two recurring tasks to move to Claude, names an owner for each, and writes down how long they take today. | Two use cases per team, each with an owner and a before number. |
| 4 | Review: who uses it weekly, which use cases stuck, which connectors are used. Remove what is not, add what teams ask for. | A short list of what changes in month two. |
Week two is the one to protect. Reading about what Claude can do does not change behaviour; building something for your own job does. A team that has each built one thing in the same room, with the rules agreed together, is a team that is still using it in month three.
How to know it is working
Not by counting seats. Three numbers tell you most of what you need: how many people use Claude every week compared with how many have access, how many use cases are running with a named owner, and how much time those use cases return against the before number you wrote down in week three. The full set, and how to collect them without a data project, is in how to measure AI adoption. For individuals who want to see their own patterns, Claude Reflect shows how they actually use it.
Week two, done properly, is exactly what a Deployed Kickstart is: every team builds something real for their own roles, with the rules set in the room. The Partner programme carries weeks three and four onward, until the use cases run without us.
Frequently asked questions
What is the Claude Team plan?
The Claude Team plan is Anthropic’s plan for companies that want Claude for a group of people rather than for individuals. It is for groups of 2 to 150 people and adds central billing and seat management, single sign-on, usage analytics and spend caps, business data terms under which Anthropic does not train its models on your content, projects that a team can share, and connectors that an administrator can switch on for the organisation. Every seat includes all models, Claude Code and Cowork. On 23 October 2026 a Standard seat cost $20 a month on an annual plan or $25 monthly, and a Premium seat $100 or $125, with usage included.
What is the difference between Claude Team and Claude Max?
Max is a personal plan for one person who works in Claude all day and needs much more usage than Pro. Team is a company plan for 2 to 150 people with one bill, an admin console, single sign-on, usage analytics, spend caps and shared projects. Several people on Max are separate personal accounts; on Team they work in the company’s own Claude.
What is the difference between a Standard and a Premium seat on Claude Team?
Both include every Claude feature. A Premium seat gives about five times the usage of a Standard seat, which itself gives more than a personal Pro plan. The two can be mixed on one Team plan, and limits are per person rather than pooled. Most companies start everyone on Standard and move the heaviest users to Premium after a month.
Does Anthropic train on data from the Claude Team plan?
No. Under Anthropic’s commercial terms, content from Claude Team and Enterprise plans is not used to train its models. This is one of the main reasons companies move from personal subscriptions to a business plan: it is usually the difference between a team being allowed to use Claude on client work and not.
How long does it take to roll out Claude to a team?
The setup takes an afternoon: publish one page of rules, create a shared project per team and connect one tool per team read-only. Getting the team to use Claude on real work takes about a month of deliberate effort. A workable plan is rules and setup in week one, a hands-on session where each person builds something for their own role in week two, two owned use cases per team in week three, and a review of what stuck in week four.
Why do Claude rollouts fail?
Most stall in week three for three reasons. People test Claude on trivial questions and judge it on those, nobody knows which data they are allowed to put in so careful people do nothing, and nothing is connected so every task starts with copying material in by hand. All three can be removed before launch with a one-page set of rules, a shared project per team and one read-only connector per team.
Is the Claude Team plan worth it for a small business?
For a group of people doing shared work, usually yes, mainly because of the business data terms and shared projects rather than raw capability. Personal subscriptions leave each person with their own setup and their own rules about what data goes in. A Team plan gives one bill, one set of rules and shared context, which is what lets Claude be used on real client and company work.
Found this useful? Send it to someone who needs it.