The Claude Team plan is the plan most small businesses should be looking at, and it is also the one people most often skip, usually by buying a few individual Pro seats and calling it a day. This post lays out what the Team plan costs as of late September 2026, what it adds over Pro, how to think about the seat math for a 5-to-50-person firm, and the handful of things that would push you to Enterprise. Prices below are Anthropic's published US prices and will change; the links at the bottom are the ones to check.
Claude Team plan pricing
- Standard seat: $25 per member per month billed monthly, or $20 per member per month billed annually.
- Premium seat: $125 per member per month billed monthly, or $100 billed annually.
- Minimum two members, up to 150 seats. Anthropic is explicit that the plan is “not intended for individual use.”
- Business email required. The account creator needs a company domain; public addresses such as Gmail or Yahoo aren't allowed, and members must be on one of the organization's approved domains.
The difference between the two seat types is usage. A standard seat carries “1.25x the Pro plan's per-session usage allowance”; a premium seat carries 6.25x, or five times a standard seat. You can mix them, which is the whole trick: most people on a standard seat, and a premium seat for the one or two who live in Claude Code or run Cowork tasks all day.
Claude Team vs Pro: the seat math
Pro is $20 a month billed monthly, or $17 a month on an annual plan. So for an eight-person shop:
- Eight Pro seats, monthly: $160 a month.
- Eight Team standard seats, monthly: $200 a month.
- Eight Team standard seats, annual: $160 a month.
On an annual commitment, Team costs the same as monthly Pro and gives you 25 percent more usage per person plus everything in the next section. The honest case for staying on Pro is a team of two or three people who don't share work and don't need anyone to administer anything. Past that, the administrative features stop being nice-to-have.
What the Team plan adds
- Admin tools and billing in one place. One invoice, seat management, and the ability to remove access the day someone leaves.
- Identity controls. SSO, just-in-time provisioning, and role-based permissions. For a small firm, the practical value is that access follows your email system instead of living in eight separate personal accounts.
- Spend controls. Spending caps at the organization and individual level, so a heavy month for one person doesn't become a surprise for the business.
- Workplace connectors and enterprise search across Google Drive, Gmail, GitHub, Microsoft 365, and Slack, with Owner-level control over which connectors are on and what actions they may take. We wrote a separate guide to rolling out connectors on a Team plan.
- Claude Code and Cowork, with organization-level settings for Cowork's cloud sessions and approval modes. If you are weighing Cowork specifically, this walkthrough covers what to hand it first.
- A 200k context window, which in plain terms means Claude can hold a very long document, or a folder of them, in view at once.
Claude Team vs Enterprise
Enterprise is priced as a seat price plus usage billed at API rates, with a $20-per-seat-per-month minimum and annual billing required. On top of everything in Team, it adds spend limits with role-based access, SCIM provisioning, audit logs, a compliance API, custom data retention, a HIPAA option, and a security product in beta.
Read that list as a checklist. A small firm needs Enterprise when at least one of these is true:
- You handle health information and need the HIPAA option.
- A client contract or your own policy requires audit logs or custom retention periods.
- Your IT provider insists on SCIM for provisioning.
- You are past 150 seats.
If none of those apply, Team is the right plan, and the money is better spent on the rollout than on the tier.
Setting it up in the first week
Sign up at claude.ai with a work email and choose Team. Invite the first few members, not everyone. Turn on the two or three connectors the team already uses, set write actions to require approval, and pick one shared project that everyone can see so the first week has a place to happen. The plan is the easy part; what people do in the first month is what decides whether the seats get used in month six. That rollout, from the permissions review to the 30-day check-in, is the work Cedar & Loam does with agencies and small firms. Proudly based in Kansas City. Say hello.
Common questions
Can a small team just share one Pro login instead? Seats are per person. A shared login gives you shared chat history and no way to remove one person's access when they leave, which are the two problems the Team plan exists to solve.
Who should get a premium seat? Start everyone on standard. The person who hits the usage ceiling twice in a month, usually whoever lives in Claude Code or runs Cowork tasks all day, moves to premium. A premium seat carries five times the usage of a standard one, so one upgrade typically covers the heaviest user with room to spare.
Do we lose anything moving from Pro to Team? You keep your work, but the move is one-way: content moved into the organization can't be moved back to a personal account, and public projects become private after the upgrade. You would need to decide what migrates before you click.
Sources
- What is the Team plan?, Anthropic Help Center
- Get started with the Team plan, Anthropic Help Center
- Claude pricing, claude.com