For if LIFE turns on a Team workspace. What a Team seat buys vs an individual Pro/Max plan — verified against the live pricing docs.
The headline: Team seats are not a usage upgrade. A $200 Max (20×) dwarfs a $100 Team Premium seat (6.25×). Team is a governance & collaboration upgrade, not capacity. (Team usage is quoted per-session/weekly, Max overall — units differ, but the gap is real.)
| Pro | Max | Team · Standard | Team · Premium | |
|---|---|---|---|---|
| Price | $20/mo $17 annual | from $100/mo (5×) $200/mo (20×) | $25/seat/mo $20 annual | $125/seat/mo $100 annual |
| Personal usage | baseline | 5× or 20× Pro | 1.25× Pro / session | 6.25× Pro / session |
| Claude Code | Yes | Yes | Yes | Yes |
| Claude Tag (@Claude in Slack) | No · uses Claude Code in Slack | No · same | Yes | Yes |
| Admin / org controls | — | — | SSO, RBAC, audit logs, SCIM, central billing, spend controls, analytics | same |
| Collaboration | — | — | shared projects, enterprise search (Slack / M365 / Drive / Gmail / GitHub) | same |
| Usage beyond included | hard cap | hard cap | usage credits → API rates | same |
| Minimum seats | — | — | 5 | 5 (mix & match) |
Enterprise (self-serve): $20/seat for access + all usage at API rates, plus compliance — Compliance API, custom retention, IP allowlist, HIPAA-ready. Sales-assisted = custom terms.
A $100 Premium seat ≈ 6.25× Pro; a $25 Standard seat barely beats Pro (1.25×). A $200 Max gives 20×. Nobody goes Team for more coding capacity — they go for the org layer.
Claude Tag (org @Claude in Slack) + the whole admin layer: central billing, SSO, audit logs, SCIM, spend controls, usage analytics, shared projects, enterprise search across the team's Slack / Drive / Gmail / GitHub. Org control + shared context — that's the reason, not raw usage.
Individual Pro/Max = flat subscription with a hard rate-limit cap (no surprise bill). Team = per-seat subscription with included usage, then usage credits at API rates once exhausted (Enterprise self-serve is API-rate from the start). The org takes on consumption risk — hence the spend controls.
claude -p agents run on the individual's Claude Code subscription. A Team seat doesn't change or replace them, and cloud Claude-in-Slack still can't see local working trees.