A cold email template that gets replies has four beats: a specific reason you're writing, one line that is about them, a single ask, and a short sign-off — under ~150 words. The template is not a script you paste and forget; it is a skeleton that forces you to fill in the one thing that makes cold email work: a reason specific to the person you're emailing. A BDR sends dozens of these a day, and the difference between a template that earns replies and one that earns spam-folder status is almost never the words — it's whether the blanks are filled with real research.
The four-beat skeleton every template shares
Read any cold email that gets a reply and you'll find the same shape, whatever the words:
Beat 1 — The reason (subject + first line). Specific enough that they know you actually looked. Not "quick question" — "saw you took over [region]."
Beat 2 — About them, not you. One line connecting their situation to a real problem or goal.
Beat 3 — Why you, in one breath. A line of context or proof. Cuttable if the email is getting long.
Beat 4 — One ask, said plainly. A 10-minute slot, a one-line answer, or a pointer — never a menu.
Keep every beat short. If the whole email can't be read in the time it takes to scroll a phone screen, tighten it. Cold email earns a reply by being easy to answer, not by being impressive.
How to write one: the 60-word rule
Think of the email as five short lines, not a paragraph. Each line has a job and a rough word budget:
Line 1 — Subject (≈6 words). Earn the open with specificity or curiosity — the full set of mechanisms is in cold email subject lines.
Line 2 — The reason (≈12 words). One specific, true thing: a trigger, their role, a change at their company.
Line 3 — About them (≈15 words). Connect that reason to a problem or goal they likely have. This is the line that makes it relevant.
Line 4 — Why you (≈12 words). One breath of credibility or context. The cuttable line.
Line 5 — The ask + sign-off (≈15 words). Exactly one, low-friction ask.
The 60-word rule: aim for roughly 60 words of body. It's a discipline, not a law — a technical message may earn 120, and the templates below sit at the longer end because they carry a proof line. 150 words is the ceiling. If you can't say it in 60, you haven't found the real reason you're writing yet; trimming forces the filler out and keeps the ask visible.
Here is a full email that fits the budget:
Subject: [Company]'s [region] expansion
Hi Dana — saw you're leading the [region] expansion. Most heads of ops there end up stretched on onboarding.
We help ops teams like yours [outcome], and I'd love to share how.
Worth 10 minutes next week?
Count it: roughly 60 words, five lines, one ask. Nothing wasted, nothing missing.
Every extra sentence has a cost: it asks the reader to spend more attention deciding whether to reply. Your email competes with a full inbox, and the reader's decision is binary — reply or delete — not "how good is this." If you find yourself defending a long email, you are usually defending a reason that isn't specific enough yet, not protecting necessary detail. Specificity comes from research done before you write, not from adjectives inside the draft.
The templates — here is the asset
Copy these, fill the brackets, and keep every blank specific to the person:
Template 1 — the research opener (your default).
Subject: [their company] and [one real change]
Hi [First name] — I saw [specific, true thing about them: recent role, funding, hire, expansion]. Most [role]s I talk to at [company stage] are [dealing with X] right now.
I work with [segment] on [what you do]. [Your proof line.]
Worth 10 minutes to see if it's relevant? [day/time]
Template 2 — the trigger email (they did something).
Subject: congrats on [the trigger]
Hi [First name] — congrats on [funding/role/launch]. That usually means [the problem you solve] gets real fast.
[Your company] helps [same segment] reach [outcome]. Thought it was worth one note before you're swamped.
Open to a 10-minute call next week?
Template 3 — the warm-angle email (they know someone).
Subject: [mutual name] said to reach out
Hi [First name] — [mutual name] at [company] and I were talking, and they mentioned you're [the situation]. Thought it might be worth a quick note.
We help [segment] [do X], and a couple of their people use us.
Mind if I send a two-line summary? No call required.
Template 4 — the resource drop (a tiny ask, real value).
Subject: [one relevant thing] for your [area]
Hi [First name] — came across [specific report/link/idea relevant to their role]. Thought of your work on [area]; it might save you [the effort].
Sharing in case it's useful. If [their problem] is on your plate, happy to point you to how we handle it.
Template 5 — the anti-spam nudge (reopening a sent email).
Subject: re: [original subject]
Hi [First name] — bumping this once in case it got buried. If it's a no, no problem — one word and I'll leave it.
If it's timing, I'm happy to check back in [month].
Line by line, the pattern is identical: be specific, be about them, earn the right to ask, and ask once. The five templates differ only in surface details — the mechanism is always the same four beats.
Why the fill-in-the-blank beats the pretty pitch
The failure mode of cold email is not weak grammar — it's a template that reads like it was sent to 400 people. Every "Hi there, we're a leading provider…" line is the template announcing itself as spam. When you fill the blanks with a real trigger, a real name from public research, and a real ask, the same skeleton stops looking like a template. That specificity is what separates outreach from spam — and it's the whole game.
Send it like a human
After you hit send, the next email in the conversation matters as much as the first — a cold email is the opening touch in a sequence, not a one-shot. But before anyone reads the follow-up, the subject line decides whether any of it gets read. That's the next piece: cold email subject lines that earn the open.