agentleFS
automatewithudayautomatewithuday/gtm-prospecting-system/skills/follow-ups/SKILL.md

follow-ups

Skill1 starsChanged 58 days agoMITView on GitHub

Use when stage 16 of the prospecting system needs the follow-up steps, timing, and channel mix drafted around the first-touch email and LinkedIn note. Also use standalone to design a multi-step outbound sequence.

7 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

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Follow-up copy rules live in /cold-email section 7.

    line 18
  2. Distinctive:

    Every email step should have 2-3 variants to enable testing:

    line 79
  3. Distinctive:

    Only test ONE variable per variant pair (subject OR body, not both)

    line 89
  4. Distinctive:

    Use a consistent naming structure so performance data is analyzable:

    line 151
  5. Distinctive:

    Don't over-engineer your first sequence.

    line 216
  6. Distinctive:

    Keep a "swipe file" of every reply you get — positive and negative.

    line 217
  7. Distinctive:

    If your open rate drops below 40% mid-campaign, stop sending.

    line 218

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “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

Sequence Architecture

Pipeline contract

Stage 16 of 20. Reads 14-emails.csv, 15-linkedin.csv. Writes 16-sequence.md (steps, day offsets, channel per step) and 16-followups.csv (segment, step, day_offset, channel, subject, body).

  • Each follow-up adds something new (proof, angle, resource). A bump that only says "following up" does not ship.
  • Follow-up copy rules live in /cold-email section 7; this skill owns order, timing, and escalation.
  • Drafts only. Sequence settings are a recommendation for the human's sender.

Files live in runs/<run>/. Column definitions: /prospecting-system. Standalone use: ignore this block.

When to Use

  • Building a new outbound campaign from scratch
  • Restructuring sequences with poor step-2+ engagement
  • Designing multi-channel cadences (email + LinkedIn + phone)
  • Setting up A/B testing frameworks for sequence optimization

Framework

Sequence Design Principles

  1. Every step earns the next — Step 1's job is to get Step 2 opened. Step 2's job is to get a reply. Never front-load everything into Step 1.
  2. New value every touch — Each step must introduce a new angle, insight, or proof point. "Following up" is not a strategy.
  3. Decay is natural — Open and reply rates drop with each step. Design for this: your best material goes in Steps 1-2, your boldest ask goes in the final step.
  4. Variants multiply learning — Run 2-3 subject/body variants per step. At 200+ sends per variant, you have statistical significance.

The 4-Step Core Sequence

This is the baseline architecture. Adapt timing and angles to your ICP.

StepDayChannelObjectiveAngle Strategy
10EmailOpen + ReplyLead with strongest signal or observation
23-4EmailReplyNew value: resource, benchmark, or case study
37-8EmailReply or ReferralSocial proof or creative ideas angle
414EmailClose or RedirectBreakup ("should I close this out?") or referral ask

Total campaign duration: 14 days Total touches: 4 emails


Extended Sequence (Multi-Channel)

For high-value accounts or enterprise targets, layer in LinkedIn and phone:

StepDayChannelObjective
10EmailSignal-based opening
21LinkedInConnection request with personalized note
33EmailNew value angle
45LinkedInEngage with their content (like/comment)
57EmailCase study or social proof
68Phone"Following up on the email I sent"
710LinkedInDirect message with resource
814EmailBreakup or referral

Total campaign duration: 14 days Total touches: 8 (4 email + 3 LinkedIn + 1 phone)


Variant Strategy

Every email step should have 2-3 variants to enable testing:

Variant TypeWhat You're TestingExample
Subject variantsWhich framing gets opensA: {{company}} outbound vs B: quick question
Opening variantsWhich personalization resonatesA: Signal-based vs B: Problem-based
CTA variantsWhich ask gets repliesA: "Worth a look?" vs B: "Want me to send the playbook?"
Angle variantsWhich value prop convertsA: ROI-focused vs B: Time-savings-focused

Testing rules:

  • Only test ONE variable per variant pair (subject OR body, not both)
  • Minimum 200 sends per variant before drawing conclusions
  • Winner = highest positive reply rate (not total reply rate — ignore "not interested" replies)
  • Rotate winning variants into the "control" and test new challengers

Timing Optimization

