Oct 12, 2026 · 8 min read
Ommnium for Legal Ops
One Agent per legal workflow, working in your Channels. They prepare, triage and draft; counsel decides and a person sends.
Lea Brandt runs legal operations for the Ruiz & Okafor studio, and Sam Okafor is counsel. Legal questions arrive in Slack from sales, often the same question with a different answer each time. The review tracker drifts out of date. Counsel 1:1s start with digging through last week's threads, and the weekly update gets rebuilt from scratch.
The fix is not one Agent that does everything. It is one Agent per workflow, each with its own memory, all in Channels where Lea and Sam can see the work.
The team
| Agent | Its one job | It never |
|---|---|---|
| Legal Ops Lead (lead) | Counsel 1:1 prep and the writeback afterwards, the legal templates inventory, the weekly update, analysis of contract-system exports | Sends, files or signs anything; changes Notion only after a yes |
| Legal Intake | Triages legal asks in Slack, links earlier guidance, flags answers that disagree, keeps the review tracker fresh | Gives legal advice on its own |
| Pushback (built-in) | Skeptical review of controls and evidence gaps, citing sources | Approves anything |
| Vendor Spend (optional, Library) | SaaS spend and renewal windows from Ramp and bills | Sends a counter-offer; it drafts |
| Contracts & Portals | Looks things up in your contract system, and fills security questionnaires and vendor portals from approved answers, in its browser | Submits or moves a document without a preview and a yes |
The people: Lea runs the desk. Sam answers the legal questions. Ana Ruiz sells, and asks them.
People and Agents work in the same Channels. When Sam answers in a thread, Legal Intake sees it and links it the next time someone asks.
Set it up
- Create the Project. Click the + next to Projects in the sidebar. Name it
legal-opsand click "Create project". - Add Channels. Project ⋯ → "New channel". Create
intake,reviewsandtemplatesas "Ongoing", "Stream", "Private". Agents read a Channel's "Description" on every turn, so put the brief there:#intake: Legal asks from Slack, sorted and deduplicated, with links to earlier answers.#reviews: Review tracker rows with deal context. Nothing in a system of record changes without a preview and a yes.#templates: New, changed or stale legal templates.#general: right-click it → "Channel settings…" → "Add a description": "The weekly picture, decisions and counsel 1:1 prep." → "Save changes".
- Create three Agents. Agents → the + card → "Create agent". Name them "Legal Ops Lead", "Legal Intake" and "Contracts & Portals", and paste each one's job and "never" line from the table into "Agent instructions". Admins: under "Advanced", set "Ownership" to "Org — uses shared organization credentials".
- Add Pushback. From the same chooser, pick "Pushback". Its instructions are ready.
- Optional: vendor spend. Library → search "SaaS spend" → "Install agent". Name it "Vendor Spend" in the install dialog. It comes from an outside creator, so read its instructions first.
- Make a team. Agents → "Agent teams" → the "New team" card → "Create team". Name it "Legal Ops Team", select the Agents, and add "Team instructions": "Legal Ops Lead leads and routes work by @mentioning a teammate in the thread. Read freely; propose every change to a tracker or system of record on a card. Drafts only: a person sends. Stay quiet when nothing changed."
- Deploy it. Project → "People & Agents" → "+" → "Deploy team". Pick the team and all four Channels → "Deploy to 4 channels".
- Connect tools. Library → "Marketplace" → "Slack" → "Connect", then "Google Sheets". Add Notion, Google Drive, Granola and Gmail if you use them. Under "Enabled in", click "Enable in…" and choose the Project.
- Salesforce needs your own Salesforce app. The "Set up Salesforce" dialog asks for its values and shows a "Redirect URL for your Salesforce app" to copy.
- Set up Slack events. Send the triage prompt below. Slack events need only a connected Slack account; there is nothing to paste.
- Sign in to portals once. Contracts & Portals works in your contract system and vendor portals in its browser. You sign in there yourself, including any two-factor step; Agents never type passwords. Keep it to previews: it shows what it would submit, and a person says yes.
- Save the automations switched off. Use the prompts below. Then open "Automations", flip each switch and click "Turn on".
What happens each day
Memory that grows
Agents remember what they learn, for themselves and for the whole Project. A live demo with sample data; try it.
- Monday 09:00 Legal Intake posts the open-items digest in
#general: open "Needs Legal" rows by age, with links. An empty queue gets one line. - Monday 09:40 Ana asks in a Slack sales channel which paper to use for a deal. The Slack automation wakes Legal Intake quietly. In
#intakeit posts the ask, Sam's earlier answer, and a flag that two past answers disagree. Sam settles it in the thread. Intake drafts the reply to Ana as a Slack draft card, and Lea clicks "Send message". - Monday 10:05 Legal Intake adds deal context to that tracker row. It shows the change and asks on a question card before writing.
- Monday 11:15 Someone posts in a retired channel. Legal Intake drafts the standard redirect as a Slack draft card. Lea sends it.
- Tuesday 16:00 The Lead posts Sam's 1:1 agenda in
#general: open questions, contradictions across channels, blockers and wins. After the 1:1, Lea asks it to write the decisions back to Notion. It lists the changes and asks on a question card. - Wednesday Sam asks @pushback to challenge a controls document. It posts the gaps, each with its source.
- Wednesday 14:00 A vendor's security questionnaire arrives. Contracts & Portals fills it in the vendor's portal from approved answers and posts a preview with a question card. Lea checks two answers with Sam, then says yes, and it submits.
- Thursday 15:00 The Lead's weekly update arrives as an email draft card. Lea edits it and clicks "Send email".
Copy these prompts
Standing rules, once, in #general:
@legal-ops-lead Remember for this Project: verify every source, make no assumptions, and use plain language. An ask is "Needs Legal" when [your rules]. The review tracker is [sheet link].
Slack triage, in #intake:
@legal-intake Watch these Slack channels for legal questions: [channels]. Look for mentions of you and words like paper, BAA, entity or redline. For each ask, link the earlier guidance and flag answers that disagree. Raise only what nobody has answered. Set up Slack events if needed, and save it switched off.
Tracker refresh, in #reviews:
@legal-intake Every hour on weekdays from 8 to 6, compare the review tracker with new asks in #intake. Raise only new "Needs Legal" rows and answers that conflict. Propose row changes on a question card before writing. Run it quietly and save it switched off.
Counsel 1:1 prep, in #general:
@legal-ops-lead Every Tuesday at 4 pm, prepare Sam's Wednesday 1:1: open questions, answers that contradict each other, blockers and wins, from Slack, Notion and our call notes. Skip weeks without a 1:1. Save it switched off.
A one-off analysis:
@legal-ops-lead I uploaded our contract-system export to the Project's Computer. Measure review cycle times and how long requests waited on the requester, Legal and the other side. Write a one-page memo as a file, with plain numbers and sources.
Rules that keep it healthy
- One Agent per workflow. Prep, triage and review stay separate, each with its own memory.
- Drafts first. Every Slack reply and email is a draft card a person sends.
- Reads are free; writes wait. Trackers, Notion and systems of record change only after a yes on a card.
- Standing rules live in Project memory. Every Agent in the Project uses them.
- Prep on a schedule, research on demand. Ask for research when you need it.
- Quiet when nothing changed. Hourly is usually enough; every 30 minutes costs twice as much.
What it can't do yet
- Ironclad or Docusign connectors. There are none. Contracts & Portals works in them in its browser instead, and uploaded exports work for analysis.
- One-click Salesforce. It needs your own Salesforce app.
- Lock a connector action. There are no per-tool approval rules. The question card is how an Agent asks.