The four-paragraph structure
Paragraph 1: restate the client's problem in their own language. Paragraph 2: name your solution and the one differentiator that matters. Paragraph 3: quantify the outcome (uptime, cost, time-to-value). Paragraph 4: call out the implementation plan and your team's credentials.
What to never put in an executive summary
No company history. No 'thank you for the opportunity.' No technical architecture diagrams. Save those for the body — the executive summary is a sales document, not a technical one.
The template outline
Paragraph 1 — Their problem
- Quote a line from their RFP
- Name the cost of inaction
- Anchor to a strategic initiative they've already announced
Paragraph 2 — Your solution
- One sentence solution statement
- One differentiator vs the obvious competitor
- One proof point
Paragraph 3 — Quantified outcome
- Hard number (% or $)
- Time-to-value
- Risk retired
Paragraph 4 — Why us
- Named delivery lead with tenure
- Comparable client logo
- Implementation timeline in weeks
Frequently asked questions
How long should an IT proposal executive summary be?
One page, 300–400 words. If it spills to a second page, you are writing the technical section.
Should I include pricing in the executive summary?
Only the total contract value as a range. Detailed pricing belongs in its own volume.