How to Write a Cold Email That Gets Replies
A cold email that works does three things: earns the open, proves you did your homework, and asks for something small. Here is the structure, the research shortcuts, why a demo link beats a meeting ask, and templates you can adapt.
A cold email gets a reply when it earns the open, proves in the first two lines that it was written for that exact person, and asks for something small. The structure is simple: a relevance line that references something specific about them or their company, one or two lines naming a problem and what you do about it, and a low-commitment ask — a yes/no question or a two-minute look at something, not 30 minutes on a calendar. Keep it to three or four sentences. Follow up two or three times, each adding new information. And instead of asking a stranger for a meeting, give them a demo link they can explore on their own time — it converts the skeptical reader who would never book a call.
The structure
1. The relevance line (the whole email lives or dies here)
The first sentence has to make the reader think "this isn't a blast." Options, roughly in order of strength:
- A specific observation about their product or site ("Your pricing page has a 'book a demo' button but no way to actually see the product first — that's the gap I want to talk about").
- A trigger event (a launch, a hire, a funding round, a job posting).
- A shared connection or context.
Avoid "I hope this email finds you well" and "I'm reaching out because." Those are the sound of a template.
2. Problem + what you do (one or two lines)
Name the problem in their terms, then say what you do about it in plain language. No adjectives, no "revolutionary." One sentence each.
3. The small ask
Not "do you have 30 minutes." Instead:
- A yes/no question: "Is getting more people to try the product before a call something you're working on this quarter?"
- Something to look at: "Here's a two-minute walkthrough of how that works — no call needed: [link]."
The small ask is what separates a 2% reply rate from a 10% one.
Research without spending an hour per prospect
You need enough to write the relevance line, not a dossier:
- The homepage and pricing page. Two minutes. Usually enough to find a specific gap or angle.
- Recent LinkedIn activity for the person — a post, a comment, a job change.
- One trigger signal — news, hiring, a product update.
If you can't find anything specific in five minutes, the prospect probably isn't a good enough fit to email.
Why a demo link beats a meeting ask
Most people you cold-email will never book a call with a stranger. But a fair number will click a link that promises a two-minute look with no commitment. An interactive demo is the ideal thing to link: it shows the product working, the reader controls the pace, and it costs them nothing:
It also does the qualifying for you. Someone who watches the whole demo and replies is a warmer lead than someone who booked a call out of politeness.
Follow-ups
Two or three, spaced out, each with a reason to exist:
- +3 days: a relevant proof point — a similar company, a result.
- +5 days: address the likely objection, or share the demo link if you didn't in email one.
- +1 week: a breakup line ("I'll stop here — if the timing's off, no worries").
Never send "just bumping this to the top of your inbox."
Send from a real person's address, not "team@" or "sales@". Keep the email plain text with at most one link. Both help deliverability and both make it read like a person wrote it.
Templates
Trigger-based:
Subject: Your new [role] hire
Saw you just brought on a [role] — usually means [relevant initiative] is ramping up.
We help [type of team] [outcome] by [one line]. [Similar company] used it to [result].
Worth a two-minute look? Here's the exact flow: [demo link]. No call needed.
Observation-based:
Subject: The gap on your pricing page
Your pricing page sends people to "book a demo" but there's no way to see the product first. That filters out everyone not ready to talk to sales yet.
We fix that with an embedded interactive demo — here's what one looks like: [demo link].
If closing that gap is on your list this quarter, happy to share how a few teams have done it.
For the demo you're linking, see how to record a sales demo and the product demo email. For the follow-up cadence, see the sales follow-up email; and for the strategy of leading with a demo, see demo-first marketing.
Frequently asked questions
What makes a cold email get a reply?
Relevance and a low ask. The email has to show, in the first two lines, that it was written for that specific person and company, and it has to ask for something small — a yes/no question, a two-minute look at something — rather than 30 minutes on a calendar. Generic templates and meeting requests get ignored; specific observations and easy next steps get answered.
How long should a cold email be?
Short enough to read on a phone in under 15 seconds — three or four sentences. One opening line that proves relevance, one or two lines on the problem and what you do about it, one small ask. Anything longer gets skimmed and deleted.
Should a cold email ask for a meeting?
Not in the first email. A meeting is a big commitment for someone who does not know you. Ask a qualifying question, or offer something they can look at on their own time — a short demo, a relevant example. Save the meeting ask for after they have replied and shown interest.
How many cold emails should I send before giving up?
Two or three well-spaced follow-ups after the first, each adding something new rather than repeating. Most replies to a cold sequence come after the first email, so one-and-done leaves responses on the table, but sending the same message four times damages your sender reputation and the relationship.