When a second developer on your team starts paying for Claude Code on a personal card, someone usually asks whether the company should buy the Team plan instead. This guide covers what the Team plan costs, which seat your developers need, what an admin can control from one place, and what it still leaves on each developer's own machine.
Prices below are from Anthropic's pricing page as of November 2026. Anthropic changes them from time to time, so check there before you buy.
What the Team plan costs
The Team plan is for 2 to 150 people. Every seat includes Claude Code, and you can mix two seat types:
| Seat | Billed monthly | Billed annually | Usage |
|---|---|---|---|
| Standard | $25 a seat | $20 a seat | More than Pro |
| Premium | $125 a seat | $100 a seat | 5x a Standard seat |
Chat and Claude Code draw from the same usage pool on each seat. A developer who runs Claude Code most of the day will reach a Standard seat's limit much sooner than someone who uses Claude for writing and research.
The plan also includes up to $500 a month in API credits, pooled across the organization. Past the limits, paid plans can turn on usage credits and keep working at standard API rates.
Standard or Premium seats
You do not have to pick one for the whole team. A common split:
- Premium for the developers who run Claude Code for hours a day, especially with long sessions, subagents or the larger models
- Standard for everyone who uses Claude Code now and then, plus the people who mostly chat
If you are not sure, start a developer on Standard and look at the usage analytics after a couple of weeks. Moving one person to Premium is cheaper than putting the whole team on it.
Claude Team vs Pro
Pro is $20 a month, or $17 a month billed annually, for one person. It includes Claude Code too. What changes on Team:
| Pro | Team | |
|---|---|---|
| Seats | 1 | 2 to 150 |
| Usage | 1x | Standard is more than Pro, Premium is 5x Standard |
| Billing | Each person pays | One bill, managed by an owner |
| Single sign-on | No | Yes |
| Shared projects in Claude | No | Yes |
| Org-wide skills | No | Yes |
| Central Claude Code settings | No | Yes |
| Model training on your content | Opt-out | Off by default |
| Usage analytics | No | Yes |
For two developers, Team Standard costs a little more than two Pro plans. What you pay for is control: one bill, sign-in through your identity provider, and settings that reach every developer's Claude Code without anyone editing a file.
What an admin controls in Claude Code
This is the part of the Team plan that matters most for engineering teams, and it is easy to miss because it lives in the admin console, not in Claude Code itself.
Server-managed settings. An owner can write Claude Code settings as JSON under Organization settings, Claude Code, Managed settings on claude.ai. Every developer who signs in with the Team account gets them. Claude Code fetches them at startup and refreshes them every hour, and they rank above each developer's own settings files. That is where you put permission rules, such as denying git push --force or reads of .env files, and the hooks every session should run. Our Claude Code hooks guide has examples worth enforcing this way.
Org-wide skills. Skills can be deployed across the organization. Claude Code downloads the skills your organization provides when a developer signs in with the Team account, so a release checklist or a migration procedure is the same for everyone. The Claude Code skills guide covers how to write one.
Two cases where these settings do not arrive, both from Anthropic's docs:
- CI and API keys. A job that signs in with an API key from the Claude Console belongs to a separate Console organization, so settings from the Team admin console never reach it. Deploy a managed settings file to the machine that runs the job.
- Provider variables. If a developer exports a
CLAUDE_CODE_USE_*variable or a customANTHROPIC_BASE_URLin their shell, Claude Code skips the settings fetch.claude doctorand/statusreport it when that happens.
When you need Enterprise instead
Enterprise is $20 a seat a month billed annually, plus usage at API rates, with a 20-seat minimum. It includes everything in Team and adds:
- SCIM provisioning and role-based access with fine-grained permissions
- Audit logs and a Compliance API
- Custom data retention controls and IP allowlisting
- Domain capture, to bring personal accounts on your domain into the organization
- A HIPAA-ready offering
The deciding questions are usually about your security review. If it asks for SCIM, audit logs or custom retention, Team will not pass. If your team is small and nobody has asked, Team is the simpler buy. The pricing model also differs: Team is a flat price per seat, and Enterprise grows with how much your team uses.
What the Team plan does not share
Here is the gap that catches teams a few weeks in. The Team plan shares billing, policy, skills and chat projects. It does not share what each developer's Claude Code has learned about your codebase.
Claude Code's auto memory, the notes it writes about your project as it works, lives in ~/.claude/projects/<project>/memory/ on each developer's machine. It never leaves that machine. It does not reach a teammate, a new laptop or a cloud session. Our Claude Code memory guide explains how it loads.
So when one developer spends an afternoon working out why the staging deploy fails on a clean checkout, the fix lives in their session, and maybe in their local memory. The next developer to hit it starts from zero, and so does their Claude Code. A shared CLAUDE.md helps with facts you can write down in advance, but nobody stops mid-fix to update it.
Skills and managed settings have the same limit. They are written by an admin ahead of time. The things that cost a team the most hours are the ones nobody knew to write down until someone hit them.
This is the problem FixMyPrompt Memories is built for. When Claude Code works something out, you tell it to save the steps: the commands, how to check it worked and what not to do. On the Biz plan, those memories are shared across the company, so the next developer's Claude Code, Codex or Cursor finds the fix instead of rediscovering it. Admins decide what is shared and whether changes to a shared memory need their approval. Biz is $25 a seat a month with a 2-seat minimum and a 7-day free trial.
It works alongside the Team plan, not instead of it. Anthropic's plan gives your developers Claude Code and the controls around it. Memories keeps what their sessions figure out.
A rollout checklist
If you are moving a team onto the Team plan this week:
- Count heavy users. Put them on Premium seats and everyone else on Standard.
- Set server-managed settings with the permission rules you never want broken: no force pushes, no reading
.env, no deploys from a session. - Check CI. Any job that uses a Console API key needs its own managed settings file.
- Fix the repo's CLAUDE.md before ten people start relying on it. Paste it into the free CLAUDE.md checker to see what it costs every session and which guardrails it never mentions. In our study of 1,431 agent files from popular GitHub repos, 82% never mention destructive git commands and 67% never mention secrets.
- Decide where fixes go. Agree how one developer's hard-won fix reaches the rest of the team, whether that is a shared memory, a skill or a pull request to CLAUDE.md. If you skip this step, the answer defaults to nowhere.