agentleFS
akash-joshiakash-joshi/agent-skills/skills/cold-outreach/follow-up-sequences/SKILL.md

follow-up-sequences

Skill8 starsChanged 3 months agoMITView on GitHub

Build multi-channel follow-up sequences that close deals. Use when the user's outreach isn't getting replies, needs a follow-up cadence, or wants to know how many times to follow up. Also use when the user mentions "follow up," "no reply," "they ghosted me," "how many times should I message," "multi-channel outreach," or "outreach cadence." Most deals close on the 3rd-5th touch, not the first. For writing the initial DM, see cold-dm.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do:: add new value with each follow-up (case study, insight, relevant article).

    line 53
  2. Distinctive:

    Keep a simple spreadsheet or CRM (Name, Company, Platform, Date Sent, Touch #, Reply?, Next Action).

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Follow-Up Sequences

Most people give up after one message. Most deals close on the 3rd-5th touch. Your job is to help the user build persistent, respectful follow-up systems.

The Core Principle

If they don't reply on one platform, don't stop there. The same person who ignores your Twitter DM might respond instantly on Telegram because that's where they actually spend their time.

The Multi-Channel Follow-Up Cadence

Standard 5-Touch Sequence

TouchTimingChannelPurpose
1Day 0Primary (where you found them)Initial outreach (see cold-dm)
2Day 2-3Same channelBrief follow-up, add new value
3Day 5-7Different channelCross-platform reach (LinkedIn → Telegram, or X → email)
4Day 10-14Original or third channelShare relevant content/case study
5Day 21-30Any channelFinal check-in, leave door open

Follow-Up Message Templates

Standard follow-up (touches 2-4, adapt to the channel in the table above):

Hey [name], just following up on my message about [specific thing]. 

Thought this might be relevant — [link to case study / relevant work / article].

No pressure either way, just wanted to make sure it didn't get buried.

For touch 3 (switching channels), swap the opener for "I reached out on [platform] about [specific thing] — wanted to try you here in case that's easier." The shape stays the same either way: reference the previous message, add one piece of new value, close with a low-friction ask.

Final touch (day 21-30, leave the door open):

Hey [name], last one from me — I know timing isn't always right.

If [your service] ever becomes relevant, I'm here. Good luck with [their project].

Finding Them on Other Channels

When they don't reply on the original platform: check their Twitter bio for a LinkedIn link, use TG Finder (tgfinder.xyz) to find Telegram handles from domains, or use Hunter.io/Apollo to find email from their website. If they're in industry Telegram/LinkedIn groups, DM directly there. Website contact forms are a last resort but show persistence.

Rules

Do: add new value with each follow-up (case study, insight, relevant article); reference your previous message; keep each follow-up shorter than the last; space them out (don't message 3 times in one day); accept "no" gracefully.

Don't: copy-paste the same message repeatedly; follow up more than 5 times without a reply; get passive-aggressive ("I guess you're not interested..."); apologise for following up; send long messages (each follow-up should be 2-3 sentences max).

Tracking

Keep a simple spreadsheet or CRM (Name, Company, Platform, Date Sent, Touch #, Reply?, Next Action). Review weekly. After 5 touches with no reply, archive and move on. Circle back in 3 months with a "just checking in" if relevant.

Related Skills

  • cold-dm — write the initial outreach message
  • keyword-search — find new prospects when current ones don't convert
  • discovery-calls — handle the call when a follow-up finally gets a reply

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.