top of page
Bell Consulting Solutions

2 Words Separate Claude Pro and Claude Team

Writer: Branden Bell
Branden Bell
Sep 4
6 min read

Pricing update, September 10, 2026: expert working sessions are $250 for 60 minutes. Build in a Day starts at $1,500; 30-Day Implementation starts at $6,000. Earlier package inclusions, credits, and hourly support terms below are historical. See current services and pricing for scope and terms.

Open Anthropic's pricing page, scroll past the seat prices, and find the comparison row labelled Model training. For Free, Pro, Max 5x and Max 20x it reads "Opt-out." For Team and both Enterprise tiers it reads "None by default."


Every other row in that comparison is capacity or admin plumbing. That one is about whether your company's work sits in a pile somebody has to go turn off. If I were putting a business on Claude it's the first row I'd read, and it's about two thirds of the way down a page most people close after looking at the price.


The Row That Isn't About Usage


Opt-out means the setting exists and somebody has to find it, one account at a time. None by default means the posture starts where you'd want it and nobody has to remember anything. Four people on four Pro subscriptions is four separate settings screens, and I've never once seen a small company audit those.


Anthropic's small business page answers the question in one line: "No. We don't train our models on your business data." That's true, and the same page's cost answer, a few questions further down, is "Claude Pro for individuals, Claude Team for your whole business," so the promise and the plan that actually delivers it are sitting in two different FAQ entries that an owner reads about ninety seconds apart.


You Cannot Buy Team Alone


My own guide to using Claude gives the Team plan a price table and three sentences. One covers the seat minimum, one covers usage, one lists two products it includes. I've had that up since August 17 and it never gets anywhere near the row above.


The Team card on the pricing page is headed "For teams of 2 to 150," and the support article says it flat:


Team plans require a minimum of two members.

If you're a company of one, that plan is not available to you at any price. Everything I run for my own business sits on a personal plan for that reason, including the research agent that reads my newsletters before the market opens, because there's no version of Team a solo operator can buy.


The ceiling is 150 seats, and past that you're into Enterprise. Between those two numbers is most of the small business economy, which is a lot of ground for one tier to cover.


Standard seats run $20 a month billed annually or $25 monthly. Premium seats are $100 annually or $125 monthly and carry 6.25x Pro usage per session against a Standard seat's 1.25x. You can mix them, so the two people who live in Claude all day don't force everyone else onto the expensive seat.


And the limits don't pool:


Usage limits on Team plans are per-member, rather than applied to the team as a whole.

I read that as a feature rather than a limitation, because a per-member allowance means one enthusiastic person running a big job on Tuesday can't take the rest of the office down with them.


9 Controls It Gets, and 9 It Does Not


The Team versus Enterprise comparison on the pricing page lists 18 security and administration controls. I counted the column. A Team plan gets exactly 9 of them and skips exactly 9.


The 9 it gets are the ones a normal company actually touches: single sign-on, domain verification, restricting org creation, central billing, admin controls for remote and local connectors, enterprise deployment of the desktop app, usage analytics, organization wide skills deployment, and org instructions.


The 9 it doesn't get are these:

  • Domain capture, which claims accounts on your domain automatically

  • Migrating accounts that already exist on your domains

  • Role-based access, meaning custom roles you define yourself

  • SCIM, for provisioning users out of your identity provider

  • Audit logs

  • The compliance API

  • Custom data retention controls

  • A HIPAA-ready offering

  • Inference hooks


Read that second list as a filter rather than a shortfall. If you're in healthcare and you need HIPAA, or you have a compliance officer who's going to ask for audit logs, you're an Enterprise buyer and it's better to find that out now than in month four, and if none of those nine words describe a problem you actually have then the gap between the tiers is costing you nothing at all.


1 Seat Holds Keys the Others Do Not


Team organizations have four roles: User, Admin, Owner, and Primary Owner. There's only one Primary Owner, and the permissions article is worth reading closely, because three abilities live there and nowhere else.


Only the Primary Owner can provision new seats. Only the Primary Owner can request a data export. Only the Primary Owner can request a transfer of Primary Ownership.


Also, and this catches people:


The Primary Owner seat uses one of your plan's licenses.

So the owner isn't sitting above the plan looking down at it, they're occupying one of the two seats you're required to buy. A two person company is the owner plus one other person, and that's the floor.


The same article mentions something I hadn't seen anywhere else, which is that your Primary Owner can be a service account rather than a human. For a business where the person who set up the billing might leave, that's a genuinely useful thing to know before you assign it to somebody's personal login.


What an Admin Cannot See on Team


Here's the detail I'd have missed if I hadn't put the two role tables next to each other. Usage analytics on Enterprise plans is available to Admins, Owners and Primary Owners. On Team plans, the same row gives it to Owners and Primary Owners only.


Same feature, same article, one role dropped depending on which plan you're on. If your plan is to hand an office manager the Admin role so they can watch what the tool is costing you, that doesn't work on Team, and the pricing page's usage analytics row, which says yes for Team, will not tell you.


Where Anthropic Contradicts Anthropic


The Team plan support article lists "Role-based permissioning" as an included feature. The pricing page's comparison table marks "Role-based access" as No for Team and Yes for Enterprise.


Both are accurate, and the roles article resolves it in a parenthetical: custom roles are Enterprise plans only. Team gives you the four fixed roles above. Enterprise lets you invent your own and attach them to groups. So the support article is describing the fixed roles and the pricing table is describing the custom ones, and a buyer comparing those two pages side by side has no way to know that.


I'm not calling it a gotcha. It's the normal condition of documentation written by different teams at different times, and it's most of the reason I read three pages before I believe a feature row.


What I'd Ask a 4 Person Shop


When somebody books an intro call about putting Claude into their business, the plan is not the first thing I ask about. It's usually the fourth or fifth. But there's one question I ask before anything gets built, and it's this: who in your company is going to be the Primary Owner, and what happens if that person leaves?


That one question sorts out most of the rest, because the answer tells me whether you've got two people or twenty, whether anybody has thought about the data export that only one login can run, and whether the plan you're on right now was chosen on purpose or just accumulated one subscription at a time.


I'd rather you answer it with the comparison table open in front of you than take my word for any of this, which is the same reason I put the row at the top of this post instead of the price.


Sources



The research agent I mentioned is free and ungated on its build page, along with the honesty rules that stop it summarizing a source it could not actually read: the Claude stock research agent.


If you want a second opinion before you move your company onto a plan, Claude consulting is $250 for a 60-minute expert working session, with hours estimated up front. The intro call is free and runs fifteen to twenty minutes.

Comments

bottom of page