The emails
Who agreed to the 12-month cap, and why? It is in a thread from two years ago.
For law firms
Every matter, on one record.
Emails, drafts and negotiation history stay with the matter, not in one partner's memory. AI coworkers review redlines against your playbook and cite the clause, the email and the precedent. Nothing goes to the other side until a partner signs off.
Reads only what you may read Partner sign-off Sources on every answer Files stay on your Mac
The problem
A matter lives in a hundred emails and one partner's memory.
Positions, drafts and the reasons behind them are spread across inboxes and desktops. When people move on, the context goes with them.
The drafts
Agreement_v5_FINAL_2.docx is on someone's desktop. Nobody is sure which markup went out.
The memory
An associate leaves, and four years of matter context leave too.
What you get
Built for how a firm runs its matters.
One channel per matter. The redlines, the questions, the answers and the sign-offs stay together, and the firm's positions grow from them.
Redlines against your playbook
Ask in the matter channel. The agent compares every changed clause with your playbook and lists the off-playbook ones, with fallbacks.
Answers that cite sources
Every answer names the clause, the email and the earlier agreement it used, so you can check it before you rely on it.
Reads only what you may read
An agent reads as the person who asked. A matter you cannot open stays out of its context and out of its answers.
A partner signs off
Anything sent to the other side waits for a partner. Approve in the workspace or in Slack. Routine work runs without approval.
Matter files, synced
Agreements, notes and trackers open in the matter. A folder on your Mac syncs both ways, and a conflict keeps both copies.
Positions that compound
Negotiation threads become firm positions, such as your stance on liability caps. Every line points to its source.
Plan your team in plain words
Describe your practice. Review the team it proposes.
Chief of Staff asks up to three questions, then proposes AI coworkers and channels. You edit or untick each role before anything is created. Legal roles carry a fixed guardrail, and every new agent starts restricted.
An example team for a commercial practice. Your proposal follows the work you describe.
- Contract ReviewerCompares redlines and incoming NDAs with the firm's playbook.
- Precedent ResearcherFinds how the firm handled the same clause before, with sources.
- Matter ClerkFiles drafts and correspondence to the matter and keeps its notes current.
The record
Everything lands on one record.
Every message, run, file change and approval is one event on an append-only record. It shows who did it, person or agent, what was approved and by whom.
- 09:15 · #matter-harbor-supplyhuman
Priya asks Contract Reviewer to check Kestrel's redline against the playbook
- 09:18 · run · Priya's MacBook Proagent
Contract Reviewer compares 14 changes. 3 are off-playbook
- 09:24 · threadhuman
Priya answers: a 12-month cap is fine if the carve-outs stay
- 09:38 · gate · markup to counselgate
Markup parked. Sending to Kestrel's counsel waits for a partner
- 09:40 · approvalhuman
Jonas approves. The record keeps who approved, and what he saw
Who agreed to what, and why
Search the record for a clause and find the message, the draft and the approval behind it.
Know what each matter costs
See reviews and agent spend per matter before you bill it, across every agent and model.
Private beta
Run one matter through Mobtasks.
Bring one live matter and your playbook. We'll set up the team with you during the private beta.