03 / Workflow Agents
Workflows that finish
when the work does.
A matter's journey from file to bundle, a contract's life from request to archive, and the approvals in between — each step completed by the event it describes, each due date computed from a fact someone gave, with the rule stated.
Get started →Illustration · Contract lifecycle run
01
Request submitted
Vendor agreement · form complete
Done
02
Triage by your rules
Legal + privacy review · each names its rule
Done
03
Draft and negotiate
Finished when the redline round was generated
Done
04
Approval
Gate · decided by a company admin
Waiting
05
Monitoring
Renewal, amendment, termination offered as steps
Queued
Key facts
- ✓A step finishes itself when the event it describes happens — a document read, a draft checked, a redline round generated, an approval given.
- ✓A due date exists only when a rule computed it from a fact a person gave, and it carries the sentence naming that rule.
- ✓A gate is decided by a role you set; a client step is completed by the client, through the client portal.
- ✓Deal Desk approval chains route a contract by role and by value thresholds you set — none is assumed.
- ✓Custom agents chain AI calls, data queries, HTTP calls and notifications; they are enabled by arrangement, not by a published plan.
- ✓Agent schedules are not dispatched yet — see Scheduled runs, which says so plainly.
What runs
The workflows
behind the work.
Matter Journey
Open the file → read it → review contradictions → triage gaps → ask the client → research → draft → review → bundle. Stages finish on their own.
Hearing preparation
Bound to a hearing; a brief over the matter's facts with sentence-level support, and the documents since the last hearing.
Contract lifecycle
Request → triage → draft → approval → monitoring, with renewal, amendment, breach and termination offered as steps.
Contract requests
A request form per contract type; triage by your rules, an owner with a task, and the lifecycle started from it.
Approval chains
Ordered steps by role and minimum approvals; every decision records who, when and why.
Legal intake
Requests captured, triaged, routed to a person and promoted into a matter — from a typed request or a public form.
Human review of AI output
Hold AI work above a risk floor until an owner or admin approves it. Off by default.
Custom agents
Your own automations, run on demand or from the agent's email inbox. Enabled by arrangement.
The work finishes the step.
Not a checkbox.
Workflows run on every plan.
Get started →Questions
Frequently asked questions
What runs here today?
The workflow engine: the Matter Journey and hearing preparation on a dispute, the contract lifecycle from request to archive with its renewal, amendment, breach and termination steps, the Contract Request Center, and Deal Desk approval chains. Steps finish themselves when the work they describe happens.
Where do due dates come from?
Only from a rule applied to a fact a person gave, and every due date carries the sentence naming the rule. There is no template offset that invents a date, and no model sets one.
Is there a library of pre-built agents?
Not on this product yet. Custom agents — your own multi-step automations of AI calls, data queries, HTTP calls and notifications — exist, and are enabled for an organisation by arrangement rather than by any published plan.
Can workflows run on a schedule or post to Slack?
No. A workflow step finishes on an event in the product, and an agent runs on demand or from its own email inbox. There is no agent scheduler, and nothing in the product posts to Slack.
Is my data secure?
Data is encrypted at rest with AES-256 and in transit with TLS 1.2 or later. Where it is stored, and which sub-processors receive content, is set out on the Security page and in the DPA.