Skip to content
Skills Library
Sales & customer service · Planning

outbound-sequence

/outbound-sequence

Designs multi-touch, multichannel outbound cadences (email, LinkedIn, phone) with a day-by-day plan, the copy for every step, a breakup email, tier-based variants and per-step metrics with kill and keep thresholds. Use when the user asks to "build an outbound sequence", "create a cadence", "multi-touch campaign", "SDR sequence", "follow-up steps for cold outreach", or "why is my sequence not booking meetings". For a single first-touch email, see cold-email.

Licence
MIT
Last repository change
29.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 29.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Designs multi-touch, multichannel outbound cadences (email, LinkedIn, phone) with a day-by-day plan, the copy for every step, a breakup email, tier-based variants and per-step metrics with kill and keep thresholds. Use when the user asks to "build an outbound sequence", "create a cadence", "multi-touch campaign", "SDR sequence", "follow-up steps for cold outreach", or "why is my sequence not booking meetings". For a single first-touch email, see cold-email.

Triggers from the description

build an outbound sequencecreate a cadencemulti-touch campaignSDR sequencefollow-up steps for cold outreachwhy is my sequence not booking meetings
Original author description

Designs multi-touch, multichannel outbound cadences (email, LinkedIn, phone) with a day-by-day plan, the copy for every step, a breakup email, tier-based variants and per-step metrics with kill and keep thresholds. Use when the user asks to "build an outbound sequence", "create a cadence", "multi-touch campaign", "SDR sequence", "follow-up steps for cold outreach", or "why is my sequence not booking meetings". For a single first-touch email, see cold-email.

How it works

  1. Before you start
  2. Design principles
  3. Standard cadence (Tier A/B, 21 days, 11 touches)
  4. Writing each step
  5. Metrics and thresholds
  6. Output format
  7. Example
  8. Related skills
Original SKILL.md headings · 129 lines, 1,208 words
SKILL.md preview
---
name: outbound-sequence
description: Designs multi-touch, multichannel outbound cadences (email, LinkedIn, phone) with a day-by-day plan, the copy for every step, a breakup email, tier-based variants and per-step metrics with kill and keep thresholds. Use when the user asks to "build an outbound sequence", "create a cadence", "multi-touch campaign", "SDR sequence", "follow-up steps for cold outreach", or "why is my sequence not booking meetings". For a single first-touch email, see cold-email.
---

You are an outbound program owner who designs sequences as experiments: every step has a job, and every step is measured.

## Before you start

- Read `.agents/sales-context.md` if it exists. If it doesn't, ask for persona, top 2-3 pains, 2 proof points and the sales motion, or suggest running the sales-context skill.
- Ask: target tier (A/B/C), persona, number of accounts, channels the rep can actually do (phone? LinkedIn?), sending tool (Outreach, Salesloft, Apollo, HubSpot, other) and whether a trigger exists.
- Ask for current metrics if a sequence already runs: reply rate, positive reply rate, meetings per 100 prospects.

## Design principles

- **Each touch adds a new angle.** "Just bumping this" is a wasted touch. Rotate: pain -> proof -> insight -> different persona angle -> breakup.
- **8-12 touches over 3-4 weeks** for Tier A/B. Most replies come after touch 1; data from large sequencing platforms consistently shows a majority of meetings come from touches 2+. Fewer than 4 touches leaves meetings on the table; past ~12 the unsubscribe and complaint rate climbs faster than replies.
- **Multichannel beats single channel.** Adding phone and LinkedIn to email typically lifts meeting rates meaningfully over email-only, because each channel reaches people the others miss.
- **Thread email follow-ups** under the first email for 1-2 steps, then start a new thread with a new subject for a fresh angle.
- **Calls:** best connect windows are commonly early morning (8-10am) and late afternoon (4-6pm) local time. Leave voicemails only when they reference an email you're sending ("subject line: ramp for 9 new AEs").
- **Multi-thread Tier A.** Run 2-3 contacts per account in parallel with persona-specific angles, staggered by 2-3 days so they don't all land the same morning.

## Standard cadence (Tier A/B, 21 days, 11 touches)

| Day | Channel | Step | Job of the step |
|---|---|---|---|
| 1 | LinkedIn | View profile + follow | Warm the name; no request yet |
| 1 | Email 1 | Observation -> implication -> ask | Main hook |
| 2 | Call 1 + voicemail | Reference email 1 | Second channel, same story |
| 3 | LinkedIn | Connection request, no pitch | Build a channel |
| 5 | Email 2 (same thread) | New proof point / case study | Credibility |
| 7 | Call 2 | No voicemail | Connect attempt |
| 9 | LinkedIn | Engage with their post or send DM if connected | Human touch |
| 11 | Email 3 (new thread) | Insight / teardown / benchmark | Give value |
| 14 | Call 3 + voicemail | Different angle | Last call push |
| 17 | Email 4 | Different persona angle or referral ask | "Am I talking to the right person?" |
| 21 | Email 5 | Breakup | Permission to close the loop |

**Tier C / low-touch:** email-only, 4-5 steps over 14 days, segment-level personalization.
**Inbound / warm (downloaded content, visited pricing):** compress to 7 days, call within 5 minutes of the signal if possible; speed-to-lead is the biggest lever on inbound conversion.

## Writing each step

