Claude Team Plan: Pricing, Seats, Worth It?
Get The Claude Starter System
20 prompts, skills, and guides that get finished work out of Claude. Free PDF.
The Claude Team plan costs $25 per person per month for a Standard seat, or $20 a month on annual billing, and $125 or $100 for a Premium seat with five times a Standard seat's usage, for teams of 2 to 150 people, according to Anthropic's pricing page. It pays off once two or more people put client or company material into Claude, because Team keeps that work out of model training by default and adds shared Projects and admin controls at about the same price per unit of usage as individual Pro plans.
This guide is for owners and team leads at companies, agencies, and consultancies of 2 to 20 people, where nobody has an IT department to run the rollout. You'll get what each seat type includes, the seat math against buying everyone Pro, what admins control, what happens to your data, and a two-week rollout checklist. Prices are in US dollars before tax, as of October 2026. If you're picking a plan for yourself rather than a team, start with our Claude pricing guide.
How much does the Claude Team plan cost?
A Claude Team Standard seat costs $25 per person per month on monthly billing or $20 a month billed annually, and a Premium seat costs $125 a month or $100 a month billed annually. Anthropic's Team plan help article says a Team plan needs at least two members and supports up to 150 seats, and organizations that need more move to Enterprise. When Anthropic launched Team in May 2024, it cost $30 per user per month with a minimum of five seats, which is why older articles about Claude for teams still quote those numbers.
You can mix seat types on one plan and add seats mid-term, so a team of eight might run six Standard seats and two Premium seats. The Team help article also says Team is available only in supported locations and that "pricing, currency, and tax handling vary by region."
| Plan or seat | Monthly billing | Annual billing | Session usage vs Pro | Fable access |
|---|---|---|---|---|
| Team Standard | $25/mo | $20/mo ($240/yr) | 1.25x | Usage credits only |
| Team Premium | $125/mo | $100/mo ($1,200/yr) | 6.25x | Up to 50% of weekly limits |
| Pro (one person) | $20/mo | $200/yr (about $17/mo) | 1x | Usage credits only |
| Max 5x (one person) | $100/mo | Monthly only | 5x | Up to 50% of weekly limits |
Sources: claude.com/pricing, the Team plan and Max plan help articles, and Fable models on your plan. Usage multiples are per-session allowances, and every paid plan also has a weekly limit.
How billing works when your seat count changes
Adding a seat or moving someone from Standard to Premium costs money right away: Anthropic charges the prorated amount immediately, according to its article on how the Team bill is calculated. Removing a person brings no immediate credit or refund. Their seat stays on your plan, still paid for, and becomes free for someone else. If you lower the seat count, the change takes effect at your next renewal, which on annual billing means the annual renewal date. Only Owners and the Primary Owner can buy seats or open billing, per the help article on purchasing and managing Team seats.
That asymmetry is the main reason to start on monthly billing. An Owner can switch a monthly Team plan to annual once the seat count settles; the annual plan starts immediately, and Anthropic credits the unused monthly time. The Team billing FAQ says Team accepts credit, debit, or prepaid cards and no ACH bank transfers, and the pricing page marks invoicing and net terms as unavailable on Team.
Team plans also earn monthly API credits: $20 per Standard seat and $100 per Premium seat, pooled into one balance capped at $500 a month. The credits pay for building on the Claude API. They don't add usage in the Claude app, Claude Code, or Cowork, and unused credits expire at the end of each billing cycle, so a team that never touches the API can leave them out of the plan comparison.
Standard vs Premium seats: usage, models, and features
A Standard seat gives one person 1.25 times the Pro plan's per-session usage, and a Premium seat gives 6.25 times, which is five times a Standard seat, according to the Team plan help article. Each seat also has a weekly limit across all models. The same article says Team limits are per member and "can't be transferred or shared between team members," so a quiet colleague's unused allowance never reaches your busiest person.
Sessions reset every five hours, and Claude on the web, Claude Code, and the desktop app all count toward the same limit, per Anthropic's article on how usage and length limits work. Cowork tasks count against your usage too, and Anthropic's Cowork guide warns that multi-step tasks "use more of your usage than a quick question." Our guide to Claude usage limits explains how the five-hour window and the weekly cap interact.
Both seat types get the same product. The pricing page lists Claude Code and Cowork, Claude Design, Slides, and Docs, Claude Science, Microsoft 365, @Claude, enterprise search, and Claude Motion and Dashboards in beta for Team, with Opus, Sonnet, and Haiku on every seat. Anthropic's Claude Tag docs describe tagging @Claude in your Slack channels on Team and Enterprise; the FAQ below covers how it bills. You don't need a Premium seat for Claude Code: Anthropic's seat article lists "Claude Code access" for Standard seats. For what Claude Code costs on each plan, see our Claude Code pricing breakdown.
The two seats differ on Fable, the model Anthropic's model overview recommends for "demanding reasoning and long-horizon agentic work." A Premium seat can spend up to 50% of its weekly limit on Fable at no extra cost, while a Standard seat can use Fable only through paid usage credits, per Anthropic's article on Fable models on your plan. Fable on its own rarely justifies a Premium seat for business work, since Anthropic says its newest Opus performs at the level of Fable on most work.
When someone hits a limit mid-task, an Owner decides whether they can keep going. On Team, Owners pre-purchase usage credits, Anthropic bills them at standard API rates, and Owners can cap spending for the whole organization and for each member under Organization settings > Usage, per the help article on usage credits for Team plans. With credits on, members "can keep working without interruption" past their seat limit. With credits off, they wait for their limits to reset.
Who should get a Premium seat?
Our rule for small teams: start everyone on Standard, then move a person to Premium only if they hit their Standard limit on three or more workdays in two weeks, or they need Fable for real work most weeks. Upgrades apply right away with a prorated charge, while a move from Premium back to Standard waits until renewal (see the seat article), so upgrading late costs less than downgrading early. To get a first seat plan, paste this into Claude with one line per teammate:
I'm choosing seats for our Claude Team plan. Use only these prices (USD per person per month, before tax): - Team Standard seat: $25 billed monthly, $20 billed annually. 1.25x the Pro plan's per-session usage. Fable only via usage credits. - Team Premium seat: $125 billed monthly, $100 billed annually. 6.25x the Pro plan's per-session usage. Fable up to 50% of weekly limits. - Individual Pro: $20 monthly, or $200 per year. - Individual Max 5x: $100 monthly, 5x Pro's usage. Our team, one line per person: [role] | [main Claude tasks] | [days per week] | [hit a limit last month? yes/no] | [handles client or confidential data? yes/no] 1. Recommend Standard or Premium for each person, with a one-line reason. 2. Total the monthly cost on monthly billing and on annual billing. 3. Compare that with individual Pro plans, plus Max 5x for anyone who needs Premium-level usage. 4. List anyone who can wait before getting a seat. Show your arithmetic. If a line is missing information, ask me.

