21 B2B Cold Email Templates
That Actually Get Replies

The average B2B cold email reads like this: "Hi [First Name], I noticed your company is growing. We help companies like yours [vague benefit]. Want to hop on a quick call?"

The recipient gets 50 of these a day. They can smell the template. And they delete it.

The problem isn't the template format — it's that most cold email templates are built around formulas (AIDA, PAS, BAB) instead of signals. A formula tells you how to structure sentences. A signal tells you why this person should care right now.

Signal-based cold emails work because they demonstrate that you've done real research. You're not guessing that the prospect has a problem. You've seen evidence of it — in a job posting, a regulatory filing, a product launch, a leadership change. That specificity is what earns the reply.

What Is a B2B Cold Email?

A B2B cold email is an unsolicited email sent to a business contact you have no prior relationship with, for the purpose of starting a sales conversation. Unlike marketing emails sent to opt-in lists, cold emails are one-to-one messages targeted at specific decision-makers.

The best B2B cold emails share three traits: they reference something specific about the recipient's business, they arrive when the recipient is likely experiencing a relevant problem, and they ask for a low-friction next step instead of a meeting.

Here are 21 B2B cold email templates organized by signal type. Each one includes the trigger that tells you when to send it, a subject line, the full email body, and why it works.

Signal-Triggered Cold Email Templates

These templates are triggered by something observable — a hiring post, a funding round, a regulatory filing. The signal IS the reason for reaching out. You don't need a clever hook because the timing does the work.

1. The Job Posting Signal

When to use it: The prospect has an open role that your product helps with — or that signals a pain your product solves. A company hiring their first "Head of Revenue Operations" is telling you they've outgrown spreadsheets.

Signal: Active job posting on LinkedIn, their careers page, or a job board.

Subject: [role] hiring

 

Saw you're hiring a [Job Title].

 

Most companies at your stage bring on that role when [specific pain the role addresses — e.g., "outbound is generating meetings but the handoff to AEs is leaking pipeline"]. The job description mentions [specific skill/responsibility from the JD] — which usually means the team is feeling that now.

 

We work with [similar company type] to [one-sentence outcome — e.g., "close the gap between signal detection and first touch so reps aren't manually researching every account"].

 

Worth a look before the new hire starts, or is the current team handling it fine?

Why it works: The job posting is public proof they have the problem. You're not guessing. And the question at the end gives them an easy way to respond.

2. The Funding Announcement

When to use it: The company just raised a round. They're about to spend money — on hiring, tools, and growth. The window is 2–4 weeks after the announcement.

Signal: Press release, Crunchbase alert, or LinkedIn announcement.

Subject: congrats on the raise

 

Congrats on the [Series X / $Xm round]. Saw the announcement this week.

 

Most teams at your stage use the first 90 days to [specific post-funding priority — e.g., "double the sales team and build outbound from scratch"]. The bottleneck is usually [specific bottleneck — e.g., "finding accounts that are actually in-market vs. blasting a purchased list"].

 

We help [similar company type] [specific outcome — e.g., "identify which accounts are showing buying signals right now so new reps aren't cold-calling into the void"].

 

Is outbound on the roadmap for this round?

Why it works: Funding is a public commitment to growth. You're connecting your product to their most likely next move, not just congratulating them.

3. The Tech Stack Change

When to use it: They recently adopted, dropped, or are evaluating a tool in your ecosystem. This signals they're actively investing in (or frustrated with) the category.

Signal: New technology detected on their site, G2 review activity, or a job posting mentioning a specific tool.

Subject: [tool name] + [your category]

 

Noticed your team recently started using [Tool Name].

 

Most companies that adopt [Tool] hit a wall with [specific limitation — e.g., "enrichment data going stale within 30 days" or "workflow automation breaking when data is inconsistent"]. It's usually the [specific department] team that feels it first.

 

We plug into [Tool Name] and [specific integration outcome — e.g., "keep your account data enriched with real-time buying signals so your sequences are hitting the right accounts at the right time"].

 

Running into that yet, or still in the honeymoon phase?

Why it works: Mentioning a specific tool they use is instant credibility. You understand their stack. The "honeymoon phase" question is disarming and real.

4. The Leadership Change

When to use it: A new VP, Director, or CXO just joined in a role relevant to what you sell. New leaders audit existing tools and processes in their first 90 days.

Signal: LinkedIn job change, press release, or company announcement.

Subject: first 90 days

 

Saw you just joined [Company] as [Title]. Congrats.

 

