Cold Email Templates: 40 Signal-Based Examples You Can Copy
A cold email template that earns replies is short, opens with a specific reason you are writing now, connects that reason to one problem the reader owns, and ends with one easy question. The 40 templates below follow that pattern. Each one starts from a buying signal you can see and cite, such as a job change, a funding round, a hiring push or a post the person engaged with, so the first line explains itself.
Disclosure: Looply publishes this guide and makes cold email software that finds prospects from buying signals. Every template here is original. The sender rules in this guide were checked on the official Google, Yahoo and Microsoft pages and the FTC's CAN-SPAM guide on October 15, 2026.
How to use these templates
•
Replace every [bracket] with something specific and true. If you cannot fill a bracket, pick another template.
•
Only mention a signal you can point to: a public post, a press release, a job listing or an announcement.
•
Keep one ask per email. A yes-or-no question is easier to answer than a calendar link.
•
Keep the first email short. Most of these are under 100 words before the signature.
•
Add your own opt-out line and postal address where the law requires them (see the sender rules below).
Signal
What it suggests
Best first ask
Job change
New priorities and a first-90-days plan
Is [problem] on your list this quarter?
Funding round
Budget and pressure to grow
Who owns [area] as you scale?
Hiring push
A team is growing or a gap is opening
How are you handling [task] until the hires land?
Post engagement
Interest in a topic, right now
Is [topic] something you are working on?
Competitor engagement
Active comparison in your category
What would make a switch worth it?
Tool change
A workflow is being rebuilt
Want the checklist we use for that move?
Engaged with your company
Awareness of you
Was there a question behind it?
Event
Shared context and timing
Worth comparing notes after the event?
No signal
Fit only
Who owns [area] at [Company]?
The anatomy of a cold email that gets replies
1.
Subject line: three to six words that name the reason, not the product.
2.
First line: the signal, in plain words, with where you saw it.
3.
Relevance: one sentence on why that signal usually matters to someone in their role.
4.
Credibility: one concrete thing you do, without invented numbers or customer names you cannot share.
5.
Ask: one question they can answer in a few words.
6.
Sign-off: your name, plus the opt-out line and address if your volume or jurisdiction requires them.
Plain text
Subject: Your post on [topic]
Hi [First name],
Saw your comment on [author]'s post about [topic] last week. <- signal and source
Teams at [Company]'s stage often hit [specific problem] when <- relevance
[situation].
We help [type of team] [plain-language outcome]. <- credibility
Is that something you're working on this quarter? <- one ask
[Your name]
Job change templates
1. New sales leader in their first 90 days
Plain text
Subject: First 90 days at [Company]
Hi [First name],
Saw you joined [Company] as [Title] in [month]. New sales leaders I speak with usually review how outbound accounts get picked before they add headcount.
We help [type of team] find accounts that are showing buying signals before reps reach out.
Is that on your list for this quarter, or already handled?
[Your name]
2. A former user who moved to a new company
Plain text
Subject: Same setup at [New company]?
Hi [First name],
You used [your product] while you were at [Previous company]. Congrats on the move to [New company].
If [problem you solved for them before] shows up in the new role, I'm happy to set it up the way you had it, without starting from scratch.
Worth a short call in the next couple of weeks?
[Your name]
3. A new leader who inherits a tool stack
Plain text
Subject: Inheriting [tool category] at [Company]
Hi [First name],
Congrats on the new role leading [team] at [Company]. Inheriting a [tool category] setup someone else built is often the first headache.
We help teams like yours [plain-language outcome] without a long migration.
Would a one-page comparison of options be useful while you review the stack?
[Your name]
4. An internal promotion
Plain text
Subject: New scope at [Company]
Hi [First name],
Saw the move to [new title] at [Company]. That usually brings [area] under your roof for the first time.
We work with [type of team] on exactly that: [plain-language outcome].
Is [area] something you plan to change, or keep as it is for now?
[Your name]
5. Your contact left the account
Plain text
Subject: Picking up from [Previous contact]
Hi [First name],
I had been talking with [Previous contact] about [topic] before they moved on from [Company]. I understand you now own [area].
No need to restart anything. Would it help if I sent a two-line summary of where that conversation stood?
[Your name]
Funding round templates
6. Series A and a growing sales team
Plain text
Subject: After the Series A
Hi [First name],
Congrats on [Company]'s Series A, announced [date]. The announcement mentions growing the [team or market].
Teams at that stage often find the hard part is not sending more email but choosing which accounts deserve it. That is the problem we help with.
Who owns outbound pipeline as you scale: you or a new hire?
[Your name]
7. Seed round and founder-led sales
Plain text
Subject: Founder-led sales at [Company]
Hi [First name],
Congrats on the seed round. At this stage most of the first deals still come from the founders themselves.
We help founders spend their selling hours on accounts that are already showing interest, instead of cold lists.
Are you still running outbound yourself, or is that changing soon?
[Your name]
8. Funding that names a new market
Plain text
Subject: Expanding into [market]
Hi [First name],
Read that [Company] plans to use the new funding to expand into [market or region].
Breaking into a new market cold usually means a lot of guesswork about who to contact first. We help teams [plain-language outcome] in markets where they have no warm network yet.
Is the expansion starting this quarter or later in the year?
[Your name]
9. A funding follow-up a month later
Plain text
Subject: A month after the round
Hi [First name],
It's been about a month since [Company] announced its [round]. Usually by now the hiring plan is set and the pipeline targets are real.
If outbound is part of hitting them, I can share how similar teams pick which accounts to contact first.
Want me to send it over?
[Your name]
Hiring templates
10. Hiring SDRs
Plain text
Subject: Your SDR openings
Hi [First name],
Noticed [Company] is hiring [number] SDRs. New reps tend to ramp faster when the accounts they work already have a reason to talk.
That is what we help with: [plain-language outcome].
How are you feeding the new team with accounts while they ramp?
[Your name]
11. The first sales hire
Plain text
Subject: First sales hire at [Company]
Hi [First name],
Saw the opening for [Company]'s first [role]. Whoever takes it will need a pipeline from day one, not a blank CRM.
We help small teams [plain-language outcome].
Would it help to have that running before your hire starts?
[Your name]
12. Hiring in RevOps or sales operations
Plain text
Subject: The [role] opening
Hi [First name],
Saw [Company] is hiring a [RevOps or Sales Ops role]. The listing mentions [responsibility from the job post].
That is usually a sign the current setup is being rebuilt. We help with [the part you solve].
Is that project waiting for the new hire, or already underway?
[Your name]
13. Hiring in a new region
Plain text
Subject: Your [region] team
Hi [First name],
Noticed [Company] is hiring for [roles] in [region]. Building pipeline in a new region is slow when nobody there knows your brand yet.
We help teams start conversations in new regions from public buying signals rather than cold lists.
Is [region] a priority for this half of the year?
[Your name]
14. Many open roles on one team
Plain text
Subject: [Team] at [Company] is growing
Hi [First name],
Counted [number] open roles on [Company]'s [team] team. Growth like that tends to expose [problem] quickly.
We help teams like yours [plain-language outcome] while headcount catches up.
Is [problem] on your radar yet?
[Your name]
Post and topic engagement templates
15. They commented on a post about your topic
Plain text
Subject: Your comment on [topic]
Hi [First name],
Saw your comment on [author]'s post about [topic], especially the point about [their point].
We see the same thing with [type of team]: [one-line observation]. We help by [plain-language outcome].
Is [topic] something you're actively working on, or more of an interest?
[Your name]
16. They engage with an industry voice
Plain text
Subject: [Industry voice]'s point on [topic]
Hi [First name],
You've been active on [industry voice]'s posts about [topic] lately. Their take on [specific point] is close to how we think about it too.
If [topic] is a live project at [Company], I can share how [type of team] are handling it.
Worth a look?
[Your name]
17. They wrote about a problem you solve
Plain text
Subject: Your post about [problem]
Hi [First name],
Read your post about [problem] on [date]. The line about [quote or paraphrase] stood out.
That is the exact problem we work on for [type of team]: [plain-language outcome].
Would it be useful if I shared what has worked for others, with no pitch attached?
[Your name]
18. They asked a question in public
Plain text
Subject: Your question about [topic]
Hi [First name],
Saw your question in [community or thread] about [topic]. Short answer from what we see: [one honest sentence].
If it helps, I can send a longer write-up of the options, including ones we don't sell.
Want it?
[Your name]
Competitor engagement templates
19. They engaged with a competitor's post
Plain text
Subject: Comparing [category] tools?
Hi [First name],
Noticed you engaged with a recent post from [Competitor] about [topic]. If you are comparing [category] tools, the main difference worth testing is [your real difference].
I can send a short side-by-side so you can judge for yourself.
Would that be useful?
[Your name]
20. They asked for recommendations in public
Plain text
Subject: Your [category] question
Hi [First name],
Saw your post asking for [category] recommendations. When teams shortlist, they usually get stuck on [real decision point].
Happy to answer that honestly for your case, even if the answer is that we're not the right fit.
What's the main thing you need the tool to do?
[Your name]
21. They publicly review tools in your category
Plain text
Subject: Your review of [Competitor]
Hi [First name],
Read your public review of [Competitor] on [site]. The point about [their complaint] comes up often.
We built [your product] around solving that: [plain-language outcome].
Would a 15-minute walkthrough focused only on that be worth it?
[Your name]
Tool change templates
22. They just adopted a new CRM
Plain text
Subject: The move to [CRM]
Hi [First name],
Saw that [Company] recently moved to [CRM]. Migrations are a good moment to fix how leads get in, not just where they are stored.
We connect to [CRM] and help [plain-language outcome].
Is the setup finished, or still in progress?
[Your name]
23. They are moving away from a tool
Plain text
Subject: After [old tool]
Hi [First name],
Noticed [Company] is moving away from [old tool]. Usually that happens because of [common reason].
If that's the case for you, I can share the checklist we use to compare replacements.
Want it?
[Your name]
24. They added a tool that pairs with yours
Plain text
Subject: [New tool] plus [your product]
Hi [First name],
Saw [Company] started using [new tool]. Teams that use it often pair it with [your category] to [plain-language outcome].
Would it help to see how the two fit together?
[Your name]
25. A job post names a tool
Plain text
Subject: [Tool] in your job listing
Hi [First name],
Your [role] listing asks for experience with [tool]. That usually means [workflow] is central for your team.
We help teams running [tool] [plain-language outcome].
Is improving [workflow] part of what the new hire will own?
[Your name]
Templates for people who engaged with your company
26. They engaged with your company's post
Plain text
Subject: Your note on our post
Hi [First name],
Thanks for engaging with our post about [topic]. Was there a question behind it, or something you're trying to solve at [Company]?
Happy to help either way.
[Your name]
27. They followed your company page
Plain text
Subject: Thanks for the follow
Hi [First name],
Saw you followed [your company] on LinkedIn. Most people who do are looking at [problem you solve].
Is that the case for you? If so, I can point you to the two pages worth reading first.
[Your name]
28. They commented on your own post
Plain text
Subject: Your comment on my post
Hi [First name],
Thanks for your comment on my post about [topic]. You mentioned [their point], which I'd love to understand better.
How are you handling that at [Company] today?
[Your name]
Event templates
29. They are speaking at a conference
Plain text
Subject: Your talk at [event]
Hi [First name],
Saw you're speaking at [event] about [topic]. I'll be there, and the subject is close to what we work on.
Would you be open to a coffee after your session?
[Your name]
30. You are both attending
Plain text
Subject: See you at [event]?
Hi [First name],
Looks like we're both going to [event] on [date]. I'm meeting a few [role]s to compare notes on [topic].
Want to grab 15 minutes there?
[Your name]
31. After the event
Plain text
Subject: After [event]
Hi [First name],
Hope [event] was worth the trip. The session on [topic] raised a point I keep hearing: [point].
If that's on your list, I can share what we're seeing across [type of team].
Interested?
[Your name]
Meeting request templates without a signal
32. The direct ask
Plain text
Subject: [Problem] at [Company]
Hi [First name],
We help [type of team] [plain-language outcome].
Teams like [Company] usually come to us when [trigger situation].
Is that happening on your side? If yes, is a 15-minute call next week reasonable?
[Your name]
33. The question only
Plain text
Subject: Quick question
Hi [First name],
How does [Company] decide which accounts your team contacts each week today?
Asking because that's the part we help [type of team] improve.
[Your name]
34. Asking for the right person
Plain text
Subject: Who owns [area]?
Hi [First name],
Who at [Company] owns [area]? I'd like to send them a short note about [plain-language outcome] and would rather not guess.
Thanks either way.
[Your name]
Follow-up templates
35. Day 3: a new angle
Plain text
Subject: Re: [original subject]
Hi [First name],
One more angle on my last note: [a different benefit or example in one sentence].
Does that change whether it's worth a look?
[Your name]
36. Day 7: something useful
Plain text
Subject: Re: [original subject]
Hi [First name],
Thought this might help whether or not we talk: [resource, with a one-line summary of what's inside].
[Link]
[Your name]
37. Day 10: one short question
Plain text
Subject: Re: [original subject]
Hi [First name],
Is [problem] a priority for [Company] this quarter, or should I check back later?
[Your name]
38. Day 14: close the loop
Plain text
Subject: Closing the loop
Hi [First name],
I haven't heard back, so I'll assume [problem] isn't a priority right now and stop here.
If that changes, just reply to this email and I'll pick it up.
[Your name]
Re-engagement templates
39. An old conversation gets a new signal
Plain text
Subject: Picking this back up
Hi [First name],
We spoke in [month] about [topic], and the timing wasn't right. Since then [new signal, such as a funding round or a new team].
Does that make it worth revisiting?
[Your name]
40. A lost deal after a trigger
Plain text
Subject: Since we last spoke
Hi [First name],
When we last talked, [Company] chose [option] for [reason]. I saw [new signal] and thought it might change the picture.
If it doesn't, no problem. If it does, I'm happy to help.
[Your name]
Subject lines that match the signal
Signal
Subject line ideas
Job change
First 90 days at [Company] · New scope at [Company]
Funding
After the Series A · Expanding into [market]
Hiring
Your SDR openings · First sales hire at [Company]
Post engagement
Your comment on [topic] · Your post about [problem]
Competitor
Comparing [category] tools? · Your [category] question
Tool change
The move to [CRM] · After [old tool]
Event
Your talk at [event] · See you at [event]?
Follow-up
Re: [original subject] · Closing the loop
Keep subject lines honest. CAN-SPAM forbids subject lines that misrepresent the message, and "Re:" belongs only on a real reply in the same thread.
Personalize without sounding like surveillance
•
Name a public source: "your post on [topic]", "the Series A announcement", "your job listing".
•
Never reference data the person would not expect you to have.
•
One specific detail beats five generic ones.
•
Do not fake familiarity. "Hope you're well" adds nothing; a real reason does.
•
Treat the signal as a reason to ask, not as proof they want to buy.
A follow-up cadence to start from
1.
Day 0: the first email, built on the signal.
2.
Day 3: a new angle in two or three lines.
3.
Day 7: something useful, with no ask attached.
4.
Day 10: one short question.
5.
Day 14: close the loop and stop.
Stop the sequence as soon as someone replies or opts out, and test changes to the cadence the same way you test templates.
Sender rules to check before you send (2026)
Templates only work if the email reaches the inbox. These are the requirements published by the mailbox providers and the FTC, checked on October 15, 2026.
Rule set
Applies to
Requirements
Gmail, all senders
Anyone sending to Gmail accounts
SPF or DKIM; valid forward and reverse DNS; TLS; spam rate in Postmaster Tools below 0.3%
Gmail, bulk senders
More than 5,000 messages a day to Gmail
SPF, DKIM and DMARC (a p=none policy is allowed); From domain aligned with SPF or DKIM; one-click unsubscribe for marketing and subscribed messages; spam rate below 0.3%, ideally below 0.1%
Yahoo, bulk senders
High-volume senders to Yahoo
SPF and DKIM; a DMARC policy of at least p=none that passes; one-click unsubscribe for marketing messages, honored within 2 days; spam rate below 0.3%
Outlook.com, high-volume senders
5,000+ messages from one From domain to Microsoft consumer addresses
SPF and DKIM must pass; a DMARC record (p=none allowed) that passes, with SPF or DKIM aligned to the From domain; non-compliant mail is rejected with error 550 5.7.515
CAN-SPAM (United States)
All commercial email, including B2B
Accurate headers; no deceptive subject lines; identify the message as an ad; a valid postal address; a clear opt-out honored within 10 business days and working for at least 30 days; penalties of up to $53,088 per email
Outside the United States, other rules apply. In the EU and the UK, B2B cold email also has to respect GDPR and local rules on electronic marketing. For France, see our guide to CNIL rules for B2B prospecting.
How to measure a template
•
Track replies and positive replies, not opens. Some mail apps load images automatically, which makes open rates unreliable.
•
Count meetings held, not meetings booked.
•
Change one thing at a time: the signal, the subject line or the ask.
•
Compare templates on similar audiences and the same send window, so the test is fair.
Where Looply fits
Writing the email is the quick part. Finding the signal and checking that the person fits your ideal customer profile is what takes the time. Looply watches several of the signals in this guide on LinkedIn: job changes, funding rounds, and engagement with topics, people, your company page and competitor pages you choose. It scores each person against your ideal customer profile and drafts a first email from that signal for you to review before it goes out from your own connected inbox.
Short enough to read on a phone in a few seconds. Most templates here are under 100 words before the signature. If the email needs a scroll, cut the explanation and keep the reason, the relevance and the ask.
How many follow-ups should I send?
Three or four follow-ups over about two weeks is a reasonable starting point. Each one should add something new, and the last one should close the loop. Stop as soon as someone replies or asks you to stop.
Is cold email legal?
In the United States, CAN-SPAM allows commercial email to businesses if you follow its rules: accurate headers, honest subject lines, a postal address and a working opt-out honored within 10 business days. In the EU and the UK, GDPR and local electronic-marketing rules apply, so check the rules for each country you send to.
What is a good reply rate for cold email?
It depends on your market, your list and your offer, so published benchmarks rarely transfer. Compare templates against each other on similar audiences and track positive replies and meetings held, not opens.
Can I send these templates from Gmail or Outlook?
Yes, as long as your domain meets the sender rules above. Authenticate your domain with SPF and DKIM, add DMARC, keep volumes reasonable per mailbox and watch your spam rate.
Do templates still work in 2026?
Templates work as structure, not as copy to paste unchanged. A template with a real signal and one specific detail reads as a personal email. The same template with empty brackets reads as spam.
Looply finds people showing buying signals, checks them against your ideal customer profile and drafts the first email for you to review. Start the 7-day free trial or see pricing.
