Cold Email
Cold email templates for SaaS: 12 frameworks and how to adapt them
12 B2B SaaS cold email templates by scenario (signals, competitors, champions, events, follow-ups), with guidance on adapting each to your segment.
Founder, OretonGTM · ·7 min read
Templates have a bad reputation in cold email, mostly deserved. The same “I noticed you’re the Head of Sales at {company}” template has been sent millions of times, and buyers spot it instantly.
But the structure behind a good template is useful. Templates save time, encode what works and give your team a shared starting point. The problem is sending them as-is.
Below are 12 SaaS cold email templates organized by scenario, each with a note on when to use it and how to adapt it. Treat them as frameworks: replace every bracket with language specific to your segment, and use real proof.
How to use these templates
Before you use any template:
- Pick a segment. Each template should be adapted to one segment, not used across your whole list. See the ICP template.
- Replace brackets with real specifics. “[problem]” should become a problem your segment would describe in their own words.
- Use real proof. A specific, modest proof point beats an impressive vague one.
- Keep it short. If your adaptation runs past 125 words, cut.
- Test angles. Run two templates against each other, not two versions of the same one with word swaps.
For the principles behind these, see how to write a cold email.
1. Hiring signal
When to use: the account is hiring for a role your product supports or replaces. See hiring signals.
Subject: [role] hiring at [Company]
Hi [Name] — saw [Company] is hiring [number] [role]s. When teams grow [function] that quickly, [specific problem that appears during ramp] usually shows up within the first couple of months.
[Product] [how it solves that problem in one sentence]. [Short proof: similar company + outcome].
Is [problem] on your radar as the team grows?
Adapt it: read the job description. It often tells you the tools they use and the problems they want solved.
2. New leader
When to use: a new VP, head or director joined in the function you sell to, in roughly the last 90 days.
Subject: first 90 days
Hi [Name] — congrats on joining [Company]. New [role]s often spend their first quarter [common priority, e.g., auditing the stack / rebuilding the pipeline process].
If [problem area] is on that list, we help [similar companies] [outcome] without [common cost or pain].
Worth comparing notes on what you’re seeing so far?
Adapt it: if you know where they came from, and their previous company used a similar tool, that’s worth mentioning.
3. Funding round
When to use: recent funding, ideally combined with another signal. See funding signals.
Subject: after the [round]
Hi [Name] — after a [round], most [segment] teams are asked to [growth goal, e.g., double pipeline] while [constraint, e.g., keeping headcount lean].
We help with the [specific part], so [outcome]. [Short proof].
Is [specific part] something you’re planning for this year?
Adapt it: newly funded companies get flooded with emails. Lead with the implication of the round, not the congratulations.
4. Tech stack
When to use: the account uses a tool you integrate with, complement or replace. See technographic targeting.
Subject: [Company] + [Tool]
Hi [Name] — looks like [Company] runs on [Tool]. Teams using [Tool] often run into [specific limitation or gap].
[Product] [connects to / fills the gap] so [outcome].
Is that a gap you’ve felt, or is it already handled?
Adapt it: be precise about the limitation. Generic “it’s missing features” won’t land.
5. Competitor user
When to use: the account uses a direct competitor.
Subject: [specific capability]
Hi [Name] — a few teams we work with moved from [Competitor] because [specific, factual reason, e.g., they needed X that Y doesn’t support].
Not saying you need to switch. But if [specific problem] has come up, we have a short comparison of how teams handle it.
Want me to send it?
Adapt it: never disparage the competitor. Be factual about one specific difference that matters to this segment.
6. Champion job change
When to use: a former customer user or buyer joined a new ICP company. Often the highest-converting outbound scenario. See job change signals.
Subject: congrats on [Company]
Hi [Name] — congrats on the move to [Company]! Great working with you at [Previous company] on [what they did with your product].
If [problem] is on your plate at [Company], happy to help set things up the way it worked at [Previous company], or just share what we’d do differently this time.
Open to a quick catch-up?
Adapt it: this should be written or at least reviewed by someone who actually worked with them.
7. Website intent (without mentioning it)
When to use: an ICP account visited your pricing or comparison pages, but nobody filled out a form.
Subject: [problem area] at [Company]
Hi [Name] — teams like [Company] usually look at [category] when [trigger, e.g., the team outgrows spreadsheets]. The decision often comes down to [key criteria].
Happy to share how [similar companies] evaluated it, including where we’re not the best fit.
Would that be useful?
Adapt it: never mention the website visit. Use it to choose who to contact and the topic, then write a helpful email.
8. Event follow-up
When to use: they attended an event you also attended, spoke at or sponsored.
Subject: [Event] follow-up
Hi [Name] — were you at [Event] last week? The [session/topic] on [topic] matched something we’re seeing with [segment]: [insight].
We help [segment] with [problem]. Worth a short conversation on how you’re approaching it?
Adapt it: only reference sessions or topics that actually happened and are relevant.
9. Referral ask (wrong person)
When to use: you’re not sure who owns the problem.
Subject: who owns [area]?
Hi [Name] — trying to find the right person at [Company] for [area, e.g., outbound data and tooling]. We help teams [outcome].
Is that you, or someone else on the team?
Adapt it: keep it very short. The ask is easy to answer, which is why it works.
10. Resource offer
When to use: you have something genuinely useful: a benchmark, checklist, audit or teardown.
Subject: [resource name]
Hi [Name] — we put together [resource] based on [source, e.g., setups we’ve audited for SaaS teams]. It covers [two or three specific things].
Want me to send it over? No call needed.
Adapt it: the resource must be good. A thin PDF wastes the goodwill. See outbound offers.
11. Follow-up with a new angle
When to use: second or third email in the sequence.
Subject: different angle
[Name] — a different thought: [second problem, different from the first email]. [One sentence on how you help].
Is that more relevant for [Company] right now?
Adapt it: the new angle should be truly different, not a reworded version of email 1. See cold email follow-ups.
12. Breakup
When to use: the final email in the sequence.
Subject: closing the loop
[Name] — I’ll stop here. If [problem] becomes a priority later this year, feel free to reach out. Good luck with [something relevant to them].
Adapt it: keep it short and polite. No guilt-trip. See breakup emails.
Templates by persona
The same template should read differently depending on who receives it:
| Persona | Emphasize | Avoid |
|---|---|---|
| Founder / CEO | Revenue, speed, focus, team leverage | Technical detail, feature lists |
| VP / Head of Sales | Pipeline, rep productivity, quota attainment | Vague “efficiency” claims |
| RevOps | Data quality, process, integrations | Hype and big promises |
| Technical buyer | Specifics, architecture, limits | Salesy language |
| Marketing | Pipeline contribution, attribution, ICP fit | Purely sales-centric framing |
A worked example: adapting template #1
Template: hiring signal.
Segment: Series A B2B SaaS companies hiring SDRs. Our product: outbound data and infrastructure.
Adapted:
Subject: sdr hiring at Northwind
Hi Daniel — saw Northwind is hiring three SDRs. When teams ramp that fast, reps usually end up building their own lists in the first month, and data quality varies by rep, which drives up bounces on the shared domains.
We build the list and enrichment pipeline so new SDRs start with verified, researched accounts on day one.
Is list building something you’ve solved, or still on each rep?
Notice what changed: the bracketed problem became a specific, recognizable situation, the proof is concrete and the question is easy to answer.
Common template mistakes
- Sending templates as-is. Recipients recognize them.
- Leaving brackets or broken variables. “Hi {first_name}” kills credibility instantly. Always test.
- Using one template for every segment. The problem changes by segment; so should the email.
- Fake personalization. A personalized line that doesn’t connect to the pitch.
- Asking for a demo in email one. Ask for interest first.
- Never retiring templates. What worked last year may be overused now. Keep testing.
Measuring templates
Track each template by positive reply rate and meetings per 1,000 contacts, broken down by segment. A template that works for one segment may fail for another. Retire templates that underperform after a meaningful sample, usually a few hundred contacts. See A/B testing cold email and improving reply rates.
Frequently asked questions
Do cold email templates still work?
As structures, yes. Copy-pasted word for word, they perform poorly because recipients have seen them many times and they're not specific to the segment. Use templates for structure and write the content for your audience.
What is the best cold email template for SaaS?
There's no single best one. Templates built around a real trigger, like a new leader, a hiring push or a tech change, tend to perform best because they give the email a specific reason to exist.
How long should a SaaS cold email be?
Usually 50 to 125 words for the first email and 30 to 60 for follow-ups. Prospects read on mobile and decide in seconds.
Should I mention competitors in a cold email?
You can mention that you work with teams that use or moved from a competitor, as long as it's factual and not disparaging. Focus on a specific problem your product solves better rather than attacking the other product.
How do I personalize a template at scale?
Write the core message per segment, then use enrichment and AI research to fill one or two account-specific details, like a trigger or a relevant fact, with a human review step for important accounts.
Should SaaS cold emails ask for a demo?
Usually not in the first email. Ask whether the problem is relevant or offer something useful. Once they reply, propose a short call or demo.