How to Write a B2B Cold Email That Gets Replies

A B2B cold email that gets replies is short, plain and about the reader: a subject line that looks like normal email, an opening line about their situation, one relevant point, a specific offer and a single easy question to end on. Most emails that get ignored break one of those rules, usually by talking about the sender first.

This guide covers each part in turn, then shows three annotated example emails and a template you can adapt. One assumption runs through all of it: the email is going to the right person at the right company. Copy can't rescue a bad list, so if you haven't defined your ideal customer profile and decision-makers yet, start there.

The Structure of a Cold Email That Gets Replies

Every effective cold email does the same five jobs, in roughly this order:

That adds up to roughly 50 to 120 words. Anything you add beyond these five parts should earn its place, because every extra sentence is another chance for the reader to stop.

Write a Subject Line That Looks Like Normal Email

The best cold subject lines look like something a colleague might send. They are short, lowercase or sentence case, and specific without giving the whole email away.

Rules of thumb: name the topic, not the product; avoid words that sound like marketing; never pretend to be a reply. A subject line that tricks someone into opening only makes the email that follows less credible.

Open With the Reader's Situation

The first line is what shows in the inbox preview, so it decides whether the rest gets read. Make it about the reader, and make it true. Strong openers draw on:

• A verifiable trigger: a new role, an acquisition, a new location, a hiring push.
• A problem common to their cohort, described in their own words.
• A specific observation about how their business works.

Weak openers talk about you ("I'm the founder of..."), state the obvious ("I hope this finds you well") or use trivia that has nothing to do with why you are writing. If you can delete the first sentence without losing meaning, delete it.

Make an Offer Worth Replying To

The offer is the reason to reply. It answers the reader's silent question: what do I get for answering a stranger? A good offer is:

• Specific to the problem you just named.
• Low-cost to accept. A short resource or a yes-or-no question asks less than a 30-minute demo.
• Credible. If you mention a result, it should be real and relevant to the reader.

Compare two ways of ending the same email. "Can I get 30 minutes on your calendar to show you a demo?" asks a stranger for half an hour on faith. "I wrote up how two companies your size cut the manual matching step.

Want a copy?" asks for one word and gives something useful either way. The second offer also tells you something when they say yes: the problem is real for them.

Proof helps when it is close to the reader's world. A customer in the same industry, or facing the same problem, is far more persuasive than a long list of famous logos.

End With One Easy Question

End with a single question that is easy to answer in a few words. Interest-based questions usually work better than time-based ones for a first email, because they ask less.

• "Worth a look?"
• "Is this on your list for this quarter?"
• "Who handles this on your team?"
• "Would the checklist be useful?"

Avoid stacking asks ("Can we talk Tuesday or Wednesday, and could you also forward this?"). One question, one decision.

Keep It Short and in Plain Text

Cold emails that read like a note from a person tend to do better than ones that look like a newsletter. In practice that means:

• Plain text, no images, no HTML templates, no attachments.
• At most one link, and often none in the first email.
• Short paragraphs of one or two sentences, readable on a phone.
• A simple signature: name, role, company. No banners or social icons.
• No tracking-heavy formatting, which can make the email look automated.

Short also means one idea. If you have three value propositions, pick the one that matches this cohort's problem and save the others for follow-ups.

Three Annotated Example Emails

The examples below are written for a fictional company, Ledgerly, which sells accounts payable software to mid-market companies. Names and details are invented for illustration.

Example 1: Problem-led, for a cohort

Subject: carrier invoices Hi Dana, At logistics companies your size, carrier and fuel invoices tend to be the part of month-end that grows with every new lane, and they're usually matched by hand. Ledgerly matches them against delivery records automatically, so the AP team reviews exceptions instead of every line. I put together a one-page breakdown of how two mid-market carriers set this up. Want me to send it over? Sam Ledgerly

• Subject names the topic in two words and looks like internal email.
• Opener describes a problem the whole cohort shares, in the controller's language.
• One sentence on what the product does, framed as the outcome for the team.
• Offer is a useful resource, not a meeting, so saying yes costs nothing.
• CTA is a yes-or-no question. About 70 words in total.

Example 2: Trigger-led, for a new leader

Subject: first 90 days Hi Priya, Congratulations on the VP Finance role at Northbank Health. With three new clinics joining this year, I imagine invoice approvals across sites are already on your list. We help multi-site healthcare groups run one approval flow for every location, so nothing waits in a clinic manager's inbox. Is consolidating approvals something you're planning to look at this quarter? Sam Ledgerly

• Opens with a verifiable trigger (new role, new sites) that explains why now.
• "I imagine" keeps the assumption honest rather than claiming to know her priorities.
• Relevance is tied to her cohort: multi-site healthcare.
• CTA asks about timing, which is easy to answer even with a "not yet".

Example 3: The short follow-up

Subject: re: carrier invoices Hi Dana, One more thought: if invoice matching isn't the bottleneck, I'd be curious what is. Is it approvals, vendor questions, or something else? Sam

• Sent in the same thread days later, so "re:" is honest here.
• Adds a new angle instead of "just bumping this".
• Invites a reply even from someone who disagrees with the original premise.
• Under 40 words.

A Fill-in-the-Blanks Template

Use this as a starting structure for each cohort, then rewrite it in your own voice:

Check Before You Send

1. Is the first line about the reader, and is it true?
2. Could a colleague of the reader explain the offer in one sentence?
3. Is there exactly one question at the end?
4. Is it under about 120 words, in plain text, with at most one link?
5. Do all personalization fields render correctly for every lead?
6. Would you be comfortable if the reader forwarded it to their CEO?

In RevFirst, emails are prepared per cohort and a RevFirst strategist reviews the campaign with you before launch. Nothing is sent until you approve every step of the sequence, and the sequence stops as soon as someone replies.