The B2B cold email sequence that gets replies: a five-touch framework

Most B2B cold email sequences do not fail on copy. They fail because the mail never reached the inbox, the list was never qualified, or the five touches all ask for the same meeting in slightly different words. I run outbound through Sail Force Marketing across Europe, Africa and the US, and the fix is almost always structural rather than literary. Here is the sequence framework I use, the infrastructure it sits on, and the five numbers that tell you which part is broken.

Fix the list before you touch the copy

A sequence is an amplifier. Point it at the wrong accounts and it amplifies the wrong thing, usually your domain reputation falling over. Before I write a single line, every account on the list has to clear a written bar: a named trigger, a problem we can state in the prospect's own language, and a buyer who owns the budget for it. I set out the full five-part test in the qualification bar that decides whether your pipeline is real, and it has not changed.

Two hundred accounts you can describe precisely will outperform two thousand you scraped by job title. The test is simple: if you cannot finish the sentence "we are writing to them this month because..." with something specific to that company, they do not belong in the sequence yet.

The deliverability floor you cannot write your way past

Since February 2024, Google requires senders of more than 5,000 messages a day to Gmail accounts to authenticate with SPF and DKIM, publish a DMARC policy, support one-click unsubscribe on subscribed mail, and keep spam complaint rates below 0.3%. Google's guidance is to stay under 0.1% and never reach 0.3%, which is a far tighter bar than most founders assume. The requirements are published in Google's email sender guidelines. Microsoft followed with equivalent rules for Outlook.com, requiring SPF, DKIM and DMARC from domains sending more than 5,000 messages a day, announced in its requirements for high-volume senders.

In practice that means the following, and it takes an afternoon rather than a quarter:

• Send from a separate domain. Use a lookalike of your primary domain for outbound so a bad month does not damage the mail your customers and investors rely on.
• Authenticate properly. SPF, DKIM and a DMARC record that is actually aligned, not a placeholder set to none and forgotten.
• Cap volume per mailbox. I keep new mailboxes well under fifty sends a day and ramp slowly over several weeks. Volume is the cheapest thing to add and the fastest way to get filtered.
• Verify every address before it enters the sequence. A bounce rate drifting above 2% is a stop signal, not a statistic to report.
• Strip the clutter. No tracking pixels you do not read, no link shorteners, no images, no HTML signature with four social icons. Plain text reads like a person wrote it, because a person did.

Copy cannot rescue a sequence that is being filtered. Infrastructure is not the boring part of outbound, it is the part that decides whether the interesting part is ever read.

Touch one: one reader, one problem, one ask

The first email has one job, which is to earn a reply, not to book a meeting. Those are different outcomes and conflating them is why so many first emails read like a brochure with a calendar link stapled to the end.

My constraint is ninety words or fewer, four moves, in this order.

1. The reason you are writing to them. One clause, specific to their company, that could not be pasted into another email.
2. The problem, in their language. Not your category, not your product name. The operational symptom they would complain about to a colleague.
3. One sentence of evidence. What you do about that problem, stated plainly, without adjectives.
4. A question, not a request. Something answerable in one line from a phone.

A skeleton you can fill in today

"Hi [name], I saw [specific trigger]. When teams do that, the usual pressure point is [operational symptom]. We handle [the narrow thing you do] for [type of company]. Is [symptom] actually on your list this quarter, or is something else ahead of it?"

That last question is doing the real work. It gives the prospect a way to reply that is not yes or no, and a no is useful: it tells you whether the problem you chose is the problem they have. The failure modes are predictable. Opening with a paragraph about yourself. Two asks in one email. A calendar link before there is any reason to click it. Flattery about their "impressive growth journey", which every buyer now reads as a template.

Touches two to five: every email has a different job

The reason "just following up" fails is that it adds no new information, so the prospect has no new reason to reply. Each touch after the first should change something: the evidence, the angle, or the ask. Five touches across roughly eighteen days is the shape I use.

• Day 1, the opener. The ninety-word email above.
• Day 3, the proof. One concrete mechanism or number from your own operation, in two sentences. Same ask, new evidence.
• Day 7, the angle change. Assume you chose the wrong problem. Name a second, adjacent problem the same buyer owns, and ask which of the two is closer to their reality.
• Day 12, the asymmetric give. Send something useful that costs them nothing to accept: a checklist, a teardown of their current funnel step, a short answer to the question most of their peers ask. No ask at all in this one.
• Day 18, close the loop. Tell them plainly you are stopping, and ask whether to revisit in a quarter or drop it. Written without sarcasm, this gets more replies than any other touch in the sequence.

Change the sender on touch three if you can. An email from the founder, after two from an SDR, legitimately changes the conversation. What should not change is the thread: keep the sequence in one thread so the prospect has the context in front of them.

Personalisation that scales without pretending

Personalisation is not a first name in a subject line. It is proof that a human chose this company. I work in three tiers and assign them by account value rather than by habit.

Tier one accounts get a researched opening clause written by a person: a hiring pattern, a new market, a product change, a comment the buyer made publicly. Tier two gets a role-level problem statement shared across a tight segment, which is honest because the problem genuinely is shared. Tier three gets no personalisation and leans entirely on specificity and brevity, which is better than a fabricated compliment.

The line I do not cross: never invent a detail, a mutual connection or a reference. I treat a stranger's attention as borrowed rather than owed, and that is stewardship as much as it is tactics. It comes from my faith before it comes from any playbook, and it also happens to be commercially correct, because every exaggeration you send is a liability you have to defend on the call.

The five numbers that tell you what to fix

Teams usually track one number and argue about it. Track these five in order, because each one isolates a different failure.

• Bounce rate. Above 2%, stop and clean the list. Nothing downstream is measurable until this is fixed.
• Open rate. Directionally useful only. Privacy proxies inflate and suppress it, so never optimise against it. Use it to detect a deliverability collapse, not to grade copy.
• Reply rate. The honest measure of whether the first email earns attention. Low replies with healthy delivery is a copy and targeting problem.
• Positive reply rate. Replies that want a conversation, as a share of all replies. This is the number that exposes a list of the wrong people, because plenty of replies can mean plenty of wrong readers.
• Meetings held, not meetings booked. The gap between the two is where most reported pipeline quietly dies. A booked meeting is an intention, a held meeting is a fact.

If one number is broken, fix that number. A rewrite of the copy will not repair a bounce rate, and a cleaner list will not repair a vague ask.

What to do this week

Pick one segment, not your whole market. Cut it to the accounts that clear the qualification bar, verify every address, check SPF, DKIM and DMARC on the sending domain, then write the five touches in one sitting so the arc holds together. Send to fifty accounts, hold the volume there for two weeks, and read the five numbers before you change a word. If you want the rest of the system this sits inside, the Sales Growth library is free and has no gate on it.