In development · For accounting firms

Make the close
easier to review.

We’re building a month-end close copilot for small accounting and bookkeeping firms. Organize supporting documents, surface exceptions, and prepare the follow-up work that keeps a close moving.

Evidence-linked close work · Accountant review

CLOSE REVIEW / SEPTEMBERILLUSTRATIVE EXAMPLE

Oak & Field Studio

Fictional client · sample review items
Missing support for a purchaseREQUEST DOCUMENT

Example ledger transaction: $480 equipment purchase. No matching receipt in the sample document set.

Evidence: ledger row 34 · receipt index
Transfer needs confirmationACCOUNTANT REVIEW

Two entries share an amount and date. Confirm the accounts before treating them as an internal transfer.

Evidence: bank statement p. 2 · ledger row 57
Planned output: evidence-linked checklist + draft client questions
All findings require accountant review.
DESIGNED FOR A REVIEWABLE CLOSEDocuments linked to findingsCalculations checked separatelyAccountant approval
The product workflow

Less time assembling the story.
More clarity at review.

The first release will support CSV ledger exports, bank-statement PDFs, and supporting documents. A focused workflow for firms managing recurring closes across small-business clients.

01

Bring the evidence together.

Import a client’s ledger export and supporting files into one review packet. Identify missing or ambiguous documents before drafting the close narrative.

02

Turn exceptions into actions.

Use Claude to read documents, explain flagged items with source references, and draft specific questions for the client. Review each proposed finding.

03

Prepare a clear handoff.

Create a draft close summary, outstanding-items checklist, and client follow-up email for accountant approval. Direct ledger integrations are future work.

Review controls

The accountant stays
in control.

Claude is planned for document interpretation and clear explanations. Numerical reconciliation will use deterministic calculations that can be inspected and checked.

Evidence before conclusionsEach exception should point to the relevant source document or ledger row and identify what remains uncertain.

Approval before actionAccountants will review output and retain control of ledger posting and client communication.

Privacy designed into the buildThe first release will include access controls, data retention settings, and review steps for handling client records.

Product development

A product plan grounded
in accounting work.

What is on the roadmap?

The first release will support ledger CSVs, bank-statement PDFs, and supporting documents. Development will focus on cited exceptions, client follow-up drafts, and close summaries, with numerical reconciliation handled by inspectable calculations.

Which firms is this designed for?

Small accounting and bookkeeping firms preparing recurring month-end closes across multiple small-business clients.

How can I help shape the first release?

Share how your firm organizes close documents, reviews exceptions, and follows up with clients. We’re focusing development on the tasks your team repeats every month.

How will it fit with accounting software?

The first release will work with document and ledger exports. Accountants will retain professional judgment, final reconciliation, and posting; direct integrations are on the longer-term roadmap.

Where does your close get stuck?

Shape the workflow around the tasks your firm repeats every month.

Discuss your workflow ↗