Skip to content This library is free, offered as dana. If it helps your work, donate here →
penguin tree ai
← back to libraryDonate here

This is one of 3,622 free prompts in the penguin tree ai library. Sign up once and the whole library opens, with new prompts by email.

open the library →

Executive meeting follow-up email generator

Generates a polished post-meeting follow-up email for C-suite or VP-level contacts that recaps the discussion, restates mutual commitments, assigns owners and dates to next steps, and reinforces the strategic value of…

download .md

Purpose

Convert raw meeting notes into a concise, executive-grade follow-up email that documents the conversation, locks in commitments with named owners and dates, and moves the deal or relationship forward. Eliminates the risk of vague "great to connect" follow-ups that let momentum and accountability slip after a high-stakes meeting.

When to Use

Invoke this skill when the user asks to:

  • Write a follow-up email after meeting with a C-suite or VP-level contact
  • Summarize a QBR, executive briefing, or steering committee discussion
  • Recap a discovery call and confirm agreed next steps
  • Document commitments and action items after a negotiation or renewal conversation
  • Send a same-day recap that keeps a stalling deal moving
  • Confirm alignment before escalating internally or looping in additional stakeholders

Inputs Required

Before starting, collect:

  • Recipient name and title: Who receives the email and their seniority (e.g., CFO, VP of Operations)
  • Meeting notes: Raw notes, bullet points, or a transcript of what was discussed
  • Meeting purpose: Why the meeting happened (discovery, QBR, renewal, escalation, etc.)
  • Commitments made: What each side agreed to do, with any names or dates mentioned
  • Sender identity: Sender's name, title, and company
  • Desired next step: The single most important action the sender wants to trigger
  • Relationship stage: New prospect / active deal / existing customer / at-risk account

If owners or dates for action items are missing, propose reasonable placeholders and flag them clearly for the sender to confirm before sending.

Instructions

Step 1: Parse the Notes and Identify the Core Narrative

Read the meeting notes and extract:

  • The 1–2 strategic themes the executive actually cares about (business outcomes, not features)
  • Any concerns, objections, or open questions raised
  • Explicit commitments made by either side
  • The natural next step the conversation was building toward

Distinguish signal from noise — executives skim. Discard tangents and small talk; keep only what advances the relationship or the deal.

Step 2: Write the Subject Line

Produce one primary subject line plus one alternative. Rules:

  • 6 words or fewer
  • Reference the meeting and the forward action, not just gratitude
  • Good: "Next steps from today's rollout discussion" — Bad: "Great meeting you!" The subject should make the email findable and signal that action lives inside.

Step 3: Open with a One-Line Anchor

The first sentence restates the meeting's purpose and the single most valuable takeaway — no throat-clearing. Executives should know within one line why this email matters and what was accomplished. Avoid "It was a pleasure" openers; lead with substance.

Step 4: Summarize the Discussion (Tight)

Write 2–4 sentences (or 3–4 bullets) capturing what was covered, framed around the executive's business priorities. Mirror their language and stated goals. This section proves you listened and creates a shared record. Keep it to what a busy leader will actually read.

Step 5: Restate Commitments and Next Steps as a Clear Action Block

Build a structured block of action items. For each item include:

  • What: the specific action
  • Who: the named owner (sender's side or recipient's side)
  • When: the target date

Format as a compact list or 3-column table. Separate "we will" items from "you'll help with" items so accountability is unambiguous. This is the load-bearing section — it must be scannable in five seconds.

Step 6: Name the Single Next Step and CTA

State the one thing that happens next and make responding effortless. Prefer a specific ask over an open one:

  • Strong: "I'll send a calendar invite for the 15th — reply if a different time works better."
  • Weak: "Let me know your availability." Match assertiveness to relationship stage: warmer and lower-pressure for new prospects, more direct for active deals and existing customers.

Step 7: Close with Strategic Reinforcement

End with one sentence connecting the next step to the outcome the executive said they wanted. Sign off professionally with the sender's name, title, and company. No filler, no over-apologizing, no exclamation-point excess.

Step 8: Apply the Executive Tone Calibration

Before finalizing, adjust for the recipient's seniority:

  • Shorter sentences; active voice; zero jargon padding
  • No hedging ("I just wanted to," "if that's okay," "sorry to bother")
  • Confident but not presumptuous — peer-to-peer, not vendor-to-buyer
  • Total read time under 45 seconds

Output Format

  • Structure: A ready-to-send email with subject line(s), then the full body
  • Length: 120–200 words in the email body; subject line 6 words or fewer
  • Format: Formatted email — subject, greeting, anchor line, brief discussion recap, action block (list or 3-column table), CTA, close, signature
  • Sections: Subject line (primary + alternate) → Anchor line → Discussion summary → Commitments & next steps block → Next-step CTA → Strategic close → Signature
  • Tone: Executive-to-executive — concise, confident, outcome-focused, warm without being casual; no filler or hype

Quality Checklist

Before delivering output, verify:

  • [ ] Email body is 200 words or fewer (count them)
  • [ ] Every action item has a named owner and a target date — no orphan commitments
  • [ ] Subject line references the meeting and forward action, not just thanks
  • [ ] The single most important next step is stated with a specific, low-friction CTA
  • [ ] No hedging or apologetic phrasing ("just wanted to," "sorry to bother," "if that's okay")
  • [ ] Any assumed owners or dates are flagged for the sender to confirm before sending

Notes

  • Same-day delivery matters more than perfect polish — a fast recap while the meeting is fresh preserves momentum and beats a flawless email sent three days later.
  • When the meeting surfaced an objection, address it briefly in the recap rather than ignoring it; documenting a concern signals you took it seriously and gives the executive confidence to move forward.
  • For at-risk accounts, tilt the strategic close toward reassurance and a concrete recovery commitment rather than upsell language.
  • If the executive delegated a follow-up to a team member, consider adding that person as a CC and naming them explicitly in the action block so ownership is visible.

How to use this skill

This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.

Installing in Claude Code:

  • ~/.claude/skills/<folder-name>/SKILL.md — auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)
  • <your-project>/.claude/skills/<folder-name>/SKILL.md — auto-loads only when working in that project (recommended for project-specific skills)

Restart Claude Code or open a new session to register.

Using in Claude.ai, ChatGPT, Gemini, or other AI tools:

  1. Drag this file into a new chat, or copy and paste its contents
  2. Send your task or request as your next message — the AI will apply the skill where it fits

For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills