Claude tends to arrive in a business the way ChatGPT did: a few people pay for Pro on their own cards because it writes well and handles long documents, and then someone asks whether the business should buy it properly. The choice that follows is between Claude Team and Claude Enterprise, and the more important decision sits one step before it.
Cardonet is Certified in the Claude Partner Network, and we are a Microsoft Solutions Partner for Microsoft 365 Copilot. We deploy both, and we put clients on ChatGPT or Gemini where those fit the work better. Since Claude, ChatGPT or Copilot covers that choice, this article assumes Claude has already earned a place.
The bigger step is leaving personal plans
Claude Free, Pro and Max are plans for individuals. Under the consumer terms Anthropic introduced in 2025, conversations on them can be used to train its models unless the person switches that off, and the account belongs to the person who signed up. Team and Enterprise run under Anthropic's commercial terms, where business content is not used for training by default and the workspace belongs to you.
So the move from a handful of Pro accounts to either business plan matters more than the choice between the two. It is the same move described for ChatGPT in what changes for your data.
What Claude Team gives you
According to Anthropic's pricing page, Team is for businesses of 2 to 150 people. It gives you:
- A company workspace, with central billing and an administrator who decides who is in it.
- Single sign-on, so people use their company identity rather than a separate password.
- Connectors to Microsoft 365, Google Workspace and other systems, switched on by an administrator. A connected Claude reads what the signed-in person can open, so the permissions checks apply here exactly as they do to Copilot.
- Claude Code for anyone who writes software.
- Standard and premium seats. Premium seats come with five times the usage of standard ones, so they belong with the people who lean on Claude hardest.
What Claude Enterprise adds
Enterprise starts at 20 seats and adds the controls a larger or more regulated business tends to be asked for:
- Automatic provisioning from your directory, so removing someone from Microsoft 365 or Google Workspace removes them from Claude on the same day.
- Audit logs, and a compliance interface that lets your own tools collect what happened.
- Retention periods that you set to match your policy.
- Role-based access, so different groups can be given different capabilities.
- Domain capture, which brings accounts already created on your company email domain under the business's control. For a business whose people signed up for Pro on their work addresses, that is the most direct way to close the gap.
Which one fits
| Claude Team | Claude Enterprise | |
|---|---|---|
| Size | 2 to 150 people | From 20 seats |
| Removing leavers | By hand | Automatic provisioning from your directory |
| Audit logs and a compliance interface | Not included | Included |
| Retention periods you set | Not included | Included |
| Role-based access | Not included | Included |
| Domain capture | Not included | Included |
Team usually fits when fewer than 150 people use it, nobody is asking you for audit logs or set retention periods, and you reliably remove people by hand when they leave. For most businesses of 50 to 500 people, Team is the sensible place to start.
Enterprise is worth it when one of these is true:
- A client, a regulator or an insurer asks for records of AI use, or for retention to match your policy.
- Enough people use it that removing people by hand when they leave is a risk you would rather not carry.
- Personal accounts on your domain are already widespread, and you want them brought in rather than chased one by one.
- You handle regulated or particularly sensitive information and need the finer controls.
A third route for Microsoft businesses
Microsoft offers Claude models inside parts of Microsoft 365 Copilot, with an administrator deciding whether they are switched on. That route runs under Microsoft's terms and inside the Microsoft admin you already have, but it gives you Claude's models within Copilot rather than Claude's own workspace, projects and connectors.
For a business already paying for Copilot seats, it is worth trying before buying a second tool. For one that wants Claude as its main assistant, Team or Enterprise is the cleaner answer.
Before you buy
Write the rules first, so the workspace opens with a policy already in place. Before any connector is switched on, decide who gets it and check what those people can reach, and give premium seats only to the people who need them. Put Claude on the register with its terms, and measure the first team's work against a before so the renewal decision has evidence behind it.
Where this fits
Choosing the tool happens in Adopt, after Govern has set the rules and moved sign-in under your company account. Connecting Claude to the systems you already run, or building something on it, is Build.