agentleFS
burnoutscriptburnoutscript/sales-skills/skills/outbound-sequence/SKILL.md

outbound-sequence

Skill0 starsChanged 14 days agoMITView on GitHub

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.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read .agents/sales-context.md if it exists.

    line 10
  2. Very specific:

    Ask: target tier (A/B/C), persona, number of accounts, channels the rep can actually do (phone?

    line 11
  3. Distinctive:

    Ask for current metrics if a sequence already runs: reply rate, positive reply rate, meetings per 100 prospects.

    line 12
  4. Distinctive:

    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 …

    line 21
  5. Distinctive:

    Test one variable at a time with at least ~200 prospects per variant before calling a winner.

    line 73
  6. Distinctive:

    follow-up: what happens after a reply or meeting.

    line 132

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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)

DayChannelStepJob of the step
1LinkedInView profile + followWarm the name; no request yet
1Email 1Observation -> implication -> askMain hook
2Call 1 + voicemailReference email 1Second channel, same story
3LinkedInConnection request, no pitchBuild a channel
5Email 2 (same thread)New proof point / case studyCredibility
7Call 2No voicemailConnect attempt
9LinkedInEngage with their post or send DM if connectedHuman touch
11Email 3 (new thread)Insight / teardown / benchmarkGive value
14Call 3 + voicemailDifferent angleLast call push
17Email 4Different persona angle or referral ask"Am I talking to the right person?"
21Email 5BreakupPermission 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.

MetricHealthyAction if below
Bounce rate< 2%Fix data source and verification; pause
Reply rate (all)3-8%Revisit targeting and email 1
Positive reply rate1-3%+Pain or proof is not resonating
Positive replies -> meeting50%+Faster response; reply with 2 times, not a link only
Meetings booked per 100 prospects1-3 (cold), 3-6 (triggered)Add phone, tighten tier
Connect rate on calls5-10% of dialsGet 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

# 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.

### 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.