Autonomous agents for business lawyers

You decide.They execute.

You didn't go through ten years of practice to spend your days in Word. Meet your AI deal team — agents that read your emails, track your deals, draft your documents, and act before you even ask.

✓

You're on the list. We'll be in touch.

or book 20 minutes with the founder — no deck, no demo script.

100 placesPrivate beta — firms selected on a rolling basis.

By requesting access, you consent to LawyerTools contacting you about the private beta. Your email is processed under our Privacy Policy, kept until the beta ends or you ask us to delete it, and never shared.

One morning, on one deal

Yesterday you told your deal agent: when the other side sends their markup, run the compare, list the issues, draft the counter — then brief the team and get us all on a call.

07:48
Their markup lands — SPA v8Nobody on your team has read it yet
08:08
In your team's inboxes
Compare v7→v8Issues list · 14Counter-markup
Sent by Jeanne, your deal agent · 17:00 call booked, calendars checked

You hadn't opened your laptop yet.

See Sarah's morning, message by message
Backed by
Incubateur du Barreau de ParisWilcoEU public fundingData hosted in FranceBuilt by a former Linklaters M&A lawyer

In action

One instruction. Three channels.

Sarah's day · Mon, 11 MayTue, 12 May14:32Scroll to follow the day

That morning was Sarah's. She is the partner in your seat — same deal, same inbox, same 07:48 — and what follows is her day exactly as it ran.

  • Sarah ChenHumanCorporate partner
  • Tom & EmmaHumanHer deal team
  • HarryAI agentHers alone
  • JeanneAI agentShared by the team

Agents also carry a squared avatar, people a round one — the convention Teams already uses for apps. Harry and Jeanne are default names; firms rename them.

Standing instruction

Set it once, like a text. It just runs.

It fires on its own

Awake and working before you are.

The team stays aligned

The whole team, briefed in seconds.

Read the day as text — no animation, no interface

Monday afternoon

14:32 · WhatsApp · Sarah to Jeanne, the Apollo deal agent. Sarah sets a standing instruction: as soon as Dupont sends their markup, run a compare against the latest version, prepare an issues list and a counter-markup, using the firm's SPA template and the Helios precedent for the W&I cap. Then send it to the deal team and organise a call.

14:33 · Jeanne replies. She will watch the inbox and run everything the moment the markup lands. She also proposes pulling the ClearWater precedent for the MAC clause, since Dupont pushed on that point last time. Sarah agrees.

14:38 · WhatsApp · Harry, Sarah's personal agent. Didier Vasseur's assistant has sent his availability for dinner. Harry proposes tomorrow 19:30 at Le Clarence and asks whether to lock it.

14:42 · Harry confirms. Booked, calendar updated, and forty-five minutes kept clear after the 17:00 call so Sarah is not rushing.

Tuesday

07:48 · Email. Marc Dupont sends the SPA markup, version 8. Nobody on the team has read it yet.

08:08 · Email · Jeanne to the deal team. Twenty minutes later the package is in their inboxes: the redline compare of v7 against v8, an issues list flagging fourteen points of which three are priority, and a counter-markup built on the firm's template with the Helios and ClearWater positions restored. Jeanne flags three things in the covering note — the narrowed MAC definition, a new earn-out mechanic that is not in the playbook, and the W&I cap moved from 30% to 20%. She has checked availability with the team and booked a call for 17:00.

08:15 · Email · Harry to Sarah alone. A personal brief: the Meridian call at 14:30 has no preparation yet and one is being drafted; there is a free window at 11:00 which Harry has blocked for reading the markup; Dupont's partner sent a courtesy note that has a reply ready for sign-off; and dinner is at 19:30, already accounted for.

10:15 · Teams, the Apollo channel. Tom Laurent has read the compare and flags the earn-out mechanic as a structure he has not seen. Emma Rousseau asks whether there is any precedent for it.

10:17 · Jeanne answers. She finds a similar ratchet mechanism in the Meridian deal from 2023, held in the firm's know-how base, and asks whether to draft an alternative position or wait for the 17:00 call. Emma asks for a conservative draft.

