B2B cold email examples: 10 personalized templates that work

A good B2B cold email is a short, specific note that tells one person why you are writing to them, why now, what problem you think they may have, why you are credible, and what small next step you are asking for. The examples below show that structure applied to ten different situations, each with notes on why it works, followed by a fill-in cold email template for B2B outreach you can adapt.

All companies, people, and situations below are fictional and for illustration only. Use them to see the pattern, then replace every detail with real evidence about your recipient. Copying the words without the research behind them is how cold email turns into spam. For the full framework (personas, triggers, sequences, compliance), see the cold email campaign guide.

What does a good B2B cold email look like?

Every example on this page follows the same skeleton:

Target 60-140 words for executives and 90-180 for managers and practitioners. Note that the emails avoid “I hope this finds you well,” feature lists, and requests for 30 minutes before relevance is established.

B2B cold email examples

1. Product to an engineering manager (hiring trigger)

Subject: review queue bottlenecks

Hi Lena,

Noticed Quarrybrook is hiring five backend engineers this quarter.

At that stage, code review often becomes the hidden bottleneck. Cycle time slows, but it is hard to tell whether the cause is reviewer load, flaky CI, or unclear ownership.

Tallyline shows those bottlenecks from GitHub and CI data, without asking engineers for status updates.

Worth sending a 2-minute example of what it would show for a team your size?

Sam

Why it works:

• The trigger (hiring) is public and directly linked to the pain (review load).
• The product is explained by the job it does, not its category.
• The CTA offers a small asset, not a meeting.

2. Services to a VP of Engineering (migration trigger)

Subject: search migration risk

Hi Marcus,

Your recent job posts mention moving customer search to OpenSearch.

The hard part usually starts after the migration looks done. Relevance tuning, shard sizing, and cost controls start interacting, and fixes in one area cause regressions in another.

We have run this kind of review for several marketplaces before cutover. It usually takes one session to spot the riskiest gaps.

Would a short review of your plan be useful, or is someone else on platform the right person?

Priya

Why it works:

• States the hypothesis carefully (“usually”), which senior engineers respect.
• Credibility is specific but not inflated with unverifiable numbers.
• Offers a delegation path in the same sentence as the ask.

3. Executive delegation email (CFO)

Subject: data platform cost attribution

Hi Dana,

Reaching out because companies expanding customer-facing analytics, as Harrowvane is, often find data platform spend hard to attribute across product, data, and infrastructure teams.

We help finance and engineering agree on who owns which costs before it turns into a budget surprise.

If this sits with your data or platform org, is there someone I should send a short note to?

Tom

Why it works:

• Under 80 words. Executives read in seconds.
• Business consequence first, no technical detail.
• The ask is easy to answer by forwarding.

4. Technical asset to a senior engineer

Subject: ClickHouse schema checklist

Hi Ravi,

Your engineering blog post on moving dashboards into the Brindlewick app made me think this might be useful.

We put together a short checklist of schema and query mistakes that show up when analytics moves from internal BI to customer-facing features: partition choices, high-cardinality filters, and materialized view tradeoffs.

Should I send it over?

Noa

Why it works:

• References their own public work, and the idea in it, not flattery.
• Names concrete technical concepts so the reader knows it is not fluff.
• Three-word CTA; no meeting.

5. Security product to a CISO (compliance trigger)

Subject: SOC 2 evidence collection

Hi Grace,

Saw that Pinewick Health posted a GRC analyst role mentioning SOC 2 and HIPAA evidence.

When teams add a second framework, evidence collection tends to double while the underlying controls barely change.

Ledgerkeep maps one set of evidence to multiple frameworks so the team collects it once.

Is this on your team's radar this year, or already handled?

Owen

Why it works:

• Trigger is a specific job post, not a vague “saw you care about security.”
• Ends with a yes-or-no question that is easy to reply to, including “already handled,” which is also useful.

6. Agency to a head of marketing (website signal)

Subject: pricing page and paid search

Hi Jordan,

Noticed Fennoway's paid search ads point to the homepage rather than the pricing page that launched last month.

For B2B SaaS with public pricing, sending high-intent searches straight to pricing often converts better, but it is worth testing before switching all traffic.

We can outline a two-week test plan for the three campaigns we think are most affected.

Want me to send it?

Elle

Why it works:

• Shows the sender actually looked, with an observation the recipient can verify in seconds.
• Hedges the claim (“often,” “worth testing”) instead of promising a result.
• Offers something concrete and scoped.

7. Partnership email (shared customers)

Subject: Rowanstack + Tidequill implementations

Hi Femi,

Several Rowanstack customers we work with mention needing help after purchase with event pipeline design, which is the part we implement.

There may be a simple referral path: when a customer needs implementation depth, we take it on, and the account stays yours.

Open to a 20-minute call to see if the overlap is real?

Ana

Why it works:

• Leads with a mutual benefit, not “synergies.”
• Removes the obvious partner fear (losing the account) in one sentence.
• Asks to test whether the overlap is real, which is honest.

8. Research or discovery email

