By Siddharth GangalThese 15 SDR email templates are first-touch starting points for specific situations. They are not “winning” copy, a substitute for prospect research, or legal approval for an outbound program. Pick the template whose use condition is actually true, replace every bracket, and delete any claim you cannot prove.
This guide intentionally excludes follow-up emails, breakups, and multi-touch sequences. Use the downloadable cold email template pack for a mixed collection across sequence positions, or the cold email follow-up guide after a genuine first message. Here, every example has one job: help an SDR write the initial email for a defined use case.
What an SDR email template should do
Direct answer. An SDR email template should connect one truthful reason for contact to one relevant idea and one proportionate next action. It should expose what must be researched, distinguish observation from hypothesis, and make unsupported personalization harder to send.
A template is a decision aid, not finished copy. “Saw you are hiring six account executives” can be an observation when a current careers page proves it. “You must be struggling to ramp them” is a hypothesis. The distinction matters: a prospect can evaluate a hypothesis, but an invented diagnosis asks them to correct the sender before a conversation can begin.
Subject lines follow the same rule. Describe the topic—such as “[initiative] onboarding question”—without faking a reply, urgency, or an existing relationship. The cold email opening-line guide helps refine the first sentence after the underlying reason is sound.
Complete the personalization input card
Fill this card before choosing copy. If a required field is blank, research it or select a less specific template. Do not let a language model fill missing facts with plausible prose.
| Input | Write down | Reject when |
|---|---|---|
| Recipient | Name, current role, company, responsibility, and source URL | The role is stale or ownership is only assumed |
| Reason now | Observable event, date, source, and direct relevance | The event is old, private, or unrelated to the offer |
| Relationship | Exact request, event, referral permission, or prior interaction | A connection, registration, or content view is overstated |
| Hypothesis | One possible operating problem, explicitly labeled as a hypothesis | It is presented as something known about the buyer |
| Value | A real idea, question, example, or resource you may share | It depends on vague proof, a gated surprise, or an unavailable asset |
| Next action | One reply, routing question, review, or short conversation | The email asks for several decisions |
| Eligibility | Policy approval, suppression check, jurisdiction, and required evidence | Any mandatory check is missing |
For a deeper research workflow, use the cold email personalization guide. The minimum standard is simple: another reviewer should be able to open the cited source and reach the same factual conclusion.
Templates 1–5: observable signals
Signal templates begin with a public, current event. The event earns specificity, not certainty about an internal problem.
1. Verified job-change email
Use when: the prospect recently entered a role and the timing is confirmed.
Subject: [role] priorities at [company]
Hi [Name]—congratulations on joining [Company] as [Role] on [date]. New leaders often have to decide how to [relevant operating decision], though I do not know whether that is on your list. We help [specific team] [bounded capability]. Would a one-page [framework/checklist] be useful as you assess the current process?
Guardrail: do not claim the person is rebuilding, replacing tools, or under pressure unless they said so.
2. Hiring-signal email
Use when: a current careers page shows hiring directly connected to your category.
Subject: [team] hiring and [job]
Hi [Name]—[Company] currently lists [number or named roles] for [team]. I’m curious whether [specific operating job] changes as those hires arrive. [Product/company] helps [team type] [bounded capability]. If useful, I can send the evaluation worksheet teams use before changing that process.
Guardrail: cite live roles precisely; never turn hiring into a claim that the team is overwhelmed.
3. Funding or expansion email
Use when: an official announcement states funding, a new market, or a new location.
Subject: [announced expansion] and [decision]
Hi [Name]—your [date] announcement says [Company] is [verified expansion]. One decision that can accompany that move is how to [specific job], but that may sit elsewhere. We provide [bounded capability]. Are you the right person to ask how [job] is being evaluated?
Guardrail: funding is not proof of budget, intent, or urgency.
4. Technology-change email
Use when: the company publicly documents an implementation, migration, or deprecation relevant to your offer.
Subject: [technology] workflow question
Hi [Name]—[source] notes that [Company] is [verified technology change]. Does your team own the [specific adjacent workflow] around that change? We help [team] [bounded job] and can share a field-mapping checklist if it is relevant. If another owner handles it, who should I ask?
Guardrail: third-party technology detection can be wrong; verify it before naming a stack.
5. Product or initiative launch email
Use when: the company announced a launch and your idea directly supports a resulting job.
Subject: [launch name] — [specific job]
Hi [Name]—I read [Company]’s announcement of [launch] on [date]. For teams taking [type of launch] to market, one planning question is [neutral question]. We help with [bounded capability]. Would the [specific artifact] be useful, or is that outside your remit?
Guardrail: reference what was announced, not confidential results or imagined launch problems.
Templates 6–9: legitimate context
Context creates a legitimate reason to write only when described accurately. A public post is not a personal endorsement, and a mutual connection is not a referral.
6. Prospect-authored content email
Use when: the prospect published a relevant, substantive point.
Subject: your point about [topic]
Hi [Name]—in [post/article/podcast], you said [short faithful paraphrase]. Your point about [specific implication] raised a question: how does [Company] handle [related job] today? We help [team] [capability]. I can send a concrete example if comparing approaches is useful.
Guardrail: link the source and paraphrase faithfully; do not manufacture praise or pretend a like equals interest.
7. Conference speaker email
Use when: the prospect spoke publicly on a topic tied to your offer.
Subject: [session] question
Hi [Name]—your [event] session covered [specific point]. I’m interested in one operational detail: [single question connected to point]. [Company/product] supports [bounded capability], so I can share [relevant example] if it helps. Is email the best place for that?
Guardrail: do not say you attended unless you did; a recording or published recap should be named as such.
8. Explicit referral email
Use when: a referrer authorized you to name them and contact the recipient.
Subject: [Referrer] suggested I ask about [job]
Hi [Name]—[Referrer full name] suggested I contact you about [specific job] and gave permission to mention them. We help [team] [bounded capability]. Would it be useful to compare your current approach with [specific alternative/artifact]? I’m happy to keep the discussion to email.
Guardrail: record the permission and do not include confidential details the referrer shared.
9. Mutual-connection email without a referral
Use when: shared context helps establish relevance, but nobody introduced you.
Subject: [community/topic] question
Hi [Name]—we both [truthful shared context], although [Mutual contact] did not refer me. I’m reaching out because [verified reason tied to recipient]. We help [team] [capability]. Is [specific job] yours, or should I leave it there?
Guardrail: the explicit non-referral prevents borrowed trust. Often the mutual connection is unnecessary; remove it when it adds no relevance.
Templates 10–12: inbound first responses
Inbound context changes the opening, but it does not justify inventing intent. State exactly what the person requested or submitted.
10. Demo-request first response
Use when: the recipient explicitly requested a demo.
Subject: your [Product] demo request
Hi [Name]—I’m responding to your demo request from [date]. To make the session useful, which is closer to your goal: [option A], [option B], or something else? Once I know, I’ll bring the relevant workflow and leave out unrelated features. You can reply here or choose [approved scheduling link].
Guardrail: do not describe a content download or newsletter signup as a demo request.
11. Resource-request first response
Use when: the recipient asked for a named guide, calculator, or template.
Subject: [resource name] you requested
Hi [Name]—here is the [resource] requested on [date]: [direct link]. It is designed for [job] and assumes [important limitation]. If you want, reply with [one diagnostic input] and I’ll point to the most relevant section. No meeting is required.
Guardrail: deliver the promised resource before adding a commercial ask.
12. Event-question first response
Use when: the person asked a recorded question or explicitly requested contact at an event.
Subject: your question about [topic] at [event]
Hi [Name]—you asked [faithful paraphrase] during [event/session] on [date]. A practical answer depends on [one variable]. Our approach is [bounded explanation], and this [resource] shows the trade-off. Would you like the version for [context A] or [context B]?
Guardrail: distinguish asking a question from merely registering or attending.
Templates 13–15: explicit hypotheses
When no strong signal or relationship exists, be honest about inference. These templates present a testable hypothesis rather than disguising firmographic fit as buyer knowledge.
13. Role-based problem-hypothesis email
Use when: the role commonly owns a job, but you have no evidence of the prospect’s current problem.
Subject: [job] at [Company]
Hi [Name]—this is a hypothesis, not something I know about your team: [role/team structure] can make [specific job] difficult when [condition]. We help [team] [bounded capability]. Is that issue present at [Company], or is the current process working well?
Guardrail: preserve the uncertainty language; do not convert “can” into “is.”
14. Current-tool evaluation email
Use when: the current tool is verified and you have a genuinely different approach.
Subject: [job] alongside [current tool]
Hi [Name]—[verified source] indicates [Company] uses [tool], though it does not reveal whether you are satisfied or evaluating alternatives. We differ on [specific, verifiable capability or operating model]. Would a neutral comparison worksheet help you decide whether the difference matters?
Guardrail: never claim a contract is expiring, a competitor is failing, or the buyer is switching without evidence.
15. Account-based owner-finding email
Use when: the account is relevant but responsibility is genuinely unclear.
Subject: who owns [job] at [Company]?
Hi [Name]—I’m trying to identify who owns [specific job] at [Company]. The reason is [one truthful account-level observation], and we help [team] [bounded capability]. Is this within your remit? If not, “not me” is enough—I do not want to create an unwanted forwarding task.
Guardrail: use this to resolve ownership, not to make the recipient sell internally on your behalf.
Apply claim and compliance guardrails
Copy quality sits downstream of campaign eligibility. In the United States, the FTC’s CAN-SPAM business guide says the law covers commercial messages, including B2B email, and requires accurate headers and subjects, a valid postal address, a clear opt-out method, and honoring opt-outs. Google’s sender guidelines separately publish authentication and unsubscribe requirements for sending to personal Gmail accounts. UK ICO guidance distinguishes corporate subscribers from sole traders and some partnerships and is currently under review. These sources are operating inputs, not a universal permission slip; get qualified advice for each jurisdiction and campaign.
| Risky draft | Why it fails | Safer rewrite |
|---|---|---|
| “[Referrer] said you need this.” | Invents endorsement and need | Use the explicit-referral template only with recorded permission |
| “Your team is losing hours every week.” | States an unverified pain and magnitude | “Does [job] create measurable manual work today?” |
| “Everyone in your industry is switching.” | Unsupported social proof | Name one authorized, relevant example or remove the claim |
| “Quick question” when pitching | Obscures the subject | Name the actual job or initiative |
| “Last chance” without a real deadline | Manufactures urgency | Remove it; state a documented deadline only when material |
The cold email compliance guide provides a broader operational checklist. Treat suppression, identity, address, unsubscribe, authentication, targeting, data provenance, and reply handling as release gates—not footer decorations.
Score every draft with this 100-point rubric
Have a second person score the populated email from zero to five on each criterion. Multiply each score by its weight, add the results, then divide by five. Reject any message that fails eligibility or factual accuracy regardless of its total; the number cannot average away a fabricated claim.
| Criterion | Weight | Evidence for a five |
|---|---|---|
| Eligibility and suppression | 20 | The recipient, purpose, channel, jurisdiction, consent or other basis, and suppression result pass current policy. |
| Factual accuracy | 20 | Identity, trigger, relationship, product, proof, dates, and links are verified and authorized. |
| Reason for this recipient | 15 | A reader can see why this message was selected without an invented pain or flattering guess. |
| Clarity | 15 | One topic, ordinary words, descriptive subject, and no unresolved placeholder or internal note. |
| Useful value | 10 | The offered idea, question, example, or resource exists and matches the stated job. |
| Proportionate ask | 10 | There is one specific next action that fits the evidence and relationship. |
| Operational readiness | 10 | Authentication, unsubscribe, address, routing, ownership, and reply handling meet applicable rules and policy. |
After QA, test one change at a time: for example, hypothesis framing while holding audience, offer, sender, timing, and routing stable. Predefine the evaluation window and meaningful-reply categories, retain delivered and bounced counts, and report raw counts with rates. The cold email A/B testing guide explains the experiment design. Do not call a template a winner because a handful of replies looked encouraging.
Print this SDR email selection sheet
Copy this one-page structure into a document or CRM checklist. It is the reusable artifact behind the examples.
- Select one use case: template number ___; use condition proven by ___.
- Record sources: recipient/role ___; signal/context ___; captured on ___; reviewer ___.
- Separate knowledge: verified observation ___; explicit buyer statement ___; labeled hypothesis ___.
- Define value: real resource, idea, or question ___; authorization checked by ___.
- Choose one action: reply / route / review / schedule; owner and destination ___.
- Run release gates: eligibility ___; suppression ___; identity ___; address ___; opt-out ___; authentication ___; routing ___.
- Score the draft: eligibility __/20; accuracy __/20; relevance __/15; clarity __/15; value __/10; ask __/10; operations __/10; total __/100.
- Approve or reject: approver ___; reason ___; version ___; experiment cell ___.
Gangly’s Outreach Writer can turn verified account context into a draft. Keep the human gate: the SDR or reviewer must confirm the source, eligibility, claim, template fit, and final wording before anything is sent.