The one-page executive summary that wins proposals

Picture the evaluation team. Three or four people, each with a stack of proposals, a scoring sheet and a deadline on top of their real job. They read the first page of every proposal carefully. After that, they hunt for the parts that match the scoring grid.

That first page sets the tone. A clear, specific summary makes an evaluator expect a good proposal, and they read the rest looking for confirmation. A vague one makes them expect a weak proposal, and that is what they tend to find.

Is it scored?

Sometimes directly, often not. But it shapes how evaluators read everything after it, and a strong summary is often quoted in the evaluation notes. If the RFP gives a page limit or asks for a specific format, follow it exactly. Anything that breaks the rules can cost you more than it gains. See how to write an RFP proposal.

What goes in it

A strong one-page summary answers five questions in order.

1. What does the buyer need? One or two sentences, in the buyer's own words, showing you understand the real problem. Not "We are pleased to submit," but "The District needs reliable winter clearing for 14 sites, with priority routes cleared before 7 a.m."

2. What will you do? Three to five plain points describing your approach. Name the crew, the equipment and the system you will use.

3. Why you? Your proof, in specifics: years doing this exact work, similar contracts, local base and response time, safety record, a named supervisor. Numbers beat adjectives.

4. What makes it low risk? The buyer's quiet worry is that something goes wrong and they get blamed. Mention transition, backup crews, reporting and how you handle problems. Read what public buyers worry about.

5. Compliance and price. Confirm you meet the mandatory requirements, acknowledge addenda if appropriate, and point to the pricing form. Do not put the price on page one unless the RFP asks for it in that place, because some RFPs require price to be separate.

A reusable outline

Understanding: [Buyer] needs [service] for [sites or scope], with [the two or three things that matter most to them].

Our approach: We will [main method], led by [named supervisor], using [crew and equipment], with [reporting or quality system].

Why us: [Years] years delivering [same service] for [similar clients]. [One measurable result.] Based in [town], [distance or response time] from your sites.

Low risk: [Transition plan], [backup coverage], [safety record or COR], [communication promise].

Compliance: We meet all mandatory requirements and have acknowledged addenda [numbers].

Keep your best version in your bid library, then rewrite it for every bid. The structure stays; the content must not.

Common mistakes

• Boilerplate. "Committed to excellence" says nothing. Evaluators have read it a hundred times.
• Talking about yourself first. Start with the buyer's need, not your history.
• Promises you cannot keep. Whatever you write may end up in the contract.
• New information. Everything in the summary should be backed up later in the proposal, where the scoring happens.
• Going over a page. If you cannot say it in a page, you do not yet know what matters most.

A quick test

Hand your summary to someone who does not know the job. After one minute, ask them: what does the buyer need, what will we do, and why should they pick us? If they cannot answer all three, rewrite it.

Small firms often have an advantage here. Your summary can name the person who will answer the phone at 5 a.m. Bigger firms usually cannot. Read why small crews beat big firms.