Executive Summary Prompt

What it does

Writes a standalone executive summary for a report, proposal, business plan, or research document. The output is structured for an executive audience: situation first, then the key finding or recommendation, then supporting evidence, then what needs to happen next. It's complete enough to read without the full document but specific enough to prompt the right questions.

undefined

How to use it

Write the full document first, then use this prompt. The executive summary is easier to write when you already know what the most important points are. If you're writing the summary before the document, you're planning, not summarizing.

The "decision or action needed" field is the most commonly omitted part. Don't leave it blank — a summary with no ask is a status update, not a decision document.

Example output

"Executive Summary: Q2 Customer Retention Initiative

Customer churn in Q2 reached 8.4%, up from 5.1% in Q1 — the highest quarterly rate in 18 months. Exit survey analysis shows 62% of churned accounts cited onboarding gaps in the first 30 days as a contributing factor, not product dissatisfaction.

This report recommends a targeted intervention to the first-30-day customer journey: a dedicated onboarding success manager for accounts over $10K ARR, and an automated touchpoint sequence for SMB accounts. Projected cost is $220K annually; projected churn reduction is 2.5 percentage points, representing $680K in retained ARR.

The analysis, segmented by customer tier and acquisition channel, is in the full report. For approval, we are requesting budget authorization of $220K and the open headcount for one Customer Success Manager role, to be executed in Q3."

Variations

Business plan executive summary: Add "This is for a business plan — the reader is a potential investor. Include market size, the problem, the solution, the business model, traction if any, and the funding ask."

Research report: Add "This is an academic or policy research summary. Lead with the research question and finding, then methodology and implications."

Internal status summary: Add "This is an internal project status summary for the leadership team. Lead with status (on track / at risk / off track), then key milestones this period, then issues requiring leadership input."

Common pitfalls

Too long. If the summary is longer than one page, it's a summary of a summary. Cut until it fits.

No recommendation. A summary that describes a situation without recommending anything forces the executive to draw their own conclusion — which often means they don't.

Jargon. Executive audiences include non-specialists. Avoid technical terms without brief definitions. If you wouldn't say it in a 5-minute verbal briefing, cut it.

Who uses this prompt

Project managers submitting reports to leadership. Consultants writing the first page of a client deliverable. Business owners writing the opening section of a business plan for investors. Analysts who have written 40 pages and need to compress it to one.