10:22 · Jeanne corrects herself. Tom notices Emma's calendar shows busy at 17:00. Jeanne acknowledges the conflict appeared after she booked, says she has already raised it with Emma's assistant, and confirms the call still holds.

10:30 · Teams, one-to-one with Harry. The Meridian brief is ready in Sarah's drafts. Harry also flags a double booking building for the following Tuesday and offers to move the more flexible of the two.

Between 07:48 and 08:08 the work was done, the team was briefed and the call was booked. Sarah read it over coffee.

That was an acquisition, because it is the world we came from. On a financing, a joint venture, a commercial contract or a dispute, the documents change — the coordination does not.

Sarah's day · Tue, 12 MayNow: WhatsApp standing instruction
  • Mon, 11 MayWA · Jeanne
  • 14:38WA · Harry
  • 8:08 AMEmail · Jeanne
  • 8:15 AMEmail · Harry
  • 10:15 AMTeams · Deal
  • 10:30 AMTeams · Harry
028:08 → 8:15 AMThe trigger fires — Jeanne delivers, Harry briefs
Email

20 minutes after Dupont's email — package ready.

Way used here③ The standing rule fires — on its own, the moment Dupont's markup lands. No one pressed a button
Search
2
New mail
Delete
Archive
Move
Flag ⌄
Mark unread
Sync
sarah.chen@wardlaw.com
Inbox 21
Archive 18
Drafts 3
Sent
Deleted Items 16
Junk Email
Conversation History
Agents
Harry · Personal
Jeanne · Apollo
Focused
Other
Today
A
Harry — Personal Agent
8:15 AM
Quick heads up + your day
Sarah, Jeanne just sent the Apollo package — counter-markup, issues list, redline compare…
T
Microsoft Teams
8:08 AM
Project Apollo — team call today at 5:00 PM
Jeanne has invited you to a meeting. Tom Laurent, Emma Rousseau, Sarah Chen…
📅
V
Jeanne — Apollo Deal Agent
8:08 AM
Project Apollo — Dupont markup received + compare, issues list & counter-markup
Team, Dupont's markup just came in. As requested by Sarah, here's what I've prepared…
📎
MD
Marc Dupont · Dupont & Associés
7:48 AM
Re: Project Apollo — SPA markup v8
Sarah, please find attached our comments on the latest draft. We have…
⚐
AL
Antoine Lefebvre · Dupont & Associés
7:52 AM
A note before the call
Sarah — quick note ahead of today's call. Hope you and the team are well…
Yesterday
TL
Tom Laurent
Wed 22:14
ClearWater — NDA first draft for your review
Sarah, please review when you get a chance. Counterparty asked for…
This week
ER
Emma Rousseau
Tue 18:31
Meridian NDA — please countersign
Sarah, the executed NDA from Meridian came back. Need your signature…
WWhatsAppMon · 14:42
Next morning››››››››
OOutlook8:08 AM
Sarah hasn't opened her laptop. Dupont's markup lands — and the rule she set days ago wakes up on its own.
01Mon, 11 May · afternoonSarah sets up a standing instruction for Apollo
WhatsApp
Ways used here① Direct — she just talks to her agent, then ③ sets a standing rule for later
OOutlook8:15 AM
2 hours later››››››››
TTeams10:15 AM
Package delivered. Now the whole team gathers in the deal channel to align — with Jeanne in the room.
0310:15 → 10:35 AMSarah follows the deal team — then Harry pings her
Teams

Jeanne surfaces a precedent no one asked for.

