See how Spellbook helps legal teams draft contracts faster than ever before.
Book Demo
Lawyers are switching to Claude because Claude for Microsoft 365 now edits inside Word and Outlook with tracked changes, and because a Claude seat costs a fraction of an enterprise legal AI seat. Claude for Legal adds ready-made legal artifacts and practice-area plugins for contract review, NDA triage and compliance work on top of that. The limits are just as concrete: Claude carries no market benchmark data, no connection to a live legal citator, and a privilege position that two 2026 federal rulings have left unsettled.
The shift accelerated after a rough February for the legal AI market. RELX, the parent of LexisNexis, shed nearly £7 billion in value in a single day, a 14.4% drop and its steepest one-day fall since 1988, as roughly £12 billion came off AI-exposed legal software stocks. Firms that read that drop as a signal started testing general-purpose models like Claude against purpose-built legal tools, not just on price but on whether the gap was closing at all. The firms with the most at stake, law firms handling transactional work for mid-market clients across industries from healthcare to manufacturing, reached a conclusion fastest: a seat that costs a fraction of a legal AI platform is worth piloting even if it only replaces part of the workflow.
Key Takeaways
[cta-1]
Lawyers are switching to Claude AI for three reasons: Anthropic put legal workflows inside Word and Outlook, Claude’s reasoning holds up across long documents, and a Claude seat costs a fraction of an enterprise legal AI seat.
That writing-quality point matters because accuracy is the thing lawyers worry about most: the ABA’s 2024 technology survey found that 74.7% of lawyers cite accuracy as their biggest AI concern, ahead of reliability at 56.3% and data privacy at 47.2%.
Zack Shapiro, a litigator, built a firm-wide workflow on Claude Skills after comparing its drafts against the legal AI tools his firm had used previously, and reported that the comparison changed how the rest of his firm approached legal work, from contract review through to client correspondence.
Legal-tech commentator Ernie Svenson reported the same result from testing Claude across several practice areas: output quality that held up against the legal AI tools he had used before.
Claude performs four legal tasks well: long-document analysis, first-draft generation, redlining inside Word, and research synthesis against sources a lawyer supplies. The current Claude models read up to one million tokens in a single request, which covers a full merger agreement set or a multi-year litigation file rather than a single 500-page document. That difference changes what a lawyer can hand the model in one pass, instead of splitting a deal file into pieces first.
Claude can ingest a long contract set or discovery production and produce a structured summary. The one-million-token context window means a lawyer can load an entire deal file rather than feeding the model one document at a time. Within that summary, Claude:
Claude drafts first versions of client memos, demand letters and routine contract language, and redlines inside Word using the same tracked-changes mechanics a reviewing partner already expects. The lawyer still reviews and finalizes every draft; Claude produces the starting point, not the filed document.
Claude for Microsoft 365 is the specific product that closes the gap lawyers used to complain about. It:
Claude can synthesize research when a lawyer supplies the source documents, cases or statutes, but it has no built-in connection to a legal citator or a verified case law database. The same independent-verification requirement applies to regulatory research, such as questions involving the EU AI Act, where the underlying framework changes faster than any model’s training data.
[cta-2]
Claude for Legal is Anthropic’s packaging of legal work into Claude, and it bundles three things:
The February 2026 release was a narrower legal plugin, one of a set of practice-area plugins Anthropic shipped that month, and it covered contract review and NDA triage on its own without the Word integration or the firm-system connectors that came later. Claude for Legal is the fuller product line that grew out of it: the same plugin concept, plus the Microsoft 365 integration, plus the connectors a firm uses to wire Claude into systems like iManage and NetDocuments through the Model Context Protocol. A firm evaluating Claude today is evaluating this broader product, not the February release in isolation.
Claude for lawyers costs $17 per month on Claude Pro with an annual plan, $20 billed monthly, and $100 per month on Claude Max. Tracked-changes redlining in Word is not on those plans: Claude for Microsoft 365 requires a Team seat at $20 per seat per month on an annual plan, or an Enterprise seat at $20 per seat per month with a 20-seat minimum. A solo practitioner can therefore run Claude for research and drafting for roughly $200 a year, while a transactional team that wants redlining inside Word is buying Team or Enterprise seats.
| Plan | Price | Billing | Includes Word and Outlook redlining |
|---|---|---|---|
| Free | $0 | N/A | No |
| Pro | $17/month (annual) or $20/month | Monthly or annual | No |
| Max | $100/month | Monthly | No |
| Ultra | $200/month | Monthly | No |
| Team (standard seat) | $20/seat/month (annual) or $25/month | Per seat | Yes |
| Team (premium seat) | $100/seat/month (annual) or $125/month | Per seat | Yes |
| Enterprise | $20/seat/month (annual), 20-seat minimum | Per seat | Yes |
Anthropic’s own pricing page carries the current figures for every tier above.
Three things to weigh beyond the table above:
Harvey is an enterprise legal AI platform; firms considering it should request pricing directly rather than relying on third-party estimates.
The risks of using Claude for legal work fall into three groups: hallucinated citations, no access to verified legal databases, and the maintenance burden of workflows a firm configures itself. A fourth risk, the unsettled attorney-client privilege position, is significant enough to cover in its own section below.
Claude can generate citations that look correct but reference cases that do not exist or do not say what the output claims. This is not a theoretical risk: a Latham & Watkins associate faced sanctions after filing a brief containing AI-fabricated citations in the Concord Music litigation.
Claude has no built-in connection to a legal citator or a verified case law database.
Claude’s training data has a cutoff date like any large language model: the current Claude lineup reads through June 2026. A lawyer relying on Claude for case law needs to confirm the law is still current and that the citation is real before relying on it.
A firm that builds contract-review artifacts, NDA triage plugins or compliance skills in Claude is also the firm responsible for updating them when a form changes, a regulation shifts, or a practice area the firm serves evolves. That maintenance work does not show up in the per-seat price, and it falls on whoever on the team is comfortable editing prompts and artifacts rather than on a vendor’s product team. In practice, this means:
Attorney-client privilege and work-product protection for Claude sessions are unsettled, and two 2026 federal rulings point in different directions. In United States v. Heppner, 820 F. Supp. 3d 292 (S.D.N.Y. 2026), Judge Rakoff denied work-product protection to documents a defendant generated with Claude on his own, because the work was not done at counsel’s direction and did not reflect counsel’s strategy. The defendant had used a publicly available version of Claude without any involvement from his lawyers, and Rakoff treated that fact, not just the absence of direction, as central to the ruling.
Eight months later, a second court reached a narrower but genuinely different conclusion on the same question. In Fontainebleau Florida Hotel, LLC v. Botach (S.D. Fla. 2026), Magistrate Judge Marty Fulgueira Elfenbein held that work-product protection can apply to AI prompts and outputs even when the AI use was not directed by counsel, expressly declining to follow Heppner’s categorical limitation. The court still rejected a blanket objection: protection must be shown document by document, with a privilege log, and the parties were required to confer about how AI providers produce a litigant’s AI materials so the litigant can assert work product first.
These are two district court decisions that reach different results on the categorical question, not settled law, and a lawyer relying on either ruling should treat the question as open rather than resolved. Whether Claude use is professionally permissible at all is the more basic question, and it should be resolved first: privilege only becomes relevant once a firm has already decided the underlying use is allowed.
Debevoise’s analysis of the Fontainebleau order walks through the document-by-document standard the court set, for firms that want the practical breakdown rather than the order itself.
That analysis sets out four requirements for a lawyer using Claude on client matters, until an appellate court or a clearer consensus emerges:
[cta-3]
Claude and purpose-built legal AI software now overlap where they did not in February 2026: both apply tracked changes inside Microsoft Word. The differences that remain are market benchmark data, prebuilt playbooks, and who carries the maintenance burden for the review workflows a legal team depends on.
Security is no longer a clean dividing line and should not be written as one. Claude for Legal documents sandboxed containers, network controls, credential isolation and audit logging at the enterprise tier, so the honest distinction today is between consumer and enterprise tiers generally, not between Claude and a specialist tool built only for contract review and redlining. The Review feature, for comparison, pairs a matching set of controls built for a transactional legal team: zero data retention, SOC 2 Type II certification, SSO, and data residency options for firms with jurisdiction-specific storage requirements.
Spellbook keeps adding to that gap:
All three ship as current, generally available capability rather than a roadmap item. Spellbook itself remains a commercial-contract specialist built for this transactional work, not a general legal-research or litigation platform, and it runs that work under its own security controls.
Your law firm should switch to Claude only if contract volume is low. Firms that handle a few agreements a month can run Claude alone, and firms that live in third-party paper should add Claude to a contract-specific platform rather than switch to it.
Firms switching from ChatGPT specifically tend to cite the same Word-native editing inside documents and the output quality practitioners report. Try Spellbook free for 7 days to see how a contract-specific Review workflow compares against a general-purpose assistant on your own documents.
Claude and ChatGPT both handle legal drafting and research competently, and the differences are in the details rather than a flat verdict. Claude’s current models read up to one million tokens of context, which favors long-document work like full contract sets, and Claude for Microsoft 365 applies tracked changes directly inside Word. The right choice depends on which workflow a firm runs most: long-document analysis favors Claude’s context window, while a firm already standardized on a different provider’s ecosystem may find switching costs outweigh the difference.
Enterprise Claude plans offer zero-retention agreements, but the privilege question is separate from the security question and remains genuinely unsettled. Two 2026 federal rulings, Heppner and Fontainebleau, reached different conclusions about whether work-product protection survives AI use that counsel did not direct. A lawyer uploading client documents should rely on an enterprise agreement with no training on inputs and should document the basis for privilege on every matter rather than assuming the question is settled.
Yes. Anthropic shipped a legal plugin as part of a broader set of practice-area plugins in February 2026, and that plugin is now one part of the larger Claude for Legal product line covering contract review, NDA triage and compliance workflows.
Yes, for drafting, summarizing, and redlining legal documents inside Word, with the lawyer reviewing and finalizing every output. Claude has no built-in connection to a verified legal database, so any citation or case law reference it produces needs independent verification before it goes near a filing.
The comparison is about deployment model rather than which tool is better outright. Harvey is an enterprise legal AI platform that itself runs on Claude models and ships a Harvey for Claude Connector, so a firm choosing between them is really choosing between a vendor-managed, purpose-built deployment with market benchmark data and prebuilt playbooks, or a more flexible, lower-cost general-purpose assistant it configures and maintains itself. Harvey’s pricing and deployment differ enough from Claude’s that the decision usually comes down to firm size and whether the firm wants to build its own workflows.
Submission Received
Thank you for your interest!
Submission Received
Thank you for your interest!
We're connecting you with the best rep