25 Cold Email Examples for B2B Sales (2026)

25 Cold Email Examples for B2B Sales (2026)

A useful cold email example does three things: it leaves personalization slots you actually fill (a trigger event, a named competitor, or a relevant metric — not just [FIRST_NAME]), it makes one ask (never "book a call, or reply, or check out our site"), and it stays short enough to scan quickly. Everything else — frameworks, power words, formatting tricks — is secondary. The examples below reflect structures we use at our cold email agency, grouped by scenario: sales, B2B, first contact with a potential client, meeting requests, cold call follow-ups, and breakups. Copy the structure, replace every [BRACKETED] token with something specific and true, and cut anything that does not earn its place. If you need the complete research-to-CTA process first, read how to write a cold email. If you would rather filter by industry and goal, use our interactive cold email template library.

Sales cold email templates

1. The trigger event

Subject: congrats on the [TRIGGER_EVENT]

Hi [FIRST_NAME],

Saw [COMPANY] just [TRIGGER_EVENT — raised a Series A / opened the Austin office / hired a new VP Sales]. Usually that means [LIKELY_PRIORITY] moves up the list fast.

We helped [SIMILAR_COMPANY] handle exactly that — they [SPECIFIC_RESULT] within [TIMEFRAME].

Worth a 15-minute look at how they did it?

[YOUR_NAME]

Why it works: the trigger event proves you researched them and gives the email a reason to exist today, not whenever.

2. The competitor mention

Subject: how [COMPETITOR] does [OUTCOME]

Hi [FIRST_NAME],

[COMPETITOR] has been using [APPROACH] to [OUTCOME] — it's part of why their [METRIC] jumped last quarter.

We built the same motion for [CLIENT] and got them [RESULT]. I put together a two-line breakdown of how it would map to [COMPANY].

Want me to send it over?

[YOUR_NAME]

Why it works: a relevant competitor gives the recipient an immediate reason to examine the approach. Use it only when the comparison and result are verifiable.

3. The specific-number opener

Subject: [NUMBER] [ICP_PLURAL] like [COMPANY]

Hi [FIRST_NAME],

We've worked with [NUMBER] [ICP — e.g. "B2B SaaS companies between 20 and 100 employees"] this year. The pattern: almost all of them were losing [METRIC] to [SPECIFIC_PROBLEM].

[CLIENT] fixed it in [TIMEFRAME] and now [RESULT].

If [SPECIFIC_PROBLEM] sounds familiar, happy to show you what they changed. Worth a look?

[YOUR_NAME]

Why it works: exact numbers read as evidence; round claims read as marketing.

4. The problem-agitate-solve

Subject: [PAIN_POINT] at [COMPANY]?

Hi [FIRST_NAME],

Most [ROLE_PLURAL] I talk to say [PAIN_POINT] quietly eats [COST — hours/week, pipeline, budget]. It rarely makes the quarterly priority list — until it stalls a number someone reports on.

We got [CLIENT] from [BEFORE] to [AFTER] without [COMMON_OBJECTION — new headcount, replacing their stack].

Open to a short call to see if the same fix applies?

[YOUR_NAME]

Why it works: it names the cost of inaction before pitching, which is the whole PAS framework in four lines. More structures like this in our guide to B2B cold email frameworks.

5. The blunt one-liner

Subject: quick question, [FIRST_NAME]

[FIRST_NAME] — are you the right person to talk to about [SPECIFIC_AREA] at [COMPANY], or is that someone else's desk?

Asking because we [ONE_LINE_VALUE_PROP], and [SIMILAR_COMPANY] just [RESULT] with it.

[YOUR_NAME]

Why it works: a routing question is easier to answer than a full sales pitch and helps you find the actual owner.

B2B cold email templates

6. The mutual connection

Subject: [MUTUAL_CONNECTION] suggested I reach out

Hi [FIRST_NAME],

[MUTUAL_CONNECTION] mentioned you're leading [INITIATIVE] at [COMPANY] and thought we should talk.

We do [ONE_LINE_VALUE_PROP] — most recently for [CLIENT], where [RESULT].