Give your team ready-made prompts from day one
- 500+ copy-paste prompts & workflows
- 35 installable Cowork skills
- Role packs for 6 professions
- New prompts & skills every week, forever
Is the Claude Team plan worth it vs giving everyone Pro?
The Claude Team plan is worth it over individual Pro plans when your team shares client or company material in Claude, because per unit of usage a Team seat costs the same as Pro, or slightly less on annual billing. A Standard seat costs $25 for 1.25 times Pro's session allowance, which works out to $20 per Pro-sized allowance, the price of a monthly Pro plan. On annual billing the figure drops to $16, against about $16.67 for annual Pro.
So the admin controls, shared Projects, and commercial data terms carry no usage premium. You pay more per person on Team only because each seat includes 25% more usage than Pro, and that extra usage is worth nothing to someone who never reaches the Pro limit. The table runs the same math for every plan.
| Plan and billing | Price per person per month | Session usage vs Pro | Price per Pro-sized allowance |
|---|---|---|---|
| Pro, monthly | $20 | 1x | $20.00 |
| Pro, annual | $16.67 ($200/yr) | 1x | $16.67 |
| Team Standard, monthly | $25 | 1.25x | $20.00 |
| Team Standard, annual | $20 | 1.25x | $16.00 |
| Team Premium, monthly | $125 | 6.25x | $20.00 |
| Team Premium, annual | $100 | 6.25x | $16.00 |
| Max 5x | $100 | 5x | $20.00 |
| Max 20x | $200 | 20x | $10.00 |
Our calculation from Anthropic's published prices and per-session multiples on the pricing page and the Team and Max help articles. The multiples are per-session figures and weekly caps also apply, so treat the last column as a guide rather than a guarantee.
Worked example: an eight-person agency
Take an agency where six people use Claude every day for writing and research, and two run long analysis and Cowork tasks that hit limits. Buying individual plans means six monthly Pro plans ($120) and two Max 5x plans ($200), or $320 a month for 16 Pro-sized allowances, with every person on their own consumer account. Team on monthly billing means six Standard seats ($150) and two Premium seats ($250), or $400 a month for 20 allowances. Team on annual billing costs $120 plus $200, which is $320 a month or $3,840 a year, for the same 20 allowances.
On annual billing, Team costs the agency exactly what the monthly individual plans cost and gives 25% more session usage, plus shared Projects, central billing, and commercial data terms. On monthly billing it costs $80 a month more for that same 25%. The plan would also earn $320 a month in pooled API credits (six seats at $20 plus two at $100, under the $500 cap), which matters only if someone builds on the API.
When individual Pro plans win
Individual Pro plans cost less for two or three light users who keep client material out of Claude. Three annual Pro plans cost $600 a year and three annual Standard seats cost $720, so if nobody hits the Pro limit, the extra $120 buys admin controls and data terms you may not need yet. Max 20x also beats every Team seat on usage per dollar, at $200 a month for 20 times Pro's usage (per the Max plan article), but it covers one person, and the pricing page's comparison table shows none of Team's admin features, such as single sign-on or usage analytics, on Pro or Max. Our Claude Pro vs Max comparison covers that choice for individuals.
Buy Team if any of these is true
- ✓Anyone will paste client, customer, or confidential company material into Claude.
- ✓Two or more people should work from the same Projects, such as brand rules, offers, or client files.
- ✓You need to cut off access when someone leaves and keep the Projects they shared with the team.
If none is true and nobody hits the Pro limit, buy Pro per person now and move to Team when one of these becomes true.
If your team will hand Claude long, multi-step tasks, read our Claude Cowork pricing guide before you settle the seat mix. Anthropic says multi-step tasks use more of your usage than a quick question, so task-heavy people reach their Standard limit first.
What Team admins control, and what happens to your data
Team admins get single sign-on, domain verification, central billing, usage analytics, user and organization spend controls, admin controls for connectors, organization-wide skills and instructions, and central deployment of the Claude desktop app, according to the comparison table on Anthropic's pricing page. The same table marks SCIM, audit logs, role-based access, custom data retention controls, and the HIPAA-ready offering as Enterprise-only.
A Team organization has four roles: User, Admin, Owner, and Primary Owner, per Anthropic's roles and permissions article. Each organization has one Primary Owner, and that person uses one of your seats. Admins can add members and reassign seat types, while buying seats and managing billing stay with Owners and the Primary Owner.
Where the main settings live
- Members.Organization settings > Members > Add member. Invites only go to email addresses on your organization's allowed domains, new Team organizations have shareable invite links on by default, and pending invitations take up seats right away, per the article on managing members.
- Memory and web search.Organization settings > Capabilities. On Team, memory stays off for each member until they turn it on, Owners decide whether the organization has it, and switching it off for the organization deletes everyone's existing memory entries, per the memory article. Owners can also turn off web search for Cowork and chat there, per the Cowork guide.
- Cowork.Cowork is on by default for Team, and Owners can switch it off in Organization settings > Cowork. Running Cowork in the cloud is a beta that starts switched on for Team, and the "Automatically approve" mode is allowed by default, per the article on Cowork on Team and Enterprise plans. When Anthropic began merging Cowork and chat into one Claude on September 16, 2026, it said Team plans "will follow soon" after Pro and Max.
- Claude in Chrome.The extension works on every paid plan, including Team. Your admin decides whether it's enabled and can limit which sites Claude visits with allowlists and blocklists, per the Claude in Chrome article. Our Claude in Chrome guide covers safe setup.
- Shared Projects. Team members can share a Project with specific colleagues or the whole organization, as Can view or Can edit, and Owners can turn project sharing off, per What are projects?
- Your email domain.Team plans can verify a domain and block new personal accounts on it, but they can't claim or migrate accounts people already have. That's an Enterprise feature, per the article on claiming accounts on your domain.
- Enterprise search. After an Owner completes the initial setup, members can search across sources such as Slack, Google Drive, and SharePoint from one dedicated Project, per Use enterprise search.
Does Anthropic train on Team plan data?
No, not by default. Anthropic's privacy center says it will not use inputs or outputs from its commercial products, such as Claude for Work, to train its models by default, and the pricing page lists Team model training as "None by default." The exception is feedback. If someone rates a reply with thumbs up or down, Anthropic may use that conversation for training, stores it for up to five years, and de-links it from user IDs. Owners can switch ratings off for everyone with the Rate chats setting under Organization settings > Data and Privacy.
On individual Free, Pro, and Max plans, each person's own Model Improvement setting decides whether Anthropic can use their chats to improve Claude. With eight people on eight personal plans, you're trusting eight settings. Consultants should pair this with the client-confidentiality checklist in our AI for consultants guide.
What happens when someone leaves
When you remove a member, they lose access to the organization immediately and their seat becomes free for someone else, per the article on managing members. Colleagues lose access to that person's chats and private Projects, while Projects shared with the whole organization stay available. Removal doesn't delete their data, and re-adding the same email restores their chats and Projects, per Anthropic's article on removed users' data. Keep anything the team depends on in an organization-shared Project, not in one person's private one.
One gap to plan for: when Cowork runs on someone's computer, its conversation history stays on that device, and Anthropic's Cowork admin article says admins can't centrally manage or delete it.
When to move to Enterprise
Move to Enterprise when you pass 150 seats or need SCIM, audit logs, custom data retention, or the HIPAA-ready offering. Enterprise costs $20 per seat per month billed annually, plus usage at API rates, with a 20-seat minimum, per the pricing page. A Team organization can upgrade itself at claude.ai/upgrade and keep its chats, Projects, and members, but Anthropic's migration article says that self-serve move can't be reversed.
If a single admin feature decides your purchase, confirm it with Anthropic before you buy. The Team help article still lists domain capture and role-based permissioning for Team, while the pricing page's comparison table marks both as Enterprise-only.

