B2B Sales Outreach Email Sequence
Added Apr 1, 2026
About This Prompt
Cold outreach is still the most direct path to B2B pipeline generation, but most sequences fail because they lead with product features instead of prospect value. This prompt creates a psychologically sequenced email series that builds trust before asking for anything. The value-first approach in Email 1 establishes credibility, the case study in Email 2 provides social proof, and the question in Email 3 creates engagement. The breakup email in Email 5 leverages loss aversion psychology to reactivate non-responders. Each email has a specific strategic purpose that builds on the previous one. Essential for SDRs, founders doing outbound sales, and sales leaders building team playbooks.
Variables to Customize
[PRODUCT_SERVICE]
What you are selling
Example: an AI-powered code review tool that catches security vulnerabilities before deployment
[TARGET_PERSONA]
Who you are emailing
Example: VP of Engineering or Head of Security
[COMPANY_TYPE]
Type of company to target
Example: Series B+ SaaS companies with 50-500 engineers
[PAIN_POINT]
Their likely pain point
Example: spending too much engineering time on manual code reviews while still missing security issues that reach production
Tips for Best Results
- Personalize the first line of every email with specific research about the prospect
- Send emails Tuesday through Thursday between 8-10 AM in the prospect's time zone
- Track response rates by email position to identify where the sequence loses momentum
Example Output
## Email 1: The Value-First Insight **Send:** Day 0 | **Purpose:** Establish credibility, not sell **Subject:** 3 CVEs your team might be missing **Subject B:** security blind spot in Node.js apps Hi [FIRST_NAME], [PERSONALIZATION: Reference a recent blog post, conference talk, or open-source contribution by the prospect] I analyzed 200 production security incidents at SaaS companies your size last quarter. Three patterns kept showing up that traditional code review misses: 1. Transitive dependency vulnerabilities (43% of incidents) 2. Auth bypass through parameter pollution (28%) 3. SSRF in internal API calls (19%) We compiled the patterns into a free checklist. Want me to send it over? [NAME] **Strategic note:** No mention of our product. Pure value delivery builds trust and gets the 'yes' habit started with a low-commitment ask.