Follow up Builder

• Source: Built by Jonathan Kvarfordt on the GTM AI OS. Supplied as a complete zip and served unchanged.
• Frameworks applied: Role scans

It covers a job one of the eight revenue seats has to finish, and it states its process, decision rules, and output format clearly enough for an agent to follow.

1. 1.Copy the SKILL.md text below, or download the raw file.
2. 2.Create a folder named exactly follow-up-builder in your agent's skills directory.
3. 3.Save the file inside that folder as SKILL.md.
4. 4.Ask the agent one of the trigger requests below.
5. 5.Check the output against what you already know before it leaves your desk.

• write the follow-up
• recap this call
• send them the next steps

---
name: follow-up-builder
description: Turn a call's Evidence Ledger into a buyer follow-up email in the buyer's words, an internal Slack recap, and proposed CRM field updates, all as drafts for human review. Use when an AE, SDR, or CSM says "write the follow-up", "recap this call", "send them the next steps", "internal recap for the team", or "what should I put in the CRM from this call".
---

# Follow-Up Builder

For AEs, SDRs, and CSMs. A follow-up that repeats the buyer's own words back to them gets read. One that recaps your pitch does not.

Rebuilt from the Momentum prompt library (Email from Transcript, Generate Meeting Summary, Prep for Follow Up).

## Inputs

- `ledger.md` and `rep-read.md`. Run `transcript-denoise` first.
- `gtm-context.md` for proof points.
- Ask if unknown: the one thing you want the buyer to do next.

## Output 1: Buyer email (draft)

Structure: Signal, Pain, Consequence, Value, Proof, Action. One ask.

```
Subject: <their words for the problem>, next steps

<Name>,

<Signal: one line on what they shared, using their phrase in quotes.>
<Pain and consequence: one or two lines, their numbers if given.>
<Value: what changes for them. Proof: one point from gtm-context.md, or leave [PROOF: not supplied].>

What we agreed:
<owner>: <action> by <date>
<owner>: <action> by <date>

<Action: one ask, specific, with a date.>
```

Rules:
- Use only Verified or Supported rows. Inferred rows stay out of anything a buyer reads.
- Only list next steps that appear as COMMITMENT rows. If the rep typed an `N:` the buyer never said out loud, list it under "Proposed" and flag it for the rep.
- No invented stats or customers. Missing proof stays a marked gap.
- Never invent a date. If no date was agreed, propose one as a question ("Does Thursday work?") and flag it as proposed for the rep.
- If the rep's desired next action is unknown and no one can be asked, use the buyer-stated COMMITMENT as the ask.
- Under 150 words.

## Output 2: Internal recap (Slack)

```
*<Account>* | <stage> | Rep confidence C<n>
Pain: "<top quote>" (<speaker>)
Why now: <moment or "none found">
Next step: <owner, action, date> or "none agreed"
Risk: <top doubt or risk>
Ask for the team: <help needed, or none>
```

Six lines. A manager reads it in ten seconds.

## Output 3: Proposed CRM updates

| Field | Proposed value | Evidence row | Confidence |

Common fields: next step, next step date, close date (only if the buyer stated a date), stage evidence, pain, competitor, champion, economic buyer. Mark every row "proposed, not written". Never write to the CRM.

## Output: `follow-up.md` with all three, each labeled "Draft for review, not sent".

What does the Follow up Builder skill do?

Turn a call's Evidence Ledger into a buyer follow-up email in the buyer's words, an internal Slack recap, and proposed CRM field updates, all as drafts for human review.

Where does the Follow up Builder skill come from?

Built by Jonathan Kvarfordt on the GTM AI OS. Supplied as a complete zip and served unchanged.. The source and included files are shown on this page and in the package download.

Why was the Follow up Builder skill chosen for this library?

It covers a job one of the eight revenue seats has to finish, and it states its process, decision rules, and output format clearly enough for an agent to follow.

When should the Follow up Builder skill not be used?

Use it only for the job named above. A skill applied outside its scope produces confident output on the wrong question.

How do I install the Follow up Builder SKILL.md file?

Download the file, create a folder named exactly follow-up-builder inside your agent's skills directory, and save the file inside it as SKILL.md. The agent loads it when a request matches the description.