Claude Team Plan: Pricing, Features, and Who It's For

The Claude Team plan is Anthropic's collaboration tier for groups of five or more, priced from $20 per seat per month billed annually. It adds shared projects, central billing, SSO, and role-based admin controls, plus higher usage than Pro. Standard seats run $20–$25; Premium seats cost $100–$125 for roughly six times the usage.

Seat minimums, seat pricing, and Team data-training terms verified 31 July 2026 against Anthropic's Team plan documentation.

We manage this site's content pipeline across several Claude subscriptions, so we've set up teams, juggled seats, and watched exactly where Team earns its keep over a stack of individual Pro accounts. Below: the real per-seat pricing, what Team adds over Pro, Project sharing, when to upgrade, and how Team differs from Enterprise. We have walked this exact path in our own terminal, so the guidance here is grounded in doing rather than describing.

What the Claude Team plan is

It is Anthropic's tier for organisations rather than individuals: five seats minimum, up to 150, with shared administration, pooled billing, and a contractual guarantee that team conversations are not used to train Anthropic's models.

The Claude Team plan is the tier Anthropic sells to organizations rather than individuals. Where Pro and Max are single-user subscriptions, Team wraps multiple people under one account with shared administration, pooled billing, and collaboration features that solo plans don't include. It slots between the consumer tiers (Free, Pro, Max) and Enterprise on Anthropic's ladder. Some searchers call it the Claude business plan; Anthropic's official name is simply Team.

The defining constraint is the seat minimum. A Claude Team plan requires at least five members and scales up to 150 seats before you have to move to Enterprise. Every seat gets the full claude.ai experience — Claude Opus 5, Projects, Cowork, Claude Code, web search, and file uploads — plus one trust guarantee that matters for any organization: Team and Enterprise conversations are not used to train Anthropic's models by default. Anthropic spells out the specifics in its Team plan help documentation.

Claude Team pricing: Standard vs Premium seats

Standard seats cost $25 a month, or $20 billed annually. Premium seats cost $125 a month, or $100 annually, for roughly 6.25 times the session usage. You can mix both seat types on one invoice.

Claude team pricing splits into two seat types, and getting the distinction right is where most of the Claude Team plan cost decision lives. Standard seats cover ordinary daily use; Premium seats exist for power users who lean on Claude Code and long Opus sessions all day.

Standard seats cost $25 per seat per month billed monthly, dropping to $20 per seat when you commit annually. Premium seats are $125 per seat monthly, or $100 per seat billed annually. The five-seat minimum applies either way, so the entry point for a Team plan is roughly $100 a month — five Standard seats at the annual rate.

You can mix seat types on one plan — assign Premium to the two engineers running Claude Code all day and Standard to everyone else — and Anthropic bills the blend on a single invoice. Usage on both seat types resets on a rolling five-hour session window, with a weekly cap layered on top; when a seat hits its ceiling, you can buy extra usage credits rather than upgrading the whole plan. The full, location-specific rates live on Anthropic's official pricing page.

The seat-mix decision is the one we actually weighed hardest, because our own usage is lopsided: whoever is driving Claude Code against this repo all day burns through a Standard seat's session window fast, while everyone drafting or reviewing barely dents theirs. Assigning a single Premium seat to the heavy Claude Code user and Standard seats to the rest matched our real pattern far better than paying up across the board. The habit we would pass on is to watch a couple of weeks of actual session limits before buying, rather than guessing in advance who the power users are.

What Claude Team adds over Pro

A Standard seat costs the same $20 as Pro but adds central billing, an admin console with roles, single sign-on, shared Projects, and about 1.25 times the per-session usage. Premium seats push that to roughly 6.25 times.

On a per-person basis, a Standard Team seat costs the same as Claude Pro — $20 a month billed annually — so the honest question is what the extra structure buys. The answer is everything that turns Claude for teams into a shared tool rather than a pile of separate logins.

Four things stand out. Central billing replaces a dozen personal credit cards with one invoice and one renewal date — the reason finance teams push groups onto Team in the first place. Admin controls let an owner add or remove members, assign roles, reset access, and see who is using what, none of which is possible when everyone runs a private Pro account. SSO ties Claude to your existing identity provider so access follows employment automatically. And more usage — Standard seats get about 1.25x a Pro plan per session — gives everyone a little more runway before limits bite. Premium seats push that to roughly 6.25x for the people who need it.

