Compress account status or meeting notes into a one-page executive brief covering situation, value, risk, and decision needed.
Transform raw account status or meeting content into a structured one-page executive brief that surfaces the situation, business value, key risks, and the exact decision required from leadership.
Use before an executive review, QBR, escalation meeting, or any time leadership needs a concise account or deal status without reading through long notes.
Ingest the raw source material below and identify the core subject — account name, deal stage, meeting context, and primary stakeholders involved: $meeting_notes_or_account_status
Analyze the raw source material below and identify the core subject — account name, deal stage, meeting context, and primary stakeholders involved:
$meeting_notes_or_account_statusSynthesize the Situation: write 2–3 sentences summarizing where things stand right now — current state of the account, deal, or discussion — with no jargon or backstory.
Articulate the Value: write 2–3 sentences on the business opportunity or outcome at stake — quantify revenue, retention, expansion, or strategic impact wherever the source material supports it.
Surface the Risk: write 2–3 sentences identifying the top 1–2 risks that could derail the outcome — competitive, technical, relationship, timeline, or budget. Flag urgency level (High / Medium / Low).
Define the Decision Needed: write a single crisp ask — what specific action, approval, or commitment does the executive need to make, by when, and what happens if they don't act.
Assemble the final one-page executive brief in the output format below. Keep total length under 300 words. Review for clarity, remove redundancy, and ensure every sentence earns its place.
Return a clean executive brief with four clearly labeled sections: **Situation** (2–3 sentences), **Value** (2–3 sentences with metrics), **Risk** (2–3 sentences with urgency tags), and **Decision Needed** (1 crisp action sentence with deadline). Add a one-line header with account/meeting name and date. Total length: under 300 words. No bullet points inside sections — prose only.
Copy this skill into your library to inject it into Claude, ChatGPT, and Gemini — or install your whole library as / slash commands in Claude Code and Cowork.
Get started free →Related skills
Convert a customer issue into a structured internal escalation brief covering impact, timeline, blockers, and team asks.
Turn usage signals and account context into a structured expansion or upsell case with value story and recommended offer.
Turn an at-risk account into a structured save play: diagnose the churn risk, then build a sequenced outreach, offer, and escalation plan.