Cold Email Templates for SDRs: 10+ Examples by Scenario

Cold Email Templates for SDRs: 10+ Examples by Scenario

A typical SDR sequence quota looks like this: 40 to 60 new contacts added per day, five to eight touches per contact, three or four active sequences running at once, and a manager asking why last week's reply rate dipped. Nobody has 20 minutes per prospect. The advice to "deeply personalize every email" collapses on contact with the job.

What actually works is a template library organized by scenario, where the variable parts are narrow enough to fill in 90 seconds and the structural parts have already been tested. You write the research once, at the account level, and let the template carry the rest.

Below are 12 templates covering the situations SDRs hit every week: trigger-based cold opens, referral asks, multithreading moves, objection replies, and follow-ups that do something other than "just bumping this up." Each one includes a subject line, the full body, and a note on when it fits.

The Two-Tier Rule: Snippets vs Full Personalization

Before the templates, decide how your list splits. Most SDRs waste effort by applying the same personalization depth to every account, which means the strategic accounts get shallow research and the volume accounts get more than they deserve.

The snippet is the unit of work. A snippet is one or two sentences you write once and reuse across every contact at that account, or across every account sharing a signal. "You posted three Enterprise AE roles in the last 45 days" is a snippet. So is "Teams running Salesforce with a HubSpot marketing layer usually hit the same attribution gap." One good snippet library beats one-off personalization, because you can build 20 snippets on a Friday and deploy them across 400 contacts the following week.

Two structural rules apply across every tier. Keep first touches short, since Gong's analysis of cold email performance found reply rates climb as emails get shorter, with the strongest results under roughly 100 words. Source: Gong. And prefer interest-based CTAs over calendar requests on the first touch. Gong Labs found that asking about a problem or offering to send something converts better than asking for time. Source: Gong.

Cold Open Templates

Template 1: The Hiring Signal

Best for: Tier B accounts where headcount growth creates the problem you solve.

Subject: {{company}}'s Q3 AE hires

{{first_name}},

Saw {{company}} posted {{number}} {{role_type}} roles since {{month}}.
Usually when a team scales that fast, {{specific_problem}} shows up
about two quarters later.

We work with {{peer_company_1}} and {{peer_company_2}} on exactly that.

Is {{specific_problem}} on your radar for this year, or handled?

{{sender_name}}

Why this works: The job posting is public, verifiable, and time-stamped, so the email reads as observation rather than flattery. The closing question is answerable in four words, which is the lowest possible bar for a reply.

Template 2: The Tech Stack Signal

Best for: Tier B and C where install data or a review site listing tells you what they run.

Subject: {{tool_name}} + {{other_tool}}

{{first_name}},

Quick one. Teams running {{tool_name}} alongside {{other_tool}}
tend to hit the same wall: {{specific_gap}}.

{{peer_company}} had the same setup. They {{one_line_outcome}}.

Worth me sending over how they wired it up? Two-minute read, no call.

{{sender_name}}

Why this works: The offer is a document, not a meeting, which removes the calendar objection entirely. Prospects who say yes have self-identified as having the problem, and that reply becomes the opening for the real conversation.

Template 3: The Funding Announcement

Best for: Accounts 2 to 10 weeks post-raise, when budget exists but process has not hardened.

Subject: post-{{round}} priorities

Congrats on the {{round}}, {{first_name}}.

The next 6 months usually mean {{predictable_pressure}}: more pipeline
targets, more headcount, same systems.

We handle {{your_category}} for {{peer_company_1}} and {{peer_company_2}},
both roughly your stage.

What's the first thing you're fixing with the new budget?

{{sender_name}}

Why this works: It congratulates in six words and moves on. The closing question is one a newly funded leader is already answering internally, so replying costs them nothing they have not already thought through.

Template 4: The Peer Problem (no trigger available)

Best for: Tier C volume sends where you have nothing but firmographics.

Subject: {{role_title}}s at {{industry}} companies

{{first_name}},

Most {{role_title}}s I talk to at {{company_size}} {{industry}} companies
are dealing with one of two things right now: {{problem_a}} or
{{problem_b}}.

If it's the first one, {{peer_company}} cut {{metric}} by {{amount}}
using {{approach}}.

Which of the two is closer to your situation? Or neither?

{{sender_name}}

Why this works: The either/or question is easier to answer than an open one, and "or neither" gives an honest out that keeps the tone non-pushy. It also segments your list for free, since every reply tells you which problem to lead with next time.

Multithreading Templates

Single-threaded accounts stall. Gong's research on deal outcomes has consistently linked more stakeholder contact to higher win rates, and the same logic applies upstream at the prospecting stage. Source: Gong. Work three to five contacts per Tier A and Tier B account, and vary the angle so the emails do not read as a mass send when they get forwarded.

Template 5: The Downward Referral Ask

Best for: VP or C-level contact who is not the day-to-day owner.

Subject: right person at {{company}}?

{{first_name}},

Probably not your desk, but hoping you can point me.

We help {{peer_company_1}} and {{peer_company_2}} with {{one_line_value}}.
For {{company}}, that would sit with whoever owns {{function}}.

Who should I be talking to?

{{sender_name}}

Why this works: It asks for a name instead of a meeting, which is the cheapest possible request. A forwarded reply from a VP also lands with borrowed authority when the actual owner opens it.

Template 6: The Sideways Move

Best for: After your first contact at the account has gone quiet for 10 or more days.

Subject: {{colleague_first_name}} + {{function}} at {{company}}

