Claude Team Premium vs Standard: which seat does each person need?

What each seat costs

Claude Team lets you mix two seat types in one plan. Anthropic describes Standard as “base features, usage limits, and Claude Code access” and Premium as everything in Standard “plus higher usage limits.” Limits apply per member, so one person running out never slows anyone else down.

Per seat per month in USD. List prices as of October 2026, from claude.com/pricing.

Anthropic’s pricing page doesn’t put a number on “higher.” One independent guide puts Premium at about five times Standard’s allowance per session, with its own weekly cap. Treat that as an orientation, not a promise.

Who needs Premium, and who doesn’t

At five times the price, Premium only pays off for someone who would otherwise be stopped by the Standard limit. A rule that holds up:

• Premium: people who hit the Standard weekly limit in most weeks of a month, usually because they work in Claude Code or run long sessions all day.
• Standard: people who use Claude daily for writing, research and questions but rarely see a limit message.
• No seat: people who haven’t opened Claude in a month. Their seat isn’t mis-tiered, it’s idle; see how to find unused ChatGPT and Claude seats.

The billing rules make Standard the safe default. An upgrade is prorated and charged immediately, so moving someone up on the day they need it costs only the days left in the cycle. A downgrade or seat reduction waits until your next renewal, which on annual plans is the annual renewal date, and there is no prorated refund. Starting someone on Standard costs nothing extra; starting them on Premium can lock in $80 a month until renewal.

What the admin console shows, and what it doesn’t

Owners and Primary Owners find usage analytics under Settings, then Analytics.

Request and token counts help you rank people, but they don’t tell you who would have fit on Standard, and Anthropic’s analytics documentation describes no per-member view of the limit. The place a limit does show up is each member’s own usage page.

How to check it by hand

1. Open Settings, then Analytics, and compare active members with assigned seats. Any gap is idle seats: cut those first.
2. Export the spend report for the last 30 days and rank your Premium members by requests. Standard candidates sit at the bottom.
3. Ask each Premium member to open their own usage page (Settings, then Usage) at the end of each week for four weeks and note whether they hit the weekly limit. The page shows their session and weekly progress and when each limit resets.
4. For everyone who never hit it, open Organization settings, then Members, and switch their Tier to Standard. The change is scheduled for your next renewal, and only one scheduled seat change can be pending at a time, so make all the switches in one go, well before the renewal date.

Then repeat it before every renewal. People change roles, and the person who needed Premium in spring may not need it in autumn.

How SeatLeak automates it

SeatLeak runs the four-week check all the time. A browser extension, pushed once from your Google Workspace or Microsoft 365 admin console, reads the usage page each member already sees, never prompts or content, and compares each person’s weekly use with what a Standard seat allows. Anyone who stays under the Standard limit every week for a month shows up with the saving and the date the downgrade lands. Standard members who keep hitting the limit show up too, as upgrade candidates.

SeatLeak opens to teams in the order they sign up, starting this winter. Until then, the calculator on our home page estimates what your team is likely leaking across all its tools.