Send the follow-up the deal stage actually owes.
A follow-up system keyed to deal stage, not a generic cadence. Each stage's exit criteria decide the ask, every send carries one ask and a dated next step, and two silences trigger a real escalation.
In plain English: “What do I send after this meeting?”
Inside: The per-stage follow-up jobs, the exit-criteria asks, the same-day rule, the forwardable demo recap, and the escalation path.
Install it in one line, or paste it in.
~/.claude/skills/ and runs automatically when it is relevant.Connect your context. Set it to your motion.
it quotes what the buyer actually said, not what you remember.
it reads the stage and exit criteria fields itself.
it checks when your last send went out and whether it got a reply.
This was built for a B2B SaaS org running a staged pipeline. Set these to your process:
Map your own stage names and exit criteria. The skill asks for the exit criterion the deal has not met yet, because that criterion becomes the ask in the email.
| Set this | What it is | Default / Example |
|---|---|---|
| STAGE names | your pipeline's actual stages | DiscoveryDemoProposalNegotiationProcurement |
| EXIT CRITERIA per stage | what must be true to advance | Discovery: problem confirmed + next meeting booked with the right people |
| FOLLOW-UP SLA | how fast the follow-up goes out | Same daybefore end of business |
| ESCALATION threshold | unanswered follow-ups before you change the play | 2 |
Everything the skill does, in full.
Writes the follow-up email a deal owes after each real interaction, keyed to the stage the deal is in. The stage's exit criteria decide the ask in the email, not a cadence template. Where trigger-outreach converts an external buying signal into a touch before the pipeline exists, this skill works inside the live deal: the buyer-facing message after each real interaction, driven by the stage and the exit criteria it still owes. It is not meeting-recap, which produces internal notes. This produces the thing the buyer reads.
- 1After discovery: confirm the problem, earn the room
The job: play the problem back in the buyer's words, not yours, and earn the next meeting with the right people in it. The exit criterion is a confirmed problem and a booked meeting with the people who feel it. So the email quotes what they said, states what you heard the cost to be, and asks for one thing: the next meeting, with the names you need in the room.
- 2After the demo: arm the champion
The job: give the champion a recap they can forward without editing. They will resell this internally whether you help them or not. So the email is written for the person who was not in the room: the problem, what they saw, what it changes for them, and the one open question. Forwardable is the test. If your champion has to rewrite it, you failed.
- 3After the proposal: surface the unspoken objection
The job: name the thing they are not saying and keep the economic buyer warm. Silence after a proposal is an objection that has not been spoken yet. So the email offers the objection on their behalf ("if the sticking point is the rollout timeline, here is what that actually looks like") and includes a reason for the economic buyer to stay in the thread.
- 4In negotiation and procurement: momentum with dates
The job: keep every open item attached to a name and a date. Never "just checking in." Every send restates where the process stands, what is owed by whom, and the next dated step. If legal has the redlines, the email says who has them, since when, and when you will reconvene.
- 5Timing and escalation
Same day, while the context is hot. Every send closes with a dated next step, never an open loop. When two follow-ups go unanswered: change the channel (call instead of email), change the person (go around or above with your champion's cover), or call the risk honestly in your forecast. A third identical email is not a strategy.
- Every follow-up contains exactly one ask. Two asks is zero asks.
- A follow-up with no dated next step does not send.
- Never "just checking in" or "bumping this." If the email has no new information and no dated step, do not send it.
- The ask must map to the stage's unmet exit criterion. If it does not, the stage is wrong or the ask is.
- Quotes come from the notes or transcript. No invented buyer statements.
SAMPLE FOLLOW-UP · Meridian Freight (fictional)
Stage: Post-demo
Exit criterion driving the ask: champion has what she needs to resell internally
Subject: What your ops team saw today, in one page
Dana,
Recap you can forward as-is:
The problem your team named: dispatch spends ~2 hours a day
reconciling load boards by hand ("we re-key the same load three
times," your words from today).
What you saw: one intake, no re-keying, exceptions flagged for a
human instead of buried.
Open question from your side: whether IT signs off on the TMS
connection. I'll bring our integration lead to answer it live.
One ask: 30 minutes Thursday with you and Marcus from IT.
Holding 2pm. Does that work?
Heath
Where an operator takes this next.
The draft is step one. Here is where an operator takes it once the manual version proves out.
The follow-up is only as good as the hours between the meeting and the send. Automate the gap.
Connect Gong or Fathom so every follow-up quotes the buyer's real words from the transcript, not your memory of them.
Read the stage field from Salesforce so the skill picks the right job automatically and flags when the ask does not match the stage.
Connect your email tool so the draft lands ready to send, and the skill can see whether the last one got a reply before writing the next.
Schedule a Claude task to scan open deals for follow-ups past your SLA and post the misses to your Slack DM each morning.
One skill is the on-ramp.
A single skill does one job. Chained into a playbook, or run as a full build, it becomes a system. Here is where this one plugs in.