11 B2B cold email templates that get replies (copy + paste)

A template is a frame with one variable slot, and the slot is the only part that earns the reply. Everything below gives you the frame, the precondition that makes each one legitimate to send, the failure condition that kills it, and where it belongs in a sequence — five for the first touch, four for follow-ups, two for closing the loop. Paste them, fill the one line that has to be true of exactly one company, and delete a sentence every time you add one.

Three rules that make a template stop reading like one

Template the frame, hand-write the hook. Lines two through five are structure. Line one has to be false about almost everybody. The mechanical test is to paste your first line into a different prospect's email — if it still reads fine there, it is filler.

Stay under 100 words. Every template below fits on one phone screen without scrolling. Adding a sentence means deleting one.

Zero links on the first touch. Autocloz's pre-send scorer starts penalising a body once it carries more than three links, at four points per extra, and adds a flat twelve for a known shortener domain. A cold message has no prior engagement with that recipient to offset any of it.

The merge variables used below — {{ first_name }}, {{ title }}, {{ company.name }}, {{ company.industry }}, {{ sender_name }} — are the ones the Autocloz renderer resolves directly, with inline fallbacks such as {{ first_name | default: "there" }}. Anything in braces that is not on that list is a slot you write yourself. The render order, what a blank actually looks like in a delivered message, and how to size a field before you write copy that depends on it are covered in personalisation at scale.

Five templates for the first touch

Each carries a precondition. Sending one whose precondition is false is not a weak email, it is a false claim, and readers punish that harder than they punish mediocrity.

1. The problem-opener

Precondition: you have one specific, checkable observation about their company and a genuine hypothesis about what it implies.

Subject: {{ company.name }} and the {problem in three words} problem

Hi {{ first_name }},

{one specific, verifiable observation about their company}.

Teams at that stage usually hit {specific pain} before they hit {next milestone} — it shows up as {how it actually looks on a Tuesday}.

We fix that by {mechanism in one clause}, which is how {comparable customer} got to {outcome} without adding headcount.

Worth 15 minutes next week?

{{ sender_name }}

Why it works. The observation buys the second sentence, and the pain is described the way their team describes it internally rather than the way your category markets it.

Fails when the observation is a commodity. If three other vendors cited the same public fact this week, the specificity is worth nothing and you have spent your best line on it.

2. The trigger event

Precondition: the trigger happened inside the last two weeks and you can name a consequence of it that is not obvious.

Subject: congrats on the {trigger}

Hi {{ first_name }},

Saw the {trigger} — congratulations.

In our experience the quarter after a {trigger} is when {consequence} gets loud: {specific operational symptom}.

{comparable customer} was in the same spot and handled it by {approach}. Happy to walk you through what they did, whether or not it involves us.

Open to a short call?

{{ sender_name }}

Why it works. The trigger is a legitimate reason to be in the inbox this week, and offering the approach regardless of the outcome lowers the perceived sales pressure enough to make a reply cheap.

Fails when the trigger is heavily mined. Funding announcements generate more competing outreach than any other public signal, so pair the trigger with a second, quieter detail or skip it.

3. The mutual connection

Precondition: the mutual has actually agreed to be named. Not "would probably be fine with it".

Subject: {mutual name} suggested I reach out

Hi {{ first_name }},

{mutual name} mentioned you own {topic} at {{ company.name }} — we worked together on {shared context}.

Short version: we help {{ title }}-level teams {outcome}. {mutual name} thought it was worth a look given {reason specific to you}.

Happy to send the two-minute version by email, or take 15 minutes if that is easier.

{{ sender_name }}

Why it works. It borrows trust you have not earned yet, and the two-option close is still one decision because both options are cheap.

Fails when the prospect checks. A vouch that turns out to be hollow costs you the account and the referrer in one message, which is the worst return available in outbound.

4. The peer proof

Precondition: the named customer is genuinely comparable — same industry, roughly the same shape — and the result is one you can defend under a follow-up question.

Subject: how {comparable customer} handled {problem}

Hi {{ first_name }},

{comparable customer}, also in {{ company.industry }}, was spending {specific effort} on {task} every week.

