Pricing & Plans
Claude Team pricing
Team is priced per seat with a minimum, and the thing you are buying is administration rather than capability. Understanding that makes the build-or-buy decision straightforward.
This page is part of the Pricing & Plans hub, which covers the whole topic end to end.
Team sits between individual subscriptions and Enterprise. Expect roughly $30 per seat per month billed monthly (less annually) with a minimum seat count in the region of five — so the real entry point is the seat minimum, not the per-seat figure.
What you get over individual Pro
| Individual Pro | Team | |
|---|---|---|
| Billing | Per person, per card | One invoice, central card |
| Admin | None | Add/remove members, central control |
| Shared work | Manual copy-paste | Shared projects and context |
| Usage visibility | Per person only | Org-level view |
| Per-seat cost | ~$20 | ~$30 |
When Team is worth the premium
- Finance is tired of expense claims. Five people expensing Pro separately costs more in admin time than the price difference.
- People join and leave. Reclaiming a seat in a console beats chasing a personal subscription.
- You want shared context. The same project instructions applied across a team is a genuine token saving — everyone stops rewriting the same preamble.
When it is not
Three people who each use Claude twice a day do not need Team. Nor do you if what you actually need is a much bigger individual allowance — that is Max, and Team seats will not solve it, because limits still apply per person rather than pooling across the org.
If procurement, SSO or a security review is involved, you are heading for Enterprise, and Team is a stopgap at best.
The cost nobody budgets for
Seat cost is the visible number; the invisible one is that team-wide habits multiply. One badly structured shared prompt template, used by eight people ten times a day, is the most expensive artifact in the organisation. This is the case where an audit pays for itself fastest, because a single fix propagates across every seat.
Start by reading what a token actually is and the playbook, then standardise the templates.