Companion & communication
Client communication kit
Request documents, remind about deadlines, ask follow-ups – firm communication is eighty per cent recurring. And it still gets typed anew every time, between two sets of accounts, sometimes friendly, sometimes curt, depending on the day.
Quote-prep assistant
01Client communication kit
The communication kit turns that into a flow: from an occasion, a deadline or a document need, a finished email draft takes shape – in the firm's tone, from reviewed text building blocks, with the right salutation per the file and a solid list of what to clear before sending. The clerk reads, adjusts, sends. Instead of starting from zero, they start at eighty per cent – and clients get communication that always sounds equally professional, however full the day.
Straight up: I don't automate tax statements as a matter of principle – the kit phrases the admin (documents, deadlines, processes), a person adds the professional content. Nothing is ever sent automatically: the draft is internal, the decision stays with your team. And the quality depends on your text building blocks – if they live only in people's heads, writing them down is the first project step.
02Demo
On the left the occasion, as it arises in everyday firm work – a deadline, a need for documents. On the right the draft email the kit prepares from it: in the firm's tone, from checked building blocks, with everything flagged that needs settling before sending. Two examples to click through.
The draft never leaves the building automatically: check, adjust, decide, send – that stays reserved for humans.
03How it works
- 01
Sort out the communication occasions
Which emails does your firm write again and again? A document request, a deadline reminder, onboarding info, follow-up emails – the list of occasions is the kit's map. Usually 10 to 15 make up 80 per cent of the volume.
- 02
Curate the text building blocks
Your best phrasings become a library: salutations, reminder levels, portal pointers, sign-offs – in your firm's tone, not in AI-speak. Often the most valuable step: the firm's tone gets written down for the first time.
- 03
Set the rules: who, when, how
Formal or casual per the file, escalation levels on deadlines (friendly → firm → a call), what's never phrased automatically. These rules turn building blocks into a system.
- 04
Build the draft flow
An occasion in, a draft plus a to-clear list out – as a lean internal tool that fits into your workflow instead of forcing a new program.
- 05
Test on a real case and adopt it
The last twenty real emails run through the kit: where does it hit the tone, where not? Building blocks get sharpened, then the team learns the flow: read the draft, clear, adjust, send.
04Stages
The entry point needs no software of its own – just your phrasings in good shape.
Entry: building blocks + templates
A curated text-building-block library plus prompt templates for your existing AI tool – the work aid that helps right away.
Extended: the internal mini tool
An occasion and mandate context in, an email draft and to-clear list out – a small tool of your own for client communication.
Full build: connected
Connection to the deadline overview and email drafts – the kit suggests of its own accord when a reminder is due. Sending stays with people.
05Technical implementation
- Input: the occasion (deadline, document need, onboarding step) plus context from your files – the more structured the occasion, the better the draft.
- Knowledge base: text building blocks, salutation rules, escalation levels and sample emails – curated, not thrown together.
- The language model combines building blocks and phrases the transitions; it invents no deadlines and makes no tax statements – it flags such spots as open.
- Output to suit your process: an email draft to check, never an automatic send.
- Client data stays in the leading system – the kit works with the minimum context the draft needs.
- Hosting: as a small internal tool or a function in the existing firm stack.
for context · This shows how something like this usually gets built – not how it has to be built for you. What actually fits is worked out in the project: around your existing setup, your team, and what stays easy to maintain.