Learn the Claude workflows your team will run every week
- 1,300+ non-technical professionals learning together
- Claude, Claude Cowork & Claude Code training
- The full 550+ prompt & skill Vault included with Premium
- A weekly live call to get unstuck
A 2-week rollout checklist for teams of 2 to 20
A Claude Team rollout takes an afternoon to set up and about two weeks to get right: one week to configure settings and shared Projects, and one week of real work before you fix the seat mix. Run the pilot on monthly billing, because seat reductions only take effect at renewal, then switch to annual once the seat count settles.
Week 1: set up
Day 1: create the plan on monthly billing
Sign in at claude.ai with your work email and choose Team. If you already pay for Pro or Max on that email, the upgrade happens in place by default and cancels your individual subscription with a prorated refund (App Store subscribers get a separate Team organization instead). Tick "Keep your personal account separate" to leave your existing chats and projects in a personal account. Buy Standard seats for the pilot group only.
Day 2: do the settings pass
Decide on memory, web search, Cowork and its auto-approve mode, Claude in Chrome, the connectors people may use, and the Rate chats setting. Turn on usage credits with an organization cap and a per-member cap, so nobody gets stuck mid-task and nobody surprises you with a bill.
Day 3: verify your domain
Ask whoever manages your domain's DNS to complete domain verification, then block new personal accounts on it. Team admins can't claim personal accounts people already use with their work email, but each person can move their own personal account into the Team organization, chats and projects included.
Day 4: build two or three shared Projects
Start with one for company voice and offers and one per major client or workflow. Share them with the whole organization as Can view, and give Can edit to one owner per Project so the instructions don't drift.
Day 5: invite the pilot and run a 30-minute kickoff
Cover what may go into Claude, who can export the organization's data, and whether ratings are on. Each person picks two recurring tasks to move into Claude next week.
Week 2: use and adjust
Days 6 to 9: work and keep a log
Each person notes which tasks Claude handled and every time they hit a limit. The Owner checks usage analytics midweek and answers questions in one shared thread.
Day 10: fix the seat mix and decide
Move heavy users to Premium, lower the seats you don't need (the change lands at renewal), invite the rest of the team, and switch to annual billing once the count looks stable.
The day 1 details come from Anthropic's guide to getting started with the Team plan, which says an in-place upgrade cancels your individual Pro or Max subscription automatically, and the billing FAQ, which says you get a prorated refund for the unused part. Teammates you invite who already use Claude personally with their work email end up with two accounts, a personal one and the Team one, so ask them to decide what happens to any personal subscription they pay for. If they move the personal account into your Team organization, their chats, projects, and files come along, and a Pro or Max subscription bought directly or through Google Play is canceled with a prorated refund. An App Store subscription isn't canceled, so they have to cancel it in their Apple ID settings.
For step 4, here is a starting point for the instructions of your company-wide Project:
You are the shared assistant for [company], a [type of business] with [number] people. Who we serve: [clients or customers, one line] How we write: [three adjectives]. [US or UK] spelling. Never use: [banned words or phrases] Files in this Project: - offers.md: what we sell, prices, and what's included - style-guide.md: tone, formatting, and examples we like - clients.md: client list with the details we're allowed to use Rules: - Use only facts from these files or from the person asking. If something is missing, ask before you write. - Replace client names and figures with [CLIENT] and [AMOUNT] unless the person asking includes them. - Mark anything you're unsure about with [CHECK]. - End every deliverable with a three-line summary a manager can skim.
For the wider case for Claude at work, including moving a team over from ChatGPT, see our guide to Claude for business.
Want help running this? Our Team AI Audit reviews how your team works and ends with a prioritized plan for where Claude saves time and who needs which seat, and our team workshop trains your people on their own workflows in a half or full day. Email contact@aitomationacademy.com with your team size and the work you want Claude to take off your plate.
Frequently Asked Questions
Can my Team admin read my chats?
Your organization's Primary Owner can get them through a data export. Anthropic says the Primary Owner manages your Work account and all associated data, including data exports that may contain your conversations, and only the Primary Owner can run an organization data export. Treat a Team account like a work email account and keep personal use on a personal plan.
Can two part-time people share one Team seat?
No. Anthropic's seat rules say each seat belongs to one named person, users can't share logins, and unused usage on one seat can't move to another. Reassigning a seat is meant for normal staff changes, not for rotating one seat around a group.
Can freelancers or contractors join our Team plan?
Only with an email address on one of your organization's allowed domains, because Team invitations require one, per Anthropic's article on managing members. A freelancer who only has a personal address can't be invited with it, so check your allowed domains before you count contractors in the seat plan.
Do Slack users need a Claude seat to use @Claude?
Not for work in channels. Claude Tag, the @Claude integration for Slack, is in public beta on Team and Enterprise, and by default anyone in your paired Slack workspace can tag Claude in a channel. Channel work bills by usage to your organization's usage balance under a spend limit an Owner sets, and an Owner can restrict use to people in your Claude organization. One-to-one DMs work differently: a DM from a member who has connected a Claude account runs on that person's own seat.
Is there a nonprofit discount on the Claude Team plan?
Yes. Anthropic's nonprofit page lists the Team plan at $8 per user per month for eligible nonprofits, or $3 per user per month for nonprofits based in low- or middle-income countries. Registered 501(c)(3) organizations and their international equivalents, K-12 public and private schools, and certain mission-based healthcare providers qualify. Organizations with fewer than 20 people verify their status through Anthropic's partner Goodstack, and larger ones contact Anthropic's sales team. The page doesn't name a seat type, so confirm what the nonprofit price covers before you buy.
Join the Academy
1,300+ professionals, the courses, the full Vault, and a weekly live call.
Join the AcademyGrab the playbook
The Claude Starter System — free PDF to your inbox.