See it run

── Scene 1 · The practice itself

An accounting practice is a small business too

Before touching a single client, the radar runs on the practice's own filings — 1120-S, quarterly 941s, the state annual report. No client data, so no §7216 consent, no security review, no integration.

• The same obligation engine, pointed at the practice's own entity
• Every obligation it picks has to cite a fact — no fact, no deadline on the board
• The practice lands on the same board as its clients, tagged as yours

── Scene 2 · Document chase

Getting the documents in

It opens on the CPA's screen; once the chase goes out, the client's side joins — a signed link, no account, no login. Two recordings of the same chase placed side by side, ending with a real AI call on a live US number. Nothing here is staged.

• Reads last year's return and works out what's actually missing this year
• Sends a chase the client can act on — approval-gated, never auto-sent
• Client uploads against the checklist; that placement is free structured labelling
• A separate check reads each file: wrong year, wrong document, unreadable — all rejected
• Three attempts with no progress, and it stops and hands you the phone

── Scene 2 · Season two

The chase that remembers last season

Same client, one season later. When a chase closes it writes down what this client tends to get wrong — and the next season's chase opens already knowing it. Recorded against the real pipeline: live gap detection, real uploads, independent verification.

• Opens on last season's note: took two requests, sent the wrong year's statement
• The new chase surfaces that memory to the CPA before anything goes out
• The recorded pattern repeats — a wrong-year document, rejected with the reason
• Checklist hits zero, the loop closes, and a new note is written for next season

── Scene 2 · Check and watch

Everything arrived. That is not the same as correct.

The chase says done. This is what happens next: the collected package gets read for what does not add up, and a standing watch works out what each client owes and when.

• Reads the assembled package and finds Form 8938 missing — the Hong Kong account peaked over the threshold
• 8938 was never on the checklist, so the chase could never have caught it
• Every finding cites its source, then a second independent pass tries to refute it
• One finding is ruled out on that second pass, and stays visible — checked and clear is a result too
• Sign-off stays locked while high-risk items are unsettled
• Deadlines are computed in code, never generated by a model — weekend and holiday roll-forward included

── Scene 2 · Beyond the return

From a client file to a signed recommendation

Compliance is the floor. This is the paid work on top of it: the engine reads what was confirmed off the return, finds what applies, refuses to price anything it cannot stand behind, and hands the CPA something they can put their name on. Sample client is synthetic — every name and number is fictitious and labelled as such on screen throughout — but the engine, the statutes, and the arithmetic are the real product.

• Nothing reaches the engine until a human confirms it — extracted return figures sit in a queue with no auto-accept path
• Missing an input means no dollar figure at all: half-answered strategies are never scored
• Every number opens its own trail — what qualified it under statute, what it assumes, and what would flip it
• Tax saved and exposure are labelled apart, because one is money you keep and the other is money you are losing
• Where the answer depends on an engineering study or an unsettled rate, it says so and shows no dollar benefit
• Open questions block sign-off; the CPA signs with a reason, and that figure is frozen against later re-runs
• Approve produces a draft client memo — marked as draft, with the CPA as the author

── Scene 3 · No accountant yet

A business with no accountant reads its own books

Asking an owner to describe their business is circular — they'd need to know what FBAR is to know what to write. So it reads the books instead, then asks only what books can never contain. QuickBooks data in this recording is a seeded fixture; the derivation, calendar, and screens are the real product.

• State, payroll, and contractors over $600 — each fact traceable to a ledger line
• Then the blind spots, asked out loud: bookkeeping never records a foreign account
• Silence is never read as a no — FBAR and Form 8938 hang on that one question
• Answer it, and the obligations that depend on it appear with the reason attached

── Scene 4 · Both sides, one record

The client stops being a row in someone else's portal

Every incumbent's client portal is an upload box. Here the client connects their own account — and the same obligation rows render twice: once for the professional, once in plain words.

• The accountant sends one link; the client accepts with their own account
• Same rows, two readers — the CPA brief and the plain-language version
• Overdue items say what we know — tracked as open — never “you missed it”
• A file sent last season is shared instead of chased, then still re-checked independently

What it will not do

• It never sends an email or places a call on its own. Every outbound message waits for your approval.
• It does not prepare, sign, or file returns. Filing decisions and signatures stay with the licensed professional.
• It does not assert a deadline it cannot stand behind. Where the rules are in flux, it says so instead of guessing.
• It does not hide a failed check behind a clean result. If a check could not run, it says it could not run.