agentleFS
BenPremBenPrem/business-brain/.claude/skills/follow-up-nurture/SKILL.md

follow-up-nurture

Skill1 starsChanged 3 months agoMITView on GitHub

Manage pipeline follow-ups by lead stage - reply handling, proposal cadence, re-engagement ladder, meeting confirmations - against workspace records and <TASK SYSTEM>. Trigger on follow up, check the pipeline, who needs a follow-up, nurture, what's next with [name]. NOT for first-touch outreach (use cold-email) - this skill handles everything AFTER the first email is sent.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    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:

    Read the pipeline in <TASK SYSTEM> and the workspace lead records.

    line 8
  2. Distinctive:

    Check <TASK SYSTEM> for active leads with a follow-up due today

    line 21
  3. Distinctive:

    Read each matching workspace record for notes, pain points, last contact, proposal links, and next-step context

    line 24
  4. Distinctive:

    Read the reply. Categorize:

    line 33
  5. Distinctive:

    After drafting: move the task to the right stage (Meeting Booked or Closed Lost) and write the follow-up note/date into the workspace …

    line 43
  6. Distinctive:

    Prep brief: run discovery-call-prep — it owns the internal brief.

    line 69
  7. Distinctive:

    Never discount without adjusting scope — add or remove deliverables instead

    line 76
  8. Distinctive:

    All follow-ups inherit the cold-email skill's tone rules:

    line 83
  9. Distinctive:

    No spam trigger words, no dollar signs, no hyperlinks in cold-pipeline sends

    line 87
  10. Distinctive:

    After every follow-up action:

    line 96
  11. Distinctive:

    When a lead goes Closed Lost, look for the pattern: follow-up too late → tighten the timing table.

    line 125

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

Read the pipeline in <TASK SYSTEM> and the workspace lead records. Identify who is due for contact. Draft the right follow-up for their stage.

Routing

  • Writing the first cold email → cold-email
  • Known contact with no active sales stage → email-composer
  • Everything after the first touch, by stage → this skill

Step 1 — Pull leads due for follow-up

  • Check <TASK SYSTEM> for active leads with a follow-up due today
  • Filter for stages: Reply Received, Proposal Sent, Meeting Booked, Negotiating, Contacted
  • Read each matching workspace record for notes, pain points, last contact, proposal links, and next-step context

Step 2 — Prioritize by stage (highest urgency first)

Reply Received (respond same day)

Read the reply. Categorize:

Reply typeActionTone
InterestedPropose 2-3 meeting timesWarm, confident, match their energy
QuestionAnswer directly, re-present the CTAHelpful, brief
"Not now"Acknowledge, ask to follow up in 60-90 daysGraceful, zero pressure
Not interestedThank them, close the leadProfessional, brief
Auto-reply / OOONote return date, set follow-up for itNo response needed

After drafting: move the task to the right stage (Meeting Booked or Closed Lost) and write the follow-up note/date into the workspace record.

Proposal Sent (touch at 3, 7, 14 days)

DayMessage
3Quick check-in. "Any questions about the proposal?" One sentence + the question.
7Add value — one insight or idea NOT in the proposal. Show you are still thinking about their business.
14Gentle breakup. "I know timing matters. Want me to check back in a month?" Usually the highest-response touch.

Contacted, no reply (10+ days)

Confirm from the activity log what first touch actually happened — never assume a sequence ran.

TimeframeAction
~14 daysCompletely different angle — new hook, different service, new subject. Never "just checking in."
30 daysOne more attempt referencing something timely (season, local event, industry trend). Last touch before archiving.
45+ daysMove to Cold. Revisit only on a trigger event (news, site visit, hiring).

Meeting Booked

  • Immediately: confirmation with date/time, brief agenda, what to expect
  • 24 hours before: short, friendly reminder
  • Prep brief: run discovery-call-prep — it owns the internal brief; do not rebuild it here

Negotiating (case by case)

  • Respond within 1-2 days
  • Address the specific objection directly
  • Never discount without adjusting scope — add or remove deliverables instead
  • Reference the cost of inaction subtly (StoryBrand stakes)

Step 3 — Draft the follow-ups

All follow-ups inherit the cold-email skill's tone rules:

  • Prospect is the hero — never open with "I" or "we"
  • Under 100 words (shorter than initial outreach)
  • No spam trigger words, no dollar signs, no hyperlinks in cold-pipeline sends
  • Trying a new angle → reuse cold-email's hook structure

Present all drafts to the founder for review. Never send without approval.


Step 4 — Update records

After every follow-up action:

  • Workspace record: last contact date, next follow-up date, current stage, short note
  • <TASK SYSTEM>: task stage and due date, moved forward when appropriate

Step 5 — Report

Pipeline Follow-Up Report — [date]
==================================
Replies handled: X  (meetings booked: X · closed lost: X)
Proposals followed up: X
Re-engagement drafted: X
Next follow-ups due tomorrow: X

Pipeline health:
  Reply Received: X (respond today)
  Meeting Booked: X
  Proposal Sent: X
  Contacted (waiting): X
  Total active: X

Self-improvement

When a lead goes Closed Lost, look for the pattern: follow-up too late → tighten the timing table; tone too pushy or too passive → adjust guidance; missed buying signal → add a classification rule. Log durable lessons to your rules file.

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.