How to write cold emails that get replies

Most cold emails fail before the pitch.

A sales leader opens the message between two meetings, sees “I hope you’re well” followed by a paragraph about your company, and deletes it. The sender may have a good product. It does not matter. The email gave the buyer no reason to spend another ten seconds on it.

The fix is not sharper adjectives or a longer list of customer logos. It is choosing the right account, finding a reason to write now, and asking for less.

Find the event that makes the email timely

A cold email needs a trigger. Not a vague fit signal such as “this company sells software,” but something that changes the account’s priorities.

A new VP of Sales, six open SDR roles, a new compliance requirement, a product launch, or a move into the enterprise market can all create a plausible reason to contact someone. The trigger does not prove that the prospect has the problem you solve. It gives you permission to raise it.

Suppose you sell sales development support to B2B software companies. A 120-person company has just hired its first VP of Sales and posted six SDR roles. That is a better account to contact this week than a similar company with no visible change.

“Noticed you’re hiring SDRs” is not enough. Connect the event to the pressure it can create:

Saw that you joined {{Company}} as VP Sales and that the team is hiring six SDRs. At that point, list quality and message consistency often become problems before the new reps are fully ramped.

That sentence makes a reasonable observation without pretending to know the company’s internal problems. The recipient can confirm it, reject it, or explain that it is already handled.

Your ideal customer profile tells you which companies belong on the list. Triggers tell you which ones deserve attention now.

Personalization should change the argument

Adding a first name is not personalization. Neither is mentioning a company’s homepage tagline.

A useful detail changes what you say. If removing the detail leaves the email untouched, it was decoration.

For example, a cybersecurity vendor writing to a 200-person fintech might notice that the company recently published its first SOC 2 report and is hiring for enterprise sales. The email could ask whether evidence collection is becoming a burden as larger customers enter the pipeline. That is materially different from the message sent to a 30-person agency with no compliance motion.

You do not need to build a biography of every contact. Before writing, identify the account’s current event, the recipient’s likely responsibility, and the business problem connected to your offer. Then stop researching.

My view is that teams over-research the wrong accounts. They spend 20 minutes finding a personal fact about a company that should never have been in the campaign. Five minutes spent confirming a meaningful trigger is worth more than an hour collecting trivia.

Make one argument in the body

A cold email should make a single case. Something changed, that change may create a specific problem, and you have a credible reason to discuss it.

Here is an example for a sales operations consultancy contacting the new VP of Sales at the 120-person software company:

Subject: SDR ramp at {{Company}}

Hi Maya,

Saw you joined {{Company}} as VP Sales and that the team is hiring six SDRs.

That hiring plan can put pressure on account selection and message consistency before the new reps are fully ramped. We help teams set those rules and review the first sequences before hiring volume turns into uneven pipeline.

Is SDR ramp a priority this quarter?

The email does not explain every service. It does not claim to know Maya’s exact situation. It gives her one problem to assess and one easy question to answer.

The common mistake is trying to sell the entire business in one message. “We improve prospecting, enrichment, messaging, meetings, conversion, and revenue” is not a clear argument. It is a catalogue. Pick the problem most closely tied to the trigger.

Proof needs the same restraint. If you have a relevant example, use one. A payments company considering a processor change will care more about experience with reconciliation across multiple entities than a list of ten unrelated logos. If you cannot provide a close example, do not fill the gap with “industry-leading” claims. Explain what you noticed and why it may matter.

Ask for a reply, not a sales process

The first email should not require the prospect to accept your entire buying process.

“Do you have 30 minutes this week for a product demonstration?” asks the reader to find time, agree that a demo is appropriate, and enter a sales conversation before showing interest. That is a large request from a stranger.

A smaller question works better:

Is SDR ramp a priority this quarter?

Or:

Worth sending over the checklist we use before a team starts hiring outbound reps?

Both can be answered quickly. A reply creates permission for the next step.

A meeting request can make sense when the trigger is strong and the recipient clearly owns the issue. Even then, tie the meeting to the event. “Could we compare notes on your SDR ramp before the new hires start?” is more grounded than “Would you be open to a quick discovery call?”

Short emails still need a point

Keeping the first email under roughly 100 words is useful, but short is not the same as vague.

“I have an idea that could help your business” is short and worthless. “Your processor change may create more reconciliation work for finance, especially across multiple entities” is also brief, but the reader can decide whether it is relevant.

Use short paragraphs and plain language. Remove your company history, feature list, and broad claims. The subject line should follow the same rule. “Question about your hiring plans” is acceptable if the email is actually about hiring. “Amazing opportunity inside” is a promotion disguised as a subject line. Do not use fake reply prefixes, all caps, or manufactured urgency.

The right length depends on the argument. If the trigger needs one sentence of context and the offer needs one sentence of explanation, write those. Do not cut the explanation simply to hit an arbitrary word count.

Follow up with a new reason to respond

One email is rarely enough, but repeating “just following up” is not a sequence.

For the VP Sales example, a second message could add a more specific observation:

Maya, one issue I see with new SDR teams is that reps start before account rules and message tests are settled. That creates activity without much useful pipeline.

Is that already covered internally, or still being worked out?

A third message can close the loop without acting offended:

I’ll leave this here. If SDR hiring is not tied to an outbound build this quarter, no problem. If it is, I can send the review checklist we use for targeting and messaging before reps start.

Each message gives the prospect a different way to respond. They can confirm the issue, say it is handled, or ask for the resource. They can also ignore it without being chased forever.

Your SDR team should record the trigger behind each account, not just the contact and email address. That makes the sequence easier to review and helps the next seller understand why the account was selected.

Judge the campaign by reply quality

Open rates are weak evidence. An open tells you that the subject line earned a look, not that the message was useful.

Review replies by account segment, trigger, role, and CTA. If newly hired sales leaders reply but general managers do not, the problem may be audience selection. If opens are healthy but replies are weak, inspect the opening and the ask. If replies say “not me,” your ownership assumptions are wrong.

Also check the basics before blaming the copy. Verify addresses, configure SPF and DKIM, watch bounce and complaint rates, and keep volume controlled. Sending more messages from the same inbox does not fix weak targeting. It only creates more bad evidence and more deliverability risk.

The best cold email is not the most polished one. It gives the right person a specific reason to answer in one sentence. That starts with a clear cold outreach hypothesis about who may have the problem, why it may exist now, and what small response you want.