Project sharing and team collaboration

Shared Projects are the usual reason to upgrade. One person builds a workspace around your brand guidelines, code conventions, or support playbook, and every member inherits that context instead of re-explaining it in each chat.

The feature people upgrade for most is shared Projects. A Claude Project bundles files, custom instructions, and conversation history into one persistent workspace, and a Team plan shares those Projects across the whole team. One person builds a Project around your brand guidelines, codebase conventions, or support playbook, and everyone inherits the same context instead of re-explaining it in every chat.

That shared context is what makes Team more than a bulk discount. A support team works from one shared knowledge Project; an engineering team points Claude Code at the same conventions; a marketing team drafts against a single house-style Project. Members can also see and build on shared work rather than each reinventing the same prompts privately — the practical difference between five people using Claude and a team using Claude together. The flip side of that central control is that your owner decides what each seat can reach, so if a colleague reports that the knowledge bases feature is not enabled, the admin console is the first place to look.

When a team should upgrade to Team

Upgrade when coordinating individual accounts becomes its own job — separate receipts, orphaned access after someone leaves, the same context pasted repeatedly. A single heavy solo user is still better served by Max.

The trigger is rarely a single feature; it's the moment coordinating individual accounts becomes its own job. If you're reimbursing five people's separate $20 receipts, chasing who still has access after someone leaves, or copy-pasting the same context into everyone's chats, the Claude Team plan pays for itself in saved overhead alone — at the same $20-per-seat annual rate as Pro.

The one case where Team is the wrong answer is a single power user with no one to collaborate with. If it's just you burning through usage, Max is leaner — you get the higher ceiling without paying for admin infrastructure you'll never open. Team earns its price the moment a second and third person need in.

Claude Team vs Enterprise: where the line is

Team is self-serve, per-seat, and capped at 150 people. Enterprise is custom-quoted and adds SCIM provisioning, advanced audit logs, usage pooled across the organisation, and dedicated support. Headcount, provisioning, and compliance decide it.

Team and Enterprise share the collaboration DNA — shared Projects, admin controls, no training on your data — but they're built for different scales. Team is self-serve, month-to-month or annual, and tops out at 150 seats. Enterprise is custom-quoted and adds the governance features large organizations require.

The Claude Team vs Enterprise decision usually comes down to three things: headcount over 150, provisioning at scale (SCIM to auto-add and remove users from your directory), and compliance evidence (audit logs, expanded data controls, dedicated support). If none of those apply, Team almost certainly covers you. Cross any of them and Enterprise is the tier built for it — you can start on Team and talk to Anthropic's sales team when you outgrow it.

How to set up Claude Team

Sign up at claude.ai/login with a work email and pick Team, or upgrade an existing account at claude.ai/upgrade. Choose your seat mix, set at least five seats, pick annual billing for the lower rate, then invite members.

Getting started takes a few minutes. If you're new, go to claude.ai/login, sign up with a work email, and choose Team when prompted; if you already have a personal account, visit claude.ai/upgrade to create your Team and invite members. Pick Standard or Premium seats (or a mix), set your seat count at five or above, and choose monthly or annual billing — annual is the cheaper Claude team plan cost at $20 per Standard seat.

From the admin console you then invite people by email, assign each a role, and manage seats as the team grows or shrinks. For the full picture of how Team sits alongside every other plan and the API, see our complete Claude pricing breakdown.

The quick version:

• Standard seats cost $25/month, or $20 billed annually
• Premium seats cost $125/month, or $100 billed annually
• Team adds shared projects, an admin console, and SSO
• Upgrade at 5+ people; move to Enterprise for large orgs

For example, a 6-person startup on Team Standard pays about $120 a month on one invoice — 5 seats at the $20 annual rate — with shared projects every member can open.

Claude pricing at a glance

Claude is free to start, $20 a month on Pro, and from $100 a month on Max, with API access billed per token. Team layers per-seat pricing and shared administration on top of that.

For the full breakdown of every plan, see our how much Claude costs guide.

Paying for a full year up front trims the per-seat cost — our Claude annual plan guide covers the yearly rate, the savings math, and how switching billing works mid-cycle.

Still torn between paying for a heavy solo plan and setting up a team? Our comparison of Claude Max vs the Team plan walks through when one all-day power user is better served by Max and when a group is better off on Team.