Would a 15-minute intro this week or next make sense?

[YOUR_NAME]

Why it works: a real mutual connection supplies context and trust. Only use it when the connection actually made the introduction or gave permission to mention them.

7. The case study lead

Subject: how [CLIENT] got [RESULT]

Hi [FIRST_NAME],

[CLIENT] — a [DESCRIPTOR] company like [COMPANY] — came to us with [PROBLEM]. [TIMEFRAME] later: [SPECIFIC_RESULT].

The playbook was three steps, and at least two apply directly to [COMPANY].

Want the one-page version?

[YOUR_NAME]

Why it works: the ask is for a document, not a meeting — a smaller yes that starts the conversation.

8. The relevant insight

Subject: noticed something on [COMPANY]'s [ASSET]

Hi [FIRST_NAME],

Was on [COMPANY]'s [ASSET — pricing page, careers page, product docs] and noticed [SPECIFIC_OBSERVATION].

Companies we work with usually see that when [ROOT_CAUSE]. [CLIENT] had the same signature and fixed it by [FIX] — worth [RESULT] to them.

Happy to share exactly what we spotted. Useful?

[YOUR_NAME]

Why it works: an observation about their asset can't be mistaken for a mail merge.

9. The industry benchmark

Subject: [INDUSTRY] benchmark: [METRIC]

Hi [FIRST_NAME],

We pulled [DATA_SCOPE — e.g. "reply data from 2M cold emails"] across [INDUSTRY]. Median [METRIC] is [NUMBER]; top quartile runs [NUMBER].

Most of the gap comes down to [FACTOR].

Want the benchmark breakdown? Takes one reply — I'll send the full data.

[YOUR_NAME]

Why it works: benchmarks exploit a universal itch — everyone wants to know where they rank.

10. The "not a pitch"

Subject: not selling anything (yet)

Hi [FIRST_NAME],

Genuinely not pitching in this email. We're researching how [ROLE_PLURAL] at [COMPANY_TYPE] handle [PROCESS], and your name keeps coming up as someone who does it well.

One question: what's the single most annoying part of [PROCESS] today?

Reply in a sentence — I'll share the aggregated answers from everyone we ask.

[YOUR_NAME]

Why it works: flattery plus a one-sentence ask plus something in return. Only run it if you'll actually share the results.

Cold email templates for emailing a potential client

11. The portfolio proof

Subject: [RESULT] for a [DESCRIPTOR] like [COMPANY]

Hi [FIRST_NAME],

We just wrapped a project for [CLIENT], a [DESCRIPTOR] in [SPACE]: [SPECIFIC_RESULT].

[COMPANY] is in a similar spot — [ONE_LINE_OBSERVATION about their situation].

If [OUTCOME] is on your roadmap this year, I'd love 15 minutes to walk through what worked.

[YOUR_NAME]

Why it works: potential clients buy pattern recognition — "we've done this for someone shaped like you" beats any feature list.

12. The free sample

Subject: did a quick [DELIVERABLE] for [COMPANY]

Hi [FIRST_NAME],

I spent 20 minutes on [COMPANY]'s [AREA] and put together [SMALL_DELIVERABLE — a teardown, three fixes, a mockup]. No strings — it's attached / linked.

The biggest quick win: [ONE_INSIGHT].

If it's useful, I'll do the full version on a call.

[YOUR_NAME]

Why it works: useful work delivered before the ask demonstrates relevance before requesting the prospect's time.

13. The referral fork

Subject: right person at [COMPANY]?

Hi [FIRST_NAME],

We help [ICP] with [OUTCOME] — [CLIENT] got [RESULT] last quarter.

Are you the person who owns [AREA] at [COMPANY]? If it's someone else, would you mind pointing me their way?

Either answer helps. Thanks!

[YOUR_NAME]

Why it works: it gives the reader two easy outs, and both move you forward.

14. The budget-season timing

Subject: before [COMPANY] locks [TIMEFRAME] budgets

Hi [FIRST_NAME],

