What Does Follow-Up Look Like When You're Full of Client Work?

It looks smaller and more decided than most owners expect. Follow-up fails in busy firms because every reply routes through the one person who is also doing the client work, and client work wins every tie. Follow-up that survives a full month is mostly agreed in advance: what a good answer looks like, who sends it, and the date of the next touch. The owner only sees the unusual ones.

On one campaign this fall, about half the people we wrote to replied, 21 of 41. They were warm replies, mostly from former colleagues who remembered the owner well and were glad to hear from them. That's an unusually good result, and the kind of problem anyone would like to have.

Then some of them waited. One waited six days for an answer. A couple of others waited more than a week. Nobody was careless. The owner wanted to see every reply before it went out, which is reasonable when the people are old colleagues. The owner was also carrying a full client load, which is the reason the firm exists.

From the owner's side, a week went by full of excellent work for paying clients. From the other side, a person who had just said "great to hear from you" heard nothing for ten days.

Why follow-up is the first thing to go

I wrote separately about why being full is the most dangerous month for a firm's pipeline, so I won't repeat that here. The narrower point for follow-up is about routing.

In an owner-led firm, the owner is usually the only person allowed to speak for the firm to a prospect. That makes sense. Buyers of expert services are buying the expert, and a stiff reply from someone else can do more harm than a slow one from you. So every reply queues behind you.

But a queue that only you can clear moves at the speed of your worst week. And follow-up has a cruel property: its cost is invisible on the day you skip it. A client email you miss produces a phone call. A prospect you don't answer produces nothing at all, which is precisely the problem.

There's also a quieter version, which I think is more common. The follow-up happens, but it's the wrong one. Recently, before sending a routine reconnect note on an owner's behalf, I read back through the thread. About three years earlier the person had written to the owner, introduced himself, attached a short bio, and asked for a call. Nobody answered. The friendly hello we were about to send would have read, to him, as "you didn't notice me then, and you still haven't." We held it and wrote one that opened with an apology.

Same with a reply I saw this fall from a partner at a small professional firm. He'd been offered something free on a campaign and answered, roughly: yes please, and also send me a quote, we just ended our agreement with our current marketing firm. The first sentence is a pleasantry. The second is a buyer telling you his timing. A busy person skimming for the request sends the free thing and marks it done.

So follow-up fails two ways when you're full: it doesn't go out, or it goes out without anyone having read what came before.

What it looks like when it works

Here is the version I set up with clients. None of it requires a new habit of heroic consistency. Most of it is deciding things once so they don't have to be decided on a busy Tuesday.

Decide in advance what a good answer looks like. Sit down once with the owner and sort the replies you usually get into a few kinds: "yes, let's talk," "not now, try me in the spring," "tell me more," "who is this again," and the occasional one that needs real thought. Write the answer to the common kinds in the owner's own words. After that, most replies can go out the same business day without waiting for the owner, and only the unusual ones queue for the owner, who still reads everything but doesn't have to approve the routine ones first.

Read the whole thread before anything goes out. Every reply, and every old thread before a reconnect. It takes a minute. It's where the second sentence and the three-year-old unanswered note turn up.

Give every open conversation a date and an owner. Not "follow up." A date, and the name of whoever has the next move, which is sometimes the prospect. I mark it as whose court the ball is in. If it's ours, it has a date. If it's theirs, it still has a date, the day we check back.

Put proposals on a fixed rhythm. After a proposal goes out, the follow-ups are dated before you hit send: day three, day seven, day fourteen. Short and useful each time, a question answered or a detail they'd want, never "just checking in." Deciding the dates in advance means nobody has to work up the nerve on the day.

Count what's waiting. Once a week, two numbers: warm replies waiting more than one business day, and open conversations with no dated next step. They should both be near zero. When they aren't, the names are right there.

That's the whole system. On a full week it takes a few minutes a day for whoever sends, and a short look from the owner. On a quiet week it takes the same, which is the point.

The trade-off I haven't settled

Agreeing on answers in advance does cost something. The replies that go out without the owner's eyes on them are a little more generic than the ones the owner would write. With former colleagues, the people most likely to reply, a little generic is noticeable.

So far I think it's the right trade. A good answer today usually beats a perfect one in ten days, and the person on the other end feels the delay far more than the polish. But owners differ in how much latitude they'll give, and reasonably so. Some want to see every reply for the first few weeks and then loosen. Some never do, and for them the better fix is a fixed fifteen minutes a day to clear the queue. I'm still working out how to tell, at the start, which kind of owner I'm working with, and I don't have a reliable way yet.

I'm also wary of the opposite failure, where follow-up turns into a sequence that fires no matter what the person said. That's how you end up sending "just circling back" to someone who told you last week that they'd just left the company. Every follow-up here assumes someone has read the last message. If nobody has, it waits.