Outreach sequences skill

Designs and manages Outreach sequences: multi-channel cadences, triggers, analytics, and team workflows.

by LeadMagic·MIT license·★ 62 Stars on the repo·GitHub ↗

Use now

Inside this skill

SKILL.md · the author's own words
# Outreach Sequences

## Overview
Outreach is the enterprise-grade sales engagement platform. Sequences here manage
complex multi-channel, multi-touch cadences with team routing, analytics, and
compliance controls that simpler tools lack.

## Authoritative Foundations
- **Outreach Support — Sequences and rulesets** — Configure sequence settings, rulesets, and task types so reps follow the same cadence and…
- **Google and Yahoo — Bulk sender requirements (2024)** — Authenticate with SPF, DKIM, and DMARC, keep spam complaints below 0.3%, and res…
- **The Bridge Group — SDR metrics research** — Benchmark activity and conversion per rep against published SDR data before judging cadence…

## When to Use
- "Set up Outreach sequences"
- "Design Outreach cadences"
- "Outreach sequence optimization"

Word-for-word excerpt, not a result. Read the full SKILL.md ↓

Files of Outreach sequences

LeadMagic/main1 file shown
SKILL.md
Show the full text149 lines

Outreach Sequences

Overview

Outreach is the enterprise-grade sales engagement platform. Sequences here manage complex multi-channel, multi-touch cadences with team routing, analytics, and compliance controls that simpler tools lack.

Authoritative Foundations

  • Outreach Support — Sequences and rulesets — Configure sequence settings, rulesets, and task types so reps follow the same cadence and replies auto-exit prospects.
  • Google and Yahoo — Bulk sender requirements (2024) — Authenticate with SPF, DKIM, and DMARC, keep spam complaints below 0.3%, and respect per-mailbox volume.
  • The Bridge Group — SDR metrics research — Benchmark activity and conversion per rep against published SDR data before judging cadence performance.

When to Use

  • "Set up Outreach sequences"
  • "Design Outreach cadences"
  • "Outreach sequence optimization"
  • "Build Outreach workflows"

Step-by-Step Process

Phase 1: Sequence Design

Outreach supports complex branching:

  • Linear: A → B → C → D → E. Simple, predictable. Best for SDR outbound.
  • Branching: If reply positive → AE handoff. If OOO → pause and retry. If no reply → continue.
  • Multi-channel: Email → Call → LinkedIn → Email → Call → Social
  • Trigger-based: Enroll on Salesforce field change, intent signal, or event
Phase 2: Cadence Architecture

Standard 5-touch cold outbound cadence:

  • Day 1: Email (problem hypothesis, 50-90 words)
  • Day 3: LinkedIn connection + note (reference email hint)
  • Day 5: Call + voicemail (if number available)
  • Day 8: Email (different angle, proof point)
  • Day 14: Email (breakup, "closing your file")
Phase 3: Deliverability Controls
  • Max 50 emails/day per mailbox in Outreach
  • Rotate across 3-5 mailboxes per rep
  • 45-second minimum between sends
  • Custom tracking domain for open/click tracking
  • Sunset sequences after 3 consecutive bounces
Phase 4: Team Workflows
  • Round-robin assignment from inbound queues
  • AE handoff triggers: positive reply, meeting booked, opportunity created
  • Manager approval gates for sequences targeting C-suite
  • Daily task dashboards per rep with prioritized actions
Phase 5: Analytics & Optimization
  • Funnel metrics: emails sent → opened → replied → meetings → opportunities
  • Sequence comparison: which sequence has highest meeting rate per persona
  • Rep performance: meetings per 100 touches by rep
  • A/B test: subject line and opener variants

Output Format

Sequence blueprint with: cadence map, step configuration, routing rules, deliverability settings, and analytics dashboard design.

Quality Check

Before delivering, verify:

  • All required sections are complete
  • Output matches the user's stated need
  • Named frameworks are cited for key recommendations
  • No vague claims — every recommendation has a specific action
  • Deliverable is ready for operational use, not just conceptual

Common Pitfalls

  1. Skipping research. Building output without understanding the specific context. Fix: always gather required inputs before producing deliverables.
  2. Generic output. "Improve your process" without concrete steps. Fix: every recommendation must include a specific action, timeline, and owner.
  3. Missing framework citations. Advice without named authorities. Fix: ground every recommendation in a cited framework from a recognized authority.

