Legal Operations. Agentic operations for law-firm intake, discovery prep, and conflict-check workflow.
We ship to law firms and in-house counsel teams whose administrative surface — intake summarization, discovery first-pass review, conflict-check workflow, calendar reconciliation — consumes hours that should belong to client work. The agent reads the matter file, drafts the intake summary, surfaces conflict candidates against the firm's matter history, and prepares discovery batches for paralegal triage. The agent is privilege-aware by construction, never asserts legal advice, and never sends a communication without a partner's signature.
- 01Privilege-aware refusal lanes.
The no-list is drafted with the firm's managing partner: no advice, no privilege-piercing summaries, no third-party disclosure without an explicit gate.
- 02DMS integration over re-architecture.
We bind to iManage, NetDocuments, SharePoint, or whatever the firm already runs. Documents stay in the system of record; the agent reads with audit-stamped provenance.
- 03Conflict-check as a continuous query.
Conflict candidates are surfaced against the firm's matter history with banded confidence and a paralegal-review gate. The agent flags; the managing partner clears.
- 04Drafted, never filed.
Every intake summary, discovery memo, and client communication is drafted by the agent and queued for partner or senior-paralegal sign-off.
Counsel. Click through it.
The console below is a composed view of the Legal system we ship. Tab between views, click rows to inspect agent reasoning, accept or override the proposed action. Every state change is local to your browser — no real client data, no remote calls — so you can poke without consequence. This vertical is still pre-publication; the demo is the discipline we'd bring on day one.
Live cases land here as clients grant publication permission.
The practice ships into legal operations today. Engagement details are published one-for-one as clients accept publication. The discipline above is what the practice applies regardless — see the build-discipline section for the spine, and your shape, of every system we ship.
No live case is published in legal operations yet — by design. The practice publishes only with explicit client permission. Until a case is published here, the right artifact is the one above: the interactive system we build, and below it, the spine + customization axes that bend to your business.
Open the conversationHardened scaffold. Yours to shape.
The fundamentals of every system we ship are fixed by discipline. Everything above them is built around your business — your roles, your refusal lanes, your integrations, your shape.
Always there
Six engineering fundamentals that ship on every engagement, regardless of industry.
- 01Refusal lanes before features.
We write the no-list before the yes-list. The boundary the system will never cross is documented and audited before the first feature ships.
- 02Operator in the loop on every decision.
The agent reads, drafts, and routes. A senior human takes every high-stakes action. The integrity of that posture is the metric we publish.
- 03Replayable event sourcing.
Every draft, every flag, every state transition is reconstructable from an audit-stamped event log. Bugs are diagnosable. Decisions are explainable.
- 04Row-level security on every table.
Postgres + RLS, applied without exception. Anonymous access is gated, client access is scoped to client rows, operator access is audited.
- 05Audit log streaming on day one.
Every read, write, and refusal is appended to an immutable log keyed to your senior operator — your security officer, your toolpusher, your managing partner.
- 06Observable from day one.
Structured logging, error-tracking, telemetry, weekly digests. The system explains itself before someone has to investigate it.
Built around you
Seven customization axes. Concrete, not cosmetic — every axis is a token, a policy, an integration, an audit.
- 01Identity & branding.
Your logo, palette, microcopy, sender domain. Brand tokens — not theme pickers — so contrast and accessibility never break under your colors.
- 02Role taxonomy.
Clinician, toolpusher, paralegal, dispatcher — your roles, not ours. The RLS scaffolding bends around the role names you actually use.
- 03Refusal lanes.
Your no-list, signed off by your senior operator. Versioned. Auditable. Replayable against any past conversation.
- 04Integration surface.
We plug into the systems you already run — EHR, rig event bus, DMS, TMS, payor portal — never the other way around. Inbound webhook, outbound idempotent on retry.
- 05Workflow gates.
Approve, override, escalate. Gated by your roles, sequenced to your operations rhythm, never to ours.
- 06Data shape.
Your schema, your types — not a generic JSONB blob trying to fit every customer. Migrations versioned, idempotent, single-transaction.
- 07Audit policy.
Who sees what. How long it is retained. How it exports to your compliance officer when an auditor asks. SOC2, HIPAA, state-bar, IADC-aligned where the industry requires it.
- Logo<your-logo.svg>
- WordmarkCounsel — Intake
- Accent● locked to AA contrast· token-bound, never hardcoded
- Sender domainsend.your-firm.law
- Managing partnerRW· refusal: no advice
- AssociateRW· refusal: privilege-aware
- ParalegalRW· draft + triage
- Client (portal)R· matter-scoped
- DMSiManage · OAuth + webhook
- Court recordsPACER · authenticated read
- Conflict-checkmatter history · banded· paralegal-review gate
- Retention10 years
- Officerethics@your-firm.law
- Exportstate-bar aligned
- Privilege logauto-redaction
Same discipline. Different domain. Always your shape.
Legal Operations is the room. Agentic AI is the capability we bring into it.
Be the engagement that opens this vertical. We’ll send back the brief.
A working session, a written scope, a clear success criterion. Then a portal URL, an intake, and the kickoff row.