- Email 1: see the cold-email skill rules (50-100 words, interest CTA).
- Email 2 (bump with value): 40-70 words. "One more thought" + a specific peer result.
- Email 3 (insight): share something useful even if they never buy: a benchmark, a 3-bullet teardown of their onboarding flow, a mistake you see peers make.
- Email 4 (referral): "If this sits with someone else, who owns <problem> at <company>?"
- Breakup: short, no guilt, no sarcasm. Give them an easy out and leave the door open. Breakups often get one of the highest reply rates in a sequence because they're easy to answer.

### Breakup template
> Subject: close the loop?
>
> Hi <first name>, I've reached out a few times about <pain> and haven't heard back, so I'll assume it's not a priority right now.
>
> If that changes, or <trigger> makes it relevant later, just reply to this thread.
>
> Either way, good luck with <their initiative>.

## Metrics and thresholds

Track per step, not just per sequence. Diagnose where it breaks.

| Metric | Healthy | Action if below |
|---|---|---|
| Bounce rate | < 2% | Fix data source and verification; pause |
| Reply rate (all) | 3-8% | Revisit targeting and email 1 |
| Positive reply rate | 1-3%+ | Pain or proof is not resonating |
| Positive replies -> meeting | 50%+ | Faster response; reply with 2 times, not a link only |
| Meetings booked per 100 prospects | 1-3 (cold), 3-6 (triggered) | Add phone, tighten tier |
| Connect rate on calls | 5-10% of dials | Get mobile numbers; change call windows |
| Opt-out rate per step | < 1% | That step is annoying; cut or rewrite it |

Test one variable at a time with at least ~200 prospects per variant before calling a winner. Test in this order: list/targeting, then email 1 angle, then subject line, then later steps.

## Output format

```markdown
# Sequence: <name>  (Tier <A/B/C>, persona: <title>, <n> days, <n> touches)

## Strategy
- Angle progression: <pain -> proof -> insight -> referral -> breakup>
- Trigger used:
- Multi-thread plan: <other personas and stagger>

## Steps
### Day <n> - <Channel> - <Step name>
Subject (if email):
Copy:
<text>
Rep note: <what to personalize / when to skip>

## Exit rules
- Reply (any) -> remove from sequence, respond manually within 2 business hours
- Out of office -> pause until return date + 1 day
- Opt-out -> remove and suppress account-wide for this contact

## Metrics to watch
| Step | Metric | Target |
```

## Example

Persona: Controller at Series B-D SaaS, product: close automation, trigger: hiring a second accountant.

```markdown
### Day 1 - Email 1 - Hook
Subject: second accountant
Copy:
Hi Maria, noticed Northwind is hiring a second staff accountant.
That usually means close is taking longer than the board wants and the fix on the table is headcount.
Brightpath went from a 9-day to a 4-day close without the hire by automating bank and card recs.
Worth comparing before you fill the role?
Rep note: skip if the posting is older than 60 days.

### Day 2 - Call 1 + voicemail
Voicemail (under 25s): "Maria, it's Sam from Ledgerly. I sent you a note about your staff
accountant posting and how Brightpath cut close to 4 days without that hire. Subject line is
'second accountant'. No need to call back, I'll follow up by email."

### Day 5 - Email 2 (same thread)
Copy:
One more data point: Brightpath's controller said the bigger win was audit prep, every rec
now has an evidence trail, so their auditors found zero adjustments. Relevant for Northwind?
```

## Related skills

- cold-email: rules for email 1 and the rewrite checklist.
- linkedin-outreach: copy for the LinkedIn steps.
- cold-call-script: what to say when a call connects.
- prospect-research: triggers that decide tier and angle.
- follow-up: what happens after a reply or meeting.

Versions

RepositoryScoreLicence
This page · burnoutscript/sales-skills100MIT
thecraighewitt/skills100MIT
calven-ai/marketing-as-code90MIT

Database snapshot: 13.11.2026 · package version c5ddb4ad7749 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100cold-email
    Write and run B2B cold outbound that gets replies, from cold emails and follow-ups to sending setup, LinkedIn, multichannel cadences, and reply handling. Use when the user mentions "cold email," "cold outreach," "outbound," "prospecting email," "SDR emails," "follow-up…
  • 100gx-outbound-cadence-expert
    Design multi-touch outbound sequences across email, LinkedIn, phone, and video. Use when the user asks for outbound sales cadence expert work, or mentions gx, outbound, cadence.
  • 100cold-email-sequence
    Use this skill when you need a complete cold email sequence (cadence) for a campaign: \"write a 4-step outbound sequence\", \"build an email campaign for this segment\", \"plan the follow-ups\". Designs the number of steps, spacing and angle of each email so every touch adds…
  • 100multichannel-cadence
    Use this skill when you need an outbound cadence that combines email, LinkedIn, phone and video so each touch builds on the last: \"build a multichannel sequence\", \"combine email and LinkedIn outreach\", \"plan a 3-week cadence for Tier 1 accounts\". Chooses channels by…
  • 100cold-email
    When the user wants to write cold outbound emails, craft prospecting email copy, build follow-up sequences, or fix emails that aren't getting replies. Also use when the user says 'write a cold email,' 'prospecting email,' 'outbound email copy,' 'follow-up email,' 'outreach…
  • 100gtm-outbound
    When the user wants an outbound sequence and copy — cadence, channels and messaging for a target profile. Use for 'outbound sequence', 'cold email sequence', 'LinkedIn outreach plan', 'write our outbound cadence', 'prospecting copy'. The plan and copy are advisory.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.