Skip to content
home
Accounting firmsFor the partner who owns busy season

Busy season should run off a checklist, not off memory.

Clients, engagements, documents, deadlines, and your checklist for each one go into one map, and a small team of agents works from it. The mechanism is the same one running on my own hotel. The vertical is not.

Nothing built here yet

Nothing is built for an accounting firm yet. This is the system I would build, and this page is written that way.

The bottleneck

Half of busy season goes on asking the same clients for the same missing statement, while new work calls in behind it.

What it would do

  • Would track what is outstanding per client, send the reminder, and log what arrives.
  • Would answer routine client questions from your engagement letters and prior-year files, with the page shown.
  • Would put a new-client call in front of a partner while the prospect is still deciding.
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 6-person accounting firm

Fields
  • Clients it files for
  • Engagements in flight
  • The checklists it works from
  • The systems it files into
Used by
  • Intake
  • Document Chaser
  • Research
  • Back Office
  • QA
Traceable to source

practice record traces to client and engagement map

  • A 6-person accounting firm has Clients. Read or written by Intake, Document Chaser, Research, Back Office. Traceable to client record, entity type field.
  • A 6-person accounting firm has Engagements. Read or written by Document Chaser, Back Office. Traceable to engagement checklist, outstanding items.
  • A 6-person accounting firm has Invoices. Read or written by Back Office, QA. Traceable to invoice record, billed engagement.
  • A 6-person accounting firm has Filing rules. Read or written by Intake, Research, QA. Traceable to filing rule set, sign-off requirement.
  • A 6-person accounting firm has Workpaper SOPs. Read or written by Document Chaser, Research, QA. Traceable to workpaper SOP, review steps.
  • A 6-person accounting firm has Staff handoff. Read or written by Intake, Document Chaser, QA. Traceable to handover note, open requests 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 accounting. Nothing here is a client record. The retrieval and messaging parts run on my own hotel today; the rest is a design.

The file that is four documents short

  1. Step 1 · Trigger

    A client file is short and the clock is running

    Four documents are missing, the deadline is eleven days out, and chasing them by hand costs half of somebody's day.

  2. Step 2 · Agents

    Document Chaser and Research would work it

    Document Chaser would know what is missing, because the engagement checklist sits in the map. It would send the reminder, log what lands and escalate what stalls. Research would answer the client question from the prior-year file.

  3. Step 3 · Action

    The outstanding list would stay current

    One screen per client, updated as documents arrive, with the stalled items marked for a person rather than resent forever.

  4. Step 4 · Trace record

    What you would be able to check

    Every reminder sent, and the source file behind the answer the client got.

    Example record — illustrative, not a client log
    source:
    engagement checklist → outstanding items
    policy:
    document request SOP
    agent:
    Document Chaser
    human_review:
    partner reviews the stalled items
03 / Proof

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

I have not built this inside an accounting firm, so there is no card to show you. The closest published build answers questions out of one business’s own approved documents and shows which record each answer came from. That retrieval is the same piece an engagement-letter or prior-year answer would run on.

Why this one

Same retrieval, same source trace. A hotel’s house rules instead of your files.

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 client file 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

Pick the job that eats your busy season.

Name the thing your team chases every March. I will show you where it would sit on the map.

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