Way used here④ Proactive — no one asked. Harry spotted it and acted first
Search (⌘E)
4
1
Conversations
All
Unread
▾Favorites
A
Harry · Personal AgentYesterday
Daily briefing sent — have a great day 👋
▾Conversations
PA
Apollo team10:22
Jeanne: Will update the invite.
ER
Emma RousseauMon
Thanks for the brief 👍
TL
Tom LaurentMon
Sure, I'll review tonight
WL
Wardlaw · CorporateFri
Brigitte: team lunch next Friday
FC
François ChevalApr 25
Tomorrow 2pm confirmed
CL
Caroline LemoineApr 22
Got it, thanks
PA
project-apollo
Conversation
Shared
Wiki
Apollo · Knowledge base
Today · Tuesday, 12 May
Tom Laurent is typing…
TL
Tom Laurent10:15
Just went through the compare — clean work @Jeanne
The earn-out mechanic is new, never seen this structure
@Emma thoughts before the call?
Emma Rousseau is typing…
ER
Emma Rousseau10:17
Agreed. @Jeanne do we have any precedent on this earn-out structure? not in the helios deal
Jeanne is typing…
V
Jeanne10:17
Checking now…

Found something — the Meridian deal (2023) had a similar ratchet mechanism. it's in the know-how base. pulling the relevant clause now.

Should i draft an alternative position for the counter-markup, or do you want to discuss first at 5pm?
Meridian_2023_Earn-out_clause.docx
Word · 84 KB · Know-how base
👍2
Emma Rousseau is typing…
ER
Emma Rousseau10:19
Draft something — we'll review at 5pm
Keep it conservative
Jeanne is typing…
V
Jeanne10:19
On it. will update the counter-markup with a conservative earn-out alternative based on meridian structure.
Counter-markup v2 in your inboxes in 20 min 🎯
Tom Laurent is typing…
TL
Tom Laurent10:21
@Jeanne one more — the call invite shows emma's calendar as busy at 5, i thought you checked availability?
Jeanne is typing…
V
Jeanne10:22
Good catch Tom — that was a conflict that appeared after i booked (she accepted a client call at 5 this morning).
I've already flagged emma's PA, she's handling the reschedule on emma's end.
5pm should still work — emma's PA confirms she can move the client call to 5:30 instead.
Will update the invite.
Sarah Chen10:24
Solid work everyone — thanks D. See you all at 5 👍
Read
SC
+
Reply
A
Harry · Personal Agent
Conversation
Shared
Routines
Today · Tuesday, 12 May
A
Harry10:30
Hey — quick check-in before your day gets hectic.
Meridian brief is ready in your drafts, took me about 8 minutes.
Want me to send it to you or wait for your review?
Sarah Chen10:32
Send it — i'll read at 11
You blocked the slot?
Read
SC
Harry is typing…
A
Harry10:32
Already done. 11:00–11:45, focus time, no interruptions. i've set your status to do-not-disturb.

Also: Antoine Lefebvre's courtesy note — i've drafted a reply, very short, warm, acknowledges the markup and confirms the call at 5.
Want me to send from your address or review first?
Sarah Chen10:33
Send it
Read
SC
Harry is typing…
A
Harry10:33
Done ✓

One last thing — you have a conflict building for next tuesday.
You're double-booked: Meridian signing and a client intro lunch that's been on for weeks.
Want me to suggest a reschedule to one of them? Meridian is more flexible.
Sarah Chen10:35
Yes — move meridian, keep the lunch
Coordinate with their PA
Read
SC
Harry is typing…
A
Harry10:35
On it. i'll reach out to Meridian's assistant and find a new slot.
I'll have options for you by end of day 🗓️

Go prep for meridian — you've got 25 minutes 🙂
+
Message Harry
Document.docx
Word · 312 KB
×

Document

Section · MAC clause

Section · W&I cap

Close
Open in Word

The model behind the day

Two colleagues you just watched.
One is yours. One per deal.

Harry handled Sarah's inbox and calendar. Jeanne knew every version of the deal. Here's how they're structured — and how they talk to each other behind the scenes. What changes isn't how you work, only how the work gets shared.

AHarrydraft · in your voice

Dear Mr Dupont,

Thank you for the revised markup. We're aligned on the earn-out; the MAC clause remains the one open point. Could we take a short call Thursday to close it?

✓ Matches your tone across 240 past emails

Personal · one per lawyer

Harry