Subject: question on search ownership

Hi Omar,

I am talking with engineering leaders who own search infrastructure to understand how teams decide between tuning the current stack and migrating.

This is not a demo request. I want to learn how the decision actually gets made when product, infrastructure cost, and relevance pull in different directions.

Would you be open to a 20-minute conversation? I will share the anonymized notes afterward.

Kai

Why it works:

• Honest about the purpose, and then keeps that promise.
• Offers something back for the person’s time.

9. Re-engaging an old lead (new reason)

Subject: since our call in March

Hi Beatriz,

When we spoke in March, you mentioned the team would revisit alerting after the Q3 platform move.

Since then we have added native support for the stack you described, which was the main gap at the time.

If alerting is back on the list, worth a 15-minute look at what changed?

Leo

Why it works:

• The prior contact is real, so referencing it is honest (never imply a call that did not happen).
• It answers the specific objection from last time instead of “circling back.”

10. Founder to founder (small company, narrow ICP)

Subject: onboarding drop-off

Hi Mei,

I run a 12-person company that builds onboarding analytics for developer tools. Your public changelog shows Cobaltnote shipped three onboarding changes in two months, which usually means someone is chasing activation.

We built a free drop-off report that works from your existing product events. No integration call needed.

Would it be useful if I set one up for you to look at?

Arjun

Why it works:

• Founder-to-founder tone is appropriate at a small company where the CEO may own the problem.
• The trigger (frequent onboarding releases) is observable and plausibly linked to the pain.
• Removes friction explicitly (“no integration call needed”).

What makes a personalized cold email example actually personalized?

Notice that none of the ten examples mention where someone went to school, their hometown, or a compliment on the company. Personalization that works connects a public signal to a likely business problem:

Public signal + likely operational implication + relevant offer

A useful test: if you can swap the recipient’s name for someone else’s at a different company and the email still makes sense, it is not personalized. Merge fields are not personalization.

At scale, aim for one sentence of true personalization per email (the trigger) and keep the rest segment-specific: the same problem hypothesis and offer for everyone in a tightly defined segment.

Fill-in B2B cold email template

Use this as a starting point. Every bracket must be replaced with evidence, not a generic phrase.

Subject: [specific problem, trigger, or asset, 2-6 words]

Hi [First name],

[Trigger: one public, business-relevant signal about their company or role.]

[Hypothesis: "At that stage, teams often run into [specific problem], because [cause]."]

[Credibility or value: what you have done, built, or can give them, in one or two sentences. No unverifiable numbers.]

[One ask: a small asset, a routing question, or a short call. Make it easy to say no or forward.]

[Your first name]
[Title, company]
[Postal address]
[One-line opt-out, e.g. "Not relevant? Reply 'no' and I won't email again."]

Before sending, check:

• Could this exact email be sent to a different company unchanged? If yes, rewrite the trigger and hypothesis.
• Is there exactly one ask?
• Is it under 140 words for an executive or 180 for a practitioner?
• Does the subject honestly describe the body? (See cold email subject lines.)
• Is there a follow-up plan that adds new information? (See cold email follow-up.)

What legal basics apply to B2B cold email?

These are general notes, not legal advice; get counsel for your specific markets.

• United States (CAN-SPAM). The FTC’s guide is explicit that the law makes no exception for business-to-business email. Commercial messages need accurate header and sender information, a subject line that reflects the content, clear disclosure that the message is an ad, a clear way to opt out, and a valid physical postal address. Opt-outs must be honored within 10 business days, and the opt-out mechanism must work for at least 30 days after sending.
• United Kingdom (PECR and UK GDPR). The ICO’s guidance says you can send marketing email to corporate subscribers (companies, LLPs, government bodies) without prior consent, but you must not hide your identity and must give a valid address to opt out. Sole traders and some partnerships are treated as individuals and generally need consent. Data protection law still applies to named employees’ work addresses.
• European Union (GDPR and national ePrivacy rules). Processing a named business contact’s data needs a lawful basis, often legitimate interests for B2B outreach. People have an absolute right to object to direct marketing, and when you collect their data from somewhere other than them, GDPR Article 14 requires telling them how you got it, at the latest at the first communication. National ePrivacy rules on B2B email vary widely; some countries, Germany among them, are generally treated as requiring prior consent even for B2B marketing email.

Separately from the law, Gmail and Yahoo require every sender to authenticate with SPF or DKIM and to keep spam complaints below 0.3%. Bulk senders (roughly 5,000 or more messages a day to Gmail) must also authenticate with both SPF and DKIM, publish DMARC, and support one-click unsubscribe for marketing mail.

Turning examples into a campaign

One good email is not a campaign. You still need a list that matches the trigger, a follow-up sequence that adds new information, suppression of customers and opted-out contacts, and someone reading replies. GTM Hacker’s email agents draft outreach, run one-to-one campaigns where each recipient gets their own thread, and respect send windows, per-sender limits, and suppression lists, with a human approving the campaign before it sends.

For the strategy behind these examples, start with the cold email campaign guide.