outbound-sequencer
Design multi-touch outbound sequences with optimal timing, channel mix, and messaging progression for SDR campaigns
What this skill does
# Outbound Sequencer > Create high-converting outbound sequences with strategic touchpoint timing, channel orchestration, and message progression. ## When to Use This Skill - Designing new outbound campaigns - Optimizing existing sequences - Creating segment-specific cadences - Testing sequence variations - Training SDRs on best practices ## Methodology Foundation Based on **Outreach.io Sequence Science** and **SalesLoft Cadence Research**, combining: - Optimal touchpoint timing - Multi-channel orchestration - Message progression strategy - Personalization at scale ## What Claude Does vs What You Decide | Claude Does | You Decide | |-------------|------------| | Designs sequence structure | Message copy | | Suggests optimal timing | Brand voice | | Recommends channel mix | Tool selection | | Creates progression logic | A/B test priorities | | Identifies optimization areas | Resource allocation | ## Instructions ### Step 1: Define Sequence Parameters **Key Variables:** | Parameter | Options | |-----------|---------| | Touches | 8-14 typical | | Duration | 14-30 days | | Channels | Email, Phone, LinkedIn, Video | | Goal | Meeting, Response, Qualification | ### Step 2: Design Channel Mix **Recommended Mix:** | Channel | Percentage | Purpose | |---------|------------|---------| | Email | 50-60% | Scale, persistence | | LinkedIn | 20-25% | Personal touch | | Phone | 15-20% | Direct connection | | Video | 5-10% | Differentiation | ### Step 3: Structure Touchpoints **Framework: 4-Phase Sequence** | Phase | Days | Purpose | Intensity | |-------|------|---------|-----------| | Opening | 1-3 | Hook, establish | High | | Building | 4-10 | Value, credibility | Medium | | Urgency | 11-18 | Social proof, FOMO | High | | Breakup | 19-25 | Final push, close loop | Low | ### Step 4: Message Progression **Progression Pattern:** 1. **Touch 1**: Hook with insight/trigger 2. **Touch 2-3**: Value proposition, social proof 3. **Touch 4-6**: Different angles, persistence 4. **Touch 7-9**: Urgency, scarcity 5. **Touch 10+**: Breakup, future timing ## Examples ### Example 1: Enterprise Outbound Sequence **Output:** ``` ## Enterprise Outbound Sequence (14 touches, 21 days) ### Sequence Overview - **Target**: VP+ at enterprise companies - **Goal**: Booked meeting - **Duration**: 21 days - **Touches**: 14 total ### Channel Mix | Channel | Touches | % | |---------|---------|---| | Email | 7 | 50% | | LinkedIn | 4 | 29% | | Phone | 2 | 14% | | Video | 1 | 7% | --- ### Full Sequence #### Phase 1: Opening (Days 1-3) **Day 1 - Email #1 (Trigger-based)** ``` Subject: [Trigger] + [Company] Hi [FirstName], [Trigger observation - funding, hire, news]. I work with [similar companies] who face [challenge]. Curious if that's on your radar? [One line value prop] Worth a quick call? [Name] ``` **Day 1 - LinkedIn Connection** - Send connection request - Note: "Hi [Name], [brief reason for connecting]" **Day 2 - Phone Call #1** - Goal: Live conversation - If VM: "Hi [Name], [Name] from [Company]. Quick call about [trigger]. Will follow up via email." **Day 3 - LinkedIn Voice Note** - 30-second personalized message - Reference trigger + offer value --- #### Phase 2: Building (Days 4-10) **Day 4 - Email #2 (Value)** ``` Subject: Re: [Previous subject] [FirstName], Wanted to share what [Similar Customer] achieved: - [Metric 1] - [Metric 2] They were in a similar situation when we first connected. Worth comparing notes? [Name] ``` **Day 6 - LinkedIn Engagement** - Engage with their content (like, comment) - OR share relevant content, tag them **Day 8 - Email #3 (Different Angle)** ``` Subject: Quick question about [specific challenge] [FirstName], Most [Titles] I talk to say [specific challenge] is their #1 priority this quarter. Quick question: Is that true for you too, or is something else taking priority? Genuinely curious—helps me understand what matters most to leaders like you. [Name] ``` **Day 10 - Phone Call #2** - Morning attempt - Different VM: "Hi [Name], following up on my emails. Would love 15 minutes to discuss [value]. [Your number]." --- #### Phase 3: Urgency (Days 11-18) **Day 11 - Email #4 (Social Proof)** ``` Subject: How [Competitor's Customer] solved [problem] [FirstName], [Competitor's Customer] was dealing with [same problem]. After [implementing solution], they saw: • [Result 1] • [Result 2] Happy to walk through their approach if useful. [Name] ``` **Day 13 - LinkedIn Direct Message** ``` Hi [Name], I've reached out a few times—wanted to try a different channel. Not trying to sell you anything. Genuinely think [insight] could help [Company]. Open to a quick chat? ``` **Day 15 - Email #5 (Video)** ``` Subject: Recorded this for you, [FirstName] [FirstName], Put together a 60-second video on why I think [Company] would benefit from [approach]. [Video thumbnail/link] If this resonates, let's talk. If not, no worries—I'll stop reaching out. [Name] ``` **Day 18 - Email #6 (Urgency)** ``` Subject: [Event/timing trigger] [FirstName], With [event/quarter end/budget cycle] coming up, a lot of [Titles] are locking in [decisions]. Last chance to get this on your calendar before [deadline]. Quick call this week? [Name] ``` --- #### Phase 4: Breakup (Days 19-21) **Day 19 - LinkedIn Final** - Send article or resource relevant to them - No ask, just value **Day 21 - Email #7 (Breakup)** ``` Subject: Should I close your file? [FirstName], I've reached out several times and haven't heard back. Totally understand—you're busy. Just want to check: should I close out your file, or is this something worth revisiting in the future? If timing isn't right, let me know and I'll circle back in [timeframe]. Either way, wishing you a great [quarter/year]. [Name] ``` --- ### Sequence Metrics (Benchmarks) | Metric | Target | Excellent | |--------|--------|-----------| | Open Rate | >40% | >55% | | Reply Rate | >8% | >15% | | Meeting Rate | >3% | >6% | | Positive Reply | >60% of replies | >75% | ``` ### Example 2: High-Velocity SMB Sequence **Output:** ``` ## SMB Quick-Hit Sequence (8 touches, 14 days) ### Sequence Overview - **Target**: Manager/Director at SMB - **Goal**: Demo or trial signup - **Duration**: 14 days - **Touches**: 8 total ### Channel Mix | Channel | Touches | % | |---------|---------|---| | Email | 5 | 63% | | LinkedIn | 2 | 25% | | Phone | 1 | 12% | --- ### Rapid Sequence **Day 1 - Email #1 (Direct)** ``` Subject: Quick question, [FirstName] Hi [FirstName], Do you handle [function] at [Company]? If so, I have an idea that could help you [specific outcome] in [timeframe]. Interested? [Name] ``` **Day 1 - LinkedIn Connect** - Simple connection request **Day 3 - Email #2 (Value)** ``` Subject: Re: Quick question [FirstName], [One stat or proof point from similar company] That's what [Customer] did with us. Worth 10 minutes to see if we can do the same for [Company]? [Name] P.S. Here's a 2-min video showing how: [link] ``` **Day 5 - Phone Call** - Quick call attempt - VM: Keep to 20 seconds **Day 7 - LinkedIn Message** ``` Hey [Name] - saw you opened my email but haven't had a chance to connect. Totally get it. Is [problem] even a priority for you right now? ``` **Day 9 - Email #3 (Different Hook)** ``` Subject: [Competitor name] alternative? [FirstName], A lot of [Company size] companies tell us they're frustrated with [competitor/status quo]. We're simpler + faster. Most customers are up and running in [timeframe]. Worth a look? [Name] ``` **Day 11 - Email #4 (Offer)** ``` Subject: Try us free? [FirstName], Want to just show you instead of tell you? Here's a free [trial/assessment/audit]: [link] No commitment, no call required. [Name] ``` **Day 14 - Email #5 (Breakup)** ``` Subject: Last one from me [FirstName], Haven't heard back, so this will be my last email. If [problem] becomes a priority, I'm here: [calendar link] Good luck with everything! [Name] ``` ``
Related 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.