An SDR cold email template is a first-touch message under 80 words that a sales development rep can personalise in under three minutes and send 40 to 80 times a day inside a sequence, built around one opener type: pain, proof, question or referral. The constraint is volume with a human on the end, so the templates are short, the personalisation is one line, and the list is verified before the day starts; an SDR sending to an unverified list spends the morning on bounces. Teams report 3 to 8% positive replies across the four openers on verified lists.
| Opener | Use when | First line shape | Reply range (industry) |
|---|---|---|---|
| Pain | You know the problem the segment has and can name it in their words | "Most {role}s at {company_type} lose {hours} a week to {problem}." | 3 to 6% |
| Proof | You have a number from a company like theirs | "{similar_company} went from {before} to {after} in {timeframe}." | 4 to 8% |
| Question | You are not sure which problem they have | "Is {problem} something {company} has solved, or still handles by hand?" | 3 to 7% |
| Referral | Someone they know pointed you to them, or a redirect reply did | "{referrer} suggested I write to you about {topic}." | 8 to 15% |
Run two openers against the same segment for 200 sends each before picking one. The ranges overlap because the segment decides more than the opener.
Subject: {problem} at {company}
Hi {first_name},
Most {role}s at {company_type} lose {hours} a week to {problem}. Usually it shows up as {symptom}.
{sender_company} takes that off the plate: {outcome_one_line}. Worth 15 minutes to see if {company} has the same shape?
{sender_name}
If this is not relevant, reply "no" and I will not write again.
{symptom} How the problem looks from the reader's desk{hours} An honest estimateSubject: {before} to {after}
{first_name},
{similar_company}, a {company_descriptor}, went from {before} to {after} in {timeframe} with {sender_company}.
They had {trigger} at the time, which is why I thought of {company}. If the number matters, I can show the mechanics in 15 minutes.
{sender_name}
If this is not relevant, reply "no" and I will not write again.
{company_descriptor} Three words: stage, sector, size{trigger} Why the comparison fitsSubject: Quick one on {problem}
Hi {first_name},
Is {problem} something {company} has solved, is working on, or still handles by hand?
Each answer changes what I would send. "Solved" means I stop; the other two mean a two-line note on how {customer_type} usually handle it.
{sender_name}
If this is not relevant, reply "no" and I will not write again.
{problem} One problem, in the segment's wordsSubject: {referrer} suggested I write
Hi {first_name},
{referrer} suggested you are the person at {company} for {topic}.
The short version: {sender_company} {outcome_one_line} for {customer_type}. If it is relevant, 15 minutes this week; if {referrer} got it wrong, let me know who is closer to it.
{sender_name}
If this is not relevant, reply "no" and I will not write again.
{referrer} The colleague who redirected you, named only with permissionAn SDR's morning on an unverified list is 14.5% bounces and a domain warning by lunch. Lists go through bulk verification the day before; only confirmed-valid rows reach the sequencer.
The first line is the personalisation; the rest is the template. Three minutes per contact keeps the day at 40 to 80 sends with a human on each one.
Each sending mailbox stays under 30 to 50 sends a day on a warmed secondary domain. Volume comes from mailboxes, not from pushing one past its limit.
Any reply, any bounce, any out-of-office with a replacement name stops the thread. Complaints under 0.3% is the rule that keeps the domains alive.
| Metric | Healthy range (industry) | If missed |
|---|---|---|
| Sends per day | 40 to 80 with one personalised line | Above 100 means the line is templated too |
| Bounce rate | Under 1% on verified lists | The list skipped verification or is older than 90 days |
| Positive replies | 3 to 8% per 100 delivered | Run the opener test; the segment may be wrong |
| Meetings booked | 1.5 to 4% of delivered | Ask smaller; the question opener converts replies to meetings best |
| Redirects | 2 to 4% | Feed them to the referral opener |
Subject: 8.4% to 0.7% Dana, Harbourline, a 40-person logistics SaaS, went from 8.4% bounces to 0.7% in a month with BounceZero. They had just hired three SDRs at the time, which is why I thought of Kestrel. If the number matters, I can show the mechanics in 15 minutes. Dan If this is not relevant, reply "no" and I will not write again.
Three minutes per contact is the budget. One line, then the template.
Volume comes from more warmed mailboxes, not from one hot one.
The first line is yours; the body changes after 200 sends, not after one bad morning.
Verify the day before. Bounces by lunch mean a domain warning by Friday.
An SDR runs several segments at once. The table shows a typical split for a day of 60 sends across four mailboxes.
| Segment | Opener | Sends | Mailbox | Follow-up cadence |
|---|---|---|---|---|
| New trigger list (hiring, funding) | Proof | 20 | Mailbox 1 and 2 | Day 3, 8, 15, break-up 24 |
| Core segment, no trigger | Pain or question (alternate weekly) | 25 | Mailbox 3 | Same |
| Redirects from last week's replies | Referral | 5 | Mailbox 4 (warmest) | Day 4, then break-up 12 |
| Re-engagement, 90-day-old closes | Question | 10 | Mailbox 4 | Opener, one follow-up, break-up |
Every list in the table was verified the previous afternoon. The mailboxes stay under 30 to 50 sends each.
The full set
Templates by prospecting method
What goes out on day 3
The SDR stack by stage
Domains, mailboxes, warm-up and caps
Building the list the SDR works from
Forty to eighty, each with one personalised first line, spread across warmed mailboxes capped at 30 to 50 sends each. Above 100 a day the personalisation is fake and replies fall. The list must be verified the day before.
Referral openers, 8 to 15%, because someone the reader knows is named. Among cold openers, proof runs 4 to 8%, question 3 to 7%, pain 3 to 6%. Test two against the same segment for 200 sends before choosing.
Under 80 words. The reader decides in the preview pane, and a short email is read in full. Evidence and detail go in the follow-ups, which carry most of the sequence's replies.
Non-freemail (business and ISP) lists ran 14.5% invalid in 2026, and an SDR sending to one spends the morning on bounces while the domain reputation drops. Verification the day before keeps bounces under 1% and the mailboxes sending.
SDRs own the personalised first line and the opener choice per segment; the template body stays shared so results compare across the team. Changes to the body go through a 200-send test, not an afternoon's rewrite.
Every SDR day starts with a verified list: confirmed valid in the sequencer, catch-all and unknown routed elsewhere. 100 free checks a month, unknowns refunded.
Ayoub built BounceZero's 5-stage validation pipeline, its dedicated BGP-announced IP infrastructure, and the Patroni HA PostgreSQL cluster behind every verification. Previously built high-volume email delivery infrastructure. Trained at 1337 Benguerir (École 42 network, 2019). Open-source: bgp_analyzer.
Templates by trigger and stage, each with the deliverability rules that apply
A SaaS trial nudge email template for signups who stopped
A LinkedIn connection request note plus the email that follows three days later
A consultant cold email template for selling judgement rather than a product
A financial services cold email template built for compliance
A real estate agent cold email template for prospecting owners, landlords and local businesses
Four sales prospecting email templates, one per prospecting method
Continue through related topics