The executive summary that fits on two pages, always
Length is a win-theme signal to evaluators. A two-page executive summary is a commitment; a six-page executive summary is a hedge. Six compression moves I run every time.
The executive summary is the first thing the buyer reads and the last thing the writers finish. Its length is a signal — to the buyer, about what the writer thinks is important — and most exec summaries are too long for the same reason: nobody trusted a sentence enough to delete its safety net.
Two pages is the right ceiling. Six is the common reality. This post is six compression moves I run every time, in order, to take a six-page draft to a two-page final.
Why two pages
Two pages is the length at which the evaluator can read the document in one sitting before another meeting. It is also the length at which every paragraph has to earn its place — a six-page exec summary has room for hedges, restatements, and “as outlined above” sentences that two pages does not.
Shipley’s Proposal Guide recommends one to two pages. Federal solicitation conventions vary; many cap the executive summary explicitly. When there is no cap, two pages is the discipline that makes you treat the summary as the win document, not the response document.
VisibleThread’s research on government proposal failures lands on the same point in different language: rushing into writing without understanding the requirements is the leading failure mode, and exec summaries that don’t compress are usually the most visible symptom of that root cause. The writer didn’t know what to keep, so they kept everything.
The six compression moves
Run them in order. Each one takes a recognizable category of bloat out.
Move 1 — delete the first paragraph
The first paragraph is almost always throat-clearing. “Acme Corp is pleased to submit this response…” or “We have carefully reviewed the requirements…” or “With over 15 years of experience…” Three sentences saying the writer is about to write something. Delete them.
What was going to be paragraph two becomes paragraph one. Read it cold. If it lands as an opening, the deletion is right. If it doesn’t, write a new opening that names the buyer’s situation directly. I covered this pattern in detail in three exec summaries I rewrote this week, part 2: the structural rule is that the first sentence is about the buyer, not about the vendor.
Move 2 — collapse the win-themes preamble
Many drafts have a paragraph that introduces the win themes (“Our response is built around three core themes…”) followed by a paragraph for each theme. Delete the introduction. The win themes are the paragraphs that follow; the introduction is meta-commentary on the structure.
If a reader can’t tell that paragraphs two through four are organized around three themes, the themes are too weak. The fix is to sharpen the themes, not to introduce them.
Move 3 — compress feature lists
Exec summaries that read like product brochures lose the reader by paragraph three. A list of capabilities is product marketing copy in an exec-summary slot. Each capability needs to be re-cast as a buyer-priority response — name the priority, name the capability that responds to it, name the evidence the buyer can verify.
Three capabilities re-cast as priority responses fits in one paragraph. The same three capabilities listed as features fills a page. Same content, one-third the space.
Move 4 — kill the swap-test failures
Every win theme that fails PropLibrary’s swap test — replace your company name with a competitor’s, the sentence still works — is filler the evaluator filters as fluff. Delete it. If the swap test passes, the win theme is generic, and a generic win theme costs space without earning weight in evaluation.
This is the move that produces the largest single delete in most drafts. A six-page exec summary often has two pages of swap-test failures. Two pages becomes zero pages and the document gets meaningfully shorter while getting better.
Move 5 — strip the conclusion
Most exec summaries end with a paragraph that summarizes the exec summary. “In summary, our solution offers…” or “We look forward to…” or “We are confident that…” Delete it. The exec summary is itself a summary; it doesn’t need a summary of itself.
The last sentence of the exec summary should be the most consequential sentence in the document — a commitment to the buyer that the rest of the response substantiates. Not a reiteration. Not a polite goodbye.
Move 6 — compress sentences
Every sentence longer than two lines is a candidate. Read each one and ask: is the dependent clause earning its place, or is it hedging? If hedging, cut it. “We believe that, based on our extensive experience in the financial services industry, our solution will deliver substantial value to your team” becomes “Our solution delivers value our financial-services customers measure.”
The shorter sentence is a stronger commitment. The longer sentence is a hedge with the appearance of substance. Buyers read past hedges.
What survives the compression
After all six moves, what remains is roughly:
- One opening paragraph that names the buyer’s situation.
- Three paragraphs, one per win theme, each tied to a buyer priority and backed by evidence.
- One paragraph that names the discriminator — what we offer that the competitive alternatives do not, in language the evaluator can verify.
- One closing sentence that commits to a specific outcome.
That is six paragraphs, two pages at standard formatting, and it is what the evaluator wants to read.
When two pages doesn’t fit
Federal pursuits with prescriptive page-by-page format requirements sometimes specify a longer executive summary section. In those cases, fill the budget — but fill it with substance, not throat-clearing. The compression moves still apply within the budget; you just have more paragraphs of the same kind.
The opposite case — a buyer that explicitly limits the exec summary to one page — is rare in commercial work and common in some federal task orders. One page forces the third compression move (priority-paired capabilities) to be even tighter and forces win themes to share paragraphs. It can be done; it is not the default.
Closing
The compression is not about brevity for its own sake. It is about making the evaluator’s first read of the document a read of the strongest material you have, in the order it makes the strongest case. Six pages of throat-clearing buries the strongest material on page four. Two pages of compressed commitments puts it where it gets read.
Pick the next exec summary in your queue. Run the six moves in order. The document gets shorter. It also gets sharper. The evaluator notices both.