outbound-email-strategy
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.
What this skill does
# Outbound Email Strategy
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 ThresholdsRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.