FactorRecommendationWhy
Send daysTuesday-ThursdayMonday = inbox overload. Friday = checked out.
Send window8:00 AM - 11:00 AM prospect's timezoneCaught during morning email triage
Step gaps3-4 days between emailsEnough to not feel pushy, close enough to maintain context
Reply windowCheck within 30 min of sendsFast replies to "interested" responses 3x close rate
Match lead ESPEnabledSend from Gmail to Gmail, Outlook to Outlook — improves deliverability

Sequence Settings Checklist

Configure these before launching any campaign:

SettingValueReason
Stop on replyONNever email someone who already responded
Stop on auto-replyOFFAuto-replies (OOO) shouldn't kill the sequence
Text onlyONHTML emails trigger spam filters more often
Link trackingOFFTracking pixels and links hurt deliverability
Open trackingOFFSame — open tracking = invisible pixel = spam risk
Daily send limitPer account limitsRespect your email provider's sending limits
Email gap10-20 minutesTime between individual sends — avoids burst patterns
Random delay5-10 minutesAdds randomness to look human

Escalation Logic

What happens when the standard sequence doesn't convert:

Standard Sequence (14 days)
    ↓ No reply
Wait 30 days
    ↓
Re-engagement Sequence (different angle, 3 steps)
    ↓ No reply
Wait 60 days
    ↓
Trigger-based Re-entry
    (Only re-enter if new signal detected: funding, hiring, tech change)

Never:

  • Re-enroll someone in the same sequence
  • Contact someone who explicitly said "not interested"
  • Send more than 2 sequences to the same person in 6 months without a new signal

Campaign Naming Convention

Use a consistent naming structure so performance data is analyzable:

{Client} - {Segment} - {Angle} - {Version}

Examples:

  • Acme - Enterprise VP Sales - Hiring Signal - v1
  • Acme - SMB Founders - Referral Ceiling - v2
  • Acme - Mid-Market Growth - Tech Stack Change - v1

This makes it trivial to filter analytics by client, segment, or angle.


Architecture Decision Tree

Is the target account high-value (>$50K ACV)?
├── YES → Extended Multi-Channel Sequence (8 touches, 14 days)
│         Layer email + LinkedIn + phone
│         Personalize every touch individually
│
└── NO → Standard 4-Step Email Sequence (4 touches, 14 days)
         Use signal-based personalization at scale
         Rely on variants for optimization

Is this a new persona/segment you haven't tested?
├── YES → Run 3 variants of Step 1 with 200+ sends each
│         Wait for data before building Steps 2-4
│
└── NO → Clone your best-performing sequence
         Swap personalization for new segment
         Keep winning structure intact

Templates

Campaign Launch Checklist

Pre-Launch:
- [ ] ICP and persona defined
- [ ] Lead list built and verified (bounce rate < 3%)
- [ ] Email accounts warmed (2+ weeks, 30+ emails/day)
- [ ] Sequence written (2-3 variants per step)
- [ ] Settings configured (tracking off, text-only, stop on reply)
- [ ] Naming convention applied
- [ ] Test send to yourself and team for QA

Post-Launch (Day 3):
- [ ] Check open rates (target: 60%+)
- [ ] Check bounce rate (must be < 3%)
- [ ] Check spam complaints (must be 0)
- [ ] Review any replies for pattern recognition

Post-Launch (Day 14):
- [ ] Calculate positive reply rate per variant
- [ ] Identify winning variants
- [ ] Document learnings
- [ ] Plan next iteration

Tips

  • Build your sequence backwards — write the breakup email first, then work back to Step 1. This forces you to think about the full arc.
  • The best Step 2 is a reply to Step 1 (literally in the same thread), not a new email. This uses the "thread effect" for higher opens.
  • Don't over-engineer your first sequence. Launch with 4 steps, 2 variants each, and iterate from data. Perfection before launch = wasted time.
  • Keep a "swipe file" of every reply you get — positive and negative. The language prospects use to say "yes" and "no" is gold for future copy.
  • If your open rate drops below 40% mid-campaign, stop sending. You have a deliverability problem, not a copy problem.

Progressive disclosure: load channel-specific templates and industry playbooks only when building sequences for a specific campaign.

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.