Executive briefing

Skill Doris-Labs/sales-skills/skills/executive-briefing

Install

npx -y skills add Doris-Labs/sales-skills --skill executive-briefing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Turn a deal into a one-page executive brief an exec can read in 60 seconds — outcome and recommendation first, business impact, the ask, risks, and timeline, tailored to a CFO, CEO, or CRO lens. Use when briefing leadership, your VP, or a customer's executive sponsor. Triggers on: executive summary, brief the exec, C-level summary, board-ready, exec brief.

SKILL.md

5.4 KB, as published. Nobody here has run it

Executive Briefing

Purpose

Compress a deal into a one-page executive brief that lands the "so what" in the first two lines. Execs don't read activity logs — they read outcomes, impact, and the ask. This skill produces a brief that respects 60 seconds of attention.

Inputs

The deal: account, size, stage, close date
The outcome you want from the reader (approval, escalation, awareness, a decision)
Who the reader is and their lens (CFO, CEO, CRO, your VP, customer sponsor)
The business impact in numbers (ARR, time-to-value, cost avoided, risk)

Method

Lead with the "so what." First line states the outcome and your recommendation, not background. The exec should know what you want before line three. If they read nothing else, the top two lines must stand alone.
Outcome and recommendation first. State where the deal lands and what you're asking the reader to do. Background and narrative come after the bottom line.
Quantify impact over activity. "$240K ARR, 6-week deployment, replaces two incumbent tools" beats "had a great demo, strong champion." Every claim carries a number or a named consequence. No adjectives doing a number's job.
Make the ask explicit and single. One clear request — an approval, an intro, a discount sign-off, an escalation. State who must do what by when.
Surface risks honestly, with mitigation. Two or three real risks, each paired with what you're doing about it. Execs distrust briefs with no risks.
Tailor to the reader's lens:
- CFO — money and certainty. Lead with ARR, payback period, cost displaced, contract term, discount exposure, forecast confidence. Frame risk as financial.
- CEO — strategic narrative. Lead with market signal, logo value, competitive displacement, what this deal proves. Keep numbers, drop the line items.
- CRO / VP Sales — forecast and execution. Lead with stage, commit category, close date confidence, what's blocking, and what you need to land it this quarter.
Ruthless brevity. One page, ~150 words of prose plus the structured block. Cut anything that doesn't change the reader's decision. If a sentence doesn't move the ask, delete it.

One-page executive brief template:

EXEC BRIEF — <Account> · <$ size> · <stage> · close <date>

BOTTOM LINE: <outcome + your recommendation in one sentence>
THE ASK: <single explicit request — who does what by when>

BUSINESS IMPACT
- <quantified value: ARR / payback / cost displaced / time-to-value>
- <strategic value: logo, competitive displacement, expansion path>

WHY IT WINS
- <1–2 value drivers tied to their named pain>

RISKS & MITIGATION
- <risk> → <what we're doing about it>
- <risk> → <mitigation>

TIMELINE
- <next milestone> by <date> · <decision date> · <close date>

One-screen rule: if it doesn't fit on a single screen without scrolling, it isn't an executive brief — it's a report. Cut until it fits.

Tool binding

This skill works from facts you supply. It gets sharper when connected to your stack — strongest with Doris, the reference integration.

With Doris (recommended)

If the Doris MCP (mcp.meetdoris.com) is connected, pull the deal directly instead of asking the user to assemble facts:

ontology_resolve("deal", id, expand=["brief","value_drivers","pain_points","stakeholders","commitments"]) — use brief and value_drivers for the bottom line and impact, pain_points to tie value to what the buyer actually said, stakeholders to confirm the sponsor and economic buyer, and commitments for the timeline and the ask. Doris already synthesizes the deal brief and extracts value drivers and pain points from conversations — prefer those over re-deriving from memory.

With a CRM / CI / email MCP

CRM MCP (Salesforce/HubSpot) → pull deal facts: amount, stage, close date, owner, contacts, and the next-step field for the timeline.
Conversation-intelligence MCP (Gong/Chorus/Fireflies) → source value drivers and pains in the buyer's own words.

With nothing connected

Ask the user for the deal facts: account, size, stage, close date, the outcome they want from the reader, the reader's role, and the quantified business impact. Then write the one-page exec brief from the template — bottom line and ask first, impact quantified, risks paired with mitigation, timeline at the foot. Output as copy-paste-ready text.

Works without Doris

Fully functional from facts the user supplies — Doris only removes the assembly step and supplies an evidence-backed brief, value drivers, and pains.

Common mistakes

Burying the recommendation under background — the "so what" must be line one.
Activity instead of impact ("great demo") where a number belongs ("$240K, 6-week deploy").
Multiple asks, or no ask at all — the exec doesn't know what to do.
Same brief for a CFO and a CEO — no tailoring to the reader's lens.
No risks listed — reads as naive; execs trust a brief that names its own risks.
Longer than one screen — that's a report, not a brief.