September 2026 · Sales operations · 4 min read

How to Write a Cold Email That Actually Gets a Reply

Real cold email examples from market entry work, plus the structure that gets replies instead of silence.

Türkçe oku →

In my early career I contacted more than 300 institutions and ran over 1,500 calls to land 110 partnerships. Most of those calls happened because an email got a reply first. After that many attempts, you stop believing in templates and start noticing the three or four things that actually make someone respond, and it is never the subject line trick or the "quick question" opener everyone recommends.

A cold email that gets a reply does four things in under 120 words: proves you looked at their business specifically, states a real reason the timing matters now, asks a question they can answer in one line, and gives them an easy way to say no without feeling rude.

A real cold email sent to a utility director

Here is an actual email I wrote for a water treatment company entering a new market, sent to the operations director of a municipal utility.

Subject: Your desalination expansion and a filtration question

Hi Rashid,

I saw your utility's board approved funding for the new desalination line in Fujairah this quarter. Most projects at that scale run into a specific issue around month four: the primary filtration vendor can supply for the pilot phase but not for full-scale rollout without a six-month lead time.

We just helped a comparable utility in Oman avoid that exact gap by bringing a secondary supplier in during the design phase instead of after the RFP.

Is lead time on filtration equipment something your procurement team is already tracking for this project, or is it still early enough to flag?

If it is not relevant, no worries, just let me know and I will not follow up.

Tunahan

That email is specific to one utility, one project, one likely operational problem. It could not be sent to a second company without rewriting the first two sentences, which is exactly the point.

A second example, written for an accounting firm

Here is a second one, written for an accounting and tax advisory firm entering a new country, sent to a finance director at a mid-size manufacturer.

Subject: Your Q3 filing and the new transfer pricing rule

Hi Elena,

I noticed [Company] expanded manufacturing capacity into Serbia last quarter. The new transfer pricing documentation requirement that took effect in July catches a lot of companies that just added a cross-border entity, usually because the local advisory relationship was set up for compliance filing, not for structuring intercompany pricing before the fact.

We recently walked a similar manufacturer through exactly this before their first filing deadline hit.

Worth a fifteen-minute call to check whether your current setup already covers this, or is it better handled by whoever runs your Serbia entity directly?

Tunahan

Notice what both emails avoid. Neither opens with "I hope this finds you well." Neither says "I wanted to reach out" or "I'm reaching out because." Neither describes the sender's company before it has earned the right to. Neither asks for "15 minutes of your time" as a generic favor, both tie the ask to a specific decision the recipient is already making.

The five-line structure behind both emails

The structure behind both, every time:

Line 1: a fact about them, specific enough that they know you did not mass-mail it. A funding approval, an expansion, a regulatory change hitting their exact situation, something a job posting or press release actually said.

Line 2 to 3: the problem that fact usually creates, stated as something you have seen before, not something you are guessing might apply to them.

Line 4: a proof point, one sentence, no case study attachment, no logo wall.

Line 5: a question they can answer with a single sentence, not "let's set up a call to discuss," which asks for a decision before they know if it is worth their time.

Last line: permission to ignore it. This is the line most people skip and it is the one that gets the highest reply rate in my experience, because it removes the awkwardness of not responding and often gets a reply specifically because you made it easy to say no.

Why genericness kills reply rates

What kills reply rates is not bad writing, it is genericness. An email that could be sent to any company in the industry reads as a mass email even when it technically was not one. Out of 1,500 calls, the ones that connected fastest were always the ones where the first line proved, in the recipient's own context, that I had done the work before asking for their time.

Write the first line last. Find the fact worth opening with, then build backward, the rest of the email nearly writes itself once that fact is real and specific.

The best subject line is the one that describes something only true about them.

Updated: September 2026