Anthropic released its first Claude plugin for legal work earlier this year. On 12 May 2026, the team shipped a much larger update: more than 20 new Model Context Protocol connectors that wire Claude into the software legal teams actually use, plus 12 practice-area plugins tailored to specific kinds of legal work. For Australian firms running on iManage, NetDocuments, or Practice Evolve, this is the moment Claude becomes a production tool rather than a research experiment.
What landed on 12 May 2026
The release breaks into three building blocks. First, MCP connectors that link Claude into contract lifecycle systems, research platforms, document management, e-discovery tools, and data rooms. Second, practice-area plugins covering the work that fills most lawyers' weeks: contracts, litigation, regulatory advisory, mergers and acquisitions, employment, and property. Third, deep integrations with Microsoft 365, so the work happens where lawyers already sit: Word, Outlook, Excel, and PowerPoint.
What makes this useful in practice is that matter context carries across all four Microsoft apps. A clause Claude reviewed in Word can be referenced when drafting the Outlook cover note, and the same matter context shows up in the Excel pricing model and the PowerPoint board deck. The legal-specific skills are what give the integration its weight:
In Word, Claude drafts, redlines, and runs clause-by-clause comparisons against firm playbooks, tracking every change so partners can review what was touched.
In Outlook, Claude triages incoming matter work, flagging contract requests, drafting first-pass responses, and scheduling follow-ups against the partner calendar.
In Cowork, the same connectors apply to work that spans many documents: triaging a batch of contracts, clearing a product feature for launch, drafting a board note on regulatory developments.
In Excel and PowerPoint, Claude pulls matter context into fee proposals, pricing models, and board reporting decks without re-keying.
Why this lands well in Australian firms
Australian legal stacks are concentrated. Most mid-tier Sydney and Melbourne firms run iManage or NetDocuments for document management, Practice Evolve or Affinity for matter management, and LexisAdvance or Westlaw AU for research. Each of those vendors is in scope for the new connector set, which means Australian firms can adopt Claude without bespoke integration projects. That is the practical difference: a 40-fee-earner firm in Pyrmont or Collins Street can have Claude live across its main systems within four weeks, rather than waiting six months for a custom build.
The Australian regulatory frame fits well too. Legal Professional Privilege requires that AI tools handling client material run with appropriate access controls, audit trails, and data residency commitments. Claude's enterprise tier offers Australian data residency and SOC 2 Type II coverage. Combined with the guidance now published by each state Law Society on generative AI use by solicitors, the new connector model gives partners the audit trail they need to sign off on a rollout. Privacy Act obligations on personal information held in matter files are addressed at the connector layer rather than left to individual practitioners.
A 40-fee-earner Sydney firm's first 90 days
For a hypothetical mid-tier Sydney firm with 40 fee-earners, here is a realistic adoption sequence drawn from Australian rollouts we have run with comparable clients.
Weeks one through four are foundation work. The firm picks two practice areas to pilot, typically the commercial team and the disputes team. The IT manager wires Claude into iManage and Outlook through the new MCP connectors. The partners agree a policy on what client matters are in scope, what sits out of scope (sensitive M&A, regulator-facing work), and what review steps every AI-touched document goes through before it leaves the firm. Training is light: one hour with each practice group, with Claude Skills installed and live demos on real, anonymised matters.
Two pilot teams selected (commercial and disputes are the typical starters).
iManage and Outlook connectors live; SharePoint folder structure mapped.
Policy signed off by the management committee on scope, review, and audit.
One-hour enablement per team with at least one Claude Skill installed.
Weeks five through eight are about deepening the integration. The contracts team starts running every incoming contract against the firm playbook. Time saved per contract review averages 35 to 45 minutes; for a team turning over 80 contracts a month, the recoverable hours are real. The disputes team starts using Claude to draft chronologies, prepare court books, and review discovered documents. Recovered fee-earner time across both teams in this period typically lands around $45,000 in billable equivalent at Sydney mid-tier rates, which is the figure the managing partner takes to the next partnership meeting.
Weeks nine through twelve are about scaling out. The other practice groups (employment, property, family) come online. The firm builds two or three custom Claude Skills that encode its own procedures: the way it formats client engagement letters, the precedents it pulls for property settlements, the regulatory checks it runs on financial services advice for ASIC-regulated clients. Custom Skills are what separate a firm that uses Claude from a firm that has actually built Claude into how it practices. By the end of the quarter, the firm is running Claude across roughly 60 percent of fee-earner workflows and the partnership is starting to think about how it should be charging differently.
Where Australian firms stumble
Three patterns turn up repeatedly in Australian rollouts that fail to land:
Treating the rollout as an IT project. The IT manager wires up the connectors and waits for the lawyers to come. They do not. The lawyers need a practice-group lead who has used Claude on real matters and can show colleagues what it does on their work.
No client-facing position. The first time a client asks what AI you are using on their matter, you need a confident, consistent answer. Firms without an agreed position end up with each partner improvising, which is the wrong outcome.
Skipping the policy step. The firm that publishes its AI policy after deploying Claude almost always has to walk something back. Get the policy signed before the first connector goes live.
What to do this fortnight
If you run a mid-tier Australian firm and you have not yet read the 12 May release, do three things. One: read the Anthropic post and the practice-area plugin list, and ask your IT lead which connectors map to your existing systems. Two: assemble a small group of fee-earners across two practice areas and let them run real matters against Claude for two weeks, with a written rule that nothing leaves the firm without a partner review. Three: talk to a consultancy that has done this work before in an Australian context, because the legal release is the kind of thing that rewards the firms that move first.
Automata AI runs Claude rollouts for mid-tier Australian firms. If you are looking at the 12 May legal release and trying to decide where to start, book a call and we will walk through the first 90 days with you.
