You are a B2B cold email expert. Write a multi-touch cold outreach sequence. Product/service: [What you offer] Target prospect: [Job title, company size, industry] ICP pain point: [Core problem you solve] Value proposition: [Key benefit in one sentence] Social proof: [Customers, results, case studies] CTA: [15-min call / Demo / Reply / PDF] Sequence length: [3 / 5 / 7 touches] Deliver the full sequence: hyper-personalized opener, value-led follow-up, case-study angle, problem-agitation, breakup email — plus subject A/B variants and reply-handling scripts.
Below is a plug-and-play B2B cold outreach sequence you can customize.
Replace the placeholders:
[PRODUCT/SERVICE][TARGET PROSPECT][COMPANY][INDUSTRY][PAIN POINT][VALUE PROP][SOCIAL PROOF][CTA][PERSONALIZATION TRIGGER]This version includes:
A: Quick idea for [COMPANY]
B: Noticed this about [COMPANY]
Hi [First Name],
I noticed [PERSONALIZATION TRIGGER] — especially how [COMPANY] is focused on [specific initiative, market, team growth, product, hiring signal, content, or recent announcement].
Usually when [TARGET PROSPECT] teams are at this stage, one challenge that starts showing up is [PAIN POINT].
That’s exactly what we help with at [YOUR COMPANY].
We offer [PRODUCT/SERVICE] for [TARGET PROSPECT / COMPANY TYPE] that helps teams [VALUE PROP].
For example, [SOCIAL PROOF].
Would it be worth a quick [CTA] to see if this could be useful for [COMPANY]?
Best,
[Your Name]
A: Thought this might be useful
B: One way to reduce [PAIN POINT]
Hi [First Name],
Following up because I think this may be relevant based on [COMPANY]’s focus on [PERSONALIZATION TRIGGER / BUSINESS PRIORITY].
A common issue we see with [TARGET PROSPECT] teams is that [PAIN POINT] often creates hidden costs:
[Consequence 1][Consequence 2][Consequence 3]The problem is not usually that teams are ignoring it. It’s that the current process makes it difficult to [desired outcome] consistently.
That’s where [PRODUCT/SERVICE] helps.
In short, we help [TARGET PROSPECT] teams [VALUE PROP] without [common objection: adding headcount / replacing existing systems / long implementation / heavy manual work].
Open to a quick [CTA] this week?
Best,
[Your Name]
A: How [CUSTOMER/PEER COMPANY] handled this
B: Example from another [INDUSTRY] team
Hi [First Name],
Sharing a quick example in case helpful.
One of our customers, [CUSTOMER / COMPANY TYPE], was dealing with [PAIN POINT].
Before working with us, they were struggling with:
[Before-state problem 1][Before-state problem 2][Before-state problem 3]After using [PRODUCT/SERVICE], they were able to [RESULT / OUTCOME].
[SOCIAL PROOF — metric, testimonial, case study, customer logo, or result]
The reason I thought of [COMPANY] is because teams in [INDUSTRY] often face the same challenge once they reach [growth stage, team size, revenue stage, market complexity, operational maturity].
Would you be open to seeing the short version of how this would apply to [COMPANY]?
Best,
[Your Name]
A: Is this becoming a bottleneck?
B: The hidden cost of [PAIN POINT]
Hi [First Name],
One thing we often hear from [TARGET PROSPECT] leaders is:
“We know [PAIN POINT] is a problem, but it hasn’t become urgent enough yet.”
The issue is that by the time it becomes urgent, the cost is usually already showing up in places like:
[process / sales cycle / delivery / onboarding / reporting]For [COMPANY], even a small improvement in [key metric] could create meaningful upside.
That’s why [PRODUCT/SERVICE] is designed to help teams [VALUE PROP].
Not sure if now is the right time, but if [PAIN POINT] is on your radar, I’d be happy to share a quick breakdown of what we’re seeing across similar [INDUSTRY] teams.
Worth a quick [CTA]?
Best,
[Your Name]
A: Should I close the loop?
B: Not a priority right now?
Hi [First Name],
I haven’t heard back, so I’ll assume improving [PAIN POINT] is not a priority for [COMPANY] right now.
Totally fair.
Before I close the loop, would it make sense for me to send over [PDF / case study / benchmark / short teardown / one-page overview] so you have it for later?
If not, no worries — I won’t keep following up.
Best,
[Your Name]
If you want a 7-touch sequence, add these between Touch 3 and Touch 4:
A: What we’re seeing in [INDUSTRY]
B: Benchmark for [TARGET PROSPECT] teams
Hi [First Name],
Quick insight from working with [TARGET PROSPECT] teams in [INDUSTRY]:
Most teams don’t realize [PAIN POINT] is costing them until it starts affecting [metric / revenue / retention / productivity / speed].
A pattern we often see:
[symptom 1][symptom 2][symptom 3]The companies that fix this earlier usually gain an advantage because they can [benefit] before the problem becomes expensive.
That’s the gap [PRODUCT/SERVICE] helps close.
Would you like me to send over a quick benchmark or example?
Best,
[Your Name]
A: Quick question
B: Is this relevant for [COMPANY]?
Hi [First Name],
Quick question:
Is [PAIN POINT] something your team is actively trying to improve this quarter?
If yes, I can share how [PRODUCT/SERVICE] helps [TARGET PROSPECT] teams [VALUE PROP].
If not, I’m happy to close the loop.
Best,
[Your Name]
If you only want 3 touches, use:
This keeps the sequence short but still covers personalization, credibility, and a low-pressure close.
Thanks, [First Name] — appreciate the reply.
Based on what I’ve seen from [COMPANY], I think the most relevant angle is helping your team [VALUE PROP], especially around [PAIN POINT].
Would [Option 1] or [Option 2] work for a quick [CTA]?
Best,
[Your Name]
Absolutely.
The short version:
[PRODUCT/SERVICE] helps [TARGET PROSPECT] teams solve [PAIN POINT] by [HOW IT WORKS IN SIMPLE TERMS].
Teams typically use it to:
[Use case 1][Use case 2][Use case 3]And we’ve helped [SOCIAL PROOF].
I’m attaching/sending [PDF / case study / overview].
If it looks relevant, would it make sense to do a quick [CTA] to map it to [COMPANY]?
Best,
[Your Name]
Thanks for letting me know, [First Name].
No problem at all.
Just so I don’t follow up on the wrong thing — is it not relevant because:
[PAIN POINT] is not a priorityEither way, appreciate the reply.
Best,
[Your Name]
That makes sense.
A lot of teams we speak with already have something in place for [PAIN POINT].
Where we usually fit is when the existing solution still leaves gaps around:
[Gap 1][Gap 2][Gap 3]Not suggesting you replace anything.
Would it be worth comparing notes to see if there’s any gap we could help close?
Best,
[Your Name]
Totally understand.
Would it be easier if I sent a short [PDF / case study / teardown / benchmark] instead?
That way you can review it when timing is better.
If useful, we can revisit later.
Best,
[Your Name]
Of course.
When would be a better time to reconnect — [specific month] or [specific quarter]?
In the meantime, I can send over [resource] so you have context when this becomes more relevant.
Best,
[Your Name]
Good question.
Pricing usually depends on [pricing variable: team size / usage / volume / plan / scope].
Most customers invest because they’re trying to improve [business outcome], not just buy another tool/service.
If helpful, I can give you a quick range after understanding:
Worth a quick [CTA]?
Best,
[Your Name]
Use one of these in Touch 1:
I saw [COMPANY] recently [raised funding / expanded / launched new market]. Usually at this stage, teams start looking more closely at [PAIN POINT].
I noticed [COMPANY] is hiring for [role/team], which usually signals increased focus on [business priority].
I saw your post/article/interview about [topic]. The point about [specific idea] stood out because it connects closely to [PAIN POINT].
I noticed [COMPANY] recently launched [product/feature]. As teams expand offerings, [PAIN POINT] can become harder to manage consistently.
A lot of [INDUSTRY] companies are trying to improve [business outcome] right now, but [PAIN POINT] keeps slowing teams down.
Use based on friction level:
Would it be worth a quick reply if this is relevant?
Open to seeing a short example?
Would you be open to a 15-minute call next week?
Would it make sense to show you how this works for a team like [COMPANY]?
Should I send over the one-page breakdown?
Worth exploring, or should I close the loop?