outbound-email-strategy — Claude Code skill: how to install
outbound-email-strategy builds cold B2B outreach sequences, writes low-friction subject lines, and plans follow-up timing. Useful for SDR workflows and founder-led sales campaigns.
MIT 263 installs ★ 114 updated 2026-09-18
npx skills add manojbajaj95/claude-gtm-plugin --skill outbound-email-strategy -a claude-codeWhat outbound-email-strategy does
The skill provides a cold outreach playbook based on peer-level tone and prospect research. It enforces strict formatting rules: subject lines stay within 2-4 words in lowercase without punctuation, while calls to action focus on interest rather than aggressive meeting requests.
It defines four sequence cadences, ranging from a fast-track 5-email sequence to a 14-touch enterprise nurture schedule. Generated drafts are saved to content/<platform>/drafts/YYYY-MM-DD_short-topic-slug.md. If strategy/brand.md and about/me.md are missing from the project, the generated copy lacks your brand voice and offer constraints.
What it helps with
- build a 7-touch cold outreach cadence for B2B prospects
- write concise subject lines without sales jargon
- apply tiered research signals to cold copy
- draft break-up follow-ups to close unanswered threads
Example prompts for the agent
- Draft a 5-step cold sequence targeting VPs of Engineering at B2B SaaS companies
- Write three lowercase subject lines using recent hiring signals
- Create a value-first follow-up email without asking for a phone call
How to install outbound-email-strategy
1Skills CLI (Vercel)
npx skills add manojbajaj95/claude-gtm-plugin --skill outbound-email-strategy -a claude-code2Manually: put the files in place
~/.claude/skills/outbound-email-strategy/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/outbound-email-strategy/
1Skills CLI (Vercel)
npx skills add manojbajaj95/claude-gtm-plugin --skill outbound-email-strategy -a codex2Manually: put the files in place
.agents/skills/outbound-email-strategy/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add manojbajaj95/claude-gtm-plugin --skill outbound-email-strategy -a cursor2Manually: put the files in place
.cursor/skills/outbound-email-strategy/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install manojbajaj95/claude-gtm-plugin skills/outbound-email-strategy2Manually: put the files in place
.github/skills/outbound-email-strategy/SKILL.md1Skills CLI (Vercel)
npx skills add manojbajaj95/claude-gtm-plugin --skill outbound-email-strategy -a gemini-cli2Platform CLI
gemini skills install https://github.com/manojbajaj95/claude-gtm-plugin --path skills/outbound-email-strategyManually: put the files in place
.devin/skills/outbound-email-strategy/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add manojbajaj95/claude-gtm-plugin --skill outbound-email-strategy -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about outbound-email-strategy
How do I install outbound-email-strategy in Claude Code?
Run npx skills add manojbajaj95/claude-gtm-plugin --skill outbound-email-strategy -a claude-code. This installs the definition file into ~/.claude/skills/outbound-email-strategy/SKILL.md.
What does outbound-email-strategy do?
It structures B2B cold emails, subject lines, and multi-step follow-ups up to 14 touches. The logic focuses on conversational phrasing rather than standard marketing copy.
Where does this skill store drafted emails?
It saves drafts to content/<platform>/drafts/YYYY-MM-DD_short-topic-slug.md. It also references strategy/brand.md and about/me.md for background context.
Source text
SKILL.md · MIT
---
name: outbound-email-strategy
description: Comprehensive outbound email strategy skill for cold outreach, email sequences, and multi-channel campaigns. Use when writing cold emails, creating outreach sequences, optimizing response rates, designing follow-up cadences, or building outbound campaigns. Covers prospecting, personalization frameworks, sequence design, subject lines, response handling, compliance, email design, HTML email templates, email layout, email marketing, newsletter design, drip campaigns, email subject lines, email headers, and cold email templates for discovery calls and SDR workflows.
---
# Outbound Email Strategy
## Workspace Context
Read bootstrap context before asking questions: `strategy/brand.md` for brand, audience, offer, channels, tools, constraints, and metrics; `about/me.md` for personal voice; `content/ideas.md` and `content/calendar.md` for content planning. Use legacy product-marketing context files only as fallback. Save generated drafts to `content/<platform>/drafts/YYYY-MM-DD_short-topic-slug.md`, and route durable learnings back to `strategy/brand.md`, `about/me.md`, or `content/ideas.md`.
## Operating Contract
This skill is self-contained for its frontmatter scope: use its local instructions, references, scripts, and assets as the playbook; ask only for missing task-specific inputs; hand off to adjacent skills instead of expanding scope; and return an actionable artifact, decision, plan, draft, or diagnostic.
Expert outbound email execution for B2B sales and business development. Build high-response cold outreach campaigns that feel personalized and drive conversations.
## Quick Start
1. **Define ICP** — Who are you targeting and why?
2. **Research Prospects** — Find personalization signals
3. **Craft the Hook** — Lead with value, not a pitch
4. **Build Sequence** — 5-7 touches across channels
5. **Handle Responses** — Script for every outcome
---
## ICP Framework
### Define Your Target
| Element | Question | Example |
|---------|----------|---------|
| Title | Who decides? | VP of Engineering |
| Company | What type? | B2B SaaS, $1-10M ARR |
| Pain | What hurts? | Content isn't converting |
| Trigger | Why NOW? | Just raised funding |
| Proof | Why YOU? | Helped similar company get result |
### Questions to Answer
> 1. What's their job title/role?
> 2. What company size/type?
> 3. What industry or vertical?
> 4. What pain are they experiencing RIGHT NOW?
> 5. Why should THEY specifically care?
---
## Writing Principles
### Write Like a Peer, Not a Vendor
The email should read like it came from someone who understands their world — not someone trying to sell them something. Use contractions. Read it aloud. If it sounds like marketing copy, rewrite it.
### Every Sentence Must Earn Its Place
Cold email is ruthlessly short. If a sentence doesn't move the reader toward replying, cut it.
### Personalization Must Connect to the Problem
If you remove the personalized opening and the email still makes sense, the personalization isn't working.
### Lead with Their World, Not Yours
"You/your" should dominate over "I/we." Don't open with who you are.
### One Ask, Low Friction
Interest-based CTAs ("Worth exploring?" / "Would this be useful?") beat meeting requests.
---
## Subject Lines
Short, boring, internal-looking. The subject line's only job is to get the email opened.
**Rules:**
- 2-4 words, lowercase, no punctuation
- Should look like it came from a colleague
- No product pitches, no urgency, no emojis
**Examples:**
- "reply rates"
- "hiring ops"
- "Q2 forecast"
---
## Email Sequence Framework
### Sequence Types
| Type | Duration | Best For |
|------|----------|----------|
| Classic Cold | 7 emails, 2 weeks | Standard outreach |
| Fast-Track | 5 emails, 1 week | Quick follow-up |
| Long-Play | 12-14 emails, 4-6 weeks | Enterprise/Nurture |
| Event-Based | 3-5 emails | Trigger-specific |
### Sequence Flow
| Email | Day | Goal | Length | CTA |
|-------|-----|------|--------|-----|
| 1: Introduction | 0 | Awareness + relevance | 50-100w | Soft ask |
| 2: Value Proof | 2 | Establish credibility | 75-125w | Meeting time |
| 3: Different Angle | 4 | Alternative pain point | 50-75w | Yes/no question |
| 4: Social Proof | 6 | Peer validation | 60-90w | Simple reply |
| 5: Resource Share | 8 | Give before asking | 40-60w | Soft |
| 6: Direct Ask | 10 | Be straightforward | 30-50w | Meeting request |
| 7: Breakup | 14 | Final attempt + opt-out | 25-40w | "Close your file?" |
### Optimal Send Times
Tue–Thu, 10–11 AM or 2–3 PM in recipient's timezone.
---
## Personalization Framework
### 4-Level System
| Level | Time | What to Include |
|-------|------|----------------|
| Tier 1 (Basic) | 30 sec | Name, company, industry |
| Tier 2 (Researched) | 2-3 min | News, LinkedIn content, job postings |
| Tier 3 (Deep) | 10-15 min | Podcast quotes, custom video, mutual connections |
### Research Sources
- LinkedIn posts and activity
- Company news/press releases
- Job postings (indicate priorities)
- Podcast appearances
- Conference presentations
- Mutual connections
### Personalization Patterns
**Content-Based:**
> "Your post on X resonated — especially the point about Y."
**Hiring Signal:**
> "Noticed you're hiring X — usually means Y pain."
**Company News:**
> "Saw the news about X. Insight: Y."
**Mutual Connection:**
> "X mentioned you're working on Y. Made me think of Z."
---
## Message Components
### The Hook (First Line)
Make it impossible to ignore. Prove you know them.
**Good:**
- "Saw your post about X — made me think of Y"
- "Noticed you're hiring X — usually means Y"
- "Your talk on X was Y"
**Bad:**
- "Hope this email finds you well"
- "I'm reaching out because..."
- "I came across your profile..."
### The Observation
Show you understand their world.
> "Companies at your stage usually struggle with X"
> "Saw you're scaling — that usually creates Y"
### The Value Offer
Give before you ask.
- "Made you a quick audit"
- "Put together resource that might help"
- "Happy to share how we solved this for X"
### The CTA
Make it natural and low-friction.
**Good:**
- "Worth a look?"
- "Interested?"
- "Want me to send it over?"
**Bad:**
- "Let's book a 30-minute call"
- "When are you free to chat?"
---
## Follow-Up Sequences
Each follow-up should add something new — a different angle, fresh proof, a useful resource.
### Follow-Up Templates
**Email 2 (Value Bump):**
> "Quick follow-up — additional insight. [Restate offer]."
**Email 3 (Different Angle):**
> "New observation about their business. Thought this might be relevant."
**Email 4 (Social Proof):**
> "Just helped similar company with result. Thought of you."
**Email 5 (Break-Up):**
> "Closing the loop. If problem isn't a priority, no worries. Door's open."
---
## Response Handling
### Classification & SLA
| Response Type | Example | SLA | Action |
|---------------|---------|-----|--------|
| **Positive** | "Yes, let's talk" | 5 min | Book meeting |
| **Curious** | "Tell me more" | 1 hr | Send proof point |
| **Objection** | "Too small" | Same day | Handle with framework |
| **Timing** | "Not now, Q3" | Same day | Set reminder |
| **Referral** | "Talk to CFO" | 1 hr | Reach out to referral |
| **Hard No** | "Not interested" | 24 hr | Polite close |
### Response Scripts
**Positive Response:**
> "Thanks! Here's what I promised. Quick question: [qualifying question]? If [condition], [next step]."
**"Not Now" Response:**
> "No problem. Would it make sense to reconnect in [timeframe]?"
**"What's This?" Response:**
> "In short: [1-sentence value]. [Reoffer value]. Worth a look?"
**Skeptical Response:**
> "Fair to ask. [Proof point]. Happy to share case study if useful."
---
## Cold Call Scripts
### Talk Track
1. **Opener**: Permission + value in one line
2. **Discovery**: 3 questions (current flow, pain metric, priority)
3. **Value Hits**: Match pain, cite proof, propose next step
4. **Objections**: Acknowledge → brief proof → micro-commit
5. **Close**: Time-bound CTA + send calendar while on call
---
## Performance Benchmarks
| Metric | Good | Great | Exceptional |
|--------|------|-------|-------------|
| Open Rate | 35-45% | 45-55% | 55%+ |
| Reply Rate | 3-8% | 8-15% | 15%+ |
| Meeting Booked | 1-3% | 3-6% | 6%+ |
### High Reply Rate Signals
- Personalized opening
- Clear value prop in first 2 sentences
- Similar-company social proof
- Low-friction CTA
- Clean plain-text formatting
---
## A/B Testing Strategy
### Test Elements
| Element | Test Approach |
|---------|---------------|
| Subject lines | Question vs. Statement |
| First line | Hook types: signal vs. pain vs. question |
| CTA | Direct vs. soft vs. value offer |
| Timing | Morning vs. afternoon |
| Length | Short (50w) vs. medium (100w) |
### Method
Send 50/50 split to 100 prospects. Wait 48h, measure opens + replies. Winner goes to remaining list.
---
## Volume Guidelines
| Stage | Volume | Focus |
|-------|--------|-------|
| Testing (Week 1-2) | 20-50/day | Find what works |
| Scaling (Week 3-4) | 50-100/day | Systematize |
| Cruising (Month 2+) | 100+/day | Maintain and iterate |
**Rule:** Never sacrifice personalization for volume.
---
## Compliance & Deliverability
### Authentication (Required)
- **SPF**: Sender Policy Framework
- **DKIM**: DomainKeys Identified Mail
- **DMARC**: Domain-based Message Authentication
### Spam Rate Thresholds
- Hard ceiling: **0.3%** complaint rate
- Target: **<0.1%** for reliable inbox
### Best Practices
- Keep sending identity stable
- Warm up new domains gradually
- One-click unsubscribe (List-Unsubscribe-Post)
- Follow CAN-SPAM requirements
---
## Common Mistakes
| Mistake | Why It Fails | Fix |
|---------|--------------|-----|
| Generic opener | "Hope you're well" ignored | Specific observation |
| Feature dump | They don't care yet | Lead with their pain |
| Multiple CTAs | Confusion | Single clear ask |
| Long emails | Won't be read | Under 75 words |
| Same angle each email | No reason to reply | New value per touch |
| No personalization | Feels like spam | Add research |
---
## The Outbound Math
**Example:**
- 100 emails/day × 5 days = 500 emails/week
- 5% response rate = 25 responses
- 50% positive = 12-13 interested
- 50% book calls = 6-7 calls/week
- 20% close = 1-2 customers/week
**That's 4-8 customers/month from outbound.**
---
## Related Skills
- [lead-generation-and-demand](../lead-generation-and-demand/SKILL.md) - Demand generation
- [sales-and-revenue-operations](../sales-and-revenue-operations/SKILL.md) - Sales processes
- [conversion-rate-optimization](../conversion-rate-optimization/SKILL.md) - CRO frameworks
© manojbajaj95 · MIT · manojbajaj95/claude-gtm-plugin