A sales prospecting email template is a first-contact message shaped by the prospecting method behind it: list-based prospecting needs a short, segment-level email sent at volume; account-based needs a researched, account-specific one; inbound-assisted follows a signal the prospect gave; event-based uses shared context. The method decides length, personalisation and list rules, which is why one template does not fit all four. On verified lists, teams report 2 to 5% replies for list-based and 10 to 20% for inbound-assisted, with account-based and event-based between.
| Method | List size | Research per contact | Email length | Reply range (industry) | List rule |
|---|---|---|---|---|---|
| List-based | 500 to 5,000 | One line, from the segment | Under 70 words | 2 to 5% | Verified in bulk the day before; built per segment |
| Account-based | 20 to 100 accounts | 30 to 60 minutes per account | 90 to 130 words | 6 to 12% | Every address found and verified individually |
| Inbound-assisted | Whatever the funnel gives | From the signal itself | 50 to 80 words | 10 to 20% | Validated at the form; re-verified if older than 90 days |
| Event-based | 100 to 500 per event | From the event | 60 to 100 words | 8 to 18% | Verified on day one, before the five-day window closes |
Subject: {problem} for {segment}
Hi {first_name},
{segment_fact}, which usually means {problem} is being handled by hand at {company}.
{sender_company} does that part: {outcome_one_line}. If it is on the list this quarter, 15 minutes would show whether it fits. If not, a one-word reply closes it.
{sender_name}
If this is not relevant, reply "no" and I will not write again.
{segment_fact} One fact true of the whole segment: size, stack, stage{segment} The segment in two or three wordsSubject: {account_initiative} at {company}
Hi {first_name},
{company}'s {account_initiative} came up in {source_one} and again in {source_two}, so it looks like the priority for {timeframe}.
The part of that initiative we have seen slow other {company_type}s down is {specific_obstacle}. {sender_company} removes it: {outcome}; {similar_account} did it as part of a similar initiative and {result}.
I have written up how it would apply to {company} in a one-page note. I can send it, or walk through it in 20 minutes with {colleague_name} if that is easier.
{sender_name}
{sender_title}, {sender_company}
If this is not relevant, reply "no" and I will not write again.
{source_one} / {source_two} Two places the initiative was visible: a post, a job ad, a filing, an interview{colleague_name} A second stakeholder you have identified{specific_obstacle} The obstacle, namedSubject: Your {signal} on {date}
Hi {first_name},
You {signal_description} on {date}. The question that usually sits behind that is {underlying_question}.
The two-line answer: {two_line_answer}. If it helps to apply it to {company}'s setup, I can do that on a call or in a short note; which would you prefer?
{sender_name}
If this is not relevant, reply "no" and I will not write again.
{signal_description} Downloaded the guide, ran a free check, visited pricing twice{underlying_question} What people who do that are usually trying to work out{two_line_answer} An answer that stands on its ownSubject: {event_name}: {theme}
Hi {first_name},
We were both at {event_name}. {speaker}'s point about {specific_point} is the problem {sender_company} works on for {customer_type}.
If {specific_point} is on your list, 15 minutes would tell us whether what we did for {similar_company} applies at {company}. If not, no follow-up beyond one note next week.
{sender_name}
If this is not relevant, reply "no" and I will not write again.
{specific_point} A real point from a real session{theme} The event theme in the organiser's wordsA 2,000-row segment sent unverified is 290 bounces at the 2026 business rate and a throttled domain by day two. Bulk-verify the day before, send to confirmed-valid only.
Twenty accounts, an hour of research each, and a bounce to the champion is visible failure. Verify each address individually; treat catch-all results as unconfirmed and route them to LinkedIn.
The signal came with an address the prospect typed. The real-time API at the form keeps typos and throwaways out, so the follow-through reaches a mailbox.
Five working days. Verification on day one, so badge-scan typos and personal addresses are handled before the context fades.
| Method | Lead metric | Healthy range (industry) |
|---|---|---|
| List-based | Replies per 100 delivered | 2 to 5% |
| Account-based | Accounts with a reply from any stakeholder | 25 to 40% |
| Inbound-assisted | Replies within 48 hours of the signal | 10 to 20% |
| Event-based | Replies within the five-day window | 8 to 18% |
| All methods | Bounce rate | Under 1% on verified lists |
| All methods | Complaint rate | Under 0.3% |
Subject: The EU expansion at Kestrel Freight
Hi Dana,
Kestrel's EU expansion came up in the Series B announcement and again in the three Berlin sales roles posted last month, so it looks like the priority for the next two quarters.
The part of that initiative we have seen slow other logistics SaaS down is the German list: t-online addresses return unknown 41% of the time, and sequences stall on them. We route those rows to phone and LinkedIn and keep the cold sequence on confirmed addresses;
I have written up how it would apply to Kestrel in a one-page note. I can send it, or walk through it in 20 minutes with your RevOps lead if that is easier.
{your_name}
{your_company}
Not relevant? Reply "no" and I will stop.
A 120-word account email sent at volume is unread; a 60-word list email to a target account is ignored.
If the first line could be sent to anyone, the hour was wasted.
Twenty accounts need each address confirmed individually and catch-all results routed elsewhere.
Reply within 48 hours; the signal fades faster than a cold list.
Trigger, stage and role templates
The methods behind these four templates
Eight methods ranked by return
Four openers for list-based volume
The event method in depth
The stack behind inbound-assisted prospecting
List-based emails are short, segment-level and sent at volume to a bulk-verified list; replies run 2 to 5%. Account-based emails are researched per account, name a specific initiative and obstacle, and go to individually verified addresses; replies run 6 to 12% and a quarter or more of accounts respond.
Inbound-assisted, 10 to 20%, because the prospect gave a signal first. Event-based follows at 8 to 18% inside the five-day window. Both depend on the address being valid: validate at the form, verify event lists on day one.
It depends on the method: one segment-level line for list-based, 30 to 60 minutes per account for account-based, the signal itself for inbound, the event for event-based. Research that does not change the email is wasted.
No. Length, personalisation and list rules all differ. A 120-word account-based email sent to 2,000 people is unread; a 60-word list-based email sent to a target account is ignored. Match the template to the method.
Because the cost of a bounce differs. A bulk list needs bulk verification to protect the domain; an account-based list needs each address confirmed because one bounce to a champion is visible; inbound lists need validation at the form; event lists need verification before the window closes.
Bulk jobs for list-based, single checks for account-based, the real-time API for inbound, day-one verification for events. 100 free checks a month, unknowns refunded.
Ayoub built BounceZero's 5-stage validation pipeline, its dedicated BGP-announced IP infrastructure, and the Patroni HA PostgreSQL cluster behind every verification. Previously built high-volume email delivery infrastructure. Trained at 1337 Benguerir (École 42 network, 2019). Open-source: bgp_analyzer.
Templates by trigger and stage, each with the deliverability rules that apply
A financial services cold email template built for compliance
A real estate agent cold email template for prospecting owners, landlords and local businesses
A warm introduction email template for the two warm moments in outreach
A meeting request email template for cold and warm threads
Twenty-four cold outreach email templates organised by trigger (funding, hiring, new role, tech change),...
A funding round cold email template with two variants and merge fields
Continue through related topics