Most new [Title]s I talk to spend the first 90 days auditing [specific area — e.g., "how pipeline is sourced and whether outbound is generating quality or just volume"]. The two things that usually surface are [Pain 1 — e.g., "reps spending 40% of their time researching accounts"] and [Pain 2 — e.g., "no way to tell which accounts are actually in-market"].

 

If either of those is on your list, happy to share what [Company Type] at your stage are doing differently.

Why it works: New leaders want to make an impact fast. You're positioning yourself as a resource for their assessment, not asking for their time.

5. The Regulatory Deadline

When to use it: A compliance deadline is approaching and the company shows signs of being unprepared. This works in any regulated industry — healthcare, finance, transportation, energy, construction.

Signal: Public filings, regulatory databases, or industry news about upcoming deadlines.

Subject: [regulation name] deadline

 

[Company] is [X months/weeks] from the [Regulation Name] deadline.

 

Based on [public data point — e.g., "your current ENERGY STAR score of 34" or "your OSHA recordable rate from last year's filing"], [specific consequence — e.g., "you're looking at roughly $X in annual penalties once the new thresholds take effect" or "an audit in the next cycle is likely"].

 

Most companies in your position [common response — e.g., "start remediation 6–9 months out, but the ones that wait past the 90-day mark face 2–3x the cost to get compliant"].

 

Already working on this, or still scoping?

Why it works: Regulatory deadlines create urgency that doesn't require convincing. You're showing you've done the math on their specific situation.

6. The Expansion Signal

When to use it: The company is opening new offices, entering new markets, or launching in new geographies. Expansion creates operational complexity your product can address.

Signal: Job postings in new locations, commercial real estate filings, press releases about market entry.

Subject: [new market/city] expansion

 

Looks like [Company] is expanding into [Market/City — e.g., "the Southeast" or "DACH region"].

 

The teams I work with that have done this same expansion usually underestimate [specific challenge — e.g., "how different the buyer journey looks in that market" or "the compliance requirements that vary state by state"]. The [specific department] team ends up scrambling about [timeframe] in.

 

We help [company type] [one-line outcome — e.g., "get outbound running in new markets in weeks instead of quarters by mapping which accounts in the region are already showing buying signals"].

 

How far along is the [market] buildout?

Why it works: Expansion is exciting but stressful. You're pointing to a specific operational risk they haven't thought through yet.

7. The Competitor Mention

When to use it: You know they're using a competitor (from their tech stack, a job posting mentioning the tool, or a review they left on G2/Capterra).

Signal: Job posting mentions a competitor tool, G2 review, or technology detection.

Subject: [competitor] → [your approach]

 

Noticed your team is using [Competitor].

 

Most [Competitor] users I talk to like [specific thing Competitor does well], but run into issues with [specific limitation — e.g., "data freshness — the intent signals are 2–3 weeks old by the time they hit your CRM" or "the enrichment layer requiring constant manual cleanup"].

 

We take a different approach: [one sentence on your differentiation — e.g., "instead of aggregated intent scores, we surface the specific public events — job postings, regulatory filings, tech changes — that show an account needs what you sell right now"].

 

Hitting any of those friction points, or is [Competitor] working well for you?

Why it works: You're not bashing the competitor. You're naming a specific, known limitation that the prospect has probably experienced. The exit question ("or is it working well for you?") makes it feel honest, not salesy.

Pain-Point Cold Email Templates

These templates don't rely on a specific trigger event. Instead, they describe a condition the prospect is likely experiencing — and do it with enough specificity that they think, "How does this person know what my Tuesday looks like?"

8. The Status Quo Cost

When to use it: When the pain isn't urgent enough to force action on its own. You need to quantify what the current approach is costing them to create urgency.

Subject: the cost of manual [process]

 

Most [Title]s at [company type — e.g., "Series B SaaS companies"] are spending [X hours/week or $X/quarter] on [manual process — e.g., "manually researching target accounts before reps can even start outreach"].

 

That's roughly [impact — e.g., "$X in loaded cost per quarter" or "Y hours that could be pipeline-generating activity"]. And the output is usually a spreadsheet that's outdated by the time it hits the rep's desk.

 

Is your team dealing with something similar, or have you already solved this?

Why it works: Quantifying the status quo makes "doing nothing" feel expensive. The numbers force the prospect to do the mental math on their own situation.

9. The Symptom Description

When to use it: When you know the day-to-day experience of someone in the prospect's role. Describe their symptoms, not your diagnosis.

Subject: [day-to-day symptom]

 