The colleague who is only yours.

Reads your inbox, knows your calendar, drafts in your voice — sealed 1:1, never shared. The 11:00 focus block, the dinner locked with the client's assistant, the brief waiting at 08:15? That was Harry.

Reads your inboxKnows your calendarDrafts in your voice
AV

Your agent and each deal agent talk to each other — so nothing falls between people.

Agent ↔ agent protocol · always on

VJeanneProject Apollo · memory
v8SPA — Dupont markup mergednow
v7Counter-markup sentTue
v6Issues list circulatedMon
Every party, every clause: Dupont · Meridian · the Helios precedent · the W&I tower.

Deal · one per matter

Jeanne

The colleague the whole team shares.

Reads every document, tracks every version, remembers every party — then briefs anyone on the deal. The standing instruction Sarah set on WhatsApp, the compare that ran itself, the precedent no one asked for? That was Jeanne.

Reads every documentTracks every versionBriefs the whole team

How they work for you

Four ways to work with them.

Three of the four ran across Sarah's morning. Here's the full range — from you asking, to them acting on their own. Same colleague, different levels of trust.

You askThey act on their own
01 · DirectSeen ↑

Ask. Done.

You just talk to your agent — like messaging a colleague. The most natural way in.

Summarise the Dupont thread
3 versions exchanged · the MAC clause is the open point · I'd suggest a call.
02 · RoutineOn a schedule

Set once, runs forever.

A standing instruction on a clock — like the morning brief, every day.

MON Morning brief 8:00 ✓
TUE Morning brief 8:00 ✓
WED Morning brief 8:00 ✓
↻ repeats every day
03 · TriggeredSeen ↑

When X, do Y.

A condition that fires on its own — no button, no reminder.

WHENDupont's markup arrives
↓
DOcompare · issues list · counter-markup
04 · ProactiveSeen ↑

Acts before you ask.

Spots what matters and moves first — no instruction at all. The precedent no one asked for.

Deadline in 48h — prep note readyNo one asked. Harry noticed and got ahead of it.

Where they work

Everything already
in your world.

No new apps to learn. Your agents slot into the tools your firm already runs on — and act inside them, like any colleague would.

WWord
XExcel
PPowerPoint
PDFPDF
iMiManage
SPSharePoint
OneDrive
Precedents
Playbooks
Live in betaPlanned

Microsoft Graph, delegated OAuth2. Agents inherit the access rights the user already has — one tenant admin consent, nothing installed on the desktop.

What they reach

Everything you'd
hand an associate.

Your documents, your matters, your know-how — every version, every precedent, every playbook. They reach the same files a trusted associate would.

Onememory. Every version,
every precedent, every deal.

Control & responsibility

Same colleague.
Different levels of trust.

You set how far each agent can go — per agent, per deal. Nothing about that is a switch you flip once and forget.

Level 1

Suggest

The agent watches and tells you what it would do. Nothing moves until you say so.

→ "Dupont's markup is in. Want the usual compare?"
Level 2

Prepare

The agent does the work and leaves it ready for you. The default for most deals.

→ Compare run, issues list drafted, counter-markup in your drafts folder
Level 3

Execute

The agent completes and delivers — internally. Outbound to a counterparty always comes back to you.

→ Package sent to the deal team, 17:00 call booked, calendars checked

Set per agent · per deal · changeable at any time

Nothing leaves the firm without youInternal preparation and coordination run on their own. Any message to a counterparty, a client or a court waits for your signature — by default, at every level.
Every claim carries its sourceEach statement points back to the document, the version and the clause it came from. No answer without provenance — so you can check it the way you'd check a trainee's note.
One agent per deal — sealedA deal agent knows its own deal and nothing else. No shared pool, no cross-reading between matters. Your Chinese walls are the architecture, not a policy document.
When it doesn't know, it stopsNo guessing, no filling in the blanks. The agent says what it can't establish and asks. You'll see it do exactly that in Sarah's day, twice.
The lawyer remains the lawyerThe agent prepares. You decide, you sign, you carry the advice. Nothing in the product is designed to sit between you and that responsibility.
Named agents, renamed by youHarry and Jeanne are defaults. Firms rename them — after a founding partner, a floor, an inside joke. The names belong to your firm, not to us.
Louis Prades, Founder of LawyerTools