{{first_name}},

I reached out to {{colleague_first_name}} a couple weeks back about
{{specific_problem}} and may have caught them at a bad time.

Short version: {{peer_company}} was dealing with {{problem}} and
{{one_line_outcome}}.

If this is more your area, happy to send the details. If not, I'll
stop cluttering inboxes at {{company}}.

{{sender_name}}

Why this works: Naming the colleague is honest, which prevents the awkward "we already talked to your company" discovery later. The self-aware closing line signals you will not spray the whole org.

Template 7: The Bottom-Up Build

Best for: Practitioners and managers who feel the problem daily but do not sign.

Subject: how you're handling {{specific_task}}

{{first_name}},

You're the one actually running {{specific_task}} at {{company}},
so you'd know better than anyone: how much of the week does
{{painful_part}} eat?

Asking because {{peer_company}}'s team was at {{number}} hours
before they changed the process.

If it's a non-issue, tell me and I'll drop it.

{{sender_name}}

Why this works: Practitioners rarely get asked about their workflow by vendors, and the question respects their expertise. Their answer becomes internal evidence you can quote when you email their director.

Follow-Up Templates

Template 8: The New-Angle Bump (touch 2)

Best for: Three to four days after the first email, no reply.

Subject: (reply to original thread)

{{first_name}},

One more data point since I wrote: {{new_specific_fact}}.

That's the pattern I was pointing at. {{peer_company}} saw the same
thing before they {{one_line_outcome}}.

Still worth a look?

{{sender_name}}

Why this works: It adds a fact instead of applying pressure. Following up with new information gives the prospect a reason to reopen the thread that has nothing to do with your quota.

Template 9: The Resource Drop (touch 4)

Best for: Two weeks in, no engagement, before you go quiet.

Subject: {{topic}} breakdown, no strings

{{first_name}},

Not going to keep pitching. Sending this because it's genuinely
useful whether or not we ever talk: {{asset_name}}, which covers
{{specific_thing}} for {{industry}} teams.

{{link}}

If it's helpful and you want to talk through it, I'm here.

{{sender_name}}

Why this works: Giving something with no ask attached resets the relationship. Clicks on the link also re-score the contact for a later sequence even when no reply comes.

Template 10: The Permission Close (final touch)

Best for: The last email in the sequence.

Subject: closing the loop

{{first_name}},

I've sent a few notes about {{specific_problem}} and haven't heard
back, which usually means one of three things: wrong person, wrong
time, or wrong problem.

Any of those is fine. Just tell me which and I'll act accordingly.

Otherwise I'll assume this isn't a priority and stop here.

{{sender_name}}

Why this works: The three-option structure makes replying almost reflexive, and each answer is actionable. "Wrong person" triggers a referral path, "wrong time" sets a nurture date, "wrong problem" tells you your targeting is off.

Reply Templates

Template 11: Answering "Not interested"

Subject: (reply to their message)

Appreciate the straight answer, {{first_name}}.

Last question and I'll leave it: is that because {{specific_problem}}
is already handled, or because it's not what you're focused on
this quarter?

Asking so I know whether to check back in {{timeframe}} or close
the file.

{{sender_name}}

Why this works: A "not interested" is a reply, which means the thread is warm. Splitting the rejection into solved versus deprioritized separates the permanent no from the timing no, and timing nos are the best source of next-quarter pipeline an SDR has.

Template 12: Answering "Send me some info"

Subject: (reply to their message)

Happy to, {{first_name}}. So I don't send you 40 pages of the
wrong thing:

Is {{problem_a}} or {{problem_b}} the closer fit right now?

Give me a one-word answer and I'll send the relevant piece plus
how {{peer_company}} handled it.

{{sender_name}}

Why this works: "Send me info" is frequently a polite exit. Requiring one word of input before you send filters real interest from brush-offs and keeps the conversation going instead of ending it with an attachment.

Common Mistakes That Kill SDR Sequences

Personalizing the opener and nothing else. A researched first line followed by three paragraphs of boilerplate reads worse than a straightforward template, because the tonal shift is obvious.

Stacking every proof point into touch one. Save the case study, the metric, and the customer logo for separate touches. Each follow-up needs its own reason to exist.

Using the same CTA in all six emails. Vary the ask across the sequence: a question, then a resource offer, then a referral ask, then a permission close.

Sending all five contacts at an account the identical email. Change the angle per role. The practitioner gets workflow language, the director gets team-level outcomes, the VP gets a referral ask.

Never retiring a template. Track reply rate per template in your sequencer. Anything running below your baseline for 300 sends gets rewritten or cut.

Your SDR Template Checklist

• First touch is under 100 words and reads as three or four sentences
• Subject line is lowercase, under 40 characters, and contains no pitch
• The researched element is verifiable and dated (job post, filing, announcement)
• CTA asks about interest or offers something, rather than requesting a calendar slot
• Every variable has a tested fallback value so nothing renders as {{blank}}
• Three or more contacts mapped per Tier A and Tier B account, each with a distinct angle
• Follow-ups introduce new information instead of repeating the original ask
• Sequence ends with a permission close rather than trailing off

Build the snippet library first, then match snippets to these templates by scenario. That sequencing keeps the research load front-loaded and off your daily send block, which is the only way volume and relevance coexist in this role.

If you would rather have the list building, snippet research, inbox infrastructure, and sequence testing run for you instead of squeezing it between dials, book a strategy call with RevenueFlow and we will map what a done-for-you outbound program would look like for your ICP.