Most [Titles] I talk to describe the same pattern: [Symptom 1 — e.g., "reps cherry-pick the easy accounts and ignore the rest of the list"]. Then [Symptom 2 — e.g., "pipeline reviews turn into debates about whether the list is any good"]. Meanwhile, [Symptom 3 — e.g., "the accounts that are actually in-market right now are sitting untouched in the CRM"].

 

Is that close to what your team is dealing with?

Why it works: You're not telling them they have a problem. You're describing what the problem feels like. That's the difference between being a vendor and being someone who gets it.

10. The Industry Benchmark

When to use it: When you have data about what "good" looks like in their industry and can compare it to their likely situation.

Subject: [industry] outbound benchmarks

 

Across the [industry] companies we work with, the teams doing [specific metric — e.g., "signal-based outbound"] are averaging [benchmark — e.g., "a 12% reply rate and 4% meeting conversion"]. The ones running traditional list-based outreach are at [lower benchmark — e.g., "2–3% reply and sub-1% conversion"].

 

The difference isn't the email copy. It's whether the account was in-market when the rep hit send.

 

Where does your team's outbound sit right now?

Why it works: Benchmarks create natural comparison. The prospect immediately evaluates where they fall — and if they're below, you've earned a conversation.

11. The Broken Process

When to use it: When you know a specific workflow in their organization is inefficient and you can name the exact steps that break down.

Subject: the account research bottleneck

 

Here's how account research usually works at [company type]: [Step 1 — e.g., "marketing hands over a list of 'target accounts'"]. [Step 2 — e.g., "SDRs spend 30–45 minutes per account googling, checking LinkedIn, reading the careers page"]. [Step 3 — e.g., "They write a semi-personalized email. Half the time the account isn't even in-market."]

 

The math doesn't work. [X] hours of research for [Y] emails sent. And there's no way to tell which accounts are worth the time before you've already spent it.

 

Has your team found a way around this, or is it just the cost of doing outbound?

Why it works: Naming the exact steps shows you've lived this. The closing question frames the problem as solvable, not inevitable.

12. The Risk Exposure

When to use it: When there's a risk the prospect hasn't fully considered — a blind spot you can illuminate with data.

Subject: [specific risk]

 

[Company] has [observable data point — e.g., "grown from 50 to 200 employees in the last 18 months"].

 

At that growth rate, most companies discover [specific risk — e.g., "their outbound infrastructure breaks — the processes that worked with 3 SDRs don't scale to 12, and pipeline generation flatlines even as headcount doubles"].

 

The fix isn't more reps. It's [one-line alternative — e.g., "giving each rep a shorter, higher-quality list based on real-time buying signals instead of a static account list that gets stale in 2 weeks"].

 

Is your team feeling any of this pressure yet?

Why it works: You're showing them the future if they don't change course. The observable data point (headcount growth) is verifiable — they can confirm you've done real research.

Value-First Cold Email Templates

These are the highest-effort, highest-reward templates. Instead of asking for time, you lead with something useful — an analysis, a benchmark, a dataset. The deliverable IS the value. If it's good enough, they'll respond even if they don't need your product yet.

The rule: if your email would make sense without the deliverable, you wrote a pitch, not a value-first email.

13. The Data Drop

When to use it: When you can compile data specific to their industry, market, or competitive landscape that they'd have to spend hours assembling themselves.

Subject: [industry] data for [Company]

 

I put together a [description of the data — e.g., "list of 47 waste hauling companies in the Southeast that had their DOT authority downgraded in the last 90 days, with their safety scores and violation history"].

 

Companies like [Company] usually find this useful for [specific use case — e.g., "identifying which competitors are vulnerable and which prospects are under regulatory pressure to switch providers"].

 

Want me to send it over?

Why it works: You've done work for them before they've asked. The "want me to send it?" CTA is low friction — they just say yes. And now you have a conversation.

14. The Free Audit

When to use it: When you can quickly analyze one aspect of their business using publicly available data and deliver a specific finding.

Subject: quick [area] audit

 

Took a look at [Company]'s [public-facing thing you analyzed — e.g., "outbound presence — your SDR team's LinkedIn activity, the job postings you're running for sales roles, and your Glassdoor reviews mentioning quota"].

 

One thing stood out: [specific finding — e.g., "you're hiring 4 SDRs but there's no signal infrastructure — which means those new reps are going to spend their first 3 months building lists from scratch instead of selling"].

 

I have a few more observations. Worth a 15-minute walkthrough?

