Writing Executive Summaries

Writing Executive Summaries

Write the executive summary as what it actually is: the most-read, most influential pages of the proposal, and a persuasion document — not a summary. Many evaluators read the executive summary first, and it frames how they read everything after. An executive summary that recaps the table of contents wastes that position. One built around the customer's concerns and the win themes uses it.

When to use this skill

Use this skill once the win strategy exists and the volume content is at least storyboarded — the executive summary distills the win themes and previews the proposal's case, so it is written with knowledge of both. It is often drafted early for direction and finalized late once the volumes are stable.

This skill writes the executive summary specifically. General section narrative is drafting-proposal-sections.

Inputs

Preferred upstream artifacts:

• 05-win-strategy.md: the win themes, discriminators, and hot buttons. The

executive summary is largely the win strategy in prose.

• 10-compliance-matrix.md: Section L rules governing the executive summary

(page limit, whether it is evaluated, content restrictions).

• 11-proposal-outline.md and 12-sections/ — the proposal's actual case, so

the summary previews it accurately.

• 00-opportunity-profile.md: the customer and requirement.

Without the win strategy, the executive summary cannot be done well — it has no themes to carry. Recommend running developing-win-strategy first.

Read ../../shared/glossary.md and ../../shared/pursuit-workspace.md if not already read this session.

Intake

Ask these as a numbered list. Skip what upstream artifacts answer.

1. Section L rules for the executive summary. Is there a page limit? Is the

executive summary evaluated, or informational only? Does Section L restrict its content (for example, prohibiting information that appears only in the executive summary)?

1. Customer hot buttons. What does this customer care about most? (From

05-win-strategy.md if available.)

1. Win themes. What are the three to five win themes the proposal carries?
2. The decision frame. In one sentence, why should this customer choose this

offeror over the field?

1. Format. Is the executive summary a cover letter, a standalone volume, or

a section — and are graphics allowed?

Workflow

Executive Summary:
- [ ] Step 1: Read the win strategy and Section L rules; complete intake
- [ ] Step 2: Confirm the central message
- [ ] Step 3: Structure around hot buttons and themes
- [ ] Step 4: Draft — customer-focused opening, themes, close
- [ ] Step 5: Run the executive summary self-check
- [ ] Step 6: Write the artifact (13-executive-summary.md)

Step 1: Read and intake. Read the win strategy and the Section L rules.

Step 2: Central message. State, in one sentence, the reason this offer wins. Everything in the executive summary serves that message. If the message is not clear, the executive summary cannot be — return to the win strategy.

Step 3: Structure. Structure the executive summary around the customer's hot buttons and the win themes, not the proposal's volume order. Use references/executive-summary-method.md for the structure: a customer-focused opening, a small number of theme-driven blocks, and a confident close.

Step 4: Draft. Draft following the method file:

• Open on the customer — their mission, their problem, what they need to

achieve — not on the offeror's history.

• Devote a short block to each win theme: the customer benefit, the

discriminator, the proof, in the customer's terms.

• Address the top hot buttons explicitly, including risk.
• Close with a confident, specific statement of why this offer is the

low-risk best value — never a generic "we look forward to working with you".

• Respect the page limit and any Section L content restriction.

Step 5: Self-check. Run the self-check in the method file: the customer is the subject of the opening; every theme is benefit-led and proven; it persuades rather than summarizes; it would still make sense to an evaluator who read nothing else; and it introduces no requirement-response that exists only here if Section L forbids that.

Step 6: Write. Write 13-executive-summary.md using templates/executive-summary.md.

Output

One artifact: 13-executive-summary.md in the pursuit workspace.

Present the user with: the executive summary draft, the central message it carries, and any Section L constraint that shaped it.

References

• references/executive-summary-method.md: what an executive summary is and is not, its structure, the customer-focused opening, threading themes, Section L pitfalls, and the self-check.
• templates/executive-summary.md: the executive summary artifact template.

Guardrails

• It is not a summary. Do not recap the proposal volume by volume. The

executive summary persuades; it is organized around the customer, not the table of contents.

• Open on the customer. The first paragraph is about the customer's mission

and problem — never the offeror's founding date or revenue.

• Themes, with proof. Every theme carries a customer benefit and real

substantiation. No unsupported superlatives.

• Watch the Section L trap. Some solicitations bar content that appears only

in the executive summary. If so, every claim here is also made and supported in the volume that owns it.

• No fabrication. Every proof point traces to real evidence.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: danielkinneyspears
• Source: danielkinneyspears/federal-proposal-skills
• License: Apache-2.0

Install and usage instructions live in the source repository linked above.