Cold Email Templates: 24 Examples Sorted by Situation

A cold email template is a skeleton, not a script: a true reason for writing, one line showing it applies to this person, and a single easy request. Below are 24 templates sorted by situation, each with when to use it and why it works. We don't quote reply rates, because results depend on the list, offer and sender far more than the wording.

Three rules apply to all of them:

1. The reason must be true. No invented triggers, contacts or customer examples.
2. One ask per email. Never two.
3. Check the addresses first with the free email verifier or the list health check. Templates can't fix a bounce.

Placeholders are in square brackets. For subject lines, see 50 cold email subject lines by situation. For what to send after no reply, see 12 follow-up email templates.

Sales: first touch

The strongest first-touch emails open with something that happened at the prospect's company, not with who you are.

1. The trigger event

Hi [Name], saw [Company] [opened a second location / launched X / posted three SDR roles] this month. Teams at that stage usually run into [specific problem]. We help [type of company] with exactly that by [one-line mechanism]. Worth a 15-minute call next week?

When to use: a dated, public event. Why it works: the first line proves the email was written for them, and the problem follows from the event.

2. The problem question

Hi [Name], quick one: how is [Company] handling [specific task] at the moment? Most [role]s I speak to are doing it [common painful way]. We built [product] to [outcome]. If it's not a priority, no worries, just let me know.

When to use: you know the role but have no trigger. Why it works: an answerable question plus an easy out lowers the cost of replying.

3. The specific observation

Hi [Name], I went through [Company]'s [checkout / pricing page / careers page] and noticed [concrete, checkable detail]. That usually means [consequence]. I've put three ideas for fixing it in a short doc. Want me to send it over?

When to use: your product fixes something visible from outside. Why it works: value first, and the ask is permission to send, not a meeting.

4. The relevant result

Hi [Name], we helped [similar company, with permission] [specific, verifiable result] over [time period]. [Company] looks like a similar setup: [one shared trait]. Open to hearing how?

When to use: you have a customer result you can stand behind. Why it works: a peer result beats a claim. Never invent or round up the number.

5. The plain ask

Hi [Name], I'll be brief. We sell [product] to [type of company] that need [outcome]. Is that something [Company] cares about this quarter? A yes or no is genuinely helpful either way.

When to use: senior buyers who prefer directness. Why it works: it respects their time and the yes/no framing makes replying trivial.

6. The "right person?" email

Hi [Name], who at [Company] looks after [area]? I'd like to share a short idea on [outcome], and I'd rather not guess at the right person.

When to use: you don't know who owns the problem. Why it works: pointing you somewhere is a small favour. Send it to one person, not five.

7. The tech-stack fit

Hi [Name], noticed [Company] uses [tool, from their site or job ads]. We plug into [tool] to [specific job it does better]. Would a two-minute screen recording of how it works be useful?

When to use: you integrate with a tool they publicly use. Why it works: concrete, and the recording costs them nothing.

Referrals and introductions

Introduction requests work when they are easy to forward without editing.

8. Asking for a warm intro

Hi [Name], I see you know [Target] at [Company]. I'd love 15 minutes with them about [topic]. Here's a two-line blurb you could forward as-is: "[short blurb]". Totally fine if it's not a fit.

When to use: a genuine connection exists. Why it works: the blurb removes the work from the person helping.

9. The mutual-connection opener

Hi [Name], [Mutual contact] suggested I get in touch. [He/She] mentioned you're working on [project]. We [one-line relevance]. Would a short call make sense?

When to use: only when the mutual contact actually suggested it. Why it works: borrowed trust. Using a name without permission destroys it.

10. After an event

Hi [Name], I was at [event] and caught your talk on [topic]. Your point about [specific point] matched what we see with [type of customer]. Would you be open to comparing notes?

When to use: within a week or two of a shared event. Why it works: a specific detail proves you were there and listening.

Partnerships and agencies

11. Partnership proposal

Hi [Name], our customers are mostly [audience], the same people [Company] serves with [their product]. We often get asked about [their category]. Would you be open to a call about a referral arrangement or a joint [webinar / guide]?

When to use: overlapping audience, non-competing products. Why it works: it leads with what they get.

12. Agency to a local business

Hi [Name], I looked up "[service] in [town]" and [Company] shows up [position / doesn't appear on page one]. We help [trade] businesses fix that. Happy to send a free one-page audit of what's holding you back. Interested?

When to use: local service businesses; see cold email for local service businesses. Why it works: the observation is checkable and the audit is a low-risk yes.

13. Freelancer pitch

Hi [Name], I'm a [role] who works with [type of company]. I noticed [specific gap, e.g. the blog hasn't been updated since March]. Here are two short samples of similar work: [links]. Would you like a quote for [specific deliverable]?

