In this fictional example, a finance director replies to a cold email: “Not me. Marta runs accounts payable, try her.” Four days later the same director receives step three of the sequence, asking whether the earlier note got buried. The seller earned one of the most useful replies a cold email can get and answered it with a template.
A follow-up to silence is a guess. A follow-up after a buyer has said something is an obligation, and most of the craft lies in keeping exactly what was said. The three examples here are invented, built around a hypothetical vendor of invoice-matching software selling to finance teams at mid-sized logistics firms. Each pairs a weak version with a stronger one. None comes with a promised reply rate, because wording alone cannot carry that.
The Referral
Jonas, the finance director, has pointed to Marta. The weak follow-up:
Hi Marta, your colleague Jonas recommended I get in touch! We help finance teams cut invoice processing time dramatically. Do you have 15 minutes this week?
Jonas recommended nothing. Jonas redirected, which is a smaller thing, and Marta can check with one message. The claim about processing time is unsupported, and the meeting request arrives before Marta knows the subject.
Marta, last week I wrote to Jonas Becker about how your team matches carrier invoices against delivery records. Jonas replied that accounts payable is yours and that I should ask you, without saying whether this is a problem worth solving. So, one question: when a carrier invoice doesn't match the proof of delivery, does someone on your team resolve it by hand? If that's rare, I'll leave it there.
This version reports the referral at its true size, restates the topic so Marta has nothing to reconstruct, and asks a question that can be answered in a line.
Two things happen outside the message. Jonas gets a short reply: “Thanks, I'll ask Marta and won't write to you about this again.” Then that promise is recorded and Jonas leaves every active sequence. The commitment kept is the stop for Jonas and the exact wording of the redirect. The next owner is the seller; Marta owes nothing yet.
The Deferred Date
In December, Ines, a controller at another firm, replies: “We're mid-migration to a new ERP until the end of February. Ask me in March.” The weak follow-up, sent in March:
Hi Ines, circling back as promised! Is now a better time to chat about automating your invoice matching?
It remembers that a promise existed and forgets everything in it. Ines has to recall who this is and why March mattered. Its weaker cousin is the January message asking whether timing has changed, which breaks the agreement outright.
Ines, in December you asked me to come back in March, once your ERP migration was done. Two questions, and a short answer to either is fine. Did the migration finish on schedule? And does the new system change how carrier invoices get matched? If it now covers that, tell me and I'll close this out.
The message restates the date and the reason in Ines's terms. It asks about the migration first, because the cause of the delay is also the thing most likely to have changed the answer. And it names the outcome in which the seller goes away.
A deferral is also a restriction. Until March, suppress sales follow-ups on this topic across channels. Record whether the buyer also asked to pause unrelated communications; do not silently broaden the meaning of the reply. The record needs the buyer's words, the reason, and a specific day, because “March” is ambiguous. The December acknowledgment settles it: “Understood. I'll write in the first week of March and not before.” If the migration slips to May, the commitment moves with it.
The Unresolved Product Gap
After a demo, Tomasz, an accounts payable lead, asks whether the product can read invoices from two carriers that still send scanned PDFs. The seller promises to check. In this hypothetical the answer is no: the product reads EDI and text-based PDFs only. The weak follow-up:
Hi Tomasz, great news! Scanned PDF support is on our roadmap and should be available soon. Shall we get a pilot scheduled in the meantime?
“Soon” is a date nobody has agreed to, and the pilot request steps over the question Tomasz asked. If the gap matters, it will surface during the pilot at a higher cost to both sides.
Tomasz, you asked whether we can read the scanned PDF invoices from your two smaller carriers. Today we can't. We read EDI and text-based PDFs, and scanned documents have no committed date, so I won't offer one. If those two carriers are a small share of your invoices, matching would cover the rest and your team would handle those two as it does now. If they're a large share, we're probably the wrong fit this year. Roughly what share are they? I also owe you one answer: our product lead is confirming by Friday whether an OCR step ahead of our import would work, and I'll send the result either way.
The answer arrives in the second sentence. The message separates what is known from what is still being checked, and it hands Tomasz the condition under which the right conclusion is no. Disclosing the gap gives the buyer a concrete basis for judging the proposal. The seller's own promise is treated like a buyer's: Friday has an owner and a deliverable, and the answer goes out even if it disappoints.
What the Record Has to Hold
| State | Commitment to Keep | Next Owner |
|---|---|---|
| Referral | Stop for the referrer; redirect quoted exactly | Seller, to the new contact |
| Deferred date | No contact before the agreed time; reason kept | Seller, on the stated day |
| Product gap | Open question, promised answer, due date | Seller, then buyer on share of volume |
In all three, the next owner is the seller. That is the common failure: a reply arrives, feels like progress, and nobody writes down that the next move is ours, by when, and within what limits. A system that stores a status such as “replied” or “nurture” without the buyer's words and a date will produce follow-ups written from the status, and they will sound like it.
These examples assume a real reply. A prospect who has never answered has given no commitment to keep, and different reasoning applies. Length should also follow the question: when a buyer asks for a yes or no, put it in the first line and let the rest be optional reading.