What makes a cold email template work?
Every template here uses the same skeleton: a first line about the reason you are writing, usually a trigger, one or two lines linking it to a problem you solve, and a small question as the next step. The trigger does most of the work, because it answers what every recipient asks first: why me, and why now?
Placeholders are in curly braces. Replace them with facts you checked, and delete any line you cannot make true. A vague trigger ("I saw you are growing") is worse than none, because it proves the email was automated.
| Template | Reason to write | Best for |
|---|---|---|
| 1. The switch | Competitor complaint | Products with a clear rival |
| 2. The shortlist | Search for an alternative | Products that hold up in side-by-side comparisons |
| 3. The answer | Tool recommendation request | Any product in an active category |
| 4. The launch | Product launch | Agencies and tools for early-stage teams |
| 5. The new hire | Hiring post | Tools and services that support a specific role |
| 6. The round | Funding announcement | Services and tools bought with growth budgets |
| 7. The first stack | New company | Finance, operations and infrastructure tools |
| 8. The right person | Business expansion | Larger accounts where the owner is unclear |
| 9. The follow-up | Pain-point post, step two | The second email of any sequence |
| 10. The break-up | Tech stack change, last step | The final email of any sequence |
| 11. The returning user | A former user starts a new job | Products with a base of active users |
| 12. The response | A post, talk or podcast by the prospect | Experts and founders selling to peers |
| 13. The observation | A visible problem on their website | Agencies and service businesses |
| 14. The second look | A lost deal you can now win | Teams with closed-lost records |
| 15. The partner ask | Another business serves the same buyers | Introductions rather than sales |
Templates for switching moments: complaints, alternatives and tool requests
These three triggers come from people who are already unhappy or already shopping. The email can be direct about your product, as long as it addresses what they actually wrote.
1. The switch (competitor complaint)
Subject: exports in {competitor}
"Hi {first name}, you mentioned on {platform} that getting a plain CSV out of {competitor} means opening a support ticket. In {product}, exports are one click, and your saved reports carry over when you import. I can record a two-minute video of an export on data shaped like yours. Worth sending?"
Why it works: it quotes their own complaint, so the relevance is obvious in line one. The proof is small and concrete, a short video rather than a demo. It says nothing bad about the competitor; the prospect already did that. Finding and qualifying these posts: competitor complaints.
2. The shortlist (alternative seeker)
Subject: for your {competitor} shortlist
"Hi {first name}, I saw you are comparing alternatives to {competitor} for a team of about {team size}. One question usually decides it: do you need {key capability} from day one, or later? If day one, we are worth a look, and I can send our comparison sheet, including the cases where {competitor} is still the better fit. Want it?"
Why it works: people comparing tools want help deciding, not a pitch. Asking the deciding question shows you know the category, and admitting where the competitor wins makes the rest believable. More on this signal: people looking for alternatives.
3. The answer (tool recommendation request)
Subject: your {category} tool question
"Hi {first name}, you asked on {platform} for a {category} tool that a {team type} can run without a dedicated admin. You listed {requirement 1} and {requirement 2}: {product} covers both, and setup takes {setup time}. Happy to answer questions here by email, no call needed. Would a short checklist of what to test, whichever tool you choose, be useful?"
Why it works: it answers their stated requirements instead of describing your product in general. Offering help by email lowers the effort of replying, and the checklist is useful even if they pick someone else. More on this signal: software recommendation requests.
Templates for growth moments: launches, hiring, funding and new companies
These triggers do not mean the company is shopping for you. They mean something changed, and change creates new problems. The email has to connect the event to one specific problem, or it reads as a generic congratulation.
4. The launch (product launch)
Subject: your {product name} launch
"Hi {first name}, congrats on launching {product name} on {launch site} this week. One thing I noticed: the signup form asks for {field} before people see the product, which adds a step at the moment they are most curious. We help early-stage teams tighten onboarding in the weeks after launch. Want the three changes I would test first, in a short doc?"
Why it works: a launch is public, recent and top of mind, so the timing feels natural. The specific observation proves you looked, and the doc gives value before asking for time. Where to spot launches: product launches.
5. The new hire (hiring post)
Subject: your {role} opening
"Hi {first name}, I saw you are hiring a {role}. The post mentions {responsibility}, which suggests someone is doing it by hand today. Teams use {product} so a new {role} starts with {outcome} on day one instead of building it from scratch. Would it help to see that setup before the person starts?"
Why it works: a job post shows budget and priority, and its wording tells you what the company cares about. Positioning the product as support for the new hire, not a replacement, removes the obvious objection. More on this signal: hiring signals.
6. The round (funding announcement)
Subject: after the {round} round
"Hi {first name}, congrats on the {round} led by {investor}. A round usually comes with a growth target and a hiring plan, and {problem area} is often one of the first things to stretch. We help {company type} with {specific outcome}. If {problem area} is on your list for next quarter, I can share how we would approach it for a team your size. Interested?"
Why it works: it ties the round to a concrete next-quarter priority instead of only congratulating. Funded companies get a lot of email, so naming a specific problem is what sets yours apart. More on this signal: recently funded startups.
7. The first stack (new company)
Subject: setting up {area} at {company}
"Hi {first name}, I saw {company} listed on {directory} recently. It is tempting to pick {area} tools quickly and switch later, but switching gets harder once data piles up. We built {product} for companies at your stage: {plan detail}. Would a one-page checklist for choosing a {area} setup you will not need to replace in two years be useful?"
Why it works: new companies are choosing tools for the first time, so there is no incumbent to displace. A neutral checklist makes you a guide rather than a vendor. More on this signal: new companies.
Templates for referrals, follow-ups and break-ups
The last three cover the parts of a sequence most people write badly: finding the right person, following up without nagging, and ending politely.
8. The right person (business expansion, referral-style)
Subject: who owns {new market} operations?
"Hi {first name}, I read that {company} is opening in {market} this {timeframe}. I work on {problem tied to expansion}, and I am not sure who is leading that for the new {market}. Could you point me to the right person? If it is you, I would welcome 15 minutes to walk through {specific approach}."
Why it works: expansion creates new owners and unclear responsibilities. A referral request is easy to answer, and an internal forward makes the next email warmer. Only say that someone referred you when they actually did. More on this signal: business expansion.
9. The follow-up (pain-point post, step two)
Subject: same thread as the first email
"Hi {first name}, one more thought on the {problem} you described. The simplest fix is usually {approach}, and it does not require {product}. Here is a short write-up with the steps: {link}. If you would rather have it set up for you, that is what we do."
Why it works: a follow-up should add something new. Giving the approach away builds trust and gives a reason to reply, and it helps people who were never going to buy, which keeps spam reports down. More on this signal: pain-point posts.
10. The break-up (tech stack change, last step)
Subject: same thread as the first email
"Hi {first name}, I will stop here. If the move to {new tool} brings up {problem} later, for example when {specific moment}, reply with later and I will check back next quarter, or with no and I will not write again."
Why it works: it is honest about being the last email and offers two one-word replies, both useful to you. Naming the moment the problem tends to appear keeps the door open without pressure. More on this signal: tech stack changes.
Reach companies with a reason to buy this week
Startories finds the buying signal, verifies the decision-maker and runs the outreach until they book a call.
Templates for job changes, content, site issues, lost deals and partners
Not every good reason to write is a public post. These five start from your own records, your own research, or a business that serves the same buyers.
11. The returning user (job change)
Subject: {product} at {new company}?
"Hi {first name}, congrats on the new role at {new company}. At {old company}, your team used {product} for {use case}. If {problem} shows up there too, I can copy your old setup so you do not start from zero. Worth 15 minutes in your first month, or too early?"
When to use it: someone who actively used or championed your product at a previous employer joins a company that fits your profile. Check your records; an old account alone is not enough.
Why it works: there is nothing to explain, and "or too early?" makes replying easy without a commitment. Other people changes worth tracking are in buying signals with examples.
12. The response (a post, talk or podcast)
Subject: your point on {topic}
"Hi {first name}, I listened to your {podcast} episode on {topic}. Your point that {specific claim} matches what we see, with one exception: {exception}. I wrote up how teams handle that case in five steps. Want it?"
When to use it: the prospect recently published something about the problem you solve. Read or listen to all of it first.
Why it works: engaging with one idea proves attention in a way no compliment can, and the exception gives them something to answer.
13. The observation (agencies and services)
Subject: the demo form on {domain}
"Hi {first name}, I tried the demo form on {page} from my phone, and it shows an error after you press submit. It works on desktop, so it may only affect mobile; happy to send a screenshot. If you want a second pair of eyes on the rest of the signup flow, that is what we do."
When to use it: you sell web design, SEO, conversion or development work and found a concrete problem anyone can check. Test it twice; a false alarm ends the conversation.
Why it works: the finding is useful even if they never hire you. More angles in lead generation for web design agencies and for SEO agencies.
14. The second look (a deal you lost)
Subject: {capability} is live
"Hi {first name}, in {month} you decided not to go ahead because we did not support {capability}. We shipped it in {month}. If {problem} is still open, I can show you just that part in 15 minutes. If you solved it another way, I would like to hear how."
When to use it: you lost a deal months ago for a specific reason you have since fixed. Skip anyone who asked not to hear from you again.
Why it works: it quotes their own reason for saying no, so it reads as follow-through. The last line earns a reply even from people who will not buy, and tells you what the market chose instead.
15. The partner ask (shared buyers)
Subject: your clients after {milestone}
"Hi {first name}, {agency} sets up {platform} for {customer type}. We build {product}, which those clients tend to need right after {milestone}. I am not asking you to resell anything. Would a simple swap help: we send you clients who need {their service}, and you mention us when {trigger}? I can send the first referral before you decide."
When to use it: an agency, consultant or complementary tool serves your buyers at a different moment, and you want introductions, not a purchase.
Why it works: it rules out the obvious worry, a reseller pitch, and offers to give first. The comparison of lead sources weighs partners against other channels.
How should you answer the replies these templates get?
A template only opens the conversation. These four replies come up often; answer them quickly, briefly and honestly, ending with one question. The outbound sales strategy guide covers the other reply types.
"Send me more information."
"Here is a one-page overview: {link}. For a team like yours, the part that matters is {section}. So I do not send the wrong thing next: is {problem A} or {problem B} the bigger issue right now?" An information request is often a polite exit; a question about their situation reopens the conversation.
"We already use {competitor}."
"Makes sense. Is it working well enough that you would not look at anything else before your renewal? If so, I will leave it there. If {known gap} comes up, that is the part we do differently." Do not argue: accept a yes and leave one specific difference behind.
"How did you get my email?"
"Fair question. I read your post on {platform} on {date} about {topic}, and found your work address through {source}. I will not write again unless you want me to: reply stop and I will remove you from every list." Name the source plainly. For people in the EU, Article 14 of the GDPR requires you to say where you got their data, at the latest in your first message.
"Not now. Maybe next quarter."
"Thanks, I will check back in {month}. So that note is useful: what would have to change for this to move up your list?" The answer tells you which event to watch for, and when it happens, your next email has its trigger.
How should you personalize a cold email template?
AI can draft these at scale if it works from the real event. That is how Startories writes: each draft references the signal that produced the lead, with a link to the original, and you can approve it before it is sent. See the AI SDR page for the full workflow. Whether a person or software fills the template, the same rules apply:
- Personalize the reason, not the compliment. The first line names a real event with a place or a date.
- Use one personal fact per email. Three read as surveillance; one reads as attention.
- Check every fact. A wrong funding amount or product name ends the conversation.
- Match the ask to the trigger: a demo for active shoppers, a useful resource for everyone else.
- Write the way you talk, and keep subject lines about their situation, not your product.
- Never fake familiarity: no false "Re:", no invented mutual contacts, no "as promised".
What does every cold email need to stay compliant and deliverable?
In the US, the FTC's CAN-SPAM guide applies to business email too: accurate sender information, a subject line that does not deceive, your valid postal address, and a clear opt-out that you honor within 10 business days.
In the EU, B2B prospecting usually relies on legitimate interest under GDPR. That means weighing your interest against the recipient's, collecting only what you need, telling people where you got their data, and stopping when they object. National rules on electronic marketing vary, so check each country you target.
Mailbox providers add their own layer: Google's sender guidelines ask for authentication, a spam rate under 0.3% and one-click unsubscribe from bulk senders. The cold email deliverability guide covers the setup step by step.
How to start using these templates
Pick the two triggers that fit your product best, adapt the matching templates, and run each on 100 to 200 contacts before you judge it. Track positive replies and meetings per template, keep the winner and rewrite the loser. The outbound sales strategy guide shows how to build a full sequence around them.
Finding the triggers is the slow part. Startories watches Reddit, X, Product Hunt, directories and niche search results for these signals, verifies the decision-maker and drafts the email from the event; read more about signal-based outbound or see plans and pricing.
Frequently asked questions
How long should a cold email be?
Short enough to read in under 30 seconds, usually 50 to 120 words: one trigger, one problem, one question. Anything longer belongs in a follow-up or behind a link the person can choose to open.
What makes a good cold email subject line?
Three to six words about the recipient's situation, written like an internal email, such as "your {role} opening" or "exports in {competitor}". Avoid fake "Re:" or "Fwd:" prefixes, clickbait and anything that misrepresents what the email says.
Should I use the same template for everyone?
Use the same structure, not the same email. Fill each template with a real trigger and checked facts for each recipient. Identical bodies sent to hundreds of people look automated to readers and to spam filters.
How many follow-ups should I send after a cold email?
Two to four follow-ups over two to three weeks is a reasonable range. Each one should add something new, and the sequence should stop as soon as the person replies or asks you to stop.
Can AI write personalized cold emails?
Yes, if it works from a real, specific event and someone checks the facts. Given only a name and a website, AI tends to produce generic compliments that readers recognize and ignore.