Menu

Individual skill

sales-followup-cadence

0upvotes

Designs a post-meeting follow-up cadence for active deals - recap within 2 hours, value-add touches on a day 0/2/5/7 rhythm, channel switches when a deal goes quiet, and a clean breakup after 5-7 touches. Use when someone says "the prospect went dark after the demo", "how do I follow up without being annoying", "what should I send after the call", or a deal has stalled between meetings. Do NOT use for cold-prospect sequences before any meeting has happened - use outreach-sequence-designer instead; do NOT use for writing the cold email itself - use cold-email-craft instead; do NOT use for structuring the close with shared milestones - use mutual-action-plan instead.

skills/sales-followup-cadence/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Sales Follow-Up Cadence

Follow-up is where most deals are won or lost after the meeting ends. The rep who follows up with something useful every time earns the right to stay in the conversation; the rep who sends "just checking in" trains the buyer to ignore them, and the costly version of that mistake is continuing past a polite close and burning the account for the whole company. Every touch needs a reason to exist, and the cadence needs a defined end.

## Operating procedure

Order matters: the Day 0 recap creates the shared record that every later touch references - skip it and every follow-up becomes a cold restart.

1. Gather the inputs below immediately after the meeting, while memory is fresh.
2. Send the Day 0 recap within 2 hours of the meeting.
3. Schedule the warm cadence (Days 2, 5, 7) in the CRM now, each touch pre-assigned a value-add - do not improvise touches on the day.
4. Before sending any touch, test it against the core rule: does it add new information, move an action item forward, or give the buyer something genuinely useful for their job? "Touching base" and "circling back" fail this test - rewrite or skip.
5. If silence continues past Day 7, shift to the cold-deal track (Days 10, 17, 25) with a channel switch.
6. Send the breakup at touch 7 (Day 25). Then stop. Park the contact in a 90-day re-engagement drip if the product remains a fit.