, Nils-Erik Jansson
Claude Team or Enterprise for a legal department
Team suits a department that buys on its own; Enterprise suits a department whose company can sign up for at least 20 seats. The features in the chat are the same. The choice turns on four things a legal department cares about: custom retention periods, where traffic is routed, who can see what in the logs, and how many seats the company has to buy. Here are the differences according to Anthropic's own pages, and what they mean for a department of one to ten lawyers.
Updated by Nils-Erik Jansson
What is the same
The models, the chat, projects, connectors, skills and the legal plugins are available on both plans. Both have sign-in through the company's identity provider (SSO), central administration and admin control over which connectors may be used [1]. Both are governed by Anthropic's commercial terms, with no training on customer content [2]. Both have the same certifications [4]. Compare the plans by what the lawyer sees on screen and you will find no difference.
What is different
| Team | Enterprise | |
|---|---|---|
| Custom retention periods | No, data is kept until the user deletes it [3] | Yes, for chats, projects and artifacts, down to 30 days, set by a Primary Owner or Owner [3] |
| Traffic routing | The default mode, in which traffic can be routed to the US, Europe, Asia and Australia [5] | Optional routing, with usage-based billing [5] |
| Data storage | US [5] | US [5] |
| Role-based access with finer permissions | Not available [1] | Available [1] |
| SCIM (users created and removed automatically from the company directory) | Not available [1] | Available [1] |
| Audit logs | Not available [1] | Available [1] |
| Compliance API for monitoring | Not available [1] | Available [1] |
Retention periods are the biggest difference for a legal department, because retention periods per matter type are one of the answers to the five data protection questions. See the insight on retention in Claude Enterprise. A department that needs to show who did what, or that will connect the tool to the company's logging, needs Enterprise.
Network. Enterprise has network-based access control and IP allowlisting [1]. That is mainly a question for IT security, and less for the legal department, but anyone with a strict policy on where company data may be accessed from will need it.
Seats and price
| Team | Enterprise | |
|---|---|---|
| Number of seats | 2 to 150 [1] | At least 20 [1] |
| Standard seat, per user per month | USD 20 billed annually, 25 billed monthly [1] | USD 20 billed annually [1] |
| Premium seat with five times more usage | USD 100 billed annually, 125 billed monthly [1] | Not stated |
| Usage | Capped at USD 500 a month in shared API credits [1] | Charged on top of the seat price at API rates, depending on model and task [1] |
The price of a standard seat is therefore the same on both plans. The pricing model differs: Team is a fixed seat cost with usage limits, while Enterprise is the seat cost plus variable consumption.
Prices are in US dollars excluding tax, read on 10 November 2026. What the company actually pays in its own currency appears in the quote from Anthropic or a reseller, and I go through it in our conversation.
What it means for a department of one to ten lawyers
The deciding question is which plan the department can get. Twenty seats is more than a department of one to ten lawyers has, so Enterprise assumes that the rest of the company is part of the agreement. The legal department then gets the retention periods and the logs as part of the package, and the question becomes who in the company is the Owner and sets the periods for the lawyers' projects.
A department that buys on its own ends up on Team. There are then no custom retention periods, and three things make up for it: a shorter list of what goes into the tool at all, a routine for deleting chats and projects when a matter closes, and projects that are closed rather than left in place. That is not as good as a retention period, but it can be documented, and documentation is what the data protection assessment asks for.
A department that plans to move to Enterprise later should already work in projects per matter type on Team, so that the structure is in place when periods can be set.
How HOVR Legal works with this
The choice of plan is step two of the setup of Claude for Legal, after the needs interview and before the data protection documentation, because the transfer assessment and the settings list look different on the two plans. What needs to be in place before the first matter goes in is set out in the checklist.
Frequently asked questions
- Can a legal department with five lawyers buy Enterprise?
- Not on its own. Enterprise has a minimum of 20 seats with annual billing [1]. A department of five lawyers gets Enterprise only if the company signs the agreement for more users, or if the department takes 20 seats and leaves the rest empty. Team can be bought from two seats. That is one reason small departments end up on Team, and it is why the list of matters kept out of the tool matters more there.
- Does Anthropic train on our content on Team?
- No. Both Team and Enterprise are governed by the commercial terms, which do not allow training on customer content, and the pricing page states no training on your content by default for Team [1] [2]. The differences between the plans lie in retention, routing and administration.
- Are the certifications different?
- No. According to Anthropic's Trust Center, Team and Enterprise have the same certifications: SOC 2 Type 2, ISO 27001, ISO 42001, CSA Star and NIST 800-171. Enterprise also has a HIPAA-ready offering [4]. The reports are released on an access request.
Statements about Anthropic's terms and products were read on Anthropic's pages on 10 November 2026 and are checked at the start of every engagement.
Sources
- [1]Pricing, Anthropic, prices in USD excluding tax, subject to change
- [2]Commercial Terms of Service, Anthropic
- [3]Configure custom data retention controls for Enterprise plans, Anthropic
- [4]Anthropic Trust Center, certifications and sub-processors
- [5]Where are your servers located?, Privacy Center, Anthropic
Insights on the topic
Back to Claude for Legal
More under Claude for Legal
- Claude for Legal setup for the in-house legal team
Fixed-scope engagement: plan and contract, data protection, playbook and escalation for Swedish law, connectors, policy, training, follow-up on real matters.
- Law firm package: Claude for Legal for Swedish firms
Claude for Legal for Swedish law firms: data protection documented under the Swedish Bar Association's guidance and an environment set up for client work.
- Putting a contract review playbook into Claude
How a contract review playbook is loaded into Claude for Legal: where it sits, what goes in beside it, the instruction, and what the lawyer still does.
- Claude for Legal compared with Legora, Juno and Lexnova
A comparison for lawyers working in Sweden: what Claude for Legal, Legora, JUNO AI and Blendow's tools are built for, and when each fits.
- Projects, skills, plugins and connectors in Claude
What a project, a skill, a plugin and a connector are in Claude, and what goes where: playbook, templates, rules, systems.
- Contract renewals with AI: tracking without a CLM
How a legal department builds a watch list of renewals and notice periods from its contract archive with an AI tool, and what the list can and cannot do.
- Claude for Legal compared with Harvey and Legora
What Claude for Legal, Harvey and Legora are according to their vendors, what they state on data, training and certifications, and how to choose between them.