Client follow-ups: closing the loops a practice quietly leaves open

To automate client follow-ups for an accounting firm, build a register of everything the firm owes clients (proposals, promised answers, planning points), give each item an owner and a due date, and attach short follow-ups to it. The register matters more than the messages. Most firms track documents they are waiting for, but not what they owe clients, so those loops stay open.

Key takeaways

• A follow-up register records what the firm owes each client, who owns it and when it falls due.
• Proposals are the most valuable open loop: three short follow-ups that each add something, ending with a request for a decision either way.
• Advice follow-ups should fire on the date the point becomes time-critical, and prompt a conversation rather than repeat the advice.
• Marketing messages to sole traders and ordinary partnerships need consent or the soft opt-in under PECR (the UK Privacy and Electronic Communications Regulations), while service messages about engaged work do not.
• A client who has gone quiet needs a call from a partner, not an automated message.

What we'll cover

• The loops a practice carries
• Why they close in some firms and not others
• Proposals, the most valuable unchased loop
• Advice that was never actioned
• Building it with CodeWords
• Follow-ups that are not reminders
• Tone, and the line before a sales sequence
• The client who has gone quiet
• What the marketing rules allow
• Making it survive
• Limits worth knowing about
• What to build first
• Frequently asked questions

The loops a practice carries

A practice carries six kinds of open loop, and most firms recognise every one and track none. Unlike a missing bank statement, none of them produces a visible gap, which is why they stay open.

Proposals and quotes. Sent, acknowledged, never decided. The client did not say no, and nobody asked again.

"I'll look into that." Said in a meeting, meant sincerely, and written in nobody's system.

Planning points. A pension contribution worth making before year end, a capital allowance decision, or a dividend timing question. Raised in the accounts meeting, relevant eight months later, forgotten by both parties.

Deadlines ahead of the client. A registration threshold they are approaching, a payment on account, or a first VAT return. You can see it coming; they cannot.

Returned work awaiting approval. A return sitting unsigned in an inbox is the commonest reason a finished job files late.

The onboarding that half-finished. A client sent two of the four things, was never chased for the rest, and is now a year in with a gap in the file.

Why they close in some firms and not others

Loops close when they exist somewhere outside a person, not because one firm is more diligent than another. An item in a shared register with an owner and a date gets closed. An item in a sent-items folder gets closed only if the sender remembers on a quiet day, so it closes in July and not in January.

Build the register first: what the firm owes, to whom, by when, and who is responsible. Sequences attach to the register afterwards and are the easy part.

Apply one test. If a senior member of staff left tomorrow, could anybody list what that person had promised clients? In most practices the honest answer is no, which is a risk as well as lost revenue.

Proposals, the most valuable unchased loop

An unanswered proposal is usually not a no. It is typically a client who read the proposal on a phone, meant to think about it, and had something else happen.

Send three follow-ups over three weeks, each short and each adding something new:

1. The first offers to walk through the proposal.
2. The second addresses the objection you suspect.
3. The third asks for a decision either way, so the loop can close.

Asking for a no is the step firms skip and the one that helps most. A proposal that is definitely dead is worth more than one that might be alive, because it stops occupying attention and tells you something about your pricing.

Log the outcome every time, including losses and the reason. A year of that is the most useful pricing data a small practice will have, and it costs one field.

Advice that was never actioned

Advice follow-ups carry the most value and have the least structure around them. A planning point raised in a year-end meeting has a window. Said in June about a March year end, it is useful. Raised the following March, the opportunity has gone. Nothing in a normal practice connects the moment a point is raised to the moment it becomes urgent.

A register fixes this cheaply. When a point is raised, record it with the date it becomes time-critical, and fire the follow-up then.

Two cautions apply. The follow-up should prompt a conversation rather than restate the advice, because circumstances change and advice given in June may not hold in February. And the record of what was advised, and when, belongs on the client file rather than in a scheduling tool.

Building it with CodeWords

CodeWords connects to 3,000+ integrations (CodeWords pricing page, 2026), and each connection is made once and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: the kinds of loop you track, who owns each, when each becomes due, and what should happen when one does.
3. Authorize the connections to your practice management system, wherever proposals and notes live, and the channels your clients have agreed to.
4. Describe the exceptions: a client who has already responded, one in a live conversation with a partner, one who has asked not to be contacted about a particular thing, and anyone whose circumstances have changed.
5. Start with one loop type, run it for a quarter, and compare what the register says with what people remember.

You describe the outcome; Cody builds it, connects it and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows (CodeWords pricing page, 2026). Details are on the pricing page.

Follow-ups that are not reminders

Some of the most valuable contact a practice makes chases nothing. Three types are worth scheduling:

A heads-up about something approaching. Examples are a client nearing the VAT registration threshold or facing a first payment on account they have not budgeted for. Clients remember this contact, and you can predict it from data you already hold.

