Companion & communication

Client communication kit

Requesting documents, reminding clients of deadlines, asking follow-up questions – eighty per cent of a firm's communication is repetitive. Yet it still gets typed from scratch every time, squeezed in between two sets of accounts, sometimes friendly, sometimes curt, depending on the day.

You'll get …

  1. 1

    A draft instead of a blank email

    Every recurring email starts from your approved text building blocks – in the firm's tone, with the form of address taken from the client file.

  2. 2

    Open points before sending

    Anything still to be clarified is listed next to the draft. Your team adds the professional content, and nothing is ever sent automatically.

  3. 3

    Your firm's tone, written down

    Occasions, text building blocks and rules – such as first-name or formal address and reminder levels – are recorded rather than only kept in people's heads.

01Intro

The communication kit turns this into a workflow: an occasion, a deadline or a missing document produces an email draft – in the firm's tone, built from approved text building blocks, with the form of address taken from the client file and a list of what needs clarifying before it's sent. The member of staff reads it, adjusts it and sends it. Instead of starting from scratch, they start at eighty per cent.

Worth knowing: as a rule, I never automate statements on tax matters – the kit handles the admin (documents, deadlines, processes), and a person adds the professional content. Nothing is ever sent automatically: the draft stays internal, and the decision stays with your team. And the quality depends on your text building blocks – if they only exist in people's heads, writing them down is the first step of the project.

02How it works

  1. 01

    Map the occasions for writing

    Which emails does your firm write again and again? Document requests, deadline reminders, onboarding information, follow-up emails – the list of occasions is the map for the kit. Usually 10 to 15 of them make up 80 per cent of the volume.

  2. 02

    Curate the text building blocks

    Your best wording becomes a library: greetings, reminder levels, portal instructions, sign-offs – in your firm's tone, not AI-speak. This step alone often makes the biggest difference: for the first time, the firm's tone is written down.

  3. 03

    Set the rules: who, when, how

    First-name or formal address according to the client file, escalation levels for deadlines (friendly → firm → phone call), what is never written automatically. These rules turn building blocks into a system.

  4. 04

    Build the drafting workflow

    An occasion in, a draft and list of points to clarify out – as a lean internal tool that fits into your workflow.

  5. 05

    Test it on real cases and adopt it

    Your last twenty real emails go through the kit: where does it get the tone right, and where not? Once the building blocks are refined, the team learns the workflow: read the draft, clarify, adjust, send.

03Stages

The entry level needs no software of its own – just your wording in good shape.

Tier 1

Starter: building blocks + templates

A curated library of text building blocks plus prompt templates for the AI tool you already use.

Tier 2

Next step: the internal mini tool

The occasion and client context in, an email draft and list of points to clarify out – a small tool of your own for client communication.

Tier 3

Full build: connected

Connected to your deadline overview and email drafts – the kit suggests a reminder on its own when one is due. Sending is still done by people.

04Try it yourself

simulation · fictional firm

On the left the occasion, as it arises in everyday firm work – a deadline, a need for documents. On the right the email starts empty – one click, and the kit puts it together from checked building blocks in the firm's tone. The last 20 % are yours: settle the open points, then send.

// occasion (incoming)
// draft email (internal)
prepared0 %

The draft never leaves the building automatically: check, adjust, decide, send – that stays reserved for humans.

05Technical implementation

  • Input: the occasion (deadline, missing documents, onboarding step) plus context from your files – the more structured the occasion, the better the draft.
  • Knowledge base: text building blocks, rules for forms of address, escalation levels and sample emails – carefully curated, not thrown together.
  • The language model combines building blocks and writes the transitions; it never makes up deadlines or makes statements on tax matters – it flags those points as open.
  • Output to suit your process: an email draft for review, never an automatic send.
  • Client data stays in your main system – the kit works with the minimum context the draft needs.
  • Hosting: as a small internal tool or a feature within your firm's existing 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.

06Related building blocks

See all use cases for firms