How to write cold emails that get replies

Most cold emails fail before the sender writes them. The target is too broad, the reason for contacting them is thin, and the writer hopes a clever subject line will fix it.

If you’re wondering how to write cold emails that get replies, make the message about one specific problem for one relevant person. Give them a reason to care now, then ask a question they can answer in one line.

That’s the whole job of the first email. Not closing the deal. Not booking a demo at any cost. Starting a sensible conversation.

How to write cold emails that get replies

Start with the account, not a template.

Choose a company type, a role, a size range, and a trigger. The trigger might be a new executive, a funding round, a public hiring plan, a product launch, or a technology change. Then work out what that event could create operationally.

Say you sell outbound support to a 60-person B2B software company. The company hired a VP of Sales and posted four SDR roles in the past month. That’s enough of a reason to write:

Saw you’re building the outbound team after hiring your VP of Sales. Teams at this stage often struggle to keep list quality and messaging consistent while new SDRs ramp. Is improving reply rates a priority this quarter?

Notice what’s missing. There’s no product tour, ten-feature pitch, case study, or calendar link. The email points at a situation the buyer may already recognize.

A good SDR workflow does this account work before writing copy. Most teams get that backwards. They pull a broad list, add first-name personalization, and expect the email to do the targeting. It won’t.

Find a real reason to contact the person

A payments company selling reconciliation software might target finance leaders at businesses processing more than $10 million per month. A new payment processor, regional expansion, or audit finding could signal that reconciliation work is about to become painful.

The email should mention that event. “Improve financial efficiency” says nothing.

For instance:

Saw that your team is moving payment processing to Adyen across the US and Canada. That usually creates a messy period for exception handling and reconciliation. Are those issues owned by finance, or by operations, at this point?

You don’t need to write a biography of the prospect. One credible detail is usually enough. A Series B followed by 12 account executive job postings. A new VP of Revenue who started three weeks ago. Two new distribution centers. A role dedicated to managing a processor integration.

Then connect the trigger to a plausible problem without pretending you know what happens inside the company. Use phrases like “teams often see,” “I’m curious whether,” or “this can create.”

The point isn’t to sound certain. It’s to offer a useful hypothesis the prospect can confirm or correct.

Subject lines should explain the email

Keep the subject plain and tied to the reason you’re writing. “Idea for your SDR ramp” is fine. So is “After the new processor rollout” or “Question about enterprise onboarding.”

“One question” is usually lazy. “URGENT: amazing opportunity inside” is worse. Fake urgency and fake reply threads make the sender look untrustworthy.

A subject line only needs to earn the open. It doesn’t need to carry the sale. If you write “After the new processor rollout,” the body should immediately explain what you noticed and why it might matter. Curiosity without relevance is clickbait.

Keep the body short, but not empty

Aim for roughly 75 to 150 words. Shorter is often better for a senior buyer, but a technical reader may tolerate more if the message contains a detail they can use.

A practical body has four parts: the trigger, the likely problem, relevant proof if you have it, and one question.

Here’s an example for a 90-person SaaS company that just raised a Series B:

Hi Maya,

Saw that Northstar is hiring its first enterprise sales team after the Series B. That often creates a gap between the messaging founders used to win early accounts and the material new reps need for larger ones.

We helped a similar 70-person SaaS company rebuild its account lists and outbound messaging. Qualified reply rates went from 2.1% to 5.4% in six weeks.

Is enterprise outbound already covered, or is that still being built?

Best,
Alex

The proof works because it’s specific. “We help companies improve sales productivity” doesn’t tell the reader anything. A result from a 12-person agency also won’t mean much to a 500-person fintech unless the sales motion and buyer are genuinely similar.

And don’t claim the prospect definitely has a problem. You’ve seen a public signal. That’s all.

Personalization should change the message

Adding a first name isn’t personalization. Mentioning the company’s logo or copying a recent LinkedIn post isn’t either.

Useful personalization changes why you’re contacting this company, this person, at this moment.

Weak:

Loved your website. We help companies improve sales productivity.

Stronger:

Your team is hiring three implementation managers while launching in Germany. That combination can create a backlog in customer handoffs, especially when sales promises vary by region. Is that showing up for you?

The second version could still be wrong. That’s okay. The prospect has an easy way to correct it.

Use business signals, not forced personal details. A prospect’s post about their dog has nothing to do with a message about SOC 2 readiness. A new executive, audit result, hiring plan, processor change, or product launch does.

My opinion: teams overinvest in personalization that proves the sender did research and underinvest in relevance that helps the reader. Nobody cares that you found their podcast episode if the email still doesn’t explain why you’re writing.

Ask for a reply, not a meeting

A cold email CTA should require very little work. “Is this a priority for your team this quarter?” works. “Are you handling that internally?” works. “Would it be useful if I sent the checklist?” can work when the checklist is actually useful.

The common mistake is asking the reader to accept your diagnosis, trust your company, find time, and enter a sales process in one move:

Are you available Tuesday or Wednesday for a 30-minute demo so I can walk you through our platform?

That’s too much from a stranger.

A reply is a smaller commitment than a meeting. Ask whether the problem exists first. If the prospect confirms it, suggest a call. Usually skip the meeting link in the first email too. Make the reply easy.

Follow-ups need a new reason

A non-reply doesn’t tell you much. The email may have been irrelevant, badly timed, buried, or never delivered.

Send two or three follow-ups, but don’t write “just bumping this up” three times. Add a new angle. Share a short example from a similar account, clarify the problem, offer a useful checklist, or close the loop politely.

For the payments example, a second email could say:

One detail I missed: the teams we see struggle most after a processor change aren’t usually finance. It’s operations, because exceptions start living in spreadsheets. Is that happening at {{Company}}, or is the handoff already tidy?

That gives the prospect something to react to. It’s part of cold outreach, not an excuse to repeat the same pitch five times.

Track positive replies, total replies, meetings booked, and qualified opportunities separately. A 12% reply rate that produces no useful conversations isn’t a winning campaign. Also, don’t trust impressive template benchmarks without checking what counts as a response. Some include negative replies and automated messages.

Deliverability can erase good copy

A sharp email still fails if it lands in spam.

Set up SPF, DKIM, and DMARC for the sending domain. Verify addresses before sending. Keep volume sensible, especially on a newer domain. One inbox sending 20 to 50 targeted emails per day is safer than blasting hundreds from one account.

Watch bounces, spam complaints, positive replies, and domain health. Open rate is noisy. Don’t make it your main signal.

Then test one thing at a time. Change the subject line while keeping the offer the same. Or change the opening trigger while keeping the CTA unchanged. If you change five things together, you won’t know what caused the result.

The best email isn’t built from magic words. It’s a clear account hypothesis, a credible reason now, one likely problem, and an easy question. Write that first. Then cut anything the reader doesn’t need.