A Sales Follow-Up Prompt That Turns Notes Into One Email

The follow-up email is where deals leak. The meeting went well, both sides agreed on a next step, and then the rep writes a four-paragraph recap two days later that buries the one action that mattered. Or worse, sends a "just checking in" with no ask at all. A sales follow-up prompt closes that gap by turning the raw notes into a tight email and a clean next-steps list, every time, in a tone you fix once.

Most of what ranks for this is a list of seven email templates. Useful once, then you're back to rewriting. Claap's roundup gives bracketed templates for thank-you, reminder, and check-in scenarios but, by its own structure, doesn't extract agreed next steps or enforce a tone across them (claap.io). Tactiq's examples are the same pattern — standalone samples, no output contract that pairs the email with an action list (tactiq.io). The gap is a single reusable prompt that does both jobs from your notes.

What you can do with this follow-up prompt

The job is narrow on purpose: take what was said, return what to send. One prompt covers the whole post-meeting moment:

• Draft the follow-up email from raw, messy notes
• Pull out the agreed next steps as a separate dated list
• Lock the tone to one setting so every email reads consistent
• Enforce one CTA, so no email carries three competing asks
• Flag any next step with no owner or date so nothing's left vague
• Keep the email under a length cap so it actually gets read
• Adapt the same prompt to a discovery call, a demo, or a proposal recap

That's the difference from a template stack. You're not picking the right template — you're feeding notes to one prompt that knows the shape of a good follow-up.

Anatomy of the prompt

The prompt takes three inputs and returns two artifacts. Put the output contract last so it survives a long, rambling notes paste.

Variables
  {{meeting_notes}}  → raw notes, however messy
  {{tone}}           → e.g. "warm but direct, no fluff"
  {{one_cta}}        → the single ask, e.g. "book the security review"

Prompt
  Role: an account executive writing a same-day follow-up.
  Task: from {{meeting_notes}}, produce an email and a next-steps list.
  Constraints: hold the {{tone}}, end on exactly one CTA ({{one_cta}}),
               cap the email at ~150 words, never invent facts.

Output contract (last lines of the prompt)
  ## Email
  Subject: <under 8 words>
  <body, ≤150 words, one CTA>

  ## Agreed next steps
  - <action> — owner — date   (mark [MISSING] if owner/date absent)

The {{tone}} variable is the one people skip, and it's the one that matters. Leave it out and the model defaults to a chipper register that doesn't match how you actually talk to a CFO. Set it once and every follow-up in the deal reads like the same person wrote them.

Step-by-step usage

1. Capture the notes

You don't need to clean them up. Bullet fragments, half-sentences, "they're worried about migration timeline," a quoted line from the buyer. Paste it all into {{meeting_notes}}. Messy input is fine; the prompt's job is to make it tidy.

2. Set tone and CTA

Fill {{tone}} in plain words ("warm but direct, no exclamation points") and {{one_cta}} with the single thing you want them to do next. If you can't name one CTA, the meeting didn't have a clear next step, which is its own signal.

3. Run the prompt

Paste and run. Claude follows the ## Email / ## Agreed next steps headings cleanly. GPT-4o sometimes merges the next-steps list back into the email body, so restate "keep the two sections separate" on the last line and it holds. Gemini will pad the email past the cap unless you repeat the word count, so keep "≤150 words" near the end.

4. Check the next-steps list for [MISSING]

This is the quiet payoff. If a next step comes back tagged [MISSING] for owner or date, the meeting left something undefined. Better to catch it now than three weeks later when the deal stalls and nobody remembers who owned the SOW.

5. Edit one line and send

The draft should need a one-line touch, not a rewrite. If you're rewriting the whole thing, the notes were too thin or the tone variable was vague. Tighten the input, not the output.

Prompt-craft patterns worth stealing

Two artifacts, one prompt. The reason a template stack fails is it gives you the email but not the accountability. Forcing the model to emit a separate, dated next-steps list turns a nice email into a deal-management tool. The list is what you paste into the CRM.

Always return two sections. The email is for the buyer.
The next-steps list is for you and your CRM. Never merge them.

Tone as a variable, not a guess. A reusable prompt with the tone baked into the instruction reads the same across a whole deal cycle. Few teams do this; most let the model re-pick a register every email, which is why follow-ups feel like they came from three different reps.

A hard refusal on invented facts. If the notes don't say a price was agreed, the email can't reference one. This boundary is what makes the prompt safe to send without reading every word.

Use only facts present in {{meeting_notes}}. If a detail isn't there,
omit it. Never state a price, date, or commitment that wasn't recorded.

One honest caveat: a follow-up prompt is only as good as the notes. Garbage in, polite garbage out. And tone is subjective — what reads "direct" to one buyer reads "cold" to another, so the first few sends are worth a human eye before you trust it on a big account.

Variables you'll set

Getting started

1. Paste your raw notes into {{meeting_notes}} right after the call.
2. Set {{tone}} and name your single {{one_cta}}.
3. Run it, scan the next-steps list for any [MISSING] tags.
4. Make a one-line edit and send within the same day.
5. Save the filled prompt so the tone carries to the next follow-up.
6. For the maintained version with a follow-up cadence built in, start with the Sales Meeting Follow-up Agent Pack.

If the deal came out of a pipeline review, the Salesforce Pipeline Agent Pack is what flags which deals need the follow-up in the first place.

A good follow-up isn't a writing exercise, it's a logistics one. Capture what was agreed, send it back the same day, make the ask once. Do that with a prompt and you stop losing deals to a recap you never got around to writing. When you need to qualify the deal that the follow-up is keeping warm, the MEDDPICC qualification prompt scores it against the eight elements that predict a close, and the Salesforce pipeline prompt tells you which deals are stalling before they stall for good.