This is about adopting Claude for HR’s own work — comp models, policies, JDs, employee comms — not a company-wide IT rollout. For that, Team is the answer: it’s self-serve, it’s live the same day, it covers 5 to 150 seats, and it already includes the things people assume need Enterprise — SSO, central admin, spend caps, per-member usage limits, and no training on your content by default. Enterprise is the company-wide, compliance-driven case, and that’s IT’s decision, not the HR team’s.
For an HR team adopting Claude for its own work, Team is the right plan. Here's what you get and what the alternative is for.
Standard seats around $20/month (annual); Premium around $100/month for heavier users. Usage is bundled into the seat, so the bill is predictable and one heavy user can't drain the rest.
Self-serve: you can buy it and have the team working the same day — no sales call, no contract, no procurement cycle. Covers 5 to 150 seats. Includes Claude Code and Cowork, SSO and domain capture, central billing and admin, org and user spend caps, connectors, and no training on your content by default and contractually.
Typically around $20/seat (annual) for access, with usage billed separately at API rates (Sonnet 4.6 roughly $3 / $15 per million tokens in/out) — so the bill scales with use and needs spend governance. (Confirm your quote.)
Adds SCIM, audit logs, the Compliance API, custom retention, IP allowlisting, fine-grained roles, and HIPAA-readiness. Sales-assisted. This is the company-wide deployment tier — an IT and leadership decision, not something the HR team buys to do its own work.
The capabilities people assume are Enterprise-only — SSO, central admin, spend caps, per-member limits, no-training-by-default — are all on Team. That's why the HR team rarely needs to wait on a company-wide contract to get started. (Two edge cases sit outside this: a single user or a couple of people, where Pro covers it, and genuine plan-side PHI, where the API on Bedrock is usually cleaner — covered in section 2.)
Enterprise exists for a short list of company-wide controls. Each one is an IT, security, or leadership requirement — not something the HR team decides on its own. If none of these is in play for the HR team's work, Team is the answer.
| Enterprise trigger | What it means — and whose call it is |
|---|---|
| SCIM, audit logs, or the Compliance API | Automated provisioning and governance evidence — a security or compliance team's requirement, set at the company level. |
| Data residency mandate | Residency written into company policy or a customer contract. Legal and IT own this, not HR. |
| Genuine plan-side PHI | This is the one case Team can't cover: Team is not BAA-covered — only the API and Enterprise are. Most HR data isn't HIPAA-PHI (see the data-classification framework); if you genuinely have plan-side PHI, it's HIPAA-ready Enterprise or the API on Bedrock. A compliance and IT call. |
| An org-wide rollout past 150 seats | Team caps at 150 seats. A company-wide deployment to the whole org is an IT-led Enterprise project, distinct from giving the HR team its own seats. |
| IP allowlisting or fine-grained roles | Network-level access lockdown, or role-based permissions beyond Team's basic set — an IT security requirement. |
| Procurement terms | A negotiated MSA, custom DPA, PO billing, or volume commitment — handled by procurement at larger orgs. |
If your company is already on Enterprise for everyone, the HR team simply works inside it — nothing to buy. If it isn't, and none of the rows above applies to HR's own work, the HR team can start on Team today and let IT lead the company-wide decision on its own timeline. Moving from Team to Enterprise later is a new, sales-assisted contract on a different billing model, so it's planned, not toggled (confirm migration specifics with Anthropic).
Most of this list is identical. The highlighted rows are the only ones that push a company to Enterprise.
| Team | Enterprise | |
|---|---|---|
| Billing | Bundled per seat | Seat + metered usage |
| Predictable bill | Yes — bundled, capped per user | Varies with use |
| Seats | 5–150 | Org-wide |
| Setup | Self-serve, live the same day | Sales-assisted, contract cycle |
| SSO + domain capture | Yes | Yes |
| Central admin + spend caps (org/user) | Yes | Yes |
| Per-member usage limits | Yes — bundled per seat | Yes — spend limits (org/group/user) |
| No training on your content (by default) | Yes — contractual | Yes |
| SCIM, audit logs, Compliance API | — | Yes |
| HIPAA-ready, custom retention | — | Yes |
| Roles & permissions | Basic | Fine-grained (RBAC) |
The billing model is the real difference — and the thing Finance will ask about.
Team is the predictable one: seats times price, usage bundled per seat with per-user caps, so one heavy user can't drain the pool. An HR team of thirty on all-Standard seats runs about $7,200 a year on annual billing; add a few Premium seats for the Claude Code users and it's closer to $10K, and monthly billing costs more. (Exceed the bundle and you add usage credits at API rates.) Enterprise decouples the seat from usage — the seat is around $20, and everything the org runs is billed at API rates on top, which is why a company-wide rollout needs spend limits and a read on who the heavy users are. Those dollar figures are a 30-seat illustration of Anthropic’s plan prices — the cost of the tool itself, not my engagement fee, which is separate and published on the engagements page. An org-wide, thousand-seat rollout is an Enterprise conversation IT owns from the start, where usage and spend governance, not seat count, drive the math.
Waiting too long: assuming HR can't start until the company signs an Enterprise contract — sitting through a sales cycle Team would have skipped, when Team already covers SSO, admin, spend caps, and no-training-by-default. Going past the line: putting genuine plan-side PHI through Team, which isn't BAA-covered, or ignoring a real audit-log or residency mandate. The list in section 2 is the whole test — and most of it is a company decision, not the HR team's.
An HR team adopting Claude for comp models, policies, JDs, and employee comms doesn't need to wait on a company-wide contract. Team is the default: predictable cost, live the same day, and it already includes Claude Code, Cowork, SSO and domain capture, central admin, spend caps, per-member limits, connectors, and no-training-on-content by default. Enterprise is the company-wide, compliance-driven tier — SCIM, audit logs, HIPAA, residency, an org-wide rollout — and that's an IT and leadership decision. The one case the HR team can't cover on Team is genuine plan-side PHI, because Team isn't BAA-covered; that goes to HIPAA-ready Enterprise or the API on Bedrock, as a compliance call.
Default to Team for the HR team’s work. Escalate to IT only when something on the section-2 list is genuinely in play.
The Sprint covers the rest — classifying your data, choosing and costing the plan, and giving HR the materials to bring Legal, Finance, and IT along.
This is my AI-for-HR practice — one of three I run, alongside Total Rewards and HR Systems. They’re separate practices; you can hire me for any one of them on its own.
Start a conversation →No cost to start the conversation.
AI for HR · Start here / 1 Data / 2 Plan / 3 Cost / 4 Rules
Plan names, prices, seat limits, and features change often — these were verified June 2026. Confirm current details at claude.com/pricing and support.claude.com before you commit. General guidance, not procurement or legal advice.