DEV Community

Cover image for How Do I Write a Cold Email That Gets Replies? (Structure, Before/After and a Pre-Send Test)
Mohammed Ali Chherawalla
Mohammed Ali Chherawalla

Posted on Originally published at docs.rightsuite.co

How Do I Write a Cold Email That Gets Replies? (Structure, Before/After and a Pre-Send Test)

Write the pain line first: one sentence naming the prospect's problem in their own words. Then add an opener that proves you looked at them, one line tying your product to the outcome they want, and a question they can answer in seconds. Keep it phone-length, and test it on simulated buyers before your list ever sees it.

RightEngagement is the test. Paste your draft, describe who you're sending to, and watch simulated buyers in that segment open, reply or delete it, with the exact line that made them decide.

Test your cold email with RightEngagement

Who this is for

You're writing cold email to B2B buyers who've never heard of you. You might be a founder doing your own outbound, or you have a sequence that's getting opens and no replies. This guide is about the single email. If you're building the follow-ups, read how to build a B2B outreach sequence next.

What structure gets replies?

Four parts, written in this order. The order you write them matters more than the order they appear.

1. Write the pain line first

One sentence that describes the problem the way your prospect would say it to a colleague. "We send 200 emails a week and book two calls" is their language. "Optimise outbound efficiency" is yours.

Find their words in reviews of competitors, community threads, job posts and your own call notes. If you can't write this sentence clearly, stop. The email isn't ready, and no subject line will save it.

2. Open with something true about them

The first line has to prove you looked at this person or company specifically. A job post, a launch, a hiring push, a change on their pricing page. "I came across your profile" proves nothing. The test: could a mail merge have written this line? If yes, rewrite it.

Tie the opener to the pain line. A random compliment followed by a pitch feels like two different emails stapled together.

3. One line connecting you to the outcome

Skip the feature list and the company intro. Say what changes for them. "We help [type of company] get [outcome] without [the part they hate]" is a useful shape to start from, as long as you fill it with specifics.

4. Ask a small question

Make the ask answerable in a few seconds. "Is this on your radar this quarter?" or "Worth sending over the teardown?" A reply to a small question opens a conversation. The meeting comes after.

A before and after

Here's an illustrative example for a founder selling an onboarding-email tool to seed-stage SaaS companies.

Before

Subject: Quick question

Hi Sam, I hope this finds you well. I'm the founder of Acme Onboarding, an AI-powered platform that helps SaaS companies improve user onboarding with automated, personalised email flows. We integrate with all major tools and our customers love us. I'd love to set up 30 minutes to show you a demo. Here's my calendar link.

What goes wrong: it opens with the sender, describes features, makes an unsupported claim ("customers love us"), and asks a stranger for 30 minutes. Nothing in it is about Sam.

After

Subject: Your trial emails after day 3

Hi Sam, I signed up for a Northwind trial last week. After the welcome email on day 1, nothing arrived until the "trial ending" email on day 14.

That gap is usually where trial users drift off before they've set anything up.

We write and run the day 2 to day 10 emails for seed-stage SaaS teams, triggered by what each user has or hasn't done.

Want me to send the three emails I'd add first?

What changed: the opener is a true, specific observation. The pain line names a problem Sam can check in five minutes. The product gets one line. The ask is a yes/no question that costs Sam nothing.

Symptom, check, fix

Symptom Check Fix
Opens, no replies Is the first line about them or about you? Lead with a specific observation; move your name and product down
Polite "not interested" replies Is the ask a meeting? Ask a yes/no question instead
No opens at all Is the subject line vague or salesy? Is it landing in spam? Make the subject specific to their situation; check deliverability
Replies say "not relevant" Does the pain line match this segment? Rewrite the pain line from this segment's own words
Feels like a template Remove the name and company. Could it go to 1,000 people? Add one true, current detail only this prospect would recognise

For more on why a sent email isn't working, see why your cold emails aren't getting replies. For first-line ideas that don't feel automated, see how to personalize cold outreach.

How to test it with RightEngagement before you send

You wrote the email, so you know what you meant. That makes it hard to read it the way a stranger will. Here's how to get an outside read in minutes.

  1. Open RightEngagement and pick Cold email.
  2. Describe your target audience the way you'd describe your list: "seed-stage B2B SaaS founders running a free trial".
  3. Paste the subject line and body.
  4. Watch the simulated buyers react, then read the report. It shows projected open, reply and book rates, a send-readiness check, a subject line score, the killer lines that triggered deletes, the hooks that worked, a tone diagnosis, and a rewritten version with the reasoning behind each change.
  5. Fix the killer line, rerun, and compare.

A run uses one to three credits depending on how deep you go. Plans start at $4.99 a month for 15 credits, and the code FIRST50 gives you the first month of Starter free.

Simulated buyers are a fast first read. Once the email passes, send it to a small batch from one segment and read the real replies before you scale. How to test a cold email before sending covers that live test step by step.

Next step

Write your pain line now, in one sentence. Build the email around it, then paste the draft into RightEngagement and fix whatever it flags before you send.

Run your draft through RightEngagement


Related: Cold email subject lines - How to build a B2B outreach sequence - Why your cold emails aren't getting replies

FAQ

How do I write a cold email that gets replies?

Write the pain line first: one sentence describing the prospect's problem in their own words. Then add an opener that proves you looked at them specifically, one line linking your product to the outcome they want, and a question they can answer in a few seconds. Keep it short enough to read on a phone without scrolling, and test it on simulated buyers or a small batch before sending to your full list.

How long should a cold email be?

Short enough to read on a phone without scrolling, which usually means four or five sentences. Length is rarely the real problem, though. A long email is usually a sign you haven't decided which single problem you're writing about. Pick one and the email gets short on its own.

What should the call to action be in a cold email?

A question the prospect can answer in a few seconds without opening a calendar. 'Is this on your list this quarter?' or 'Worth a look?' are easy to answer. A calendar link or a request for 30 minutes asks a stranger for a commitment before they trust you.

Does AI personalisation still work in cold email?

Generic AI personalisation, like a compliment about someone's recent post bolted onto a template, now reads as automated because so many senders use it. What still works is relevance: a specific, true observation that connects to the problem you solve. If the first line could be swapped onto any other prospect's email, it isn't doing its job.

How do I know if my cold email will get replies before I send it?

Run it through RightEngagement, which shows how simulated buyers in your target segment react, including projected reply rate and the exact lines that made them delete it. Then send to a small batch from one segment before scaling to the full list.


Originally published on Right Suite.

Top comments (0)