Most [COMPANY_TYPE] teams we work with finalize [NEXT_PERIOD] plans around now — and [CATEGORY] is usually decided in the next few weeks.

Quick context before that happens: [CLIENT] moved to us mid-cycle and [RESULT], at [COST_COMPARISON].

Worth a call before the numbers are locked?

[YOUR_NAME]

Why it works: it attaches your pitch to a deadline the prospect already has, so "later" stops being the default answer.

Meeting request cold email templates

15. The 15-minute frame

Subject: 15 minutes, [DAY]?

Hi [FIRST_NAME],

We help [ICP] [OUTCOME] — [CLIENT] saw [RESULT] in [TIMEFRAME].

I think [COMPANY] could get similar numbers because [ONE_LINE_REASON].

Do you have 15 minutes on [DAY] or [DAY]? I'll bring the [CLIENT] playbook and you keep it either way.

[YOUR_NAME]

Why it works: two concrete day options make the next step unambiguous and easy to answer.

16. The agenda-first meeting ask

Subject: agenda for a 15-min call

Hi [FIRST_NAME],

If you gave me 15 minutes, here's exactly how I'd spend them:

1. Two minutes: how [CLIENT] fixed [PROBLEM]
2. Ten minutes: whether the same approach maps to [COMPANY]
3. Three minutes: you decide if it's worth a second call

No deck, no discovery-question marathon. [DAY] or [DAY] work?

[YOUR_NAME]

Why it works: the agenda kills the real objection to sales calls — fear of a wasted hour.

17. The event tie-in

Subject: both at [EVENT]?

Hi [FIRST_NAME],

Saw [COMPANY] is at [EVENT] next month — we'll be there too.

We work with [ICP] on [OUTCOME] ([CLIENT]: [RESULT]). Rather than pitch you in a hallway, want to lock 15 minutes for coffee on [DAY]?

If schedules don't line up, happy to do a call the week after instead.

[YOUR_NAME]

Why it works: a shared event makes a meeting request feel like logistics, not a pitch.

18. The named-stakeholder meeting

Subject: [YOUR_COMPANY] + [COMPANY] — intro call

Hi [FIRST_NAME],

I'm reaching out to you and not someone else at [COMPANY] because [SPECIFIC_REASON — you own X, you posted about Y].

One sentence on us: we [VALUE_PROP], and [CLIENT] [RESULT].

Can we take 15 minutes on [DAY]? If I'm wrong about you being the owner, tell me who is and I'll leave you alone.

[YOUR_NAME]

Why it works: explaining why them preempts the most common silent objection: "why am I getting this?"

Cold call follow-up email templates

19. After a voicemail

Subject: just left you a voicemail

Hi [FIRST_NAME],

Just left a voicemail — short version in writing:

We help [ICP] with [OUTCOME]. [CLIENT] got [RESULT] in [TIMEFRAME], and I think [COMPANY] fits the same pattern because [REASON].

Easier to reply here than call back? Just say "send more" or "not interested" — both totally fine.

[YOUR_NAME]

Why it works: voicemail plus email is one touch in two channels — and offering "not interested" as a valid reply gets answers either way.

20. After a call that went well

Subject: recap + the [RESOURCE] I mentioned

Hi [FIRST_NAME],

Good talking earlier. Recapping so nothing lives only in my notes:

• Your priority: [WHAT_THEY_SAID]
• Where we can help: [ONE_LINE_FIT]
• Next step we agreed: [NEXT_STEP] by [DATE]

The [RESOURCE] I mentioned is attached. Anything I misheard, correct me — otherwise I'll get [NEXT_STEP] moving.

[YOUR_NAME]

Why it works: the prospect's own words, played back, do the selling — and a written next step actually gets kept.

21. After a call where they said "not now"

Subject: noted — circling back [MONTH]

Hi [FIRST_NAME],

Understood on the timing — you said [THEIR_REASON], which makes sense.

I've set a note to check back in [MONTH]. Until then, one thing worth having: [RESOURCE] — it's what [CLIENT] used to prep before working with us.

If anything changes sooner, you know where I am.

