Executive Summary: What It Is, Examples, and How to Write One

An executive summary is a condensed, standalone version of a longer document that gives a decision-maker everything they need to understand the situation and act — the problem, your recommendation, the impact (with numbers), and the ask. It's written for someone who may never read the full document. That last part is the whole game. You are not introducing the report; you are replacing it for the person who won't read it.

Where it shows up changes what it emphasizes:

• Business plan — for a lender or investor. The SBA's own guidance is to "briefly tell your reader what your company is and why it will be successful," covering the mission, product or service, leadership team, and location — plus financials and growth plans if you're asking for financing.
• Report or research — for an executive who won't read 30 pages: the findings, what they mean, and what you recommend.
• Proposal or RFP response — for a buyer: their problem, your solution, the price and ROI, and why you.
• Grant or academic — closer to an abstract, but still pointed at an outcome.

Now the part people get wrong — what it is not:

• Not an abstract. An abstract describes what a document covers ("this report examines pricing across three regions"). A summary delivers the conclusion ("we should raise prices 8% in Denver; here's the projected margin") and asks for a decision.
• Not an introduction or background. It doesn't set up the document. It stands in for it.
• Not a table of contents in prose. "Section 1 covers our history, Section 2 covers the market…" is the single most common failure mode. Nobody makes a decision off a map of where things are.
• Not a teaser. Give away the ending. Do not withhold the conclusion to make them keep reading — they won't.

There's a quiet irony here: the executive summary is usually the most-read and least-carefully-written part of any document. Executives read it and often only it. Meanwhile everyone else's careful edits tend to peter out before they reach it. Flip that.

The working rule: aim for one page, roughly 250–500 words. That's the safe default and the target. Reach for a second page only when the decision genuinely requires it — a long, complex plan with financials the reader has to see. Past two pages it stops being a summary and becomes a second document nobody asked for.

For investors, go shorter still. Plenty of VCs and lenders want one page, and some want a single paragraph in the body of your email. Length signals something here: a summary that sprawls tells the reader you couldn't decide what mattered, which is not the impression you want when you're asking for money. The SBA, notably, gives no fixed length for the business-plan summary — practitioners have simply standardized on one page because it works.

The honest tradeoff: cutting hard forces you to prioritize, which is good, but it also risks dropping the one number that would have closed the deal. The fix is not to write more. It's to cut the right things — adjectives, background, throat-clearing — and never cut the ask or the key figure. If you're over length, delete "we are thrilled to present," not "$2.1M/yr in savings."

The method, in order:

1. Write it last. You cannot summarize a document that doesn't exist yet. Writing the summary before the document is settled is how you end up with a table of contents in prose — an outline of where things will go, drafted before the author knew their own conclusion. Distill the summary from a finished doc; it's the final step, not the opener.

2. Draft the one-sentence answer first. Before anything else, write: "We should do X because Y, and I need Z from you." Everything else in the summary exists to support that one sentence. If a paragraph doesn't, cut it.

3. Pull, don't rewrite. Lift the real numbers and findings straight from the body. Don't invent summary-only claims — the moment a figure in your summary contradicts the body, your credibility is gone, and the reader stops trusting every other number too.

4. Cut to one page, then read it cold. Pretend you've never seen the full document. Can you make the decision from the summary alone? If not, what's missing — and add only that.

5. Tailor to the actual decision. Lead with the criterion governing it — cash, risk, timing, growth, or compliance — not the reader's job title alone. The same underlying document can yield a different summary for a different decision; one generic version sent to everyone is optimized for no one.

On AI drafting: Claude, ChatGPT, and Gemini can produce a genuinely useful first-pass summary. Before you upload anything sensitive — board, client, financial, or personnel material — check your organization's approved tools, retention settings, and data policy. Then paste the full document and prompt something like "write a one-page executive summary for a CFO whose decision is whether to approve this budget; lead with the recommendation, quantify the impact, end with a clear ask." Then edit hard, because three failure modes are reliable. AI over-produces connective filler and hedging adjectives — you cut them. It will soften or fabricate numbers when the source is ambiguous — verify every figure against the doc. And it defaults to abstract, intro-voice openings ("this report explores…") — you force BLUF ordering in the prompt and again in the edit.

For structure without AI, the SBA guide linked above ships two complete sample business plans you can model directly, and proposal platforms like PandaDoc and Proposify include executive-summary blocks inside their editors. The honest catch with any template: it solves structure but produces fill-in-the-blank prose that looks like everyone else's. The parts that actually win — the specific number, the tailored ask — are exactly what a template can't hand you.

Then there's delivery, which most authors skip entirely. The sharpest summary still fails if it's stranded on page one of a 40-page PDF the executive never opens, or lost three replies deep in an email thread. So: put the summary in the body of the email, not only the attachment. For proposals and decks, deliver it as something that stands on its own. And for high-stakes sends, it helps to know whether it was opened at all before you make the follow-up call.

That last point is where a specific tool fits, honestly and narrowly. If your summary or the proposal it fronts already exists as HTML — increasingly common now that people have Claude or ChatGPT draft and format a one-pager — Pagelive turns it into a private, tracked link you send instead of a PDF, and it's free for 5 pages with no card. You see whether the link was opened, when, roughly how long the viewer spent, and what country it opened from — a much stronger signal than an email open pixel, because the fetch is the page itself rather than a proxy image, though it's not proof of who read it or how closely (corporate scanners can pre-fetch links, and a forwarded link muddies identity). Pages are private and marked noindex by default, with an optional password; access is not restricted to named recipients — anyone with the link and the password can open it. Scope it correctly: if your summary is one page of a Word or PDF business plan going to a bank, they expect a formal document, not a link — send the document. If colleagues need to redline it, that's Google Docs. It's a delivery-and-tracking layer for a finished HTML page, nothing more.

So finish the doc, distill the summary from it, lead with the answer — and then don't lose it on page one of an attachment nobody opens. Put it where the decision-maker will actually read it.