Why it works: You've already done the work. The finding is specific enough to be credible but incomplete enough to warrant a conversation. The "few more observations" creates curiosity.

15. The Insight Share

When to use it: When you've uncovered something non-obvious about their market or competitive landscape that they probably haven't seen.

Subject: something interesting about [their market]

 

Spent some time researching [their market/industry] this week and found something your team might want to know:

 

[Non-obvious insight — e.g., "3 of your top 5 competitors have posted Head of Partnerships roles in the last 60 days. That usually signals a shift from direct sales to channel — which means the accounts they're selling into directly right now are about to be underserved."]

 

Could be noise. Could be an opening. Figured it was worth flagging.

Why it works: The insight is genuinely useful regardless of whether they buy from you. "Could be noise" shows intellectual honesty, not just salesmanship.

16. The Benchmark Comparison

When to use it: When you have enough data to show where they stand relative to peers in a specific metric that matters to them.

Subject: [Company] vs. [industry] average

 

I pulled [metric] data for [number] companies in [their industry/segment].

 

[Company] is at [their number]. The industry average is [average]. The top quartile is at [top number].

 

The gap between your current position and the top performers usually comes down to [1–2 specific factors — e.g., "how accounts are prioritized and whether outreach is triggered by signals or just list position"].

 

I built a full breakdown. Want to see it?

Why it works: Numbers create urgency that words can't. Seeing themselves below average motivates action. And you've done the analysis for free — they just have to say yes to see it.

17. The Custom Projection

When to use it: When you can take their current data and project forward — showing what happens if they continue on the current path vs. making a change.

Subject: [Company] projection

 

Based on [observable data points — e.g., "your current team size, hiring pace, and the outbound volume your SDRs are running"], I modeled two scenarios for [Company]:

 

Current path: [Projection — e.g., "At 50 accounts/rep/month with a 2% reply rate, your 4 SDRs generate roughly 4 meetings/month. Adding 4 more reps doubles cost but the reply rate stays flat."]

 

Signal-based path: [Projection — e.g., "Same 4 SDRs, but only hitting accounts showing active buying signals. Reply rate jumps to 8–12%. That's 16–24 meetings/month without adding headcount."]

 

Want the full model? Takes 15 minutes to walk through.

Why it works: Two scenarios, one number-based, one outcome-based. The prospect can immediately see the ROI of changing their approach. And you've done the math for them.

Follow-Up Cold Email Templates

Most deals don't close on the first touch. Most replies don't come from the first email. Follow-ups are where pipeline actually gets created — but only if each one adds something new. A "just bumping this to the top of your inbox" email is not a follow-up. It's spam.

18. The New Angle

When to use it: 3–5 days after the first email. Same signal, different implication.

Subject: Re: [original subject]

 

One more thing on this —

 

[New angle on the same signal — e.g., "The job posting for a Head of RevOps also mentions Salesforce CPQ implementation. In my experience, that project alone takes 3–6 months and creates a data quality mess that hits outbound performance hard. If your team is running outbound in parallel, the timing matters."]

 

Relevant to what's happening at [Company]?

Why it works: You're not repeating yourself. You're showing deeper research — a second layer of the same signal. That signals persistence and intelligence, not desperation.

19. The Social Proof Bump

When to use it: 5–7 days after the first email. Share a result from a similar company.

Subject: Re: [original subject]

 

Quick follow-up with some context —

 

[Similar company] had the same [problem/situation] last quarter. [Specific result — e.g., "They went from 3% outbound reply rates to 14% in 6 weeks by switching from static lists to signal-triggered outreach. Their pipeline doubled without adding headcount."]

 

Happy to share how they set it up if useful.

Why it works: Social proof from a peer company is more credible than any claim you can make. "Similar company, similar problem, specific result" is the formula.

20. The Value Add

When to use it: 7–10 days after the first email. Send something genuinely useful — not your content, not your case study. Something they'd actually read.

Subject: thought you'd find this useful

 

Came across this [resource type — e.g., "teardown of how Ramp's outbound team restructured around buying signals"] and thought of our earlier thread.

 

[1-sentence summary of the resource — e.g., "The key insight: they stopped measuring SDR activity (emails sent, calls made) and started measuring signal coverage (% of in-market accounts touched). Reply rates tripled."]

 

Worth a read if you're thinking about this at [Company].

Why it works: You're being a resource, not a salesperson. The implied message: "I'm paying attention to your space regardless of whether you buy from me." That builds trust.

21. The Breakup