A check-in after something changed. Examples are a first employee, a property purchase, or trading in another country. Each creates obligations the client does not know about yet.

A confirmation that nothing is needed. A short message saying the quarter is done and nothing is required is the cheapest goodwill available.

These cost nothing to schedule and change how the relationship feels. Without them, the client only hears from you when you want something.

Tone, and the line before a sales sequence

Follow-ups from an accountancy practice must not read like a subscription business's sales sequence, because that tone damages the relationship they exist to protect.

Two or three contacts on a loop, then a person. Beyond that, a reminder becomes pressure.

One subject per message. A follow-up carrying three unrelated asks gets none of them answered.

Nothing manufactured. Clients who deal with real deadlines all year recognise an invented one instantly.

Signed by somebody. A follow-up from a named person reads differently from one from the firm.

The client who has gone quiet

Silence is information, and most practices do not act on it. A client who has not been in contact for a full cycle, whose records arrive later each year, or who stopped asking their usual questions may already be partway out of the door. By the time another firm's disengagement letter arrives, the decision was made months earlier.

Automate only the first step here. A flag that says "this client has gone quiet" is useful. An automated message asking how they are is not the right intervention. A partner picking up the phone is.

What the marketing rules allow

The marketing rules differ by client type, and much of a typical practice's client base falls on the stricter side. Under PECR, limited companies and limited liability partnerships are corporate subscribers, and electronic marketing to them does not require consent. Sole traders and ordinary partnerships are individual subscribers, so unsolicited electronic marketing to them needs consent or the soft opt-in.

The soft opt-in requires that you obtained the details during a sale or negotiation, that you are marketing similar services, and that you offer an opt-out when you collect the details and in every message (ICO guidance). Where you cannot tell which type a contact is, the ICO's position is to treat them as an individual subscriber.

Administrative messages about work you are engaged to do are not marketing. "We need your bank statements" is service. "We also offer payroll" is marketing, and the rules above govern it on any channel.

Making it survive

Five habits keep the register useful.

Give every loop an owner and a due date, or it is a note rather than a register.

Close loops explicitly, including the ones that end in no. An unclosed loop with no outcome is the same as having no register.

Check for a live conversation before any send. An automated nudge landing mid-discussion damages the relationship quickly.

Record what was advised on the file, not in the tool that scheduled the reminder.

Review the register quarterly with a person looking at it. A register nobody reads goes out of date.

Limits worth knowing about

Follow-up automation has five limits.

A follow-up cannot rescue a proposal the client never wanted. Treating every silence as winnable wastes attention.

Contacts beyond the third add little and cost goodwill you will want later. Hand the loop to a person instead.

Advice has a shelf life. A point raised eight months ago may no longer hold, so the follow-up prompts a conversation rather than repeating the advice.

Some loops are not yours to close. A client waiting on a third party cannot be moved by a message to the client.

Automation cannot tell you which relationships are in trouble. It can flag the silence; only a person can work out what the silence means.

What to build first

Build one register for one loop type, and start with proposals. Record every proposal sent, who owns it, when it was sent and what happened, including the losses. Attach three short follow-ups and close each loop explicitly, either way.

Two habits make the difference. Ask for a decision rather than a reply, because a clear no releases attention that a maybe keeps consuming. And record the outcome of every loop you close, since a year of those gives you an honest picture of what your practice converts and at what price.

Frequently asked questions

What is a follow-up register?

A follow-up register is a shared list of everything the practice owes clients, with an owner and a due date for each item. Without it, follow-ups depend on somebody remembering, so they happen in quiet months and not in busy ones.

How many times should a proposal be followed up?

Follow up two or three times over about three weeks, with each message adding something new rather than repeating the last. Then ask for a decision either way and close the loop, whether the answer is yes or no.

Why ask a client to say no?

A closed loop stops consuming attention, and a recorded loss tells you something about your pricing. A proposal that might still be alive is worth less than one you know is dead, because you can plan around a certain no.

How do I follow up advice given months ago?

Record the point when it is raised, together with the date it becomes time-critical, and fire the follow-up on that date. The message should prompt a conversation rather than restate the advice, since circumstances may have changed since then.

Do follow-ups need consent?

Service messages about work you are engaged to do are not marketing and need no consent. Marketing another service does. For sole traders and ordinary partnerships, PECR treats them as individual subscribers, so marketing needs consent or the soft opt-in.

What should never be automated?

Do not automate any response to a client going quiet, anything that amounts to advice, or anything about fees in a difficult period. Flagging these cases for a person is useful. Sending messages about them automatically is not.

How often should the register be reviewed?

Review the register quarterly, with a person looking at what is open and what has aged. A register that nobody reads goes out of date, and an out-of-date register is no better than having none.

Related reading

• Making a document request land
• Which channel is the client file
• Tax season as a queueing problem