The B2B cold email templates that get replies are short (50–120 words), open with a reason that is specific to the prospect, offer one clear outcome, and end with a low-effort question rather than a demand for a 30-minute call. Below are 25 ready-to-adapt templates, grouped by situation: trigger events, problem-led openers, social proof, referrals, low-friction asks, follow-ups and break-up emails.
Replace every [placeholder] with real research on the account; generic fill-ins read like spam. For the full outreach system (targeting, list building, deliverability and compliance), read our guide to B2B cold email that books meetings without burning your domain.
Contents
- What makes a B2B cold email template work
- Subject lines that fit these templates
- Trigger-event templates (1–5)
- Problem-led templates (6–10)
- Proof and case-study templates (11–14)
- Referral and mutual-connection templates (15–17)
- Low-friction ask templates (18–20)
- Follow-up and break-up templates (21–25)
- Template selection table
- Personalisation worksheet
- Compliance basics before you send
- How to test templates
- FAQ
What makes a B2B cold email template work
Every template below follows the same four-part structure, because each part answers a question the reader is silently asking:
- Why me? A first line that could only have been written to this person or company: a trigger event, a public post, a hiring signal, a product change.
- Why should I care? One problem or outcome that matters to their role, stated in their language rather than yours.
- Why believe you? One piece of proof: a similar customer, a specific result you can verify, or a credible observation.
- What now? One easy next step: a yes/no question, an offer to send something, or a short call.
Leave out long company introductions, multiple links, attachments, images and second calls to action; they make the email longer and, on new domains, more likely to be filtered.
Subject lines that fit these templates
Good subject lines look like an internal email: short, lower-case, specific and honest about the content (deceptive subject lines are prohibited under the US CAN-SPAM Act). Patterns that pair with the templates:
- Trigger: "your new [region] office", "congrats on the [round/launch]", "[role] hire at [company]"
- Problem: "[problem] at [company]?", "question about [process]"
- Proof: "how [similar company] fixed [problem]", "idea from [peer company]"
- Referral: "[mutual contact] suggested I reach out"
- Follow-up: reply in the same thread so the subject stays "Re: [original]"
Avoid all-caps, exclamation marks and fake "Re:" or "Fwd:" on a first email.
Trigger-event templates (1–5)
Trigger events give you a legitimate reason to write today, so the relevance is obvious.
1. New funding round
Subject: congrats on the [round]
Hi [First name], saw [Company] closed its [Series A] last week. Congratulations. Teams at this stage usually have to grow pipeline faster than they can hire SDRs. We help [type of company] build [outcome, e.g. a predictable outbound channel] in [timeframe] without adding headcount. Worth a short conversation, or is this already covered?
2. New executive hire
Subject: your first 90 days
Hi [First name], congratulations on joining [Company] as [title]. New [role] leaders often start with an audit of [area]. When we worked with [similar company], the quickest win was [specific change]. Happy to send a one-page checklist we use for that audit. Would it be useful?
3. Hiring for a relevant role
Subject: [role] hire at [Company]
Hi [First name], noticed you're hiring a [job title]. That usually means [problem the role solves] is a priority. While you recruit, we can [cover the gap / support the new hire] so [outcome] doesn't stall. Open to comparing notes on what the role needs to deliver in month one?
4. Expansion or new location
Subject: your new [city] office
Hi [First name], read that [Company] is opening in [city/market]. Launching a new market tends to mean [specific challenge, e.g. building local leads from zero]. We did this for [similar company] when they entered [market], and [verifiable result]. Want me to share what worked in their first quarter?
5. Content they published
Subject: your post on [topic]
Hi [First name], your post on [topic] made a sharp point about [specific idea]. One thing we see with teams that think this way is [related problem]. We help [type of company] solve it by [mechanism]. Curious whether that's on your radar for [quarter]?
Problem-led templates (6–10)
Use these when there is no fresh trigger but research shows a likely problem. Ask; don't accuse.
6. The observed gap
Subject: question about [process]
Hi [First name], I noticed [specific observation, e.g. your demo form asks for 11 fields]. For many [industry] teams that step [cost], because [reason]. We help fix it by [mechanism]. Would it help if I sent two quick ideas specific to your page?
7. The role-specific pain
Subject: [pain] at [Company]?
Hi [First name], most [job titles] I speak with say [pain] eats into [valuable thing, e.g. selling time]. Is that true at [Company] too? If it is, we've helped teams like [peer] [outcome] in about [timeframe]. If not, no worries, I'll leave it there.
8. The cost of doing nothing
Subject: [problem] and [quarter] targets
Hi [First name], when [problem] goes unfixed, it usually shows up later as [business consequence, e.g. a pipeline gap at quarter end]. A quick way to check: [simple diagnostic]. If the number looks off, we can help with [solution]. Want the diagnostic as a one-page sheet?
9. The industry change
Subject: [regulation/platform] change
Hi [First name], with [real industry change, e.g. new bulk-sender rules at Gmail and Yahoo], many [industry] teams are reviewing [process]. We've been helping [type of company] adapt by [mechanism]. Is this something your team has already worked through?
10. The competitor comparison (handle with care)
Subject: idea from [industry]
Hi [First name], a few [industry] companies have started [approach] to [outcome]. I don't know if it fits [Company], but given [reason it might], it seemed worth flagging. Want a short summary of how they set it up?
Proof and case-study templates (11–14)
Use these only with a comparable customer and a result you can verify if asked.
11. The similar-customer story
Subject: how [similar company] fixed [problem]
Hi [First name], [similar company], also a [size/industry] team, had the same [problem] last year. We helped them [what you did], and [verifiable result]. Given [shared trait], I thought a similar approach might work at [Company]. Worth 15 minutes to see?
12. The before-and-after
Subject: from [before] to [after]
Hi [First name], before working with us, [customer] [before state]. Now they [after state]. The change came from [one key mechanism]. If [Company] faces anything similar, I can walk you through exactly what we changed. Interested?
13. The free teardown
Subject: quick teardown of your [asset]
Hi [First name], I put together three notes on your [landing page / onboarding emails / ad] based on what has worked for [similar companies]. No pitch attached. Want me to send them over?
14. The credible observation (no case study yet)
Subject: something I noticed
Hi [First name], we're new to [industry], so I won't pretend to have a case study. But I noticed [specific, useful observation about their business], and I think [suggestion] could help with [outcome]. Is it worth me explaining in more detail?
Referral and mutual-connection templates (15–17)
Only use these when the connection is real; implying a relationship that doesn't exist destroys trust.
15. Direct referral
Subject: [mutual contact] suggested I reach out
Hi [First name], [mutual contact] at [their company] suggested I get in touch. We helped them with [outcome], and they thought [Company] might be dealing with something similar around [problem]. Would a short call make sense?
16. Right-person referral
Subject: right person for [topic]?
Hi [First name], I'm trying to reach whoever owns [area] at [Company]. Is that you? If not, could you point me in the right direction? Thanks either way.
17. Shared community or event
Subject: [event/community] follow-up
Hi [First name], we were both at [event] / are both members of [community]. Your comment about [topic] stuck with me, because [reason]. We work on [related problem] with [type of company]. Open to swapping notes?
Low-friction ask templates (18–20)
These suit senior prospects who rarely accept cold meetings.
18. The yes/no question
Subject: quick question
Hi [First name], is improving [outcome] a priority for [Company] this [quarter/half]? A one-word yes or no is perfect. If yes, I'll send a short idea; if no, I won't follow up.
19. The resource offer
Subject: [resource name] for [Company]
Hi [First name], we built a [checklist / calculator / benchmark template] that [job titles] use to [outcome]. It's free and takes about [time] to use. Want me to send it over?
20. The permission email
Subject: worth a conversation?
Hi [First name], I have an idea for how [Company] could [outcome], based on [research point]. Rather than write a long email, can I send a two-minute video walkthrough?
Follow-up and break-up templates (21–25)
Most replies to cold sequences come after the first email, so plan follow-ups before you send. Reply in the same thread, add something new each time, and stop when the person asks you to.
21. Follow-up 1 (2–3 days later): add value
Hi [First name], one more thought on [topic]: [new insight, resource or example]. Happy to share more if it's useful.
22. Follow-up 2 (4–5 days later): new angle
Hi [First name], a different way to look at [problem]: [second angle, e.g. cost, risk, time saved]. Does that match what you're seeing at [Company]?
23. Follow-up 3: social proof
Hi [First name], in case it's helpful, here's how [similar company] approached [problem]: [one-sentence summary]. Would a similar approach be relevant for you?
24. Follow-up 4: wrong person check
Hi [First name], I may have the wrong person. If someone else on the team owns [area], I'd be grateful for a name. If it's not a priority, just let me know and I'll close the loop.
25. Break-up email
Hi [First name], I haven't heard back, so I'll assume [problem] isn't a priority right now and won't email again about it. If that changes, my door is open. All the best with [current initiative].
Template selection table
| What you found | Best templates | Proof needed | Typical ask |
|---|---|---|---|
| Funding, launch or expansion news | 1, 4 | Low | Short conversation |
| New leader in a relevant role | 2, 19 | Low to medium | Send a checklist |
| Open job posting tied to your solution | 3 | Low | Compare notes |
| A visible weakness on their site or ads | 6, 13 | Medium | Send ideas or teardown |
| No trigger, but a clear role pain | 7, 8, 18 | Medium | Yes/no question |
| A comparable customer result | 11, 12 | High (must be verifiable) | 15-minute call |
| A real mutual contact or community | 15, 17 | Low | Short call |
| Not sure who owns the area | 16, 24 | None | Name of right person |
| Senior prospect, low meeting appetite | 18, 19, 20 | Low | Resource or video |
Personalisation worksheet
Fill in this worksheet for each account before you open a template. If you cannot fill in the first two rows, the prospect is probably not ready for a cold email yet.
| Field | Example (fictional) |
|---|---|
| Reason to write now | Hiring two SDRs, posted last week |
| Likely problem for this role | Ramping new reps while keeping pipeline steady |
| Outcome they care about | Booked meetings per rep per month |
| Proof you can verify | A similar 40-person SaaS client |
| Easiest next step | Send a 1-page ramp plan |
| Template number | 3, then 19 as follow-up |
Worked example
Here is template 3 filled in for the fictional example above (a 40-person software company, "Northbeam Analytics", hiring SDRs):
Subject: SDR hires at Northbeam
Hi Priya, noticed Northbeam is hiring two SDRs. That usually means outbound pipeline is a priority for Q1. While you recruit, we can run the research and first-touch sequences so meetings don't dip during ramp-up. Open to comparing notes on what the new reps need to deliver in month one?
Compliance basics before you send
The basics (general information, not legal advice):
- United States: the CAN-SPAM Act applies to B2B email with no exemption. According to the FTC's compliance guide, you need accurate header information, a non-deceptive subject line, identification of the message as an ad, a valid physical postal address and a clear way to opt out, with opt-outs honoured within 10 business days.
- United Kingdom: the ICO's B2B guidance says PECR's consent rule for marketing email does not apply to corporate subscribers, but you must identify yourself and give a valid opt-out address. Sole traders and some partnerships are treated as individuals and need consent or the soft opt-in. UK GDPR still applies when you email a named person.
- EU: rules vary by country; some member states require consent even for B2B email. Check the rules for each country you target.
- Mailbox providers: Gmail and Yahoo's bulk-sender requirements (in force since February 2024 for senders of 5,000+ messages a day to personal accounts) include SPF, DKIM and DMARC, a spam-complaint rate below 0.3%, and one-click unsubscribe for promotional mail. Cold B2B senders should treat these as the minimum standard even below that volume.
Our Affiliate Compliance: TCPA & PECR course covers consent and opt-out handling in more depth.
How to test templates
Treat templates as hypotheses. Test one variable at a time (the opening line or the call to action), send each version to a similar segment large enough that one or two replies don't decide the winner, and measure replies and meetings rather than opens, which privacy features in mail apps make unreliable. Classify replies as positive, "not now", negative or unsubscribe, and keep a swipe file of emails that earned meetings.
When a prospect does reply, answer fast. The same principle we explain in speed-to-lead follow-up applies to cold email replies: a quick, helpful response keeps the momentum the email created. You can also check a draft with the BFOUNT Cold Email Lab before it goes into a sequence.
FAQ
How long should a B2B cold email be?
Aim for roughly 50–120 words: enough for relevance and one piece of proof, short enough to read on a phone without scrolling.
How many follow-ups should I send?
A common sequence is the first email plus three or four follow-ups over two to three weeks, each adding something new. Stop as soon as the prospect asks.
Should I include links or attachments in a first cold email?
Usually not. They add friction and can trigger filtering on new domains. Offer to send the resource instead (templates 13 and 19).
Is cold emailing legal?
In the US and UK, B2B cold email is generally legal if you follow the rules summarised above (CAN-SPAM; PECR and UK GDPR). EU rules differ by country, so check each market and take legal advice where needed.
Can I use AI to personalise these templates?
Yes, for research and first drafts, but check every fact: a wrong "personalised" line is worse than none. Our Claude for Sales & Marketing Automation course shows a safe research-to-draft workflow.
Next step: build an outbound system around these templates
Templates are the last step of good outreach. To build the full system — ICP, list building, sequences, deliverability and meetings — take the B2B Outbound Prospecting course. Then sharpen your copy with Copywriting That Sells, define who to target in Customer Research & Positioning, and test your next draft in the free Cold Email Lab.