They moved it to {mechanism} and now {result you can defend}, with the same team.

If {{ company.name }} runs that process the same way, the comparison is probably useful either way.

Worth a 15-minute look?

{{ sender_name }}

Why it works. The proof carries the claim, so you never have to describe yourself as leading or best-in-class.

Fails when the number is invented. State the qualitative change instead if you cannot defend the figure — a fabricated statistic loses a technical buyer permanently and is not recoverable by a later correction.

5. The one-line ask

Precondition: the recipient is senior enough that brevity reads as respect rather than as carelessness.

Subject: {one specific thing about their business}

{{ first_name }} — you are {observation}. We handle {job to be done} for {two peer companies}. Worth a look, or should I send this to {likely owner of the problem} instead?

{{ sender_name }}

Why it works. The redirect question is answerable in three words and gives a busy executive an easy, face-saving reply that still routes you to the right person.

Fails when it is sent below director level, where it reads as abrupt rather than as considerate of time.

Four follow-up templates

Most positive replies land on the third touch or later, so the follow-ups carry more weight than the opener. The rule for all four is the same: give a new reason to reply. The job each individual follow-up should do, and the threading and footer mechanics underneath them, are worked through in follow-up email templates that get replies.

6. The new angle

Subject: re: {original subject}

Hi {{ first_name }},

Different angle on my last note: the teams that get the most out of this are usually dealing with {second, narrower pain}, not {first pain} — I may have led with the wrong one.

{one-sentence proof tied to the second pain}.

Still worth 15 minutes, or is this not a this-quarter problem?

{{ sender_name }}

Fails when the second pain is a rephrasing of the first. That is transparent, and it converts a second chance into evidence that you are working from a script.

7. The value-first, no-ask

Subject: the {resource} I mentioned

Hi {{ first_name }},

No ask here. We pulled together {specific, genuinely useful artefact} for {{ company.industry }} teams and yours is the profile it was built for.

{one line on what is in it and why it is not a brochure}.

Happy to send it over if useful.

{{ sender_name }}

Fails when the artefact is a gated whitepaper. Send the thing; a form in place of the thing turns a gift into a transaction and the reader can see the switch.

8. The three-line bump

Subject: re: {original subject}

{{ first_name }} — bumping this once in case it got buried.

If {outcome} is not a priority this quarter, say so and I will close the loop.

{{ sender_name }}

Fails when it is used as touch two. A bump carrying no new information this early wastes your best remaining attempt on a message with nothing in it.

9. The internal referral ask

Subject: wrong person?

Hi {{ first_name }},

I may have this wrong — is {problem area} yours, or does it sit with someone else at {{ company.name }}?

Happy to take it there directly if so, and I will stop emailing you either way.

{{ sender_name }}

Fails when you keep emailing after the referral. The promise to stop is the part that gets this answered, so honour it or do not send it.

Two templates for closing the loop

10. The breakup

Subject: closing the file on this

Hi {{ first_name }},

I will stop here so I am not cluttering your inbox.

If {outcome} moves up the list — usually around {realistic trigger} — reply to this thread and I will pick it straight back up.

All the best,

{{ sender_name }}

Why it works. It is frequently the highest-replying message in a sequence, and the mechanism is loss aversion rather than persuasion: it is the only touch that is credibly final. How to write a breakup email covers the phrasing that keeps it from reading as a tactic.

Fails when you send another email afterwards. That single follow-up destroys the credibility of every breakup email sent from that domain, including the ones already delivered.

11. The re-engagement, six months later

Subject: {specific thing that changed}

Hi {{ first_name }},

We spoke in {month} and the timing was wrong. {Specific thing that has changed since — a capability, a new peer customer, a shift in their market}.

Reason I am back: {why the change matters specifically to them}.

Worth revisiting, or still not now?

{{ sender_name }}

Fails when nothing has actually changed. "Circling back after six months" is worse than never emailing again, because it tells the reader your sequences run on a calendar rather than on a reason.

Assembling eleven templates into one five-touch sequence

Templates are not interchangeable, and the most common mistake is treating the list above as a menu rather than as parts.

