Work out what a Claude Team plan changes for a small department
Two people in your department pay for Claude themselves, one expenses it, and the rest keep asking to borrow a login. Somebody has to write the page that turns this into a proper arrangement, and the decision that matters is how many of which kind of seat.
What you'll make
a one-page proposal with four headings: what the Team plan changes, the proposed seat mix, what it doesn’t solve, and what to confirm before buying.
What you'll need
a headcount with one or two recurring tasks per person, Anthropic’s current Team plan pages and any AI chat to draft the note. You don’t need a Team plan to prepare it. Weighing ChatGPT instead? The ChatGPT Business version of this guide uses the same shape.
Example result.
| Option | Seats | We’d know it was wrong if… |
|---|---|---|
| A | Nine Standard | The two heavy users hit their weekly limit repeatedly in month one |
| B | Seven Standard, two Premium | The Premium seats are no better used than the Standard ones |
| C | Nine Premium | Unlikely first: it pays the higher rate for seven occasional users |
1. Start with the department’s work
List who needs access and one or two recurring tasks for each, using roles rather than personal details. Separate someone who drafts occasionally from someone who repeatedly runs out of allowance. Then name what’s missing from the present arrangement: central billing, managed access, collaboration or capacity. If none is a real gap, write that down. A proposal is allowed to recommend waiting.
Why this works: the workload decides the seat mix. A list of every feature is longer, but it won’t tell you whether the ninth person needs a seat.
What you should see: a short table of roles, tasks and how often each runs into limits, plus one honest sentence about how the department works today.
2. Record the current offer from Anthropic’s pages
Copy the relevant passages from the Team plan overview into your notes. It lists:
| Seat | Billed monthly | Billed annually |
|---|---|---|
| Standard | USD 25 per member | USD 20 per member per month |
| Premium | USD 125 per member | USD 100 per member per month |
These are US prices excluding tax; pricing, currency and tax vary by region. A Team plan needs at least two members and supports up to 150 seats. Usage limits are per member, not pooled, so one heavy user can’t exhaust anyone else’s allowance. Limits reset weekly at a fixed time for the account, visible in Settings › Usage, and admins can prepay for usage credits so people keep working past them.
Don’t convert the prices to pounds. Put the published figures in the note, say they are US list prices, and send someone to the upgrade page for your location. A confident pound figure is the thing finance will test first.
Why this works: seat types on this plan are fairly recent, and a model’s remembered version of “Claude Team” may not include Premium seats at all. Pasted source text keeps the facts current.
What you should see: a block of quoted passages with their links, ready to paste in step 3.
3. Draft the proposal from your notes
Paste your workload notes and the source passages into a new chat.
Draft a one-page internal proposal for a Claude Team plan for a
department of [number] people.
Use four headings: "What this changes", "Proposed seat mix", "What
this does not solve" and "To confirm before we buy".
Under "Proposed seat mix", give three options: all Standard; mostly
Standard with a few Premium; and a note on why all Premium is unlikely
to be right first. For each option, state what we would have to
observe in the first month to know we chose wrong.
Use only the pasted source text for features, seat types, limits and
prices. Keep prices in the published currency and say that pricing,
currency and tax vary by region. Do not convert to pounds. Do not
estimate time saved or return on investment. Do not claim the plan
makes any use of data compliant. Mark anything unverified "to confirm".
[Paste the source passages and how the department works today.][number] is your headcount; the last line is where your step 1 and step 2 notes go.
Why this works: asking what would prove each option wrong turns a recommendation into something you can review. Forbidding savings estimates matters because the first invented number in a proposal becomes the only thing anyone discusses.
What you should see: four short sections, three options with a failure test each, and a “To confirm” list.
4. Read “What this does not solve” first
If that section is thin, the draft is a brochure. The Team plan buys administration, identity controls, connectors and per-member limits. It doesn’t decide what your department may put into Claude, train anybody or change who may see which document. Then check every number against your pasted source.
Why this works: the gaps are what a sceptical reader will ask about, and the brochure version leaves them out.
What you should see: a section that names who decides what data may be used, who owns the workspace, and what training people need.
Check the result
- Every price appears in the pasted source, in the same currency, with the regional note attached.
- Each seat option has a test that would show it was wrong.
- “What this does not solve” covers data, training and permissions.
- Nothing claims savings, compliance or a connector that hasn’t been agreed.
The usual failure: Premium seats go to the people who asked loudest, with no evidence about their usage, or a price arrives converted into pounds. Spot it by asking “where did that come from?” for each Premium seat and each figure.
Remove [the unsupported figure or Premium allocation]. It is not in
the pasted source or our usage notes. Restore the published figure and
currency, or show the seat as an open question with the usage evidence
we would need. List every other number not supported by the pasted text.[the unsupported figure or Premium allocation] is the line you found.
Worked example: nine people and a shared login
Fictional example. The line pasted in alongside the source text:
Nine people. Two personal Pro subscriptions, one expensed, the rest no
access. Two heavy daily users (long document work), seven occasional.
The two heavy users are the most vocal about wanting Premium. One
shared login currently in use, which we want to stop.The first draft recommends “seven Standard seats and two Premium seats (about £190 a month) for the two senior staff who need it most.” Both halves fail the check: the pound figure isn’t in the source, and nobody has measured whether the two hit their limits.
After the repair prompt, the seat-mix section matches the options at the top of this page, and To confirm before we buy reads: “Published prices are US list and exclude tax; confirm the local figure on the upgrade page. Decide who holds the owner role and who covers absence. Decide whether to enable usage credits, and with what cap, before anyone meets the limit on a deadline.”
What mattered:
- The shared login is the real problem. Individual seats with single sign-on mean access follows employment, not a password in a message thread.
- Option B is a guess until month one. “Give the busy people the expensive seats” sounds right and is about usage nobody has measured. Seats can be moved between Standard and Premium, which turns the purchase into something reversible.
- No pound figure. The note quotes US list prices and sends finance to the local offer.
Task kit for this job: Download (ZIP) · Reusable instructions
Go deeper
Write the connector paragraph before IT writes it for you
The Team plan lists connectors for Google Drive, Gmail, Google Calendar, GitHub, Microsoft 365 and Slack. That’s the part that makes security teams sit up, reasonably. Get ahead of it with a short, sober paragraph.
Draft one short paragraph for our IT and information security contacts
about the workplace connectors named in the pasted source. State which
services the source names and what it says about permissions. Ask two
questions: which connectors they would want enabled, and who agrees
that. No reassurance and no security claims beyond the source. If the
source does not establish something, write "not established in the
documentation we have read".That last phrase tells a reviewer where to start and stops you implying a guarantee you can’t support.
Plan what happens at the limit, before someone hits it
People find usage limits at the worst possible moment. Two facts carry the note: limits reset weekly at a fixed time shown in Settings › Usage, and admins can enable usage credits so members can continue.
From the pasted source on usage limits and usage credits, draft a
five-line internal note telling colleagues what happens when they reach
a limit, where to see their reset time, and what to do next. Use only
what the source states and leave out allowance figures.Admins and owners change a member’s seat type in Organization settings › Members with the Tier dropdown. Upgrades are charged straight away; moving someone back to Standard takes effect at renewal.
Know when the answer is Enterprise, not Team
Team supports up to 150 seats, and Anthropic points larger organisations to Enterprise. Seat count is rarely the real trigger, though. Procurement terms, retention commitments and how much control your security team wants usually move the decision. Ask Claude to list the conditions under which Team stops being the right answer, using only the pasted source and writing “would need to ask” wherever the source is silent. Check privacy separately: Anthropic’s training policy covers model training, not your employer’s rules on retention or sharing.