![\"\"](\"https:\/\/www.newsbeep.com\/uk\/wp-content\/uploads\/2026\/02\/Screenshot-2026-02-02-at-09.27.00-678x381.png\" "\\"Screenshot")
<\/p>\n<\/p>\n
For years people have wondered if the big AI players would ever target legal tech. Well, now they have. LLM giant Anthropic has launched new capabilities for its agentic Cowork facility for finance, sales, marketing, and\u2026.legal, via a range of plugins. <\/p>\n
As the pioneering AI company explained in a statement sent to Artificial Lawyer: \u2018Anthropic is releasing plugins for Cowork that extend Claude\u2019s agentic capabilities beyond general tasks into specialized business functions. Plugins bundle skills, connectors, slash commands, and sub-agents that make Claude work like a domain expert for specific roles and teams, sales, finance, legal, data analysis, marketing, customer support, and more.\u2019<\/p>\n
As you can see below, there are a range of skills, including for contract review.<\/p>\n
![\"\"](\"https:\/\/www.newsbeep.com\/uk\/wp-content\/uploads\/2026\/02\/Screenshot-2026-02-02-at-08.36.42-1024x550.png\")
Note: these are from the official Anthropic Github.<\/p>\n
![\"\"](\"https:\/\/www.newsbeep.com\/uk\/wp-content\/uploads\/2026\/02\/Screenshot-2026-02-02-at-09.10.03-1024x219.png\")
<\/p>\n
For contract review it sets out the master prompt, then sub-prompts for different needs. <\/p>\n
\u2018Playbook-Based Review Methodology<\/p>\n
![\"\"](\"https:\/\/www.newsbeep.com\/uk\/wp-content\/uploads\/2026\/02\/Screenshot-2026-02-02-at-08.43.55-1024x173.png\")
<\/p>\n
Loading the Playbook<\/p>\n
Before reviewing any contract, check for a configured playbook in the user\u2019s local settings. The playbook defines the organization\u2019s standard positions, acceptable ranges, and escalation triggers for each major clause type.<\/p>\n
If no playbook is available:<\/p>\n
Inform the user and offer to help create one<\/p>\n
If proceeding without a playbook, use widely-accepted commercial standards as a baseline<\/p>\n
Clearly label the review as \u201cbased on general commercial standards\u201d rather than organizational positions<\/p>\n
Review Process<\/p>\n
Identify the contract type: SaaS agreement, professional services, license, partnership, procurement, etc. The contract type affects which clauses are most material.<\/p>\n
Determine the user\u2019s side: Vendor, customer, licensor, licensee, partner. This fundamentally changes the analysis (e.g., limitation of liability protections favor different parties).<\/p>\n
Read the entire contract\u00a0before flagging issues. Clauses interact with each other (e.g., an uncapped indemnity may be partially mitigated by a broad limitation of liability).<\/p>\n
Analyze each material clause\u00a0against the playbook position.<\/p>\n
Consider the contract holistically: Are the overall risk allocation and commercial terms balanced?<\/p>\n
Common Clause Analysis<\/p>\n
Limitation of Liability<\/p>\n
Key elements to review:<\/p>\n
Cap amount (fixed dollar amount, multiple of fees, or uncapped)<\/p>\n
Whether the cap is mutual or applies differently to each party<\/p>\n
Carveouts from the cap (what liabilities are uncapped)<\/p>\n
Whether consequential, indirect, special, or punitive damages are excluded<\/p>\n
Whether the exclusion is mutual<\/p>\n
Carveouts from the consequential damages exclusion<\/p>\n
Whether the cap applies per-claim, per-year, or aggregate<\/p>\n
Common issues:<\/p>\n
Cap set at a fraction of fees paid (e.g., \u201cfees paid in the prior 3 months\u201d on a low-value contract)<\/p>\n
Asymmetric carveouts favoring the drafter<\/p>\n
Broad carveouts that effectively eliminate the cap (e.g., \u201cany breach of Section X\u201d where Section X covers most obligations)<\/p>\n
No consequential damages exclusion for one party\u2019s breaches.\u2019<\/p>\n
There are several other aspects to explore, for IP, data, and more.<\/p>\n
And it also includes instructions on \u2018Redline best practice\u2019 \u2013 see here:<\/p>\n
\u2018Redline Generation Best Practices<\/p>\n
When generating redline suggestions:<\/p>\n
Be specific: Provide exact language, not vague guidance. The redline should be ready to insert.<\/p>\n
Be balanced: Propose language that is firm on critical points but commercially reasonable. Overly aggressive redlines slow negotiations.<\/p>\n
Explain the rationale: Include a brief, professional rationale suitable for sharing with the counterparty\u2019s counsel.<\/p>\n
Provide fallback positions: For YELLOW items, include a fallback position if the primary ask is rejected.<\/p>\n
Prioritize: Not all redlines are equal. Indicate which are must-haves and which are nice-to-haves.<\/p>\n
Consider the relationship: Adjust tone and approach based on whether this is a new vendor, strategic partner, or commodity supplier.\u2019<\/p>\n
As can be seen these seem to favour NDAs and related documents, but one can assume they are hoping to expand this.<\/p>\n
\u2013<\/p>\n
In short, they are really thinking about this and thinking especially in terms of how a lawyer might approach the subject.<\/p>\n
Why are they doing this?<\/p>\n
AL would guess there is one main reason: the need for a lot more revenue. Anthropic and OpenAI both want and need to increase their revenues very quickly. They\u2019ve taken on billions in funding and want to do IPOs. But, to get there they need more cashflow, hence more business users. And legal is one area to target. <\/p>\n
This is their reasoning:<\/p>\n
\u2018The core challenge with AI agents in the enterprise is that general assistants can\u2019t handle specialized work. Plugins solve this by combining domain expertise with the tools teams already use\u2014CRMs, document systems, data platforms\u2014so Claude can handle routine work while professionals focus on higher-value decisions. It\u2019s a meaningful step from AI as a chatbot to AI as a capable teammate across business functions.\u2019<\/p>\n
What\u2019s available at launch:<\/p>\n
\u2018Plugins for job\/team roles: 11 open-source plugins built by Anthropic, spanning Productivity, Enterprise Search, Sales, Finance, Data, Legal, Marketing, Customer Support, Product Management, and Biology Research\u2014with more to come. The full collection is available on\u00a0GitHub<\/a>.\u00a0<\/p>\n Ready to go out of the box: Each plugin comes loaded with domain-specific capabilities. A sales plugin connects Claude to your CRM and knowledge base, helping with everything from prospect research to call follow ups. A legal plugin adds document review and contract analysis. A data plugin links to dashboards to help explore trends faster.\u00a0<\/p>\n Plugin builder: Users can customize existing plugins or create their own from scratch.\u00a0<\/p>\n Available today in research preview: Support for plugins in Cowork is available now to all paid Claude users. Plugins are currently saved locally, with broader org-wide support coming in the weeks ahead.\u2019<\/p>\n Will This Impact Legal Tech?<\/p>\n Well, the short answer is: it could.<\/p>\n But, the challenge is that this is not a question of just clicking one button on a desktop and everything is done for you. Law firms and inhouse teams will need some tech skills to deploy these plugin tools, and no doubt will want reassurances around data security.<\/p>\n That said, most large law firms and legal teams at global corporations will be able to leap that hurdle very quickly with their tech teams and move to deployment.<\/p>\n The question is: how many law firms and teams will go this way? Given the rise in interest in DIY legal tech tools then it seems likely that some firms will go for this, especially if some of their lawyers are already using Claude. <\/p>\n But, as noted, a quick, generic review with the instructions above is one thing, a super-detailed one that meets your style, that connects to your past data, that can tell you what is market, is something else. So, high quality legal tech tools have little to fear here\u2026for now. Although, perhaps better customisation of what\u2019s on offer could go some way to addressing the limitations of what\u2019s on offer? <\/p>\n As noted before by AL, the real risk is for those vendors selling commoditised legal AI skills. Those indeed face something of an existential threat. Why buy a tool that is no better than the legal plugin above?<\/p>\n And finally, this all goes back to the initial point: we have been waiting for the big AI companies to move into legal. Now, at least via plugins, they have. How long before others do the same? And then what impact will this make?<\/p>\n Plus, will they move beyond this and really provide a clear and separate product division for legal, as OpenAI, for example is now doing for medical diagnosis? <\/p>\n For legal AI companies the message is clear: with vibe-coders on one flank and Big AI now on the other, they need to really show value over and above what can be provided by these two encroaching paths. <\/p>\n You can see more here<\/a> \u2013 Knowledge Work Plugins. <\/p>\n \u2014<\/p>\n Conference News<\/p>\n
![\"\"](\"https:\/\/www.newsbeep.com\/uk\/wp-content\/uploads\/2026\/02\/Screenshot-2026-01-27-at-10.24.07-1024x720.png\")
<\/a><\/p>\n