Close the loop, don’t break up: following up with enterprise buyers who went quiet
The break-up email is the most copied template in B2B selling and the worst one for an enterprise buyer. Here is the follow-up discipline that replaces it — every touch carries something new, and the last one leaves a door with a condition on it.
There is a template every seller has received and most have sent. It arrives after three unanswered emails and says, in one voice or another: I guess this is not a priority, so I will close your file — sometimes with a joke about being abducted by aliens. It is called the break-up email, and in enterprise selling it is wrong on every count. The buyer did not go quiet because of you. They went quiet because an outage ate their week, a reorganization moved the budget, or the thing you wrote about is now being discussed in a meeting you are not in. The break-up email tells that buyer you measure their silence as a verdict on you, which is the least useful thing you can tell them.
The alternative is a follow-up discipline that treats silence as information, carries something new in every touch, and ends by closing the loop — leaving the door open with a specific condition for coming back. This piece describes that discipline as I run it in The Seven C’s Outreach Program™, with five templates from the library.
- The “break-up email” — guilt, a joke, “I guess this isn’t a priority” — is the most copied template in B2B selling and the one least suited to an enterprise buyer, who went quiet for a reason that has nothing to do with you.
- Every follow-up carries something new: a second door, a labelled proof point, a question they can answer in a sentence. No “just checking in.” The last touch closes the loop with dignity: permission to stop, a resource, the right name, and a specific condition for coming back.
- Silence is not a no. Eight reply types each get a rule; a closed sequence rests the account for ninety days; a re-approach needs a new signal. Five templates follow; the full library of ninety-three is part of the program.
1. Why the break-up email fails with enterprise buyers
- 01It mistakes silence for a decisionIn The Seven C’s, a deal moves when a Compelling Event makes delay expensive. A buyer with no dated reason to act is not rejecting you; they are doing what large organizations do, which is nothing, defensibly. Guilt does not create urgency. A signal does.
- 02It burns the only asset you builtThree or four messages have, at best, established that you understand the buyer’s job. A sardonic last note spends that on a laugh.
- 03It closes a door the buyer will later needInfrastructure buyers come back — after the next failed change, when the audit lands, when the new leader arrives. The last message should make that return easy, not awkward.
- 04It is single-threadedThe folklore break-up is sent to one person. In a committee deal, the right response to silence from the operator is often a different hook to the leader, not a fourth email to the operator.
2. Every touch carries something new
The sequence spine the program runs is five touches over thirteen days for a segment play and seven over twenty-one for a researched top-tier account. The craft rule for all of them is the same: no touch exists to remind the buyer that you exist. Each one changes the angle.
| Touch | Intent | What is new |
|---|---|---|
| Day 1 · Email | Earn a read with the signal; make the ask small | The verified event in the buyer’s world and one small, dated ask |
| Day 3 · LinkedIn note | Put a face to the email | One question they can answer in a sentence |
| Day 6 · Email | Change the angle | A second door — if the first email was about incidents, this one is about changes or resilience — or the insight behind the first |
| Day 9 · Call and voicemail | Make the sender real | Twenty seconds: the hook and the ask; it lifts the next read |
| Day 13 · Proof email (top tier) | Lower the cost of saying yes | One labelled proof point — measured, pilot-measured or an honest design target |
| Day 16 · Executive or peer note (top tier) | Borrow credibility | Three sentences from the founder, or a door-opener’s forwarded blurb |
| Last touch · Close the loop | End with dignity and a door | Permission, a resource, the right name, a condition |
“Just checking in” and “bumping this to the top of your inbox” are not touches. If there is nothing new to say, the touch is skipped. That rule alone removes most of what makes outbound feel like harassment.
3. The eight reply types, and the rule for each
Most replies are not yes. They are one of eight things, and a seller who has a rule for each never improvises under pressure.
| Reply | Rule |
|---|---|
| Interested, proposes a time | Confirm within the hour; send the hold with one line on what the call is for; no deck |
| Interested, asks for information | Send the two-pager and two time options; information without a time is a polite no, so offer the time |
| “Not now” with a reason | Thank them for saying so; record the reason and the date; ask one question that tests whether the reason is a Compelling Event in waiting |
| “We use [incumbent]” | “Keep it”; one question about what happens after the incumbent says “network”; no comparison, ever |
| “Wrong person” | Thank them; ask for the right name by role; ask permission to mention them |
| Objection | The fifteen-second response in writing, then one question back; never argue past the point |
| Opt-out or hostile | Same-day suppression; the account rests for a quarter; no reply beyond what the platform requires |
| Out of office | Note the return date; pause; resume two business days after return, not on it |
Speed is the one variable the seller controls completely. Replies inside two hours during the send block, the same day otherwise. In my experience it is the largest single factor in whether a reply becomes a meeting.
4. Close the loop
The last touch is not a break-up. It does four things in under eighty words: gives permission to stop, offers one resource, asks for the right name, and states the specific condition under which the seller would be glad to hear from them. Here are two from the library, written for a seller of network operations software; the brackets are the parts that change.
Subject: closing the loop
[First name]: I will stop here unless you tell me otherwise. If [a failed change / a site incident / an untested failover] makes this urgent later, this two-page overview explains what [Product] does and how a bounded pilot works: [link]. Thank you either way.
Subject: if the next change window goes wrong
[First name]: I will pause here. If the next change window at [Company] does not do what was intended and nobody can prove why, that is the moment this becomes worth twenty-five minutes — and the moment I would be glad to hear from you. [link] has the detail until then.
Notice what the condition does. It names the signal that will bring the buyer back, in their language, so that when the event happens — and in network operations it will — the seller is the first name they think of. The break-up email asks the buyer to feel something. The close-the-loop email tells them when to call.
5. Follow-through after the meeting
The sequence that fails most often is the one after a good call. Three templates fix it. The recap goes out the same day, in the buyer’s words, with the next step and the date in the first line:
Subject: what I heard, and the next step on [date]
[First name]: thank you for the time. What I heard, in your words: [the top pain, one line]; [the second, one line]; the cost: [hours / downtime / audit exposure]; the date that matters: [the Compelling Event]. Next step: [the walkthrough / the scoping session] on [date] at [time] with [names]. Before then I will send [the security summary / the pilot outline]. If I have any of this wrong, tell me and I will correct it.
A no-show gets two alternatives and an exit, with no reproach. And when a reply goes quiet after a meeting was agreed, a twenty-second voicemail takes the blame: “entirely my fault if I missed a message — if the walkthrough is still useful, two times are in your inbox; if not, no need to call back.” Nobody has ever been annoyed by that voicemail. Many have called back.
6. Re-engagement: a new signal, or nothing
A closed sequence rests the account for ninety days. The re-approach is not a fifth email; it is a new first email, built on a new signal, that references the earlier conversation in one line. Two shapes from the library:
Subject: before [the deadline]
[First name]: when we spoke you mentioned [the reason it was not the time]. With [the audit / migration / renewal] now on the calendar for [date], the evidence question — what changed, did it work, will failover work — gets asked by someone else. A bounded pilot finishes before that date if it starts by [date]. Twenty-five minutes to see whether that is realistic?
The other shape is the proof update: “one number since we spoke, measured, not modelled.” It is the only re-engagement email a buyer reads with interest, and it is available only to a vendor that labels its claims honestly — the subject of Infrastructure Buyers Have Heard “AIOps” Before.
7. The rules, in one place
- Every touch carries something new — a second door, a proof point, a question. No “just checking in.”
- Three contacts per account; silence from one is a reason to change the hook to another, not to send a fourth email to the first.
- Replies inside two hours during send blocks; same day otherwise.
- Eight reply types, eight rules. Never improvise an objection.
- The last touch closes the loop: permission, a resource, the right name, a condition. No guilt, no humour.
- A closed sequence rests ninety days. Re-approach only with a new signal.
- An opt-out is honoured the same day, everywhere, and the account rests a quarter.
The Seven C’s Outreach Program™
Ninety-three original templates by persona, trigger and stage — first touches, second doors, proof touches, close-the-loop notes, replies, re-engagement and events — adapted to your product and run with your team.
See the program »Your Biggest Competitor Is “No Decision”
Why most lost enterprise revenue has no competitor’s name on it, and the ninety-day program that beats indecision.
Read the program »Questions this piece answers
What should the last email in a sales sequence say?
Four things, in under eighty words: permission to stop (“I will stop here unless you tell me otherwise”), one resource (a two-page overview or a three-minute recording), a request for the right name if it is not them, and a specific condition for coming back (“if the next change window does not do what was intended”). No guilt, no humour, no “I guess this isn’t a priority.”
How many times should you follow up with an enterprise prospect?
Five touches over thirteen days for a segment play, seven over twenty-one for a researched top-tier account — across email, LinkedIn and the phone, with three contacts per account rather than one. Then rest the account for ninety days and come back only with a new signal.
How do you re-engage a prospect who said “not now”?
Thank them for saying so, ask one question that tests whether their reason is a Compelling Event in waiting (“does the migration make change evidence more important next quarter, or less?”), record the date they gave you, and do not write before it. When you return, name the new signal in the first line and reference the earlier conversation in one.
Part of the outreach series for companies selling into AIOps and network operations: Signal-Based Outbound for Network Operations, Selling to the NOC, this piece, Infrastructure Buyers Have Heard “AIOps” Before, Proof of Value That Converts and Operator Edition No. 05: The Outbound Agent Mandate.
Insight and ICP
One of the five stages of the Revenue Foundation. Every piece for this stage, in order, is on the Field Guide.
Open »The Seven C’s Outreach Program™
Sequences, reply handling and re-engagement are one part of the motion. The full system — signals, the committee, the message spine, the proof of value — is built with you.
See the program »New essays and operator tools, as they publish.
A few times a month, by email. No list is sold or shared; one click to leave.