11 B2B cold email frameworks that actually get replies
Intros, follow-ups, break-ups, referral asks — with commentary on why each structure works. Understanding the thinking is what makes the difference. The words are the easy part.
Part of our complete guide to B2B cold email.
The frameworks below are not ready-made emails — they’re annotated structures. The reply rates on these come from three things working together: a specific opening that proves you’ve done your research, a short value statement that speaks to a real problem, and a single low-friction CTA. None of those elements can be lifted wholesale from a template. The placeholders in accent are not cosmetic tweaks — they’re the entire job.
Most cold email fails not because the structure is wrong, but because the research behind it is thin. A generic observation in an “observation opener” is worse than no opener at all — it signals immediately that you haven’t done the work. The frameworks here show you what good execution looks like at the sentence level, so you understand what you’re actually producing when it’s done properly.
Tested on UK B2B outreach across SaaS, agencies, recruitment and professional services. These structures have pulled 5%+ reply rates when properly executed — with genuine research behind each personalisation point and clean deliverability infrastructure. Pair with a subject line from our subject line guide, or see the full best practices playbook for the wider context.
Browse by sequence position. For each framework, read the Why it works note — that’s the part that transfers to new contexts.
1. The specific-observation opener
Hi {first name},
Noticed {specific observation — hire, launch, funding, post, initiative}. Makes sense given {why it's interesting for their business}.
We help {their type of company} {specific outcome — e.g. "book 3–5 qualified calls a week from UK SMB accounts"} without adding headcount. Thought it might be timely.
Worth a 15-minute chat next week?
{Your name}
Why this is harder than it looks
The specific-observation opener only works if the observation is genuinely specific. “Noticed you’re growing fast” is not an observation — it’s filler. A real observation is: “Noticed you just hired a Head of Partnerships after two years of purely founder-led sales.” Finding that, validating it, and connecting it to a relevant business point takes 15–25 minutes per prospect. Multiply that across 200 contacts per month and you have a full-time research job before you’ve written a single word.
2. The “permission to pitch”
Hi {first name},
Is {specific problem — e.g. "building predictable outbound pipeline"} something {their company} is actively working on right now?
If yes, I'll send over how we've helped {similar company} {specific result}. If no, happy to bow out.
{Your name}
3. The “peer result”
Hi {first name},
Short version: {similar company in their sector} came to us {timeframe} ago with {problem}. In {timeframe} they {specific measurable outcome}.
{Their company} feels structurally similar — same {ICP / GTM motion / stage}.
Happy to walk through exactly what we did if it's relevant. 15 minutes?
{Your name}
4. The “bump” (3 days later)
Hi {first name},
Bumping this up — imagine your inbox is chaos.
Worth a quick look, or shall I park it?
{Your name}
5. The value-add follow-up
Hi {first name},
In case it's useful — wrote up {relevant resource / data point / short insight} that covers {the thing I thought would matter to them}: {link or one-line takeaway}.
No reply needed. If the original email isn't relevant, just say and I'll stop following up.
{Your name}
6. The clean break
Hi {first name},
Last one from me — doesn't look like now's the right time for {what you offered}, which is fair enough.
If things change, you know where I am. Genuinely wishing {their company} the best.
{Your name}
7. The “wrong person?” break-up
Hi {first name},
Might have pinged the wrong person — who handles {specific area} at {their company} these days?
Happy to stop here if it's not you.
{Your name}
8. The warm referral ask
Hi {first name},
Short and direct: we're looking to talk to {specific role} at {specific company type / size} about {specific thing}.
Anyone obvious come to mind from your network?
No pressure if not — just thought I'd ask directly rather than circle round.
{Your name}
9. The new-hire trigger
Hi {first name},
Saw {new hire's name} joined as {role} — congrats.
If {specific thing that new role typically triggers — e.g. "you're now mapping out outbound for the first time"} is on the near-term list, we've helped {similar company} {specific outcome} in a setup almost identical to yours.
Want me to send a 90-second Loom of how we'd approach it for {their company}?
{Your name}
10. The funding-round trigger
Hi {first name},
Congrats on the {round size / stage}.
Usually post-raise the pressure's on to {specific thing — scale pipeline, hit revenue plan, justify the valuation}. If {outbound / the thing you do} is part of that, we help {similar stage companies} {specific outcome} without hiring an SDR team you'll have to unwind.
Worth a 15-minute call?
{Your name}
11. The “it’s been a while”
Hi {first name},
We spoke back in {month / year} about {what you discussed}. Timing wasn't right then.
Checking in — is {same problem, maybe rephrased for their current stage} back on the agenda? We've shipped a lot since we last spoke, and {similar company that's gone through the same cycle} just came back round for exactly this reason.
If timing's still off, all good.
{Your name}
Before you build a sequence around these
Two things to understand: first, none of these structures survive without genuine research per contact — a templated “observation opener” with a generic observation is immediately detectable and will hurt your reply rate. Second, even well-executed emails land in spam if your infrastructure isn’t right. Run the deliverability checklist before sending a single email. And if the research load or the infrastructure setup sounds like more than you want to own, that’s exactly what PrawnMail handles. You can also browse all our free cold email guides for the full picture.
Want these written for you, properly?
The frameworks above take minutes to read and months to execute well at scale. PrawnMail handles the research, the writing, the infrastructure, and the follow-up. You just take the calls.
Hand us the writing