Who built this

Louis Prades

Founder · twelve years M&A at Linklaters, Paris

"The law was the part I trained for. It was never the part that filled my days."

What filled them was hunting for the precedent that already existed somewhere in the firm. Running the compare again because the version I had wasn't the version they sent. Working out which of four files was the one to keep. Triaging an inbox at midnight. Rebuilding the same issues list for the third time.

And underneath all of it, the part nobody puts on a timesheet: carrying the weight of never forgetting anything that mattered.

I learned to build software because I wanted the colleague I never had — one that holds the whole deal in its head, does the coordination, and hands the judgment back to me. I used it on my own files before I showed it to anyone.

contact@lawyertools.aiLinkedInMore on why now

Questions we actually get

The ones partners ask first.

Does an agent send emails as me without my approval?

No. Anything going outside the firm — a counterparty, a client, a court — waits for your sign-off, at every autonomy level. Internal preparation and coordination are what run on their own.

What happens when it gets something wrong? Who is responsible?

You are, and the product is built so that stays workable. The agent prepares; you decide and sign. Every claim it makes points back to the document, version and clause it came from, so you can check it before you rely on it.

When it can't establish something, it stops and says so rather than filling the gap.

Are my emails and documents used to train a model?

No. Your data is not used for training, by us or by any model provider we work with. See Security for the detail.

Where is the data hosted?

In France, on EU infrastructure. No transfer outside the EU for storage.

How is one matter kept separate from another?

Structurally. There is one deal agent per deal, and it only ever sees its own deal. There's no shared pool of matter knowledge an agent could read across — so the separation your conflicts team requires is the architecture, not a setting someone could misconfigure.

Do we have to install anything? How long is deployment?

Nothing on the desktop. The agents connect to Microsoft 365 through Microsoft Graph with delegated OAuth2 consent, and they inherit the access rights the user already has — an agent can never reach a file its lawyer couldn't open.

A tenant admin consent is required once. Beyond that, onboarding a lawyer is a matter of minutes.

Can my partner see what my personal agent knows about me?

No. A personal agent is sealed to one lawyer. A deal agent is shared by the deal team — and it only ever knows the deal, never your inbox or your calendar.

How is this different from Copilot or ChatGPT Enterprise?

Those answer when you ask. These act when you don't. An agent holds a standing instruction, watches for the trigger, does the work overnight and hands you the result — with the deal's whole history behind it rather than a fresh context window each time.

How is this different from Harvey or Legora?

Those are assistants for legal research and drafting, and good ones. This is a colleague with persistent memory of a specific deal, who works inside Outlook, Teams and Word instead of asking you to come to a new interface.

And it's built for the transactional workflow specifically, not for legal work in general.

What if we stop? Do we get everything back?

Yes. Documents live where they already live — your mailbox, your DMS, your drives. What we hold is the deal memory, and it's exportable. Nothing is designed to be hard to leave.

What does it cost?

Pricing is on request during the private beta, and it is not priced like the US incumbents. See pricing or ask directly.

Can we rename the agents?

Yes — Harry and Jeanne are defaults. Most firms rename them to something of their own.

When you want to check in

One platform to rule them all.

You don't live here — your agents work inside the tools you already use. This is just the calm overview, for when you want to see everything at a glance.

The LawyerTools workspace — the morning-brief dashboard, with the agent roster open on the right.

·The call Jeanne booked, starting now.

Your deal team,
always on.

Sarah didn't book it, didn't chase anyone, didn't check a calendar. That is the whole product.

✓

You're on the list. We'll be in touch.

100 places · selection in progress

By requesting access, you consent to LawyerTools contacting you about the private beta. Your email is processed under our Privacy Policy, kept until the beta ends or you ask us to delete it, and never shared.