Claude Team arrived at $30 per seat with a five-seat minimum, turning individual Claude use into something a sales team can standardise on.
Most sales teams' Claude usage is a dozen personal accounts with no shared context and no admin oversight. A Team tier is what converts that from a collection of individual habits into something a manager can actually standardise, audit and pay for on one invoice.
A seat-based plan means you buy per person, with a minimum headcount — here, five. Below that you stay on individual Pro subscriptions.
The substantive difference over Pro is shared Projects: a workspace where the account context, custom instructions and prior conversations are visible to the team rather than trapped in one rep's history. Team seats also carry higher usage limits than Pro.
Projects are the same feature Anthropic shipped to Pro users in June 2024, but on Team they are shareable — the difference is who else can open them.
The short version: the same Claude, bought per seat, with shared workspaces so context stops living in one person's private chat history.
Anthropic launched the Claude Team plan on 1 May 2024, alongside an iOS app for Claude.
Price: $30 per user per month billed monthly, or $25 per user per month billed annually.
Seat minimum: Five users.
Included: Higher per-user usage than Pro, access to the full Claude model range, and Projects for organising chats, documents and files into shared contexts.
Availability: Select supported locations — the announcement does not enumerate them.
Admin controls: Not detailed in the announcement; SSO and role-based access arrived later with the Enterprise tier.
What it doesn't do: Team is not the Enterprise tier. It does not include single sign-on, role-based access control, audit logs or the 500,000-token context window — those came four months later with Claude for Enterprise. If your security team requires SSO, this plan will not clear review.
SDR — Higher usage limits are the practical gain — volume drafting is exactly the workload that hits Pro's ceiling mid-afternoon.
AE — Shared Projects matter more than the limits. An account context that a colleague can pick up is the difference between AI-assisted work surviving a territory change and vanishing with the rep.
Manager — This is the first version you can standardise on. A shared Project is an enforceable working standard in a way that a circulated prompt document never was, because nobody opens the document twice.
RevOps — Five-seat minimum and per-seat billing are the planning facts. Note that individual reps already paying for Pro personally will need migrating, and that consolidation is the actual rollout work.
Before buying seats, find out whether shared context actually changes the output. Build one account brief the whole team could work from.
Two minutes, once a week. What changed in AI, and what to run because of it.