AGENT SKILL

sales-followup-cadence

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.

License 许可
MIT
所属仓库
SkillMedev/skills
最近更新
2026-10-14
Stars
★ 25
Forks
3

01 前言 Front Matter

name
sales-followup-cadence
metadata
{ "title": "Sales Follow-Up Cadence" }
description
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.

03 SKILL.md 正文

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.

Step 1: gather inputs

  • What was discussed and what the buyer named as their top priority (their words, not the pitch's words).
  • Agreed next steps with owners and dates - including the action item the buyer owns.
  • Open questions left unanswered in the meeting.
  • Deal cycle length (default: standard B2B cycle; if transactional or expected to close within a week, use the compressed track below).
  • Two or three value-add candidates: a case study from a similar company, a relevant article, an answer to an open question. Label any assumption about the buyer's priority as a guess until they confirm it.

Cadence calendar

WARM TRACK (post-meeting, first 7 days)
Day 0   Email   Recap within 2 hours: discussed / their #1 priority /
                next steps w/ owners+dates / open questions. Confirms
                shared understanding + paper trail. Does not sell.
Day 2   Email   ONE value-add: case study, article on the problem they
                named, or answer to an open question. One link, one
                sentence of context. No pitch restatement.
Day 5   Email   Nudge THEIR action item: "Were you able to get time
                with your IT lead? Happy to join if useful."
Day 7   Email   Forward the Day 0 recap + one line: "Making sure this
                didn't get buried - has timing shifted?"

COLD TRACK (8-30 days of silence)
Day 10  LinkedIn or phone - different channel, not another email.
Day 17  Email   Useful-without-expectation: resource or insight, NO
                ask. Subject line does not reference the deal.
Day 25  Email   Breakup: "I don't want to keep reaching out if the
                timing is off. If things change and you want to
                revisit, I'm here - otherwise I'll close this out."

AFTER   Stop unless they re-engage. Park in 90-day re-engagement
        drip if still a fit. Never restart the same cadence.

COMPRESSED TRACK (transactional / <1-week cycles)
Day 0 recap → Day 2 value-add → Day 5 breakup.

That is 7 touches before the break - within the 5-7 touch band a stalled deal deserves. The breakup email gets more replies than almost any other touch in the cadence; sending it is not giving up, it is the highest-leverage move left.

Bad Day 5 touch: "Hi Sam, just circling back on my last email to see if you had any thoughts!" Good Day 5 touch: "Hi Sam - you mentioned looping in your IT lead before Friday. Were you able to get time with them? Happy to join that conversation and handle the security questions directly."

Deliverable

Produce a filled-in cadence calendar for the specific deal: each touch dated from the meeting, channel assigned, and value-add named in advance - plus the drafted Day 0 recap ready to send within the 2-hour window.

Do NOT

  • Do not send "just checking in" - a touch with no new information, no action-item motion, and no value teaches the buyer your emails are skippable.
  • Do not continue past the breakup email - following up after a polite close destroys the relationship and the brand, not just the deal.
  • Do not improvise touches day-of - unplanned follow-ups default to check-ins because the value-add was never sourced.
  • Do not restate the pitch in the Day 2 value-add - the recap already established fit; the value-add builds credibility instead.
  • Do not run the full 25-day cadence on a transactional deal - over-engineered follow-up on a one-week deal reads as desperate; use the compressed track.

Quality bar

Before the cadence ships: the Day 0 recap goes out within 2 hours and contains the buyer's stated priority in their own words plus next steps with owners and dates; every scheduled touch passes the three-purpose rule; at least one touch after Day 7 uses a non-email channel; the breakup is scheduled, not optional; and there is an explicit stop-and-park rule after touch 7. If the deal predates any meeting, this is the wrong skill - build the cold cadence in outreach-sequence-designer.

04 同仓库更多 Skills

SkillMedev
SkillMedev/skills

zone-2-cardio-plan

Use when someone asks to build a steady-state cardio plan, train an aerobic base or Zone 2, structure easy or endurance weekly cardio, train by heart-rate zones, or improve resting heart rate, VO2, or endurance. Builds a heart-rate-zone aerobic training block with session structure, modality choice, and progression. General fitness guidance, not medical advice. Do NOT use to design a strength or lifting program (use Strength Training Plan), high-intensity interval conditioning, HIIT, or circuits (use Conditioning & HIIT Program), or a mobility/flexibility routine (use Mobility Routine).

★ 25
SkillMedev
SkillMedev/skills

youtube-script-writer

Writes retention-engineered long-form YouTube scripts on a hook/body/payoff architecture - a first-30-seconds hook that survives the retention cliff, a beat-sheet body with mini-hooks and bridges, timed pattern interrupts, and a payoff that over-delivers - with B-roll and editing cues marked inline. Use when someone says "script my next video", "my retention graph dies at the start", "tighten this draft", or "outline a video on X". Do NOT use for the 3-second opener of TikTok, Reels, or Shorts - use video-hook-writer instead; do NOT use for spoken voiceover synced to on-screen tutorial actions - use narration-script instead; do NOT use for a sales demo built on a buyer's discovery notes - use demo-script instead; do NOT use to design the thumbnail and title - use thumbnail-concept instead.

★ 25
SkillMedev
SkillMedev/skills

win-back-campaign

Designs segmented win-back email sequences for dormant users - dormancy tiers, a three-beat sequence with a single proportional incentive, and a suppression rule - and measures success by re-activation, not opens. Use when someone says "our users went quiet", "design a win-back campaign", "how do I re-engage lapsed customers", "should we email people who haven't logged in for months", or lifecycle messaging has stopped landing with a lapsed segment. Do NOT use for recovering an unfinished checkout - use abandoned-cart-sequence instead. Do NOT use for diagnosing and fixing why active customers cancel - use churn-reduction instead. Do NOT use for building always-on onboarding or nurture flows - use email-drip-builder instead.

★ 25
SkillMedev
SkillMedev/skills

wikipedia-style

Writes neutral, verifiable, encyclopedic prose following Wikipedia's core content policies and manual of style - NPOV, inline citations, notability-backed claims, and a strict ban on promotional language. Use when someone asks "write this like a Wikipedia article", "draft a Wikipedia page for this company or person", "make this neutral and encyclopedic", or "why does my article draft keep getting rejected". Do NOT use for persuasive or opinion writing - use op-ed-writer instead; for thesis-driven academic papers, use academic-essay; for verifying claims in existing text, use fact-checker.

★ 25
SkillMedev
SkillMedev/skills

whitepapers

Structures and writes authoritative B2B whitepapers - a standalone executive summary, a data-sized problem statement, methodology, evidence-driven findings, recommendations, and a soft call to action - flagging every claim that needs a real citation. Use when a marketer asks "write a whitepaper on this topic", "turn our research into a lead-gen asset", "make this credible enough for executives", or a draft reads like a product pitch instead of analysis. Do NOT use for customer-story-driven proof - use case-study-builder instead; for policy audiences, use policy-brief.

★ 25
SkillMedev
SkillMedev/skills

white-space-analysis

Finds unmet market gaps by ranking jobs-to-be-done on importance versus satisfaction, overlaying them against current solutions and workarounds, and validating that each gap is real, winnable, and worth winning. Use when someone asks "where are the gaps in this market", "what's underserved here", "where should we play next", or is hunting for product, feature, or market-entry opportunities. Do NOT use for profiling competitors and building battle cards - use competitive-intelligence instead; for putting a dollar figure on an identified opportunity - use market-sizing instead; for extracting jobs-to-be-done from raw customer interviews - use jtbd-extractor instead.

★ 25