As of 18 October 2026, Anthropic's pricing page lists Claude Team at $20 per standard seat per month billed annually or $25 billed monthly, and $100 or $125 for a premium seat, for two to 150 seats. Usage limits apply. What the provider spends internally is not public, so we do not guess.
Fetched from the Claude pricing page on 18 October 2026. Prices exclude tax. Check the live page before you buy, because plans change.
What are the published prices?
The Team plan on the page is described for teams of 2 to 150. The listed prices:
- Standard seat: $20 per seat per month billed annually, $25 billed monthly.
- Premium seat: $100 per seat per month billed annually, $125 billed monthly.
- You can mix seat types.
The page states a minimum of two seats and a maximum of 150.
What limits does the page state?
The page does not publish token counts for the Team plan. It uses relative language, quoted from the page:
- Standard seat: "more usage than Pro."
- Premium seat: "5x more usage than standard seats."
- Extra usage is available.
- Priority access at high traffic times is listed as included.
- "Up to $500 per month in pooled API credits" is listed, with a footnote marker whose conditions we could not read from the page text.
- The page says usage limits apply.
Because limits are relative, you cannot compute a per-task cost from the page alone. If you need a number, test with your team for a few weeks and watch where people hit limits.
What features come with a seat?
The page lists, among others, Claude Code and Claude Cowork, enterprise search across your organization, central billing and administration, single sign-on, admin controls for connectors, enterprise deployment for the desktop app, and no model training on your content by default. Check the page for the full and current list, since it names several products and some are marked beta.
What do you pay for, and what do you not see?
You pay for seats, and for extra usage if you choose it. Those are the lines on the page.
You do not see the provider's own costs, such as compute, staff or contracts. They are not published, and any number you read elsewhere is an estimate. A price page tells you what you owe, not what delivery costs the vendor, so we make no claim about the second.
Treat the pooled API credits as a separate allowance from seat usage, and ask the vendor how it is shared and what happens at the cap.
How should a team decide on seat types?
Split by usage pattern, not job title. A person who works in the tool most of the day and hits limits is a candidate for a premium seat. A person who uses it a few times a week likely fits a standard seat. Start everyone on standard, track who hits limits, then move those people.
Billing period matters. The page shows annual billing at a lower monthly rate than monthly billing. Annual means a commitment, so check cancellation terms in the agreement.
What to do
- Open the live pricing page and confirm each number above.
- Count seats by usage pattern, not by headcount.
- Start with standard seats for most people and a few premium seats for heavy users.
- Log limit hits for a month and adjust.
- Ask the vendor how pooled API credits are shared and capped.
- Check data handling and admin controls against your security policy.
- Compare annual and monthly cost for your seat count before committing.
Quick check
Does the Team plan publish a token allowance?
Not on the page we read. It describes usage in relative terms and says limits apply. Measure with a pilot if you need numbers.
Can I mix standard and premium seats?
The page says you can mix and match seat types.
Sources
- Claude pricing page, fetched 18 October 2026
Last reviewed: 18 October 2026.
