Send the follow-up the deal stage actually owes.

“What do I send after this meeting so the deal actually moves instead of going quiet?”

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.

CLOSE MORE DEALSEASYCRMENRICHMENT TOOL WITH PEOPLE AND JOB-POSTINGS DATACONVERSATION TOOL✓ APPROVED 4/4
EXAMPLE PROMPTS
>What should I send after this discovery call? Here is the deal stage and my notes
>Write the follow-up for this demo, with one ask and a dated next step
>My deal went quiet after the proposal. Draft the escalation email for the second silence
ABOUT THIS SKILL

What this skill does

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.

Inputs

  • Works today with: the deal's stage, what happened in the last interaction (paste the notes or transcript), and who was in the room.
  • More powerful connected to conversation intelligence (Gong, Fathom, Fireflies): it quotes what the buyer actually said, not what you remember.
  • Sharper with a CRM: it reads the stage and exit criteria fields itself.
  • Sharper with email connected: it checks when your last send went out and whether it got a reply.

How it works

  1. 1
    After 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.

  2. 2
    After 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.

  3. 3
    After 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.

  4. 4
    In 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.

  5. 5
    Timing 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.

Output format

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

Tips

  • 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.
RELATED SKILLS
NO SETUPADVANCED · Deal Signals

Never miss a contact's job change again.

Who changed jobs this month?

CONNECTS TO CRM, ENRICHMENT TOOL WITH PEOPLE AND JOB-POSTINGS DATA, CONVERSATION TOOLAPPROVED · INSTALL →
NO SETUPINTERMEDIATE · Deal Signals

Turn a champion's job change into two plays.

My champion just left. Now what?

CONNECTS TO CRM, ENRICHMENT TOOL WITH PEOPLE AND JOB-POSTINGS DATA, CONVERSATION TOOLAPPROVED · INSTALL →
ALL CLOSE MORE DEALS SKILLS →