Design an outbound cadence where every touch has a point.
The steps, timing, channel, and intent of each touch, tuned to the segment's value.
Inside: The touch plan, the timing, the channel mix, and a clean break-up.
Install it in one line, or paste it in.
~/.claude/skills/ and runs automatically when it is relevant.Connect your context. Set it to your motion.
it reads segment history and past outcomes so the shape reflects what has worked, not a guess.
it loads the steps, channels, and timing straight into a sequence you can turn on.
pulls phone and social coverage so it only plans channels you can reach on.
This was built for B2B outbound to a defined segment. Set these to your motion:
Build for any segment you like. A high-value segment earns more manual, personalized touches; a broad one runs lighter. The skill tunes the shape to the segment, not a fixed template.
| Set this | What it is | Default / Example |
|---|---|---|
| SEGMENT | who this cadence targets | persona plus tier or fit |
| CHANNELS | what you can actually run | emailphoneLinkedInvideo |
| DURATION | how long the cadence runs | 14 to 21 days (re-tune) |
| TOUCH_COUNT | total touches across channels | 8 to 12 (re-tune to segment) |
| INTENSITY | how tightly touches cluster | front-loaded vs even |
| OFFER | the one problem you solve | stated in the buyer's words |
| SEQUENCER | where the steps run | a sequencer you already run |
| CRM | your CRM connector | a CRM you already run |
Everything the skill does, in full.
Designs a full outbound cadence for a segment: how many touches, over how many days, on which channels, and what each touch is actually for. Every step has an intent, so the cadence builds a case across email, phone, and social instead of nagging the same person the same way eight times.
- 1Every touch has an intent
No step exists just to hit a number. Each touch is tagged with its job: introduce the problem, add a proof point, change the channel, break the pattern, or make the graceful last ask. If a touch has no distinct intent, it gets cut, not padded.
- 2Multi-channel by design
The cadence spreads across the channels you actually run, so a prospect who ignores email might answer a call or a LinkedIn note. Channels reinforce each other: a call references the email, the social touch references both. One story, several doors.
- 3Timing and spacing
Touches cluster early when attention is freshest, then space out. The default runs 8 to 12 touches over 14 to 21 days, front-loaded, with room to breathe near the end. Segment sets the intensity: a strong-fit segment earns tighter, higher-effort touches; a broad one runs lighter and longer.
- 4Tune the effort to the segment
High-value segments get more manual, researched touches and fewer templated ones. Broad segments get efficient, repeatable steps. The skill sets the mix so you are not hand-writing a video for a low-fit lead or blasting a template at a must-win account.
- 5A clean ending
The last touch is an honest break-up: one graceful, low-pressure close that gives the prospect an easy exit and often earns a reply. No touch 13. No fake "final notice."
- Every touch carries a distinct intent. No filler steps to pad a number.
- The cadence spans more than one channel wherever coverage exists.
- Touch effort matches segment value. No hand-crafted touches for low-fit leads, no pure templates for must-wins.
- The cadence ends with a clean break-up, never an endless nag.
CADENCE · segment: mid-market RevOps · 10 touches / 18 days Day Channel Intent 0 Email Introduce the problem + soft CTA 1 LinkedIn Connection request, no pitch 3 Phone Reference the email, permission opener 5 Email One proof point, new angle 7 LinkedIn Value-first message (resource) 9 Phone Second dial, different time of day 12 Email Short case-style example 14 Video Pattern break, personal 30-sec note 16 Phone Last live attempt 18 Email Graceful break-up, easy exit Effort mix: 3 personalized touches (video, first email, breakup), 7 efficient templated touches. Tighten for higher-fit accounts.
Where an operator takes this next.
The design is step one. Here is where an operator takes it once the shape holds.
Build the intent map once and the cadence stops being a static template. It reshapes itself to the segment in front of it, then goes live where your team already sends.
Connect Salesforce so the cadence reads the segment's past outcomes and weights the channels that actually convert, instead of a sensible default.
Wire an enrichment tool like Clay for phone and social coverage, so the cadence never schedules a dial for a number you don't have.
Push the steps, channels, and timing straight into your sequencer, so the design becomes a running sequence the same day instead of a doc someone has to rebuild by hand.
One skill is the on-ramp.
A single skill does one job. Chained into a playbook, or run as a full build, it becomes a system. Here is where this one plugs in.