When to use it: Final touch, 14+ days after the first email. Low pressure, high signal.

Subject: Re: [original subject]

 

Closing the loop on this — I know timing might not be right.

 

If [pain/situation from original email] becomes a priority down the road, I'm easy to find.

 

Either way — no hard feelings. Good luck with [specific thing they're working on — e.g., "the RevOps hire"].

Why it works: The breakup email often gets the highest response rate in a sequence. It's unexpected. It removes all pressure. And the specific reference to something they're working on shows you're still paying attention — but you're not desperate.

Cold Email Best Practices That Actually Matter

Templates are the structure. These practices are what separate the emails that get replies from the ones that get archived.

Start with their situation, never with you

Your first sentence should describe something about the prospect's world. Not "I'm reaching out because..." Not "We help companies like yours..." The prospect should read the first line and think, "This person knows something about my business."

Keep it under 75 words

Cold emails aren't blog posts. Every word you add reduces the chance they'll read the whole thing. The best cold emails are 50–75 words. That forces you to cut everything that isn't essential. If you can't say it in 75 words, you don't understand the problem well enough.

Subject lines: 2–5 words

Long subject lines look like marketing. Short subject lines look like something a colleague would send. "compliance timeline" — diagnostic. "[Company] penalty projection" — value-first. "quick question" — never. Match the subject to the email type.

One CTA. Make it low friction.

"Want to hop on a quick call?" is medium friction. "Worth a look?" is low friction. "Want me to send it over?" is the lowest. The goal of the first email isn't to book a meeting. It's to get a reply. Design the CTA accordingly.

Hide the signal

Never say "I noticed your company posted a job for..." or "I saw in your LinkedIn that..." Everyone does this. Instead, demonstrate that you know their situation by describing the consequences of what you found. "Most companies at your stage bring on a RevOps lead when..." is better than "I saw you posted a RevOps role."

Personalization is about conditions, not compliments

"Love what you're building at [Company]" is not personalization. It's flattery. And the prospect has heard it from the last 10 SDRs. Real personalization is referencing a condition that affects their business — a specific challenge, a market shift, a data point about their company. That's what makes them stop scrolling.

The template isn't the hard part

Choosing the right template is about 10% of the work. The other 90% is the research that tells you which template to use and what data to put in the variables. A signal-triggered template with the wrong signal is worse than no template at all. Start with the research. The template is just the delivery vehicle.

Frequently Asked Questions

How long should a B2B cold email be?

Keep cold emails under 75 words. That forces you to cut everything that isn't essential — no company backstory, no feature lists, no "I hope this finds you well." The best-performing cold emails are 50–75 words: one observation about the prospect's situation, one sentence connecting it to an outcome, and one low-friction question.

What is the best cold email opening line?

The best opening line describes something about the prospect's business, not about you. Reference a specific signal: a job posting, a regulatory filing, a tech stack change, or a recent company announcement. For example: "Saw you're hiring a Head of RevOps" or "Your team just expanded into the Southeast." Never start with "I'm reaching out because..." or "We help companies like yours..."

How many follow-up emails should I send?

Send 3–4 follow-ups spaced 3–7 days apart. Each follow-up must add something new — a different angle on the same signal, a relevant case study, or a useful resource. "Just bumping this to the top of your inbox" is not a follow-up. It's spam. The final email should be a low-pressure breakup that removes all urgency.

What is signal-based outbound?

Signal-based outbound is an approach to cold outreach where emails are triggered by observable events — job postings, funding rounds, regulatory filings, leadership changes, or tech stack shifts — rather than sent to static lists. The signal tells you why a prospect should care right now, which makes the email relevant instead of generic. Signal-based cold emails typically see 3–5x higher reply rates than traditional list-based outreach.

Should I use cold email templates or write from scratch?

Use templates, but the template is only 10% of the work. The other 90% is the research that tells you which template to use and what data to put in the variables. A well-researched email using a template will outperform a "handwritten" email that's based on surface-level personalization like "Love what you're building at [Company]."

These 21 templates share one thing in common: they're built around signals, not formulas. The signal is what makes the prospect care. The template is just how you deliver it.

The hard part isn't writing the email. It's the research that comes before it — finding the signal, validating that the prospect is experiencing the pain, and choosing whether to lead with a question or a deliverable. (For the step-by-step system behind these templates, read the signal-based cold outreach playbook. For the philosophy, read the 40 outbound principles.)

That research layer — the system that turns public data into specific, timely reasons to reach out — is what I build at Thresh.