In-house legal departments were the structurally happiest readers of Anthropic's February 2026 Cowork legal plugin launch. They've spent five years trying to build internal NDA triage and clause review tooling without engineering budget. Per Anthropic's pricing, a 50-person in-house team running on Claude Team at $20-25/seat/month lands at $12,000-15,000/year total, for the model layer plus the open-source Cowork plugin. That's the floor for workflows that vendor procurement would historically price at $50,000+ annual minimum. This checklist covers what to deploy, in what order, and what to lock down before activating the seats.

Step 1: Decide whether you're replacing existing tooling or layering on top

In-house departments approach Claude deployment from one of two starting positions, and the deployment plan depends entirely on which:

The second-order read: layering is structurally easier and politically cheaper but doesn't capture the procurement-budget shrink that makes Claude attractive in the first place. Replacing is harder and slower but produces the cost reduction that justifies the project to finance.

The third-order read: most successful in-house Claude deployments start as layering, then convert to replacement at the next vendor renewal cycle. The 12-month sequence: deploy Claude alongside existing tooling, document the workflow coverage gap, present the data at renewal time, drop or downgrade the existing vendor.

Step 2: Pick the tier: Team is the floor, never Pro

In-house tier selection follows the same rule as outside firm deployments: Claude Team is the floor; consumer Pro is not appropriate for matter work. The reason is structural, per Anthropic's terms, Team, Enterprise, and API inputs are not used for model training, but consumer Pro inputs may be. Privileged or commercially sensitive in-house work cannot run on consumer Pro.

Tier breakdown for in-house deployments:

For a 50-person in-house team: provision Claude Team Standard for the full team. Annual cost lands at $12,000 (annual billing). For a 200-person legal department: 80% Team Standard, 15% Team Premium for senior counsel running M&A and complex deal work, 5% on dedicated API access for tooling builds. Annual run-rate roughly $90,000-108,000.

The Cowork legal plugin is open source and free. The configuration step is what determines whether it produces useful output for your specific in-house workflows.

The configuration surface:

First-month configuration time: 8-16 hours of legal-ops time plus 4-8 hours of senior counsel review of the playbook. The Cowork /review-contract overview walks through the configuration pattern.

Step 4: Establish the four use cases first, expand from there

In-house departments that try to deploy Claude across every workflow simultaneously usually produce inconsistent adoption and inconclusive ROI. The cleaner pattern: pick four named use cases, deploy them deeply, expand only after each is in production for 30+ days.

The four starter use cases for most in-house departments:

The second-order pattern: power users in your department will drift toward use cases 5-15 (clause negotiation against opposing counsel, complex transaction structuring, litigation prep). That's expected and healthy. The discipline is keeping the firm-wide deployment focused on the four-starter set so the ROI memo at year one is defensible.

Step 5: Build the privilege and confidentiality protocol explicitly

In-house Claude deployments inherit different privilege questions than outside firm deployments. The key risks:

The protocol covers each of these in writing, with named owners for protocol enforcement. The Heppner ruling meets enterprise Claude privilege defense spoke goes deeper on the privilege architecture.

Step 6: Instrument the dashboard before activation

Every in-house Claude deployment that doesn't capture baseline metrics on day one ends up with a defensibility problem at year-one renewal. The dashboard isn't optional infrastructure: it's the artifact that decides whether the legal department renews the procurement contract.

Metrics to capture day one:

The second-order read: the legal department that runs Claude without the dashboard is in the same position as a finance department that doesn't reconcile its accounts. The numbers exist; they just aren't being captured. The dashboard takes about a week of legal-ops engineering time to set up. The cost of not setting it up is the entire defensibility of the original procurement decision.

The bottom line. My take: In-house legal departments have the cleanest path to Claude deployment in 2026. Pick Team Standard tier, configure the open-source Cowork plugin against your actual playbook, deploy four named use cases first, lock down the privilege and confidentiality protocol explicitly, instrument the dashboard before activation. A 50-person in-house team lands at $12,000-15,000/year for the model layer plus the plugin: replacing or supplementing legal-ops tooling that historically priced at $50,000+ annual. The structural advantage in-house teams have over outside firms: the budget conversation is internal, and the procurement battle with finance shrinks because the cost folds into a subscription the company likely already has.

AI-Assisted Research. This piece was researched and written with AI assistance, reviewed and edited by Manu Ayala. For deeper takes and the perspective behind the research, follow me on LinkedIn or email me directly.

Price sources, checked 22 October 2026: Claude (Anthropic), Claude API token rates. Each figure above is a list price from the vendor's own pricing page, or arithmetic on one. Plans, seat minimums and promotions change; confirm on the vendor's page before you buy.

Next reads

Anthropic Microsoft Foundry Azure Deployment Firm IT Ai Contract Management In House Spellbook Word Add in Deployment Firm IT Procurement