B2B cold email template for customers (2026)
B2B cold email template for customers: a trigger-based opener, a one-sentence value prop, a soft CTA, and the personalization line that lifts replies.
b2b-cold-email-template-customers.txt
Subject: {{FIRST_NAME}}, {{TRIGGER}}
Hi {{FIRST_NAME}},
Saw {{TRIGGER}}. Usually when that happens, the next 30 days
get eaten by {{PAIN_HYPOTHESIS}}.
We built {{ONE_SENTENCE_VALUE}}. {{PROOF_POINT}}.
{{LOW_FRICTION_ASK}}?
{{YOUR_FIRST_NAME}}
Variables · fill before sending
- FIRST_NAMEProspect's first name. Pull from LinkedIn, never 'Hi there'.
- TRIGGERA specific recent event: a hire, a launch, a podcast appearance, a job opening, a tweet. Must be from the last 30 days.
- PAIN_HYPOTHESISThe one specific problem the trigger implies they have. Not 'scaling'; 'onboarding the 12 reps you just hired without burning your enablement lead'.
- ONE_SENTENCE_VALUEWhat you do, phrased as the inverse of PAIN_HYPOTHESIS. Eight words or fewer.
- PROOF_POINTOne concrete customer outcome with a number. '[Customer] cut their onboarding from 6 weeks to 9 days.' Skip if you don't have one.
- LOW_FRICTION_ASKNot a 15-min call. Ask for a yes/no, a forward, or a 90-second loom reply.
- YOUR_FIRST_NAMEYour first name. Sign-off is one line.
How to use it
- Subject line is the trigger, not the pitch: the prospect's first name plus a recent event. Keep it under 60 characters so the preview pane doesn't truncate the signal.
- The opener must cite the trigger verbatim, then name the specific second-order pain it implies. That is the personalization that lifts replies — and the line founders skip when they're tired.
- Value is one sentence framed as the inverse of the pain, not a product description. Proof is one customer with a number; delete the line rather than fake it.
- Ask for the lowest-friction yes (a yes/no, a forward, a 90-second Loom), never a 15-minute call. The first email earns a reply; the second earns the meeting.
- Track three numbers weekly: reply rate (under 5% means rewrite the trigger), positive-reply rate (under 50% means the value sentence is off), and trigger-to-send latency (over a week and the trigger reads as stale).