Product

An Agent for Every Matter, Built Your Way

by Prasad Hemakumara11 October 20266 min read

Every investigation team has a method that took years to build. We built Workflow Agents so a team can write that method down once, in plain language, and run it on every matter it opens. There is no code to write and no feature request to wait on. The method the team already follows becomes the agent.

How Your Team Works

A supplier-payments review at one firm looks different from the same review at the next. Each team has its own tests, its own thresholds for what counts as unusual and its own way of writing a finding. That judgement is a large part of what clients pay for, and it is what we think an agent should carry.

So we built an agent that the team shapes. A Workflow Agent is your sequence of steps, your tests and your standard of evidence, written once and carried out by Donna with everything underneath it: processing, review, table extraction, fund tracing, chronologies and a citation for every claim.

  1. Your processWritten once, in plain language.
  2. Workflow AgentYour steps, the matter’s documents and Donna’s tools.
  3. Matter A, Matter B, Matter CEach run grounded and cited.
  4. Every run ends at your approval.
Written once, run on every matter. A process written once in plain language becomes an agent. Each run is grounded in that matter's own evidence, cites its sources, and ends at your approval.

Building an Agent

You build a Workflow Agent the way you would brief a capable analyst. You describe the steps, name what to look for and say what good output looks like. For example: “Test every vendor payment for duplicates, round amounts and invoices split under the approval limit. For each hit, find the emails that approved it. Summarise for the client in plain terms, with the evidence linked.” Those words are the build itself. You can also describe the job and have Donna draft the steps for you to refine. In practice, refining an agent means running it, reading the output and adjusting the wording.

Edit workflow agent

NDA Review & Summary MemoSaved···
Step 1·Ask User

Ask which NDA should be reviewed, and whether there are any focus areas: confidentiality scope, term, carve-outs, permitted disclosures, remedies or governing law. If none are given, review all standard NDA provisions.

Step 2·Examples

Examples

Add precedents, templates, or past outputs so Donna knows your standard.

NDA review memo · Harbour Foods (precedent).docx
Step 3·Prompt

Review the NDA against the firm’s playbook. Record the parties, the term and survival period, the definition of confidential information and any carve-outs. Flag anything outside our positions, then draft a one-page summary memo for the client in the precedent’s format.

The builder as it appears in Donna: an agent written as steps.

Running Inside the Matter

A Workflow Agent runs inside a Space, against that matter’s own evidence and under that Space’s permissions. It reads only what the person running it is entitled to see, and its claims carry citations that open the exact page, row or message. Anything that would change the matter stops at an approval step first. Every run leaves a full audit trail of each step, each tool call, each source consulted and what the run cost.

Sharing and Control

  • Agents sit in the Library. Workflow Agents live in the Library alongside your templates and report formats, where they can be foldered, starred and found in one search.
  • Running an agent is separate from editing it. When you share an agent with the team, they can run it and read it. Changes stay with you, the editors you name and your admins, so the method only changes when someone decides it should.
  • Any Space can run it. Pick a Space, run the agent and the work arrives in a thread. The hundredth matter gets the same method, applied as carefully as the first.
  • A stage can run it for you. Attach an agent to a stage of your matters, and each matter that reaches that stage gets the same work, ready for your review.

Donna

Workflow Agents

Supplier Payments Tests

Fraud

Map Mailbox to Notice Categories

Regulatory

Build the Notification List

Breach response

Trace Funds Across Accounts

Financial crime

Privilege First Pass

Review

Duplicate and Split Invoices

Fraud

Sensitive Data Assessment

Breach response

Key Document Chronology

Disputes

Related Party Payments

Financial crime

QC Sample and Recall Check

Review

Privilege Schedule for the Notice

Regulatory

Conflict of Interest Scan

Integrity

A few of the agents investigation teams build first. Every one is someone’s own method, written down.

What Teams Build First

Most teams start with the work they repeat on every matter: the payment tests they always run, the mapping of a mailbox to a regulator’s notice categories, the steps that turn a breached data set into a notification list, or the trace that follows money from account to account. Each takes about an afternoon to build as a Workflow Agent, and every matter after that inherits it.

Where This Leaves Us

The main point is about who writes the method. With Workflow Agents, your team decides how it investigates, and Donna runs that method on every matter, with sources and approvals built in. The expertise stays with the people who built it, and Donna carries it out.

See Donna on your next investigation

Bring a matter. See the agents trace the money, review the mailbox or build the notification list, every finding cited.

Country *
Organisation type *
Team size *
How did you hear about us?