The executive summary is the most read page in most proposals, and it's often the last one written. Someone finishes forty pages of scope at the end of a long week, then squeezes the whole thing into a few paragraphs on page two. It shows. A strong proposal executive summary gets written first, and it gets written for one person, the executive who signs and who probably skipped your demo.
Who reads it
Think about how the decision goes. Your champion forwards the proposal to their boss, maybe their boss's boss, with a note like "take a look before Thursday." That reader opens it between meetings. They read the summary, glance at the price and decide whether the rest is worth their time. If they have questions, they ask your champion. They don't ask you.
So the summary has two jobs. It has to make the case on its own, and it has to give your champion the words to repeat when you're out of the room.
Start with their problem, in their words
Open with the situation the buyer described to you, using the words they used. If the VP of operations said the current vendor "keeps missing the Monday cutoff," put that in. A reader recognizes their own problem faster than your description of it.
Then say what it costs them, if they told you. Lost hours, missed revenue, a project stuck behind it. Use their numbers. If they never gave you a number, don't invent one.
Say what you'll do in one paragraph
Next comes the plan. One paragraph, plain words, no list of features. What you'll do, in what order, and when they'll see the first result. A reader should be able to say it back in one sentence. "They'll move us over in six weeks without shutting down the warehouse."
If you can't write that sentence yourself, the proposal isn't ready yet.
Put the price next to the outcome
Executives go looking for the number. Give it to them in the summary, right next to what it buys. Hiding the price on page 30 only sends the reader hunting for it, and they'll be a little annoyed when they find it.
For more on framing the number itself, see how to present pricing in a proposal.
Show why you, briefly
One or two lines on why your team is right for this job. A past client in the same spot, a result you can point to, a part of the plan nobody else will offer. Keep it specific. "We've run this rollout for three regional hospital systems" says more than "deep experience in healthcare."
End with the next step
Close with exactly what happens if they say yes. Who signs, by when, and what kicks off the week after. A summary that ends on a clear next step is easier to approve than one that ends on a thank-you.
Keep it to one page
If the summary runs past a page, cut. Every extra paragraph is one more place for a busy reader to stop. The detail belongs in the sections that follow, and a good summary points the reader to them.
Design it like the most important page
In a live web proposal, the summary is the opening screen. Give it room. Big type for the headline outcome, the price visible without scrolling and a clear way into the detail behind each point. In the PDF, it's the first full page after the cover, and it should look like someone designed it on purpose.
A proposal executive summary, before and after
Here's a made-up example to show the difference. A software company is pitching a regional bank on a new loan processing system.
The first draft opened like this. "Founded in 2009, the company is a leading provider of lending technology serving financial institutions nationwide. We are pleased to submit this proposal." Two sentences in, the reader has learned nothing about their own problem.
The rewrite opened with the bank's situation. "Your loan officers told us a small business loan takes about three weeks to approve, and two of your larger competitors now approve in days. This proposal brings your approvals into the same range by the second quarter, without replacing your core system." Then came one paragraph on the plan, the price and the outcome on one line, and a closing line with the signing date that keeps the second quarter start.
Same company, same product. The second version gives the bank's COO something to say out loud in the meeting.
Questions we hear about executive summaries
How long should a proposal executive summary be?
One page, and shorter is fine. If the plan takes more than a paragraph to explain, the detail belongs in the plan section. The summary's job is to get the reader to keep going, or to give them enough to approve if they don't.
Should the executive summary include the price?
Yes. The executive will look for it anyway. Putting it in the summary, next to the outcome, means they see the number in context instead of on its own. Our guide to the business proposal layout shows where the full pricing page fits after it.
Is an executive summary the same as a cover letter?
No. A cover letter introduces the proposal and thanks the buyer for the opportunity. The executive summary makes the case. Plenty of proposals can skip the cover letter. Very few should skip the summary.
The short version
Write the executive summary first. Open with their problem in their words, say what you'll do in a paragraph, put the price next to the outcome and end on the next step. If the executive who signs only reads one page, make it this one.
If you've got a deal where the summary has to carry the whole proposal, we can help. See the work or start a proposal.
