Clients already expect the firm to use it.
AI operating systems for firms whose clients now expect AI-assisted service.
Tax and accounting firms went from 9% AI adoption to 41% in a single year, but most of that is a preparer pasting text into a chat window — not a system the firm can rely on, audit, or bill against safely. We build the layer underneath: a close-process agent that automates invoicing, reconciliation, and expense audits, a tax-research copilot grounded in current code and rulings, and a client-communication assistant that drafts without ever sending on its own.
Part of
Accounting & Tax Firms is one vertical view of a single system. The layer underneath — retrieval, scoped permissions, evaluation, and the audit trail — is the same one we build in every sector.
Where AI earns its keep.
The workflows in accounting & tax firms where AI does real work today — not a someday roadmap, the jobs it can take off your plate now.
Close & reconciliation agent
Automates invoicing, reconciliation, and expense audits — speeding up the close process substantially.
Tax research copilot
Retrieval-grounded research against current code and rulings, with citations, not guesses.
Client communication assistant
Drafts client updates and requests for review — nothing goes out without a human reading it first.
Document intake & extraction
Pulls structured data out of client-submitted statements, receipts, and filings automatically.
Don’t take our word. Take the call.
3 of the agents above, live in your browser right now. Pick the job you actually need covered, press call, and talk to it the way your customers would — objections included.
A real call, not a recording. Press call once, then just talk — it hears you stop and answers. No buttons to hold.
This browser can’t capture speech — you can still type your side of the call. Chrome, Edge, or Safari for the full thing.
Live agents on fictional businesses and invented records. Nothing you say or paste here is recorded or stored — it lives in this tab and dies with it. A production deployment runs on your data, your systems, and your policy.
A client invoice, from intake to reconciled close
Not a feature list — the mechanism, step by step, from trigger to logged outcome.
Capture
The invoice, receipt, or statement arrives from the client portal or the AP inbox and is read against the client's own chart of accounts and prior filings — not a generic bookkeeping template.
Extract & match
Structured line items are pulled out and matched against the general ledger and any open purchase order, with every match citing the source document it came from so a preparer can check it, not just trust it.
Route for review
The reconciled entry goes to the responsible preparer or reviewer before it posts. Nothing books itself onto a client's books unreviewed.
Log
The entry, its source document, and who approved it log into the working papers — so the trail exists at the time of the close, not reconstructed for the next audit.
Illustrative — the events this system emits, not a log from any client’s production run.
Every part of it. Not the demo part.
The whole operation, workstream by workstream — including the unglamorous pieces that decide whether any of the rest of it works.
Overnight intake & AP sweep
Client-portal uploads, AP inbox items, and prior-day working papers are read before the team logs on, and compiled into one prioritized close list — each item already tagged with the client and engagement it belongs to, so a preparer opens one queue instead of six inboxes.
Invoice-to-PO matching & reconciliation
An incoming invoice or statement is matched against its purchase order and the client's general ledger. A discrepancy is flagged, never silently approved, and a draft coding entry is prepared for whoever actually authorizes the posting.
Tax research grounded in current code & rulings
A research question is answered with retrieval-grounded citations to the actual code section, ruling, or guidance it pulled from — never a citation that sounds right but wasn't checked. Where nothing on point is found, it says so plainly instead of filling the gap.
Document intake & extraction
Structured line items are pulled out of client-submitted statements, receipts, and filings automatically, cited back to the source document, so a preparer reviews extracted figures instead of retyping them from a PDF.
Client communication drafting
Status updates, document requests, and review reminders are drafted from the engagement file itself — what's outstanding, what's next — for the responsible preparer to edit and send. Nothing goes out on a client's engagement without that review.
Filing-deadline & engagement tracking
The practice management calendar is read daily and upcoming filing deadlines and extension dates are flagged well ahead of time, with a drafted reminder for the responsible preparer — a deadline is never marked handled until a person confirms the filing actually happened.
Working-paper & audit-trail logging
Every reconciled entry, research answer, and extracted figure logs who reviewed and approved it directly into the working papers at the time it happened, so the record the next audit needs already exists instead of being reconstructed months later.
Engagement letter & intake support
New client and engagement intake is drafted from the client's own information and the firm's standard terms, not a blank template, so a partner reviews a ready draft engagement letter instead of writing one from scratch.
The numbers aren’t ours.
Published industry figures and the rules themselves, each with its source named — this is the gap the build is aimed at, not a claim about our results.
Tell us which part of accounting & tax firms is the bottleneck.
What it will never do.
Enforced outside the model, in the control layer — these are constraints the system can't talk itself out of, not instructions we hope it follows.
- 01Never posts an entry to a client's books without the responsible preparer or reviewer approving it first.
- 02Never cites a code section, ruling, or source it didn't actually retrieve — every citation points to the exact source it pulled from, or says plainly it found nothing.
- 03Never sends a client communication, filing, or deliverable without the responsible preparer reviewing it first.
- 04Never treats a filing deadline as met until a person confirms the filing or extension actually happened.
- 05Never carries one client's data into work on an unrelated client's file, even inside the same engagement team.
- 06Never changes the firm's tax position or working-paper conclusions on its own authority — a deviation is flagged for a partner to decide.
- 07Never releases a payment or authorizes a posting itself — it drafts the reconciliation and coding, a person authorizes it.
- 08Never replaces the firm's accounting or practice-management platform as the system of record — it reads and writes inside the one already in use.
Built for the rules of your industry.
Services that fit this industry.
AI Agents & Workflow Automation
Autonomous agents and copilots wired into your real workflows.
AI Integration & Modernization
LLMs and automation wired into the systems you already run.
AI Security & Compliance Engineering
Scoped permissions, audit trails, and compliance-aligned delivery for AI that touches real systems.
What it plugs into.
An AI operating system only earns that name if it runs inside the systems you already have — not beside them.
Asked before the contract, not after.
No — every reconciled entry routes to the responsible preparer or reviewer before it posts. The agent drafts and cites the source document it matched against; a person decides what actually goes on the books.
No rip-and-replace — the agent reads and writes inside the accounting or ERP platform you already run, whatever that is, rather than adding a separate tool the close process has to check on top of it.
No — it removes the retyping and searching between them and the decision, not the decision itself. A preparer still approves every reconciled entry; a partner still owns the filed position. What changes is how much of their day goes to data entry and citation-chasing versus reviewing and deciding.
It says so. The system is built to refuse a fabricated citation rather than fill the gap with something plausible-sounding — a 'nothing on point found' answer is correct behavior, not a failure, and it's the reason grounded retrieval exists instead of an open chat window.
The reconciliation and filing load per client is often worse at a smaller firm, not better — there's no dedicated bookkeeper or a preparer whose whole job is deadline tracking. We scope the first build to one workstream, usually invoice matching or tax research, so you see it working on a live engagement before it touches the rest.
Weeks, not a season — we start with the highest-volume workstream, usually AP matching or research, measure it against your current turnaround, and expand into the other workstreams once that one has proven itself.
Let's put AI to work in your business.
A 30-minute call. You bring the workflow or the roadmap — we'll tell you what's feasible, what it costs, and what we'd build first.