The writing around bookkeeping falls into two kinds, and they behave very differently. There is communication — requests, summaries, reminders — which is repetitive and safe to draft. And there is interpretation — what a number means, what a client should do, whether something is a problem — which is professional judgement and should not be generated.
Keeping that line straight is most of the work.
Where it clearly helped
Document chases
The highest-value use. A chase email is a formula: what is missing, from which period, by when, and what happens if it does not arrive. Generated drafts removed the friction that made us delay sending them, and consistency meant the tone stayed neutral across repeated requests — which is what prevents a chase reading as an accusation.
Monthly summaries
Turning a set of figures into a short readable summary went from about 30 minutes to roughly 10. The numbers are entered by hand; the tool handles the prose around them. The drafts were reliable when the template specified what to include — period, revenue, costs, margin, notable movements, what needs the client's attention.
Onboarding sequences
A standard sequence of four or five messages covering what access is needed, what to expect in month one, and how communication works. Formulaic, verifiable, and worth generating once and reviewing periodically.
Where it nearly caused problems
Interpreting what a figure means
Given a set of numbers, the tools reliably produced an interpretation — and the interpretation was plausible rather than correct. "Margin improved because of X" when the data supported three possible explanations. Interpretation is the service; do not delegate it.
Tax and filing statements
Drafts made confident statements about deductibility, deadlines and obligations. These vary by jurisdiction, entity type and circumstance, and getting one wrong has direct consequences for the client.
Implying review that did not happen
The subtle one. A polished, well-written monthly summary implies more scrutiny than may have occurred. State explicitly what was and was not checked, rather than letting the prose imply thoroughness.
The two sentences clients misread
Most of the client friction we saw came from two sentences that were technically accurate and practically misleading. The first is "the accounts are up to date". It means the entries have been posted; clients hear that the figures are correct and complete. Worth stating what the entries rest on — which statements were reconciled, which were estimated, what is still outstanding. The second is "everything looks fine". It gets read as assurance. Better to say what was reviewed and what that review would not have caught.
The other habit that paid off was writing the question back. When a client asks something, restate in one line what you understood them to be asking, then answer that. It takes seconds, and it surfaced several cases where we had answered a different question from the one being asked — usually about the timing of cash rather than the level of profit.
Editing time, from our 30-day benchmark
A monthly summary that took about 28 minutes to write manually took roughly 11 minutes to draft and verify, near $8.50 saved at $30 per hour. Chase emails were the biggest relative win: what had taken around 8 minutes each — mostly deciding how to phrase it — came down to about 1.5 minutes.
A workflow that holds up
Keep templates for the three recurring documents: monthly summary, document chase, onboarding sequence. Enter all figures yourself. Generate the surrounding prose, then check every sentence containing a number against the source. Anything that interprets, advises or certifies is written by the bookkeeper — including a clear statement of what was reviewed. When the writing is this clean, the temptation to let it imply more than you did is the main risk.
Draft the communication, not the judgement
Requests and summaries scale. Interpretation stays with the professional.
Try Claude →Frequently Asked Questions
Can AI write my client summaries?
The prose around the numbers, yes. Enter the figures yourself and check every sentence containing one against the source data.
Should it interpret the figures?
No. Interpretation is the professional service. Generated interpretations are plausible rather than correct, which is worse than obviously wrong.
Can it chase clients for documents?
This is the best use. A consistent, neutral tone across repeated requests prevents the chase reading as an accusation.
What about tax advice?
Never generated. Obligations vary by jurisdiction, entity type and circumstance.
Will clients notice?
They notice polish. Make sure the polish reflects work that actually happened, and say what was reviewed.
How much time does it save?
Around 17 minutes per monthly summary and 6 minutes per chase email in our 30-day test.