| name | executive-briefing-builder |
| description | Build executive briefing notes and pre-reads for strategic customer meetings, internal leadership prep, and high-stakes decision discussions. Use when asked to prepare an executive briefing, align leaders on the meeting objective, or craft concise decision-oriented talking points. For recurring business review decks, use qbr-ebr-builder. |
Executive Briefing Builder
Produce a briefing that helps leaders walk into the meeting with a clear ask, clear story, and clear fallback positions.
Confirm Inputs First
Collect the minimum required inputs:
- Whether a current
revenue-enablement-context exists; if yes, use it as baseline assumptions, if no, capture only the highest-impact missing context.
- Meeting type (
internal exec alignment or customer exec meeting)
- Meeting objective and target decision
- Audience list and attendee roles
- Account/business context and current priorities
- Key risks, sensitivities, and non-negotiables
- Proposed asks, offers, and preferred outcomes
If critical inputs are missing, ask for the smallest missing set. If speed is prioritized, proceed with labeled assumptions.
Read The Right Reference
Default Workflow
-
Define the decision frame.
State the decision, commitment, or alignment the meeting needs to produce.
-
Calibrate to audience.
Map each attendee's priority, influence, likely objection, and decision authority.
-
Build the briefing note.
Use a simple flow: current situation, why it matters, recommendation, ask, and fallback.
-
Prepare meeting flow.
Set the opener, speaker roles, objection moments, and close plan.
-
Stress-test the brief.
Check for unsupported claims, unclear asks, and too many points.
Trim the brief to the few things leaders must remember.
Tool Notes
CRM is useful for account timeline, stakeholders, and commercial context.
BI is useful for outcome trend evidence when available.
Docs/Slides are useful for distribution, but keep a source brief that is easy to update quickly.
Keep workflow tool-agnostic when these systems are unavailable.
Output Contract
Deliver:
- Executive summary with decision requested
- Audience map with priority and stance
- Strategic narrative (situation, impact, recommendation)
- Meeting plan (agenda, owner by segment, timing)
- Key talking points and likely objections
- Ask/offer matrix and fallback positions
- Open questions and assumptions
- Meeting-type notes (
internal vs customer-facing) and confidentiality flags
Quality Bar
- Keep it short enough to use as a pre-read.
- Make the decision request explicit and easy to repeat.
- Tie recommendations to evidence, not opinion.
- Limit the message to the essential points.
- Keep internal notes separate from customer-facing material.
- Do not fabricate account facts, business metrics, or stakeholder positions.