21 Cold Email Templates Built on Real Prospect Research
The cold email templates that get replies are short, tied to a recent trigger, and built on a fact you can link to. The bar is high: Instantly's 2026 benchmark puts the average cold email reply rate at 3.43%, while the top 10% of senders clear 10.7%. Gartner found 73% of B2B buyers actively avoid suppliers who send irrelevant outreach.
Each template below names the trigger, the research input you need before you send, the email itself (all under 90 words) and why it works. Swap the bracketed fields with facts you can link to. If you can't find the input, don't send that template.
How should you use cold email templates without sounding templated?
Use the template as a structure and the research as the content. The structure (trigger, relevance, one question) can repeat across 500 sends. The first two lines cannot.
Three rules apply to every template on this page:
- Every specific claim in the email maps to a source URL you saved. If a reply says "where did you see that?", you can answer.
- The trigger must be recent. A funding round from 14 months ago or a job change from last year reads as automation, which is the problem covered in stale personalization is killing your outreach.
- One ask per email, and make it small: a yes/no question or a resource, not a 30-minute meeting.
Keep the email short. Instantly found that its top performers average fewer than 80 words in the first email. Hunter's analysis of 34 million emails found that 20 to 39 words got the highest reply rate (4.5%), though it called the gap to longer emails modest. Gong's data on executives puts the sweet spot at 50 to 100 words, with replies dropping sharply above 100. Every template here is under 90 words for that reason.
Which templates work for job changes? (1 to 3)
Job change templates work when they quote the person's own words or past results. New leaders review vendors and processes early, which makes this one of the most reliable triggers in B2B outbound. Sales signals covers how to rank this trigger against the others.
1. New VP in their first 90 days
Research input: start date and previous company from their LinkedIn profile, plus one priority they've stated publicly (post, interview, job description they wrote).
Subject: first 90 days at [Company]
Hi [Name], congrats on the move to [Company] from [Previous company]. In your [post/interview] you said [stated priority]. Most [role]s we talk to in their first quarter find [specific gap] before they find the fix. We help [peer type] with [outcome] using [one-line how]. Worth a 2-line reply on whether [stated priority] is on this quarter's list?
Why it works: it references the leader's own words, so it can't be mistaken for a mass send.
2. Former customer champion at a new company
Research input: confirmation the person used your product at their last company (your CRM), their new title and company, and one sign the new company has the same problem.
Subject: [Product] at [New company]?
Hi [Name], saw you joined [New company] as [title]. When you were at [Old company] your team used [Product] for [use case]. [New company] is [hiring for X / running Y], which looks like the same setup you had. Happy to send the before-and-after numbers your old team tracked if they'd help your planning. Want them?
Why it works: you're offering their own past results, not a pitch.
3. Internal promotion
Research input: promotion date and new scope (team size or region) from LinkedIn or a company announcement.
Subject: new scope at [Company]
Hi [Name], congrats on the move to [new title]. Taking on [new region/team] usually means inheriting someone else's [process/tool]. When [peer company] went through this, the first thing they rebuilt was [specific workflow]. Is that on your list, or already sorted?
Why it works: promotions bring inherited problems, and naming one shows you understand the job.
Which templates work for funding and hiring? (4 to 8)
Funding and hiring templates work when you pair the event with a second fact, such as open roles or a stated use of funds. A round tells you budget exists, not what they'll spend it on. Job posts are the most honest public document a company publishes: they list the tools, the problems and the budget owner.
4. Fresh round plus a hiring plan
Research input: round size and date from the press release or Crunchbase, plus open roles on their careers page.
Subject: after the [Series X]
Hi [Name], congrats on the [Series X] announced [date]. Your careers page lists [N] open [function] roles, so I'm guessing [function] is where the money goes first. Teams scaling [function] that fast tend to hit [specific bottleneck] around hire [N]. We [one-line how]. Useful to compare notes before the new hires start?
Why it works: it connects the money to a visible plan and predicts a problem they haven't hit yet.
5. Round announced with a stated use of funds
Research input: the quote in the funding announcement where the CEO says what the money is for.
Subject: "[quoted use of funds]"
Hi [Name], in the [Series X] announcement [CEO] said the round will go toward "[quoted use of funds]". We help [peer type] do exactly that with [outcome]. One question: is [function] owned by your team, or someone else I should talk to?
Why it works: you're quoting their stated plan back to them and asking a routing question that's easy to answer.
6. Hiring for the role you sell to
Research input: the job post URL, date posted, and one responsibility from the description.
Subject: your [job title] posting
Hi [Name], your [job title] post says the hire will "[responsibility]". Until they start, someone is covering that. We help teams like [peer] handle [responsibility] without adding headcount, or make the new hire productive faster. Which matters more right now?
Why it works: it gives two outcomes and lets them pick, which invites a reply.
7. First hire in a new function
Research input: evidence it's the first role in the function (no current employees with that title on LinkedIn, or "first [role]" in the post).
Subject: building [function] from zero
Hi [Name], looks like [job title] is your first [function] hire. First hires usually spend month one choosing tools and month two cleaning data. We've helped [N] teams set up [function] before the first hire starts. I can send the 1-page setup checklist we use. Interested?
Why it works: it offers a useful asset to the hiring manager before the new hire arrives.
8. Job post names a tool or pain
Research input: the exact tool or problem named in the job description.
Subject: [tool] in your job post
Hi [Name], your [role] listing asks for experience with [tool] and "[pain phrase]". That usually means [interpretation]. We [how you help with that tool or pain]. Open to a short note on how [peer] handled the same thing?
Why it works: the company wrote the problem statement for you.
How do you write to someone who posted a pain point? (9 to 11)
Write to the author only if they identified themselves publicly, and respond to the exact problem they described. People describe problems more honestly in communities than anywhere else, so respect the setting and don't try to unmask anonymous posters. If the author is anonymous, use the pain language to reach lookalike accounts instead.
9. Author identified themselves in a pain post
Research input: the post URL, the specific complaint, and the author's public identity as they stated it.
Subject: your post in r/[subreddit]
Hi [Name], read your r/[subreddit] post about [problem] at [Company]. You mentioned [detail]. We built [product] for that exact situation: [one-line how]. No pitch call needed; happy to answer in the thread or by email if useful. Did you find a fix yet?
Why it works: it responds to a problem they chose to share publicly and asks whether it's still open.
10. Recurring pain theme, lookalike accounts
Research input: 3 or more public posts describing the same pain, and a list of accounts with the same profile as the posters.
Subject: [problem] at [type of company]
Hi [Name], we keep seeing [role]s at [type of company] describe the same problem: "[paraphrased pain]". It usually shows up when [condition that applies to their company]. Is that true for [Company] too, or have you solved it?
Why it works: it uses the buyer's own vocabulary without pretending you know their situation.
11. Someone asked for tool recommendations
Research input: the thread URL asking "what do you use for X", and the author's company if they shared it.
Subject: your question about [category]
Hi [Name], saw you asked which [category] tools people use. The honest answer depends on [deciding factor]. If [condition], [competitor or approach] is probably the better fit. If [other condition], we built [product] for that. Happy to share a comparison either way.
Why it works: recommending an alternative when it fits earns trust faster than any claim.
Which templates work for tech changes and competitor mentions? (12 to 15)
Tech change and competitor templates work when you name the change and ask one qualifying question. A new tool creates integration work, a dropped tool creates a gap, and a competitor complaint means the prospect has already named the problem. Twelve buying signals only a logged-in browser session can see lists where these changes show up.
12. Adopted a complementary tool
Research input: evidence of adoption (script on their site, job post, vendor case study) and its date.
Subject: [new tool] plus [your category]
Hi [Name], looks like [Company] added [new tool] recently. Teams that add it usually find [specific gap] next, because [reason]. We plug into [new tool] in [time]. Want the 3-step setup [peer] used?
Why it works: it attaches you to a project that's already funded and in motion.
13. Moving off a competitor
Research input: a public sign of the switch (job post dropping the tool, review, community post, or removed script).
Subject: after [competitor]
Hi [Name], noticed [evidence of switch]. Teams leaving [competitor] usually do it for [reason A] or [reason B]. If it's [reason A], we're a good fit. If it's [reason B], we'd struggle and [alternative] is better. Which one was it?
Why it works: a qualifying question with an honest exit is easy to answer.
14. Public complaint about a competitor
Research input: the public review or post URL and the specific complaint.
Subject: [competitor] and [complaint]
Hi [Name], read your review of [competitor] where you mentioned [complaint]. We handle that differently: [one-line how]. We're weaker at [honest gap], so it's not a fit for everyone. Worth a look?
Why it works: naming your own weakness makes the strength believable.
15. Their competitor is a customer of yours
Research input: a public case study or logo of a competitor company using your product (only if public).
Subject: how [competitor company] handles [process]
Hi [Name], [competitor company] published how they use [product] for [process]: [result from the public case study]. [Company] runs a similar [motion]. Curious whether [process] is already solved on your side?
Why it works: peer pressure works when the proof is public and linked.
Which templates work for events, launches and posts? (16 to 21)
Event, launch and post templates only work within a week of the date. Each gives you a dated, public reason to write, and that reason expires fast.
16. They spoke at a conference
Research input: talk title, event, date, and one point from the talk or slides.
Subject: your [event] talk
Hi [Name], caught the recording of "[talk title]" at [event]. Your point about [specific point] matched what we see at [peer type]. One thing we'd add: [single useful insight]. Did the Q&A push back on that?
Why it works: it adds to their thinking instead of flattering it.
17. Attending the same event
Research input: their name on the attendee list, speaker list or a public post saying they'll attend.
Subject: [event] next week
Hi [Name], saw you're at [event] on [date]. We'll be at [booth/session]. If [problem] is on your mind, I can show you how [peer] handles it in 10 minutes there. Want me to hold a time?
Why it works: the ask is small, specific and already on their calendar.
18. New product launch
Research input: launch post, date, and the target customer it names.
Subject: [product name] launch
Hi [Name], congrats on launching [product name]. You're going after [target segment], which means [new motion they'll need]. We help teams [outcome] when they open a new segment. Who owns that work on your side?
Why it works: launches create new work, and the routing question gets you to the owner.
19. Expansion into a new market
Research input: announcement of a new office, region or language site.
Subject: [Company] in [region]
Hi [Name], saw [Company] opened in [region] this [month]. Teams entering [region] usually hit [specific issue: compliance, data, hiring] in the first 6 months. We helped [peer] with [outcome] there. Is that on your radar?
Why it works: it's specific to the region and forward-looking.
20. They posted on LinkedIn
Research input: the post URL, date (last 7 days) and the argument they made.
Subject: your post on [topic]
Hi [Name], your post on [topic] said [argument]. Agree on [part], and we'd push back on [part] because [evidence]. Here's the data if useful: [link]. How are you measuring [metric] today?
Why it works: polite disagreement with evidence gets more replies than agreement.
21. Podcast or interview appearance
Research input: episode link, timestamp and the quote.
Subject: [podcast] at [timestamp]
Hi [Name], at [timestamp] on [podcast] you said [quote]. That's the problem we work on: [one-line how]. If you're open to it, I'll send a 1-page summary of how [peer] tackled it. Yes or no?
Why it works: the timestamp proves you listened.
Which template should you start with?
Start with the hiring templates (6 to 8) if you sell to a function, and the job change templates (1 to 3) if you sell to a leader. Both triggers are public, dated and easy to verify, so your research time per contact stays low.
Save Reddit and competitor templates for when you have a clear point of view, because they need more judgement to send well.
Each template is a first touch. Plan 2 or 3 follow-ups that add a new fact rather than "bumping" the thread. The data on follow-ups disagrees on where replies come from: Instantly says 58% of replies come from the first email and recommends 4 to 7 touchpoints, while Belkins' 2025 study of 7.5 million emails found the first email captured only 41.4% of replies. Both agree that stopping after one email leaves replies on the table. Hunter saw 3.3% replies from single emails against 6.8% from three-message sequences.
Your sending tool decides whether these emails land at all. Our comparison of cold email software covers which senders handle warmup, inbox rotation and deliverability checks. For how these templates fit into a full team motion, see the outbound sales playbook.
How do you find the research inputs fast?
Find inputs by working from the trigger to the person, not the other way round. Start with a list of companies that hired, raised, launched or posted this week, then find the right contact.
Doing this by hand takes 10 to 20 minutes per account. Drevon does it from your own browser session: it reads LinkedIn, Reddit, job boards, Crunchbase and company sites, then returns a brief where every claim links to its source, so the [research input] fields above come pre-filled with evidence. The AI lead generation playbook shows where this step sits in the wider workflow.
Frequently asked questions
How long should a cold email be?
Aim for 50 to 90 words in the first email. Instantly's top performers average under 80 words, and Gong found executive replies drop sharply above 100 words.
How many follow-ups should I send?
Two or three, each with a new piece of evidence. Hunter found three-message sequences got 6.8% replies against 3.3% for a single email, and Instantly recommends 4 to 7 touches in total across channels.
Is it OK to mention someone's Reddit post in a cold email?
Only if the author made their identity public in the post or profile. Don't try to unmask anonymous accounts. If they're anonymous, use the pain language for lookalike accounts (template 10) instead.
Should I use AI to write cold emails?
Use AI to gather and summarise the research inputs, then keep the template structure fixed. AI-written first lines without a linked source tend to invent details, which costs you more trust than a plain email.
Do these templates work for LinkedIn messages?
Yes, with shorter versions. Drop the subject line and cut each one to 2 or 3 sentences. LinkedIn messages are read on mobile.
Start with one trigger, 20 accounts and a saved source for every claim. Download Drevon to pull the research inputs for those 20 accounts in one session.
Sources
- Instantly, "Cold Email Benchmark Report 2026", accessed 2026-10-10.
- Gartner, "Gartner Sales Survey Finds 61% of B2B Buyers Prefer a Rep-Free Buying Experience", June 2025, accessed 2026-10-10 via syndicated copy.
- Hunter, "Cold email word count study", accessed 2026-10-10.
- Hunter, "The State of Email Outreach 2026", accessed 2026-10-10.
- Gong, "Do execs reply to cold email", accessed 2026-10-10.
- Belkins, "Sales follow-up statistics", accessed 2026-10-10.