The matter file is assembled by an agent. The advice stays with your people.
Intake, conflicts searches, document review and billing. Agents carry the work between your matter system, the document store and email. A lawyer or adviser approves every change to a client document.
A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.
The work around the advice
We build AI agents for law and advisory firms that take on the work around the advice: opening a matter, searching for conflicts, marking up a draft and putting the bill together. Today a fee earner or an assistant carries each of those between the matter system, the document store, email and the time records.
The agent reads, searches, drafts and routes. Your lawyers, advisers and conflicts staff decide.
- Each agent signs in as itself and works on one matter at a time.
- Every proposed change to a client document waits for the responsible lawyer.
- Client identifiers you list are removed from content before it leaves the firm.
An agent on Ares does not give legal advice, and we do not build one that does. If your document system already has an assistant your people use, keep it. If it can connect over A2A or MCP, it can enrol on Ares and work inside the same limits. The assessment confirms whether yours can.
One new matter, from the intake email to a cleared conflicts check.
The task: open a matter for a new client and check it for conflicts. This workflow is designed and has not run yet. The contract review in the sandbox shows the same guarantees on a built workflow.
- 01In-house tool
Receive a credential for this intake only. It expires when the matter is opened or declined.
- Who approves
- No approval on this step
- On the record
- credential issued · this intake only
- 02Email
Read the intake form and the covering email from the prospective client.
- Who approves
- No approval on this step
- On the record
- read-intake · allowed
- 03In-house tool
Search past and current matters for the client and every other party named.
- Who approves
- No approval on this step
- On the record
- search-parties · allowed
- 04Documents
Open the file of a past matter that one search result points to. Matter files are outside the permission for intake, so the step is refused.
- Who approves
- No approval on this step
- On the record
- open-matter-file · refused · outside permission
- 05Office suite
Draft the conflicts memo: each possible match, where it was found, and why.
- Who approves
- No approval on this step
- On the record
- draft-memo · allowed
- 06In-house tool
Open the new matter. The step waits until the conflicts reviewer approves it.
- Who approves
- Conflicts reviewer
- On the record
- open-matter · approved by conflicts reviewer
In short
- Will an agent tell a client what the law says?No. It prepares memos, mark-ups and lists for your people. Advice to a client comes from a lawyer or an adviser, outside Ares.
- Can an agent read matters it has no reason to see?Each job gets a permission for the records it needs. A request for any other matter file is refused, and the refusal is on the record.
- Who changes the wording of a client document?The responsible lawyer. In the workflow we design, the agent proposes each change as a marked edit, and the document does not change until that person accepts it.
- What stops client names from leaving in a summary?Outbound content is checked before it leaves the firm. The identifiers you list are redacted, and the record names what was removed.
Workflows for law and advisory firms.
Each card carries its state. The built workflow runs in the sandbox today.
- Built
- We have run it.
- Designed
- The steps and approvals are designed. It has not run yet.
- On request
- We scope it with you before we design it.
- Built
Contract review with redaction on the way out
Agents flag the indemnity and termination clauses and draft a summary for the client. Client identifiers are removed on the way out, a fetch to an outside page is refused, and counsel reviews the uncapped indemnity.
Run it in the sandbox - Designed
Matter intake and conflicts check
The steps above: the intake read, the parties searched, a matter file refused, the memo drafted, the new matter held for the conflicts reviewer.
- Designed
Document review with a person on every change
The agent compares a draft with your standard terms and proposes each change as a marked edit. The responsible lawyer accepts or rejects every one.
- Designed
Draft bills from time entries
The agent collects the time entries for a matter, checks them against the engagement terms and lists each entry outside them. The billing partner approves the bill before it goes out.
- Designed
Invoice matching for the firm’s own purchasing
Supplier invoices matched to orders and receipts. Your finance team approves each adjustment.
See the workflow - On request
Engagement letters from your templates
- On request
Client questionnaires on security and data handling
Where the agent stops
The line is the advice. An agent can find the clause, compare it with your standard terms, list the past matters that name the same party and total the hours. It does not decide what a clause means for the client, whether a conflict can be waived, or what to recommend.
Ares does not decide what is confidential or privileged either. Your firm sets which records each job may reach, and Ares enforces that list on every call. The record shows what each agent read, what it was refused and who approved each step. Your risk partner can check it offline, without us.
The five guarantees
Every workflow on this page carries them. Each one has a limit, and we state it.
- 01
Each agent can do only what it was allowed to do, for that job.
The limit
Permissions are only as good as the rules you approve.
- 02
Sensitive steps go to a person.
The limit
You decide which steps are sensitive.
- 03
Documents are inspected before an agent sees them, and answers are checked before they leave.
The limit
Filters cover stated patterns and languages.
- 04
Every decision is recorded, including refusals, in a record an outside party can check.
The limit
It shows what agents did, not whether a business rule was wise.
- 05
It can run in your building, on one small machine.
The limit
Local models differ from the largest cloud models.
What it does not do
- It gives no legal, tax or financial advice. A qualified person in your firm advises the client.
- It does not decide a conflict. It lists the possible matches, and your conflicts reviewer decides.
- It does not decide what is confidential or privileged. Your firm sets the records each job may reach.
- Only the identifier patterns you list are redacted. Ares does not judge what a recipient may see.
Assessment, pilot, production.
Each step has a fixed scope and ends with something you keep.
- 01
Workflow assessment
A look at one process: where an agent can act, which steps go to a person, what a wrong action would cost, and what the data allows.
- What you get
- A short, paid look at one process, with your process owner.
- What you keep
- A written scope and a price for a pilot.
Fixed price, quoted after one call.
- 02
Pilot workflow
One workflow on your systems, supervised, with the record on from the first run.
- What you get
- One workflow at a fixed scope, with your people approving the sensitive steps.
- What you keep
- A working workflow and a measured result.
Fixed price, quoted after one call.
- 03
Production and run
The workflow in production on Ares, on your hardware or hosted in your country.
- What you get
- Support, and the next workflows.
- What you keep
- The workflow, and the record of every decision it made.
Recurring fee for operation and support.
Who else decides
Questions and answers
Tell us about one workflow.
Name one task your fee earners carry between systems before the advice starts. We will say whether an agent should do it, and what the first step costs. The first step is a workflow assessment. Fixed price, quoted after one call.
A senior member of the team replies within two business days.