Skip to content
home
Law firmsFor the managing partner or firm administrator

Firm knowledge that outlasts the associate who had it.

Clients, matters, intake rules, and your own precedent bank go into one map. The assistant takes details and hands the caller to a person. It does not give advice.

Nothing built here yet

Nothing is built for a law firm yet. This is the system I would build.

The bottleneck

Intake is the whole business, and the same matter details get re-keyed into three systems after it.

What it would do

  • Would take the caller’s details and the matter type, then hand them to a person. It would not advise.
  • Would run a new name against your client and matter list before intake goes further.
  • Would find the clause in your own precedent bank and cite the document and page.
No published build here yet — pattern proven on my own hotel
01 / Ontology

Your business’s shared memory

Every answer shows you where it came from.

Illustrative model — not a client record
Entity / Root

A 4-partner law firm

Fields
  • Clients it acts for
  • Matters open now
  • The intake and conflict rules
  • The systems it records into
Used by
  • Intake
  • Conflict Screen
  • Research
  • Back Office
  • QA
Traceable to source

practice record traces to client and matter map

  • A 4-partner law firm has Clients. Read or written by Intake, Conflict Screen, Back Office. Traceable to client list, related parties.
  • A 4-partner law firm has Matters. Read or written by Intake, Conflict Screen, Research, Back Office. Traceable to matter record, responsible lawyer.
  • A 4-partner law firm has Billing. Read or written by Back Office, QA. Traceable to billing record, linked matter.
  • A 4-partner law firm has Conflict & retention policy. Read or written by Conflict Screen, Research, QA. Traceable to conflict policy, escalation trigger.
  • A 4-partner law firm has Intake SOPs. Read or written by Intake, Research, QA. Traceable to intake SOP, disclosure script.
  • A 4-partner law firm has Staff handoff. Read or written by Intake, QA. Traceable to handover note, open intakes list.

Every edge is a stored relation. Every answer cites the record it came from.

02 / Use cases

Every job ends in a record you can check

The trigger, who works it, what it does, and what it leaves behind.

Illustrative model — not a client record

Example composition for law firm. Nothing here is a client record. The retrieval and messaging parts run on my own hotel today; the rest is a design.

The 7pm intake

  1. Step 1 · Trigger

    A prospective client calls after hours

    Voicemail is the current answer, and the next firm on the results page is one tap away.

  2. Step 2 · Agents

    Intake and Conflict Screen would work it

    Intake would disclose that it is an AI assistant, then capture the caller, the matter type and the urgency. Conflict Screen would run the name against your client and matter list. A hit would stop the intake and notify a lawyer. Call handling is in development.

  3. Step 3 · Action

    A clear name would be booked or bridged

    Back Office would enter the matter details once, with a change log, so nobody re-keys them into a second system.

  4. Step 4 · Trace record

    What you would be able to check

    The transcript, the conflict result and what it was checked against, with a note that no advice was given.

    Example record — illustrative, not a client log
    source:
    client and matter list → conflict check
    policy:
    conflict and retention policy
    agent:
    Conflict Screen
    human_review:
    a lawyer reviews every hit
03 / Proof

No published build here yet — here’s the closest one

There is no law-firm card here, because I have not built one. The closest published build answers only from an approved set of documents, names the record behind each answer, and raises a human when the answer is not in the material. That behaviour is the point of a precedent lookup.

Why this one

Answers only from the approved material, cites the record, and stops when it does not have one.

Nothing on this page is running in this vertical yet. The fastest way to find out whether it should be is to bring me one job and watch me map it.

Book a call (opens in a new tab)
CS-02Evidence label: Live / visible

Guests get answered in four languages, out of the house rules.

  • Hotel
  • Next.js · Convex · retrieval over an approved knowledge base
  • Public route re-verified 4 Sep 2026

MY OWN 50-ROOM PROPERTY — FOUNDER-OWNED, NOT A CLIENT ENGAGEMENT

Situation
Guests ask the same handful of questions in Korean, English, Japanese and Chinese. Parking, late check-in, luggage, often at hours when nobody is at the desk. Before this they got whatever the person on shift remembered.
What I built
A guest chat page for the hotel that answers only from an approved Korean knowledge base and shows which record the answer came from. When the answer is not in the base it raises a request for a human instead of guessing. Behind it sits knowledge-base tooling for the people who own the answers.
What it does now
The public guest chat page is deployed and reachable. I re-checked it on 4 September 2026 before writing this card. The newer knowledge-base and conversation-review tooling is built and tested locally and is not deployed yet. There is no current production answer-quality measurement, so no accuracy figure appears here.

artifact: The public chat URL below. Re-checked 2026-09-04: it served the hotel chat page with its Korean question field.

Open the live page (opens in a new tab)

The builds these parts come from, each with the label it earned, are on one page. See the case studies.

What I promise

Every answer shows the record it came from

I build the map out of your own documents, run the system on my own business before it goes near yours, and hand over the trace log with it. If an agent cannot show you where an answer came from, it does not ship.

What I promise

  • The map is built from your own documents and records, not from a template.
  • Every answer an agent gives names the record it came from.
  • You get the trace log with the system, and it stays yours.

What I don't

  • A specific number of bookings, a revenue figure, or a result.
  • Anyone who guarantees you revenue on a system they haven't run in your business yet is guessing.

How you check

  • Open the record an answer cites and read it yourself.
  • Every claim on this site carries an evidence label.
  • Watch it run on a matter you pick before it touches anything live.
04 / Other verticals

The other two run on the same parts.

Your own records, a small team of agents that works from them, and a trace on every answer. What changes between these pages is the nouns, and which of them has something running behind it.

All three verticals
05 / Next step

Start with intake. One step, mapped on a 30-minute call.

Walk me through what happens to a 7pm caller today. I will show you where each detail would land.

Book a call (opens in a new tab)
30 minutes · no deck · we look at your actual workflow