[YOUR_NAME]

Why it works: it converts a rejection into a scheduled re-open with permission attached. For the full sequencing playbook — timing, spacing, how many touches — see our cold email follow-up guide.

Breakup and re-engagement templates

22. The classic breakup

Subject: closing the loop

Hi [FIRST_NAME],

I've reached out a few times about [TOPIC] and haven't heard back — which usually means it's not a priority right now. No hard feelings; I'll stop emailing.

If things change, this is the one line to remember: we help [ICP] [OUTCOME], and it takes one reply to restart.

All the best with [INITIATIVE/COMPANY].

[YOUR_NAME]

Why it works: it closes the sequence clearly, removes pressure, and gives an interested prospect one simple way to restart it.

23. The permission close

Subject: should I close your file?

Hi [FIRST_NAME],

Quick one: I'm cleaning up my pipeline and [COMPANY] is on the "no response" list.

Before I close it out — was the silence a "not interested," a "not now," or a "wrong person"?

One-word reply is plenty. If it's "not now," I'll check back in [TIMEFRAME] and not before.

[YOUR_NAME]

Why it works: multiple-choice replies take five seconds to answer, and each option tells you exactly what to do next.

24. The something-changed re-engagement

Subject: new since we last spoke

Hi [FIRST_NAME],

We talked back in [MONTH] and the timing wasn't right. Two things have changed since:

1. [NEW_DEVELOPMENT on your side — feature, result, offer]
2. [TRIGGER at their company — funding, hire, launch]

Given #2, [OUTCOME] might have moved up your list. Worth revisiting for 15 minutes?

[YOUR_NAME]

Why it works: "checking in" gives them nothing to respond to; two concrete changes give them a reason.

25. The 90-day revival

Subject: [COMPANY] still doing [PROCESS] the old way?

Hi [FIRST_NAME],

When we spoke ~90 days ago, [COMPANY] was handling [PROCESS] with [OLD_APPROACH] and it was costing [PAIN].

If that's still true, the math got worse: [CLIENT] switched last quarter and is now at [RESULT].

If you've since fixed it — genuinely, congrats, ignore me. If not, want to see their setup?

[YOUR_NAME]

Why it works: it reopens the original pain with a fresh data point, and the "ignore me" out keeps the tone human.

The rules that make any template work

Templates fail in the execution, not the copy. The non-negotiables:

• Keep subject lines concise. Put the useful context first so truncation does not hide it. See our cold email subject lines guide.
• One CTA per email. Every additional ask lowers the odds of any action. Pick the meeting, the reply, or the resource — never all three.
• Keep it brief. If a line can be deleted without changing the meaning, delete it.
• Plain text, no HTML. No images, no logos, no more than one link. Heavy formatting reads as marketing to both humans and spam filters.
• Fill every token with research, not defaults. [FIRST_NAME] alone is not personalization; a trigger event, competitor, or observation is.
• Follow up deliberately. The follow-up sequence matters as much as the opener; each touch should add context rather than repeat the first email.

FAQ

How long should a cold email template be?

There is no universal word count, but shorter is usually easier to scan. Put the reason for writing and the relevance in the first two lines, make one request, and remove anything that does not help the recipient decide whether to respond.

Should I personalize every cold email, or is a template enough?

Both. The template is the structure; personalization is what goes in the slots. A template sent with only [FIRST_NAME] and [COMPANY] swapped is a mail merge and performs like one. Fill at least one slot per email with genuine research — a trigger event, a named competitor, an observation about their site — and the template stops feeling like a template.

How many follow-ups should I send with these templates?

Use one initial email plus two or three follow-ups over roughly two weeks, each adding something new — a relevant case study, a useful observation, or a different angle — rather than "just bumping this." The breakup example (#22) is the final touch. Full spacing and timing are in our follow-up guide.

Do these templates work for any industry?

The structures do; the slots don't. A trigger-event email works identically for SaaS, agencies, or logistics — but the trigger, metric, and proof point must come from the prospect's world. If you want templates pre-filtered by industry and goal, use the interactive template library, then customize from there.