Sales Meeting Recap

Meeting Recap

Convert the user's call notes into two artifacts: a recap email the buyer will ratify by replying, and mutual close plan items when the deal is complex enough to warrant a shared plan. The organizing rule is Armand Farrokh's (30MPC): a recap email answers exactly two questions - "Did you make it clear what the prospect needs to do next?" and "Did you remind them why they agreed to take action?" Everything else is decoration, and "nothing should get in the way of what we want them to do."

Second rule: the recap is champion-enablement content. A buying group gives any single vendor only around 5-6% of its purchase time (Gartner 2017 B2B buyer survey), so the email does most of its selling in rooms the rep never enters - write it to be forwarded.

Scope boundaries:

• Work only from notes, transcripts, or descriptions the user supplies.
• Never score or critique how the call was run - that belongs to mbfinotti/sales-skills@sales-call-review.
• The post-sale handoff from sales to customer success is out of scope entirely.

Interview

Ask one question per message; offer multiple-choice options; skip anything the notes or context already answer.

1. Who was on the call - names and roles on both sides? Which buyer contacts should receive the recap?
2. B2B or B2C? Buying committee, or a single decision-maker?
3. Deal stage: first connect, discovery, demo, proposal, or negotiation?
4. Rough deal size and expected cycle length? This sets the recap's weight and whether a close plan pays off.
5. What was actually agreed on the call - commitments, owners, dates, exactly as stated?
6. Is the next meeting booked with a calendar invite? If not, was a specific date discussed?
7. Does a mutual close plan already exist for this deal, or should this call seed one?
8. By when must the recap land - within the hour, today, or is tomorrow acceptable? A same-hour answer promotes the short recap and deletes anything needing a working session.
9. One-off win or compounding asset: this deal's follow-up only, or a pattern repeated across the pipeline? Compounding promotes the close plan and the automated sequence; one-off promotes the hand-written recap alone.
10. Effort ceiling: how many minutes per recap, across how many live deals? A tight ceiling deletes the full mutual action plan and caps the recap at one screen.

Every ordering below is a default, not a law - it shifts with the deal, with the pipeline, and with who executes it. Re-rank each one against these answers and against what you already know about the user: a rep running dozens of small deals, a single strategic pursuit, and a CRM that already auto-drafts recaps each invert a different ordering. Delete the options their constraints rule out rather than parking them at the bottom, where they quietly reappear as scope.

Anti-fabrication rule

The load-bearing guard. A recap containing a commitment the buyer never made destroys the shared record it exists to create.

• Never invent a commitment, owner, date, quote, attendee, or decision the notes do not contain.
• Treat a gap as output, not as something to fill: list missing owners, dates, and unconfirmed items in an "Open gaps" block and ask the user.
• Mark any step the buyer did not explicitly agree to as "proposed - confirm before sending".
• Reuse the buyer's own words for the pain, verbatim - their phrasing, their numbers. Never translate their language into marketing copy (practitioner rule: "confirmation, not summary").

The recap email

30MPC's 3-step recap email (Armand Farrokh):

1. Lead with next steps - action items at the very top, each with an owner and a date; make the buyer's own items visually unmissable.
2. Recap problems, not features - restate the pain in the prospect's own words, never a list of capabilities.
3. Keep it short and skimmable - the whole email fits on one phone screen.

What earns space on the one screen

One phone screen is the whole budget, so these elements compete for it. Ranked by value per rep minute, best ratio first:

1. Dated next-steps block at the top - near-zero extra minutes, part of the recap email already being written. Buys the only thing separating a call from progress: something the buyer must do, by a date.
2. The buyer's pain in their own words - near-zero when the notes caught the quote, one more pass through the transcript when they did not. Buys the forward: it is the line that survives the champion's internal debrief.
3. A send list across the committee - minutes per deal to find and justify the contacts, redone from scratch on the next deal. Buys the largest measured effect in this section: single-threading is the dominant structural failure, closed-won deals carry 67% more contacts, and multithreading lifts win rates ~130% on $50K+ deals (Gong Labs; sample disclosed, method proprietary).
4. A closing ratification question - one line, "Anything I missed?". Buys a reply, and a reply turns the recap into an agreed record.
5. A subject under 50 characters, next-step-anchored - one line, plain: "Next steps - Acme + Yourco". Buys the open and nothing past it; 1-4 words performs best (Gong).
6. The one attachment the buyer asked for - near-zero to attach, longer when it must be produced first. Buys credibility on a single asked-for item. Never list attachments as action items.

• value: next-steps block > pain in their words > send list > ratification question > subject line > attachment
• effort: send list > attachment > next-steps block == pain quote == ratification question == subject line - those four tie at genuinely near-zero, each being one line or one paste written in the same pass as the email itself

The ratio starves the send list: it is the only row costing real minutes per deal, so a minutes ceiling cuts it first. Promote it regardless of ratio the moment the notes name more than one buyer stakeholder - there is no cheaper substitute for a contact who was never emailed.

Deleted, not demoted. Keep these out of the draft entirely, since they lose on every axis:

• A capability or feature recap (step 2 forbids it).
• Full meeting minutes (a different artifact).
• Rapport prose like "wonderful to connect", which reads as automation.

Unranked on purpose, because they cost nothing and apply to every recap:

• Cap bullets at ~4, max two lines each (30MPC).
• Write plain text that any email client renders as-is - no markdown syntax, headers, or asterisk-bold.

When to send. value: within hours of the call > later the same day > next morning > multi-day. Effort is identical at every rung - same email, same minutes - so nothing trades against speed. Send before the buyer's internal debrief, always (timing norm).

Filled strong and negative examples: references/recap-email-examples.md.

What makes a next step real

• Real = Owner + Date + Deliverable, plus a calendar invite for any meeting. Missing any part means a nice conversation, not progress (practitioner definition).
• Reject "circle back", "next week", "soon", "ASAP" as dates. The forced choice defeats vagueness: "Thursday or Friday?" (technique).
• Assign one named owner per item - a person, never a team.
• Activity is not advancement: extra demos and reference calls without confirmed movement through the buyer's decision process are not progress (MEDDICC).
• When the notes show no committed next step, do not manufacture one. Flag it, and prescribe 30MPC's 5 Minute Drill for the next touch (framework): "Do you wanna buy?", "When do you wanna buy?", "How do you wanna buy?" - commitment, timeline, then the recommended multi-step path.

Mutual close plan

Three rungs answer "how much plan does this deal need". Ranked by value per rep minute, best ratio first: