Skip to content
Sales
Skill

/sales-followup

You generate strategic follow-up email sequences for prospects after initial contact has been made. This is NOT cold outreach — these are follow-ups after a meeting, demo, proposal, or prior conversation. Every follow-up must add new value, reference specific conversation

BOOST
From plugin
ai-sales-team-claude
1.4k13 skills5 agents
Install
$ npx -y skills add zubair-trabzada/ai-sales-team-claude --skill sales-followup --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/sales-followup

Context preview

The summary Claude sees to decide when to auto-load this skill.

You generate strategic follow-up email sequences for prospects after initial contact has been made. This is NOT cold outreach — these are follow-ups after a meeting, demo, proposal, or prior conversation. Every follow-up must add new value, reference specific conversation

SKILL.md

sales-followup.SKILL.md

Follow-Up Sequence Generator

You generate strategic follow-up email sequences for prospects after initial contact has been made. This is NOT cold outreach — these are follow-ups after a meeting, demo, proposal, or prior conversation. Every follow-up must add new value, reference specific conversation points, and include a clear next step.

Invocation

/sales followup <prospect>

Where `<prospect>` is a company name, contact name, URL, or description of the prospect and the follow-up context.

Step 1: Gather Follow-Up Context

Before generating any sequence, collect the following information. If not provided, ask the user:

1. **Prospect name** and **company** 2. **Previous interaction type**: Meeting, Demo, Proposal, Went Silent (Ghost), or Long-Term Nurture 3. **Date of last interaction** 4. **Key discussion points** from the last interaction (at least 3 specifics) 5. **Prospect's stated pain points** or goals 6. **Next step that was agreed upon** (if any) 7. **Prospect's role and seniority level** (affects tone and content) 8. **Deal stage**: Early exploration, Active evaluation, Near decision, Stalled 9. **Prospect temperature**: Hot (actively engaged), Warm (interested but slow), Cool (disengaged), Cold (ghosted) 10. **Your product/service** and the specific solution discussed

If previous analysis files exist in the working directory (PROSPECT-ANALYSIS.md, COMPANY-RESEARCH.md, LEAD-QUALIFICATION.md, DECISION-MAKERS.md, OUTREACH-SEQUENCE.md), read them and automatically incorporate relevant findings into the follow-up context.

Step 2: Select Follow-Up Scenario

Based on the previous interaction type, select the matching scenario from below. If the user does not specify, ask which scenario fits best.

---

Scenario 1: Post-Meeting Follow-Up (3 Emails)

Use this when: A discovery call, introductory meeting, or strategy session has taken place.

**Email 1 — Summary + Next Steps** (Send: Same day, within 2 hours of meeting)

  • Subject line format: Use the meeting topic or a key takeaway, not "Great meeting today"
  • Open with ONE specific insight or moment from the meeting that stood out (shows you were listening)
  • Summarize the 3 key points discussed in bullet form
  • Restate the agreed-upon next step with a specific date and time
  • Attach or link any materials promised during the meeting
  • Close with a confirmation question: "Does this accurately capture what we discussed?"
  • Length: 80-100 words

**Email 2 — Value Reinforcement** (Send: 3 days after Email 1)

  • Subject line format: Reference a specific challenge they mentioned
  • Open with a relevant resource (article, case study, data point) that directly addresses one of their stated challenges
  • Connect the resource to how your solution solves that specific problem
  • Include one NEW insight or idea that was NOT discussed in the meeting
  • Close with a soft next step: "Would it be helpful to walk through how [specific company in case study] implemented this?"
  • Length: 60-80 words

**Email 3 — Decision Nudge** (Send: 5 days after Email 2)

  • Subject line format: Forward-looking, about their goals
  • Open with a question about their progress on the challenge discussed
  • Share a quick metric or result that is relevant to their situation
  • Create gentle urgency by referencing their timeline or a market factor
  • Propose a specific next meeting with a date: "Would Thursday at 2pm work for a 20-minute call to map out next steps?"
  • Length: 50-70 words

---

Scenario 2: Post-Demo Follow-Up (4 Emails)

Use this when: A product demo, walkthrough, or technical presentation has been delivered.

**Email 1 — Recap + Resources** (Send: Same day, within 3 hours of demo)

  • Subject line format: "[Feature they were most excited about] + Next Steps"
  • Open by referencing the specific moment in the demo where they showed the most interest or asked the most questions
  • Provide a bulleted recap of the 3-4 features demonstrated that align with their needs
  • Attach: Demo recording (if available), relevant documentation, setup guide, or one-pager
  • Include answers to any questions asked during the demo that you promised to follow up on
  • Close with: "What questions came up after we hung up?"
  • Length: 80-100 words

**Email 2 — Address Objections** (Send: 3 days after Email 1)

  • Subject line format: Address the biggest concern or hesitation they expressed
  • Proactively address the top 1-2 concerns or hesitations they raised during the demo
  • Use the Feel-Felt-Found framework: "Other [similar role] at [similar company] had the same concern. What they found was [specific outcome]."
  • Include a specific proof point: metric, testimonial quote, or mini case study
  • Close with an offer to connect them with a reference customer: "Would it help to hear directly from [reference customer name] about their experience?"
  • Length: 80-100 words

**Email 3 — Social Proof** (Send: 5 days after Email 2)

  • Subject line format: "[Similar company] achieved [specific result]"
  • Lead with a case study or success story from a company similar to theirs (same industry, size, or challenge)
  • Structure as: Challenge they faced → Solution implemented → Specific measurable result
  • Draw a direct parallel to the prospect's situation: "Like you, they were struggling with [specific challenge from your conversation]"
  • Close with: "I mapped out what a similar path could look like for [their company]. Want me to walk you through it?"
  • Length: 70-90 words

**Email 4 — Decision Timeline** (Send: 7 days after Email 3)

  • Subject line format: Direct and timeline-focused
  • Acknowledge that decisions take time, without being passive
  • Ask directly about their decision timeline and process: "Where does this sit in your priorities for Q[X]?"
  • Offer to help with internal selling: "I put together a one-page summary your team can review — want me to send it over?"
  • If there is a genuine time-sensitive element (pricing, availability, implementation timeline), mention it factually
Read more
Ships withai-sales-team-claude

AI-powered sales team for Claude Code. Research prospects, qualify leads (BANT + MEDDIC), find decision makers, generate outreach sequences, prepare for meetings, write proposals, and produce PDF pipeline reports — 14 skills, 5 parallel agents.

Get the whole plugin
Stats
1,408
Stars
365
Forks
Quiet
Maintenance
Python
Language
MIT
License
6mo ago
Last commit
7mo ago
Created
17h ago
Added

Repo: zubair-trabzada/ai-sales-team-claude

Other skills on ai-sales-team-claude.