sales-outbound-sequence

The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.

---
name: sales-outbound-sequence
description: Plans a touch-by-touch outbound cadence - which channel on which day, touch count, spacing, channel mix, multi-threading, exit and stop rules, recycle and re-entry, and the capacity math behind it, with pre-committed metric thresholds. Use whenever the user mentions a sequence, cadence, follow-up timing, Outreach or Salesloft steps, a drip, "how many touches", inbound-lead or event follow-up, closed-lost re-engagement, or B2C lifecycle and SMS flows, even without the word cadence. Do NOT use for message copy, subject lines (mbfinotti/sales-skills@cold-email-subject-line-tester), call scripts (mbfinotti/sales-skills@cold-call-opener), or inbox placement (mbfinotti/sales-skills@cold-email-deliverability).
license: MIT
metadata:
  author: Maya-Beth Finotti
  version: "1.3.6"
---

# Outbound Sequence

Design the skeleton of an outbound cadence - the touch-by-touch plan of channels, days, spacing, exits, and recycling - sized to the user's segment, list, and rep capacity, with metric thresholds committed before launch.

Two facts frame everything here:

- **Cadence length is contested.** Sales-training practitioners and sales-engagement vendors teach roughly 10-15 touches over 14-30 days. Email-quality vendors and outbound agencies cap it at 3-5 emails, fewer when multi-channel, and call long sequences a symptom of low relevance. Neither is law: this skill applies a decision rule instead of picking a side, see [references/cadence-patterns.md](references/cadence-patterns.md).
- **Most figures are vendor-published.** Nearly every statistic in the references comes from companies selling outreach tooling - trust the direction, never the magnitude, and label it as vendor-published when quoting it to the user. The only hard numbers are mailbox-provider policies (spam-complaint ceilings), flagged as platform policy where they appear.

Scope: the cadence plan is the whole deliverable. Never write message copy in depth, route it to the sibling skill for that copy type:

- Subject lines: `mbfinotti/sales-skills@cold-email-subject-line-tester`
- Call openers: `mbfinotti/sales-skills@cold-call-opener`
- Personalization-angle selection: `mbfinotti/sales-skills@sales-outreach-personalization`
- Rebuttals: `mbfinotti/sales-skills@sales-objection-handling`
- Post-meeting follow-up: `mbfinotti/sales-skills@sales-meeting-recap`

Never audit deliverability, domains, or authentication - plan within the sending constraints, then hand the audit to `mbfinotti/sales-skills@cold-email-deliverability`.

## Interview

- Ask one question per message.
- Offer multiple-choice options.
- Skip anything context already answers.

If your harness has persistent memory and a prior run stored this user's answers, confirm them instead of re-asking.

1. Regime: B2B outbound to businesses, or B2C to consumers? Ask first - consent, speed, and volume rules diverge.
2. By what date must this land results? A hard near date promotes the short pattern, the near-zero channels, and reply rate as the committed metric. A soft date lets the long multi-channel pattern and meetings-per-100 back in.
3. A one-off win, or a compounding asset? One-off promotes a single sprint on the best-scored cohort. Compounding promotes staggered cohort entry, a recycle window, and the trigger-watching that makes re-entry work - all of which cost more now and pay from cohort two onward.
4. Effort ceiling: rep hours per day, headcount, and how much sender risk is acceptable? A founder doing their own outbound has no daily call block, which deletes the manual channels rather than demoting them. A new or warm-up-limited domain caps email touches at any budget and promotes the call block instead.
5. Motion: cold outbound, inbound-lead follow-up, event follow-up, or closed-lost/dormant re-engagement? For B2C: which lifecycle trigger - signup, cart or browse abandonment, win-back?
6. B2B segment: SMB high-velocity, mid-market, or enterprise ABM? This drives the