Execution Artifacts

  • references/framework-notes.md — Outreach triggers, Clay→CRM path, Eric agency scale
  • templates/output-template.md — CRM map + triggers + sequence deliverable
  • scripts/check-output.py — local checklist validator This skill includes lightweight artifacts the agent can load on demand:
  • references/enrichment-enrollment-gate.md — verify gate + trigger architecture
  • references/pat-spielmann-outbound-copy.md — verify-before-enroll (Pat Spielmann)
  • references/eric-nowoslawski-outbound.md — Clay agency execution (Eric Nowoslawski)
  • references/gtm-table-blueprints.md — clay-toolkit table → CRM upsert
  • the n8n-toolkit skill (gtm-flow-catalog.md) — OUT-01 API enrollment
  • references/gtm-experts-outbound-index.md — expert router Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.

Implementation Depth

Use this section when the user asks for a finished asset, not a high-level explanation.

Diagnostic Questions
  1. What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
  2. Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
  3. What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
  4. What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
  5. What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure?
Framework Application

Map the recommendation explicitly to the named frameworks in this skill:

  • Outreach Sequence Best Practices: apply only the part that directly improves the requested deliverable.
  • ColdIQ Cadence Design: apply only the part that directly improves the requested deliverable.
  • Outreach — Sales Engagement Cadence Design: apply only the part that directly improves the requested deliverable.
Deliverable Standard

A strong output from this skill includes:

  • A crisp diagnosis of the current situation
  • A recommended path with tradeoffs, not a generic list
  • A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan
  • A measurement plan with leading and lagging indicators
  • Risks and edge cases called out before execution
Adaptation Rules
  • For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity.
  • For mid-market: include workflow ownership, handoffs, integrations, and enablement assets.
  • For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements.
  • cold-email-strategy, multi-channel-outreach, email-deliverability, sending-platforms, pipeline-management
1---
2name: outreach-sequences
3description: >-
4 Designs and manages Outreach sequences: multi-channel cadences, triggers,
5 analytics, and team workflows. Use when the user is building or optimizing
6 sequences in Outreach. Triggers on: "Outreach sequences", "Outreach cadence",
7 "Outreach setup", "Outreach automation".
8license: MIT
9compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
10metadata:
11 version: "1.0.0"
12 author: LeadMagic
13 category: tools
14 tags: [outreach, sequences, cadence, sales-engagement, outbound]
15 frameworks:
16 - "Outreach Support — Sequences and rulesets"
17 - "Google and Yahoo — Bulk sender requirements (2024)"
18 - "The Bridge Group — SDR metrics research"
19---
20 
21# Outreach Sequences
22 
23## Overview
24Outreach is the enterprise-grade sales engagement platform. Sequences here manage
25complex multi-channel, multi-touch cadences with team routing, analytics, and
26compliance controls that simpler tools lack.
27 
28## Authoritative Foundations
29- **Outreach Support — Sequences and rulesets** — Configure sequence settings, rulesets, and task types so reps follow the same cadence and replies auto-exit prospects.
30- **Google and Yahoo — Bulk sender requirements (2024)** — Authenticate with SPF, DKIM, and DMARC, keep spam complaints below 0.3%, and respect per-mailbox volume.
31- **The Bridge Group — SDR metrics research** — Benchmark activity and conversion per rep against published SDR data before judging cadence performance.
32 
33## When to Use
34- "Set up Outreach sequences"
35- "Design Outreach cadences"
36- "Outreach sequence optimization"
37- "Build Outreach workflows"
38 
39## Step-by-Step Process
40 
41### Phase 1: Sequence Design
42Outreach supports complex branching:
43- **Linear:** A → B → C → D → E. Simple, predictable. Best for SDR outbound.
44- **Branching:** If reply positive → AE handoff. If OOO → pause and retry. If no reply → continue.
45- **Multi-channel:** Email → Call → LinkedIn → Email → Call → Social
46- **Trigger-based:** Enroll on Salesforce field change, intent signal, or event
47 
48### Phase 2: Cadence Architecture
49Standard 5-touch cold outbound cadence:
50- **Day 1:** Email (problem hypothesis, 50-90 words)
51- **Day 3:** LinkedIn connection + note (reference email hint)
52- **Day 5:** Call + voicemail (if number available)
53- **Day 8:** Email (different angle, proof point)
54- **Day 14:** Email (breakup, "closing your file")
55 
56### Phase 3: Deliverability Controls
57- Max 50 emails/day per mailbox in Outreach
58- Rotate across 3-5 mailboxes per rep
59- 45-second minimum between sends
60- Custom tracking domain for open/click tracking
61- Sunset sequences after 3 consecutive bounces
62 
63### Phase 4: Team Workflows
64- Round-robin assignment from inbound queues
65- AE handoff triggers: positive reply, meeting booked, opportunity created
66- Manager approval gates for sequences targeting C-suite
67- Daily task dashboards per rep with prioritized actions
68 
69### Phase 5: Analytics & Optimization
70- Funnel metrics: emails sent → opened → replied → meetings → opportunities
71- Sequence comparison: which sequence has highest meeting rate per persona
72- Rep performance: meetings per 100 touches by rep
73- A/B test: subject line and opener variants
74 
75## Output Format
76Sequence blueprint with: cadence map, step configuration, routing rules, deliverability
77settings, and analytics dashboard design.
78 
79 
80 
81## Quality Check
82 
83Before delivering, verify:
84- [ ] All required sections are complete
85- [ ] Output matches the user's stated need
86- [ ] Named frameworks are cited for key recommendations
87- [ ] No vague claims — every recommendation has a specific action
88- [ ] Deliverable is ready for operational use, not just conceptual
89 
90## Common Pitfalls
91 
921. **Skipping research.** Building output without understanding the specific context. Fix: always gather required inputs before producing deliverables.
932. **Generic output.** "Improve your process" without concrete steps. Fix: every recommendation must include a specific action, timeline, and owner.
943. **Missing framework citations.** Advice without named authorities. Fix: ground every recommendation in a cited framework from a recognized authority.
95 
96## Execution Artifacts
97 
98- `references/framework-notes.md` — Outreach triggers, Clay→CRM path, Eric agency scale
99- `templates/output-template.md` — CRM map + triggers + sequence deliverable
100- `scripts/check-output.py` — local checklist validator
101This skill includes lightweight artifacts the agent can load on demand:
102- `references/enrichment-enrollment-gate.md` — verify gate + trigger architecture
103- `references/pat-spielmann-outbound-copy.md` — verify-before-enroll (Pat Spielmann)
104- `references/eric-nowoslawski-outbound.md` — Clay agency execution (Eric Nowoslawski)
105- `references/gtm-table-blueprints.md` — clay-toolkit table → CRM upsert
106- the `n8n-toolkit` skill (gtm-flow-catalog.md) — OUT-01 API enrollment
107- `references/gtm-experts-outbound-index.md` — expert router
108Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.
109 
110## Implementation Depth
111 
112Use this section when the user asks for a finished asset, not a high-level explanation.
113 
114### Diagnostic Questions
115 
1161. What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
1172. Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
1183. What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
1194. What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
1205. What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure?
121 
122### Framework Application
123 
124Map the recommendation explicitly to the named frameworks in this skill:
125 
126- Outreach Sequence Best Practices: apply only the part that directly improves the requested deliverable.
127- ColdIQ Cadence Design: apply only the part that directly improves the requested deliverable.
128- Outreach — Sales Engagement Cadence Design: apply only the part that directly improves the requested deliverable.
129 
130### Deliverable Standard
131 
132A strong output from this skill includes:
133 
134- A crisp diagnosis of the current situation
135- A recommended path with tradeoffs, not a generic list
136- A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan
137- A measurement plan with leading and lagging indicators
138- Risks and edge cases called out before execution
139 
140### Adaptation Rules
141 
142- For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity.
143- For mid-market: include workflow ownership, handoffs, integrations, and enablement assets.
144- For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements.
145 
146 
147## Related Skills
148- cold-email-strategy, multi-channel-outreach, email-deliverability, sending-platforms, pipeline-management
149 

