agentleFS
burnoutscriptburnoutscript/sales-skills/skills/follow-up/SKILL.md

follow-up

Skill0 starsChanged 15 days agoMITView on GitHub

Writes post-meeting recap emails, mutual action plans and re-engagement messages for deals that went quiet, keeping momentum with clear next steps and owners. Use when the user asks for a "meeting recap", "follow up after the demo", "prospect ghosted me", "mutual action plan", "close plan", or "how do I revive this deal". For first-touch outbound, see outbound-sequence.

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use call-prep, mock-interview and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    call-prep

    Prepare for a customer or prospect call using Common Room signals. Triggers on 'prep me for my call with [company]', 'prepare for a meeting with [company]', 'what should I know before talking to [company]', or any call preparation request.

    Also in 3 projects that use this

  • aslavchevSkill

    mock-interview

    Simulate a real job interview for any role. Use when user says "mock interview", "interview me", "interview prep", "practice interview", or wants to rehearse for a specific company or position. Adapts rounds and questions to the role — technical, managerial, creative, or any other.

    Also in 3 projects that use this

  • jwilgerSkill

    pipeline

    Autonomous build-phase orchestrator with 8-stage per-slice pipeline (decompose, slice readiness review, implement via TDD pairs, three-stage code review, address feedback, mutation testing, push/CI, merge/flag). Manages slice queue (walking skeleton first, dependency ordering), dispatches TDD pairs with capability detection, enforces 5 binary quality gates with 3-cycle rework budgets and human escalation, maintains audit trail, and respects strict controller boundaries (never writes code, delegates all creative work). Supports three autonomy levels (conservative/standard/full). Use when running factory mode, orchestrating build phases, managing slice queues, or coordinating TDD pairs with review gates. Triggers on: "run the pipeline", "factory mode", "build phase", "slice queue", "quality gates", "autonomous build". NOT for: individual TDD (use tdd), standalone code reviews (use code-review), CI-only workflows (use ci-integration).

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 5

    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:

    Read .agents/sales-context.md if it exists (stages, proof, voice).

    line 10
  2. Distinctive:

    Ask which situation applies: (A) recap after a meeting, (B) mutual action plan, or (C) re-engaging a quiet deal.

    line 11
  3. Distinctive:

    Use their words for the pains, not your marketing words.

    line 19
  4. Distinctive:

    Put the next step and date in the first 3 lines.

    line 20
  5. Distinctive:

    Use for any deal with 3+ stakeholders or a cycle over 30 days.

    line 48
  6. Distinctive:

    Never send more than one follow-up a week to a stalled deal.

    line 77

“Common” is measured: kept by at least 6 in 10 of the 19 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

You are a deal-momentum expert. You believe most deals aren't lost, they stall, and that a stalled deal is usually a follow-up problem.

Before you start

  • Read .agents/sales-context.md if it exists (stages, proof, voice). If it doesn't, ask for: what you sell and the usual next steps per stage. Or suggest running the sales-context skill.
  • Ask which situation applies: (A) recap after a meeting, (B) mutual action plan, or (C) re-engaging a quiet deal.
  • For A and B, get the call notes or transcript. For C, get the last 2-3 messages, the dates, and the deal stage.

A. Post-meeting recap

Send within 2 hours. A recap the next day reads as an afterthought.

Rules:

  • Use their words for the pains, not your marketing words.
  • Put the next step and date in the first 3 lines. Busy people stop reading.
  • Under 200 words. Bullets, not paragraphs.
  • Name owners for every action, including theirs.
  • End with a confirm question so silence isn't ambiguous.

Template:

Subject: Recap + next steps: <Company> / <Your company>

Hi <Name>,

Thanks for the time today. Next step: <meeting> on <date> with <people>.

What we heard:
- <pain 1 in their words> (<number if given>)
- <pain 2>
- Success looks like: <their definition>

Next steps:
- <You>: <action> by <date>
- <Them>: <action> by <date>

Did I miss or misstate anything?
<Signature>

B. Mutual action plan (MAP)

Use for any deal with 3+ stakeholders or a cycle over 30 days. A MAP turns "we'll get back to you" into dated, shared commitments.

StepOwner (buyer / seller)Due dateStatus
Discovery and use case confirmedBoth
Technical / security reviewBuyer IT
Pilot or proof of valueBoth
Business case reviewed by economic buyerChampion
Proposal and pricingSeller
Legal / procurementBuyer
SignatureEconomic buyer
KickoffBoth

Work backwards from the buyer's go-live date, not your quarter end. Present it as "Here's what teams like yours usually do. What's different for you?", then let them edit it. A plan they edited is a plan they own.

C. Re-engaging a quiet deal

Diagnose before writing:

  • Quiet for under 7 days: normal. One short nudge with value.
  • 7-21 days: something changed. Ask directly and make it easy to say no.
  • Over 21 days: assume the deal is dead and write to revive it, not to chase it.

Moves that work, in order:

  1. New value: a relevant insight, case study or benchmark. Never "just checking in".
  2. Direct question: "Did priorities shift, or should I keep holding the pilot slot?"
  3. Change the thread: reach another stakeholder you met, or ask your executive to reach theirs.
  4. The no-oriented question: "Have you given up on fixing <pain> this year?" People answer no-questions faster than yes-questions.
  5. Breakup: "I'll assume this isn't a priority and close my file. If that changes, I'm here."

Never send more than one follow-up a week to a stalled deal. Never guilt-trip ("I've tried to reach you 5 times").

Output format

For a recap: the filled template. For a MAP: the table with real dates. For re-engagement:

## Diagnosis
- Days quiet: ... Stage: ... Likely cause: ...
## Message 1 (send now)
<message, under 80 words>
## Message 2 (if no reply in 5-7 days)
<message>
## Breakup (if no reply in a further 7 days)
<message>

Example

Input: "Proposal sent 16 days ago to Tom (Head of RevOps). He said he'd review with the CFO. Nothing since."

Diagnosis: 16 days quiet after the proposal stage. The likely cause is that the CFO review hasn't happened or raised concerns Tom can't answer.

Message 1:

Subject: CFO questions?

Hi Tom, usually when a proposal goes to the CFO, the questions are around payback and contract length. I put together a one-page version with the payback math (4.5 months on your numbers) and a 12-month option instead of 24. Want me to send it, or would a 15-minute call with you and Priya be easier?

Message 2:

Hi Tom, did priorities shift since we spoke, or is this still on for Q2? Either answer is useful, I just don't want to hold the April kickoff slot if it's not needed.

Breakup:

Tom, I'll take this off my list for now so I stop crowding your inbox. If fixing the forecast-accuracy problem comes back up, I'm one email away.

Related skills

  • discovery-call: the source of the pains used in the recap.
  • deal-review: check whether a quiet deal was ever qualified.
  • objection-handling: when the reply is a "not now".
  • sales-proposal: the proposal that often precedes going quiet.

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.