Cold email templates that get replies (and why they work)
Templates are useful right up until everyone uses the same one. So here are five that still work — and, more importantly, the anatomy underneath, so you can build your own that actually sounds like you.
By Thomas Maitre, Founder, Otto
Cold email templates have a short shelf life. The moment one starts working, it gets screenshotted, swiped, and sent by ten thousand people — and the inbox learns to ignore it. So this isn't really a list of scripts to copy. It's five structures that still work, with the reasoning underneath each, so you can write your own version that sounds like a person and not a template.
One rule before we start: a good cold email is short, it's about the reader, and it asks for one easy thing. Three to five sentences. If yours needs a scrollbar, it's already too long.
1. The observation, problem, ask
Subject: Quick thought on {{company}}
Hi {{first name}}, Noticed {{specific, real observation about their business}} — usually that means {{the problem it implies}}. We help {{similar companies}} {{outcome}} without {{the painful part}}. Worth a quick look? {{your name}}
The whole email turns on the first line. A real observation — something you actually noticed, not a merge tag — earns the next sentence. The problem line proves you understand their world. The ask is small. This is the workhorse; master it before the rest.
2. The trigger-event email
Subject: Congrats on {{the trigger}}
Hi {{first name}}, Saw {{the funding / hire / launch / expansion}} — congrats. Usually right after {{that event}}, teams start running into {{the predictable next problem}}. That's exactly what we help with. Open to comparing notes next week? {{your name}}
Timing beats cleverness. A new round, a new VP, a new market — each one creates a predictable problem you can speak to. The trigger gives you a non-creepy reason to be in their inbox today, which is half the battle.
3. The short referral ask
Subject: Right person?
Hi {{first name}}, We help {{role}} at {{company type}} {{outcome}}. If that's not you, could you point me to whoever owns {{the area}}? Thanks either way. {{your name}}
Sometimes you're emailing the wrong person on purpose. This one is disarmingly short, makes a tiny ask, and routes you to the right desk. It works because it's easy to answer in five seconds — even with a no.
4. The "quick question"
Subject: Question about {{their process}}
Hi {{first name}}, How is your team handling {{specific process}} right now? Asking because we've been helping {{similar companies}} {{outcome}}, and the approach only really matters if {{condition}}. {{your name}}
A genuine question invites a reply more naturally than a pitch does. The trap is the fake question — the one that's obviously a setup. Make it real, make it specific, and actually be ready to care about the answer.
5. The follow-up that adds something
Subject: re: {{previous subject}}
Hi {{first name}}, Following up — but I'll make it worth it: {{a relevant proof point, short case, or useful resource}}. Still happy to {{the small ask}} if it's useful. If not, I'll get out of your inbox. {{your name}}
Most replies come from follow-ups — but only if they add something. "Just bumping this" adds nothing and trains people to ignore you. A follow-up that brings a proof point or a useful nugget earns its place, and the graceful exit at the end actually makes people more likely to respond.
The anatomy underneath all five
Strip the specifics and every one of these has the same skeleton:
- An opening line that proves relevance — why you, why now — instead of introducing yourself.
- A middle that's about their world: a problem, a trigger, or a question they recognize.
- One low-friction ask. "Worth a look?" converts better than "book a 30-minute demo."
- A length you can read in the preview pane without scrolling.
- A human sign-off — no nine-line signature with a banner.
Why tokens aren't personalization
Dropping a first-name token into a generic email fools no one — everybody knows what a mail merge looks like now. Real personalization is a real observation: a line that could only have been written to this person, about their company, today. That's the part that's hard to do at scale, and it's exactly the part that decides whether your email reads as "a person wrote this" or "a robot did." If you remember one thing here, remember that specificity beats tokens every time.
Use these as scaffolding, then make them yours — your voice, your proof, your actual observations. And once they're landing, make sure they're landing in the inbox at all; a perfect template in the spam folder is still silence. (More on that in the deliverability guide, and on diagnosing weak campaigns in the four ways outbound goes wrong.)