10 cold email templates that get replies (with the structure behind each one)

1. Hook (line 1) — a concrete reason this email exists right now. Not "I hope this finds you well".
2. Value (lines 2–4) — what you do or what you've seen, in their language, with one quantified detail if you can.
3. Ask (line 5) — one low-friction question. Not "15 min call this week". A real question they can answer with yes or no.

Maximum 120 words. Maximum one link. No images. Sent from a mailbox that's warmed up. (See the deliverability guide for the why.)

Subject: Your post on {{topic}}

Hi {{first_name}},

Saw your post on {{topic}} — particularly the bit about {{specific_detail}}. We just shipped something close to what you described.

{{your_company}} is a {{one_sentence_what_you_do}}. Two teams using it for what you wrote about: {{example_1}} and {{example_2}}.

Worth a 10-line summary by email?

— {{your_name}}

Works when you have a real reason to write — a post, a podcast, a recent announcement. Don't fake it; receivers notice.

Subject: {{specific_outcome}} for {{company}}

Hi {{first_name}},

Most {{segment}} teams spend {{N}} hours a week on {{task}}. We've cut it to {{less_N}} for {{customer_1}} and {{customer_2}}.

The mechanism is dull — {{one_line_how}}. The outcome is what matters: {{quantified_win}}.

Should I send you the 90-second walkthrough we used to close those?

— {{your_name}}

Strong for problem-aware segments. Don't make up the numbers; if you don't have customers yet, use the "skeptical question" variant below instead.

Subject: Quick {{topic}} question

{{first_name}},

How do you currently handle {{specific_pain}}?

Asking because we're building something for {{segment}} teams that {{one_line_value}}. Not sure if it'd land for {{company}} — wanted to hear how you do it today before pitching anything.

— {{your_name}}

Works for early-stage products. The cheat code is that you're asking a real question, not selling. Replies are high-quality because the recipient self-qualifies.

Subject: Thinking about {{company}}'s {{specific_thing}}

Hi {{first_name}},

I was looking at {{company}}'s {{specific_thing}} and noticed {{observation}}.

We help {{segment}} with {{adjacent_problem}}; one pattern we see a lot is {{related_insight}}.

If that resonates, I'd love to compare notes — happy to share what we've seen elsewhere even if there's no fit.

— {{your_name}}

Only works if the observation is real. Generic "saw your website, looks great" is worse than not sending at all.

Subject: Re: {{previous_subject}}

{{first_name}},

Bumping this in case the timing was wrong.

One thing I forgot to mention: {{new_angle_not_in_first_email}}. Specifically — {{tangible_example}}.

Worth a 10-line reply?

— {{your_name}}

Two rules: add one new piece of information they didn't see in the first message (otherwise you're just nagging), and never send more than two follow-ups. Three is when complaint rates spike.

Subject: Right person for {{topic}}?

Hi {{first_name}},

Quick one — who's the right person at {{company}} for {{topic}}? I have something I'd like to share, but want to send it to the person who'd actually care.

Happy to send it your way too if you'd rather it route via you.

— {{your_name}}

Specifically for when LinkedIn says someone is in "Growth" but you don't know if they handle the topic. Lets the recipient redirect you without feeling pitched.

Subject: Built this for {{segment}}

{{first_name}},

We talked to ~50 {{segment}} founders about {{pain}}. The pattern: {{shared_insight}}.

We built {{your_product}} as a direct response. The 30-second version: {{one_line_value}}.

If it sounds remotely close to what you'd want, I can send the demo link.

— {{your_name}}

Works post-product-market-fit, when you have real conversation data behind the claim. Don't use this template if you haven't actually talked to those 50 people — receivers can tell.

Subject: {{single_word_topic}}

{{first_name}} — when {{company}} {{does_action}}, do you {{specific_question_with_two_options}}?

Asking because we've seen both, and it turns out it predicts {{outcome}}. Curious which side {{company}} sits on.

— {{your_name}}

Very low-volume technique. Single-word subject + a real curiosity question. Pay-off: extremely high open rate, conversational replies that don't feel like a sales loop. Don't scale this past 50/day per mailbox — the receiver-side patterns matter.

Subject: {{mutual_name}} said to reach out

Hi {{first_name}},

{{mutual_name}} mentioned you'd be the right person to talk to about {{topic}}. We help {{segment}} with {{value}}.

Specifically: {{one_sentence_outcome}} — {{mutual}} thought there might be overlap.

Worth a quick reply?

— {{your_name}}

Use only when the mutual is real and the recipient knows them. Faking a referral is the single fastest way to a complaint.

Subject: Closing the loop on {{topic}}

{{first_name}},

I've reached out a couple of times — I'll stop after this one.

If timing or fit isn't right, no worries. If you'd like me to circle back in {{N}} months, just reply with "later" and I'll set a reminder.

— {{your_name}}

Sometimes pulls a reply, sometimes doesn't. The real reason to send it is the explicit close — it gives the recipient a clean exit and reduces the chance they mark you as spam later.

• Rewrite, don't copy. The structure is the template; the words have to be yours. Receivers detect mass-sent wording quickly.
• A/B-test subject lines first, body second. Subject moves open rate most.
• Cut, don't add. When in doubt, delete a sentence. 100 words beats 200.
• One ask, never two. If you ask for two things, you get neither.