Core & Strategy
Executive Briefing Builder
Build executive-facing briefing materials for strategic customer meetings, internal leadership prep, and high-stakes decision discussions. Use when asked to prepare an executive briefing, align leadership on meeting goals, or craft concise decision-oriented talking points. For recurring business review cadence decks, use qbr-ebr-builder.
Executive Briefing Builder
Produce a strategic briefing that equips leaders to drive a specific decision in a customer or internal executive meeting.
Confirm Inputs First
Collect the minimum required inputs:
- Whether a current
revenue-enablement-contextexists; if yes, use it as baseline assumptions, if no, capture only the highest-impact missing context. - Meeting type (
internal exec alignmentorcustomer 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
- For default structure and executive writing constraints, read references/executive-brief-template.md.
Default Workflow
Define the decision frame. State what decision, commitment, or alignment is required from the meeting. Tailor the frame for internal alignment versus customer-facing negotiation.
Calibrate to audience. Map attendee priorities, influence, likely objections, and decision authority.
Build the strategic narrative. Structure as current situation, business impact, recommendation, and explicit ask.
Prepare meeting choreography. Set opening narrative, role assignments, objection handling moments, and close plan.
Stress-test the brief. Check for unsupported claims, unclear asks, and message overload. Reduce to the few points leaders must remember.
Tool Notes
CRMis useful for account timeline, stakeholders, and commercial context.BIis useful for outcome trend evidence when available.Docs/Slidesare 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 (
internalvscustomer-facing) and confidentiality flags
Quality Bar
- Keep content short enough for executive pre-read.
- Make the decision request explicit and testable.
- Tie recommendations to evidence, not opinion.
- Limit messaging to essential points only.
- Internal-only strategy notes are clearly separated from customer-facing material.
- Do not fabricate account facts, business metrics, or stakeholder positions.
Open source
This playbook is part of 37 open-source enablement workflows. Read, copy, and adapt — attribution welcome but not required.
Run this playbook with your team
Pointer's workspace lets you assign playbooks to people, track progress, and pair them with role blueprints and ramp plans.
More from Core & Strategy
All playbooks →Revenue Enablement Context
Create or update a canonical revenue enablement context used by other enablement skills. Use when the user needs to document ICP, personas, sales stages, qualification rules, pricing and packaging, core objections, competitors, and current initiatives, or when downstream skill outputs are weak because shared context is missing. Route multi-skill sequencing requests to enablement-router.
Enablement Router
Route revenue enablement requests to the best-fit skill or sequence of skills. Use when the user asks which enablement skill to use, combines multiple enablement asks in one prompt, or needs a staged workflow across planning, messaging, coaching, delivery, and measurement. Route single-artifact requests directly to the corresponding specialist skill instead of this router.