Discussion

Alternatives

Browser Automation SkillWeb browser automation with AI-optimized snapshots for claude-flow agentsCoding · MITDeepevalDeepEval evaluation workflow for AI agents and LLM applications. TRIGGER when the user wants to evaluate or improve an AI agent, tool-using workflow, multi-turn chatbot, RAG pipeline, or LLM app; add evals; generate datasets or goldens; use deepeval generate; use deepeval test run; send results to Confident AI; monitor production; run online evals; inspect traces; or iterate on prompts, tools, retrieval, or agent behavior from eval failures. AI agents are the primary use case. Covers Python SDK, pytest eval suites, CLI generation, traced evals, Confident AI reporting, and agent-driven improvement loops. DO NOT TRIGGER for unrelated generic pytest, non-AI test setup, or non-DeepEval observability work unless the user asks to compare or migrate to DeepEval; for instrumenting an app with DeepEval tracing, @observe, or framework integrations (use the `deepeval-tracing` skill); or for raw OpenTelemetry / OTLP export without the deepeval package (use the `deepeval-otel` skill).Business & ops · Apache-2.0Dev browserBrowser automation with persistent named pages via the dev-browser CLI. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, log into sites, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", "open the browser", or any browser interaction request.Business & ops · MITTurn into appTurn visible project context, a proven thread, skill, or workflow into a runnable Agent-Native app with simple buttons, visible agent steps, preview, and deployment handoff. Use when a user invokes `/turn-into-app` or asks to make a workflow into an app, including from Claude or ChatGPT on the web, including when the source is a spreadsheet link or upload.Business & ops · MIT