When to use: pitching a defined piece of work. Why it works: samples replace adjectives about your quality.

Recruiting

14. Passive candidate

Hi [Name], I read your [post / project / talk] on [topic]. We're hiring a [role] to [specific problem], and your work on [thing] is close to what the role needs. Open to a 15-minute chat, even just to hear what we're building?

When to use: someone not actively looking. Why it works: specific about why them, low-commitment ask.

15. Recruiter to hiring manager

Hi [Name], saw [Company] has had the [role] post open for [time]. I've placed [number] [roles] in [industry] this year and have two candidates who match the brief. Want their anonymised profiles?

When to use: a role that has been open a while. Why it works: the offer is tangible and costs nothing to accept.

PR, content and link building

16. Journalist pitch

Hi [Name], your piece on [topic] last week mentioned [gap or open question]. We have [data / a customer story / an expert] that speaks to it directly: [one-line summary]. Happy to share the details if it's useful for a follow-up.

When to use: you have something newsworthy and specific. Why it works: it ties to their published work and offers material, not a press release.

17. Guest post or resource

Hi [Name], I liked your guide on [topic], especially [section]. I've written a [checklist / data study] on [related subtopic] that your readers might find useful: [link]. Would it fit as a resource in the guide?

When to use: your resource adds something the page lacks. Why it works: a narrow ask that improves their page.

18. Podcast guest

Hi [Name], I've listened to [episode], and your question about [topic] stuck with me. I [one-line credibility] and could talk about [three specific angles]. Would that suit an upcoming episode?

When to use: you have listened, and can name the episode. Why it works: the angles make it easy to picture the episode.

Founders and investors

19. Founder to early customer

Hi [Name], I'm the founder of [Company]. We're building [product] for [audience] who struggle with [problem]. I'm not selling anything yet: I'd value 20 minutes to hear how you handle [problem] today.

When to use: problem discovery before or just after launch. See cold email for SaaS founders. Why it works: a learning request is easier to accept than a sales call.

20. Investor outreach

Hi [Name], you invested in [portfolio company], so I think [Company] fits your thesis. We [one-line description], and [one verifiable traction fact]. Would you be open to a short deck?

When to use: the portfolio clearly overlaps. Why it works: it shows research and asks for something easy to review.

Re-engaging and closing out

21. Old lead, new reason

Hi [Name], we spoke in [month] about [topic]. Since then [change: new feature, price, case study]. Is [problem] still on the list for [Company]?

When to use: a past conversation that stalled. Why it works: a genuine change gives a reason to reopen. Check the address first: B2B contact data decays as people change jobs.

22. Champion who changed jobs

Hi [Name], congrats on the move to [New Company]. You used [product] at [Old Company] for [use]. If [problem] exists at [New Company] too, happy to help you set it up faster this time.

When to use: a former user starts a new role. Why it works: they already know the value, so the email is a reminder, not a pitch.

23. The resource offer

Hi [Name], we put together [specific resource] for [role]s dealing with [problem]. No call attached. Want me to send it?

When to use: a cooler audience. Why it works: asking permission keeps links out of the first email.

24. The close-out

Hi [Name], I haven't heard back, so I'll assume [problem] isn't a priority right now and won't follow up again. If that changes, this thread is here.

When to use: the last step of a sequence. Why it works: a clean ending is less likely to be reported than another nudge.

How to adapt a template without breaking it

Change the words, keep the structure: reason, relevance, ask.

• Personalise with real data only, with a fallback for every merge field; see personalization at scale.
• Keep it plain. No images and ideally no links in the first email; filters weigh links and reputation more than words (see spam trigger words).
• Include who you are and how to opt out. In the US, CAN-SPAM requires a postal address and a working opt-out on commercial email; see CAN-SPAM and cold email.
• Plan the follow-ups before you send. Three or four is a sensible start; see how many follow-ups a sequence should have.

Before you send any of them

Invalid addresses become hard bounces, which hurt the domain every later email depends on (why cold emails bounce). Verify the list and decide how to treat catch-all addresses. SimpleVerifier's paid plans exist for exactly this pre-send check (see pricing), and the free verifier is enough to test a sample first.

For the full process from list to reply, see how to write a cold email.