A workable default cadence, with the reason each slot holds what it holds.

• Touch 1, day 0 — the problem-opener, or the trigger event if you have a fresh trigger, or the mutual connection if you have a real one. Those three are alternatives, never a sequence: they are all first touches and stacking two of them means the second one is claiming a relationship the first already used up.
• Touch 2, day 3 — the new angle. Early enough that the first message is still faintly in memory, and it does the one job a second touch can do that a bump cannot: it offers a second way for the reader to recognise themselves.
• Touch 3, day 7 — the value-first, no-ask. This is the touch that changes the reply from a commitment into an opinion, which is a far lower bar, and it is the slot where most sequences waste a message on "just checking in".
• Touch 4, day 12 — the three-line bump, or the internal referral ask if you suspect you have the wrong person. Both are cheap to answer and both convert silence into information.
• Touch 5, day 18 — the breakup. Final, and it has to actually be final.

The peer proof and the one-line ask are alternates for touch one against particular segments rather than additional touches, and the six-month re-engagement is a separate campaign that runs later against the closed pile.

Two spacing notes. Do not compress this below about eighteen days end to end; the gaps are what stop five messages reading as pressure. And past six touches you are usually making a volume decision presented as persistence, which concentrates your least-wanted messages on the people least interested in receiving them. The sequence builder lays the spacing out in the browser before you commit to it.

Three checks before any of these enters a sequence

Send yourself the version with a blank field. Set the company name empty and read what arrives. A greeting addressed to nobody at nothing ships regularly and produces no error at any layer; Autocloz's scorer treats an unresolved {{ ... }} reaching the final text as its single heaviest structural penalty, 25 points, precisely because it means a template met a record it did not fit.

Check coverage before you check copy. If only 40% of a segment has a job title, a template whose second line depends on {{ title }} is a template that is wrong for the other 60%. Segment those rows out or write them a different message.

Test the exits, not just the send. Reply to your own test and confirm the next touch does not fire. If your cadence runs on more than one channel, check specifically whether a reply on one stops the others — in Autocloz an inbound SMS or WhatsApp message does not stop an email enrolment, so a mixed cadence needs that checked by hand rather than assumed.

Autocloz's free plan covers 5 users, 10 mailboxes and 100,000 contacts with mailbox warmup and authentication monitoring included — start free and load one of these into a real sequence rather than a test file.

Template debt, and the quarterly review that clears it

Template libraries rot in a specific way: the copy stays fine and the precondition underneath it stops being true. The named customer is no longer comparable, the mechanism changed, the market moved, the person who could vouch has left.

Once a quarter, read every active template and answer three questions in writing. Is its precondition still true? Is every factual claim in it still defensible under a follow-up question? Has it been sent at least once in ninety days? A template failing the first is a false claim in production. One failing the second is a liability with a technical buyer. One failing the third is dead and should be archived, because a library nobody trusts is one people write around.

Then check the one thing that quietly invalidates the whole set: the pricing, plan limits and capability claims embedded in your copy. Those are the claims most likely to have moved without anyone updating the templates that repeat them.

What a template cannot do for you

It cannot substitute for the researched line. A template that supplies line one is a mail merge. The reader cannot tell you how they knew, but they knew.

It cannot rescue a wrong list. A well-structured message to somebody without the problem is a well-structured no.

It cannot make an undelivered message work. Copy is the last thing to fix, not the first. Authentication, warmup state and list hygiene decide whether any of this is read, and a copy test run on mail that landed in spam produces a confident, wrong conclusion.

It cannot carry a claim you cannot defend. Every slot marked "result you can defend" means exactly that. If the honest answer is qualitative, write the qualitative version.

And a first touch cannot be multi-channel by itself. Where a sequence mixes email with a call, a LinkedIn touch or a message, the channels have to share a timeline and a stop rule or you will contact somebody twice about the same thing on two surfaces. One sequence spanning email, calling, LinkedIn, SMS and WhatsApp is the shape that makes the templates above safe to combine, and the Autocloz and Apollo comparison sets out where a template library sits inside a wider engagement stack.