AgentWorks for Legal

The agent drafts. A lawyer decides.

Contracts to review, questions from the business, the precedent somebody wrote two years ago. A team of agents does the first read and the search. The judgement and the signature stay with your lawyers.

Law firms and in-house legal teams in companies of roughly 10 to 250 people.

The work that comes back every week.

First read of a contract

Which clauses deviate from your standard, and how far.

Intake of requests

Who is asking, what kind of matter, by when. Often buried in an email thread.

Finding the precedent

The clause, memo or letter you know exists somewhere on SharePoint.

Everyday GDPR questions

Can we share this list, do we need a DPIA, what goes in the register.

Supplier due diligence

The same question set for every new vendor, adjusted each time.

Your team

A team of agents, each with one job.

Each agent does one thing well, in your own apps, and asks before it sends or changes anything. You give them their rules. They share the board with your people.

Intake handler

Called by the workflow

Reads new requests and contracts: party, contract type, deadline, who asked. Puts them on the board.

Reads and logs on its own. It doesn’t reply to the requester.

Outlook

Contract reviewer

Called by the workflow

Compares clauses with your playbook and standard terms and flags deviations, with the clause quoted.

Writes a review memo only. A lawyer decides what to accept.

SharePointReady-made

Precedent finder

You ask in chat

Finds earlier contracts, memos and letters across SharePoint, OneDrive and Drive and summarises them.

Read-only. Restricted sources are cited but open only for those allowed.

SharePointOneDriveGoogle DriveReady-made

GDPR desk

You ask in chat

Answers everyday GDPR questions from colleagues and says what to check next.

Explains and points to sources. Not legal advice; it hands hard questions to a lawyer.

SharePointReady-made

Working together

Contract in, review memo out

Starts when A new email arrives in the legal mailbox, for example contracts@, or a colleague fills in the request form.. One workflow hands the work from agent to agent, and stops where a person needs to decide.

  • A lawyer reviews every memo before anyone outside legal sees it.
  • What to accept, negotiate or refuse is the lawyer’s decision. The agent only flags.
  • Restricted knowledge sources are cited in answers, but only people you allow can open them.

The apps it works in

OutlookSharePointOneDriveGoogle DriveMicrosoft Teams

Document management and practice systems such as iManage, NetDocuments, Clio or BaseNet, and e-signature tools, have no ready connector. Reach them through the HTTP request step if they have an API, an MCP server, or a webhook that starts a workflow.

All 40 apps

What you need

On Free you can try this with up to 3 agents, 2 workflows and one email trigger. The full team, live sync of your SharePoint or OneDrive documents and team boards need Business.

Pricing

The agent drafts and flags; a lawyer decides. Its output isn’t legal advice. Client files are confidential, so share agents and knowledge bases only with the people on the matter. All models run in the EU.

Questions

AgentWorks for Legal

Runs in the EU. Every action that changes something asks first.

No. It quotes each deviation from your playbook and suggests a position. A lawyer decides, and the memo goes out only after that approval.