The section everyone reads and nobody plans
In a long proposal, most evaluators read their assigned sections and skim the rest. The executive summary is the exception: it is the one part the people with real authority read start to finish, and often the only part. Yet on most teams it gets written last, after everyone is exhausted, as a two-paragraph recap of what follows. That is backwards. The executive summary is not a summary at all. It is the argument for why the customer should choose you, made before they read a single technical detail, and it deserves to be planned first.
The mistake is treating "executive summary" literally, as if the job were to compress the rest of the document. The job is to persuade. A good executive summary tells the customer that you understand their problem better than anyone else competing, that you have a credible and specific way to solve it, and that you have done it before. Everything after it is evidence; the summary is the case.
Write it first, not last
The strongest reason to draft the executive summary early is that it forces you to decide what you are actually arguing before you write 60 pages defending it. If you cannot state in a page why you win, the proposal underneath does not have a spine, and evaluators will feel that even if they cannot name it.
Writing it first also makes it a planning tool. The summary becomes the brief the rest of the team writes against: every technical volume should reinforce a claim the summary makes, and any claim in the summary that no later section supports is a promise you cannot keep. This is the same discipline a bid/no-bid decision applies to the whole pursuit, pulled forward into the document itself.
If your capture work was done well, the raw material is already there: you know the customer’s hot buttons, you know your discriminators, and you know what the incumbent or competition cannot say. The summary is where that intelligence finally pays off.
Anchor to hot buttons, not your features
The fastest way to lose a reader in an executive summary is to open with yourself: your founding date, your headcount, your mission statement. The customer does not care yet. They care about their problem.
Open instead with their hot buttons — the handful of outcomes and risks the customer has signaled matter most, drawn from the RFP, from discovery conversations, and from the relationship you built during capture. Name the problem in their language, show you grasp why it is hard, and only then introduce your solution as the answer to that problem. The structure is simple and almost never followed: their problem, your approach to it, the proof you can deliver, the benefit they get.
When you can map each paragraph of the summary to a specific customer concern, the document stops being about you and starts being about them, which is the only frame in which "why you" is a question worth answering.
Lead with discriminators, prove them with past performance
A discriminator is something you can claim that your competitors cannot, that the customer cares about, and that you can prove. "We are committed to quality" is not a discriminator; everyone says it. "Our team delivered this exact capability for an agency of comparable scale, on schedule, with measured results" is, because it is specific and verifiable.
The executive summary should state your two or three strongest discriminators plainly and then immediately back them with evidence. That evidence is usually your past performance: concrete, relevant prior work with outcomes attached. A discriminator without proof is a slogan; proof without a stated discriminator is trivia. The summary is where you weld them together.
This is also where your teaming decisions earn their place. If a partner closes a capability gap or brings the incumbent-beating reference, the summary is where that combined strength becomes a single, confident claim rather than a footnote in a staffing table.
Make it readable, then make it scored
Evaluators are reading under time pressure, so the summary has to be skimmable and persuasive at the same time. A few habits do most of the work: short paragraphs, a clear claim in the first sentence of each, and visuals or callouts that carry the argument for someone who only reads headings. If a busy reader skims only the bold lines and section openers, they should still come away with your win theme intact.
Then pressure-test it the way the customer will. The same color team reviews that vet the full proposal should hit the executive summary hardest, because it is the highest-leverage page in the document. A pink-team read asks whether the argument is even there; a red-team read asks whether it is convincing to someone who wants to score you down. If the summary survives both, the proposal underneath has something to live up to.
Where the CRM fits
An executive summary is only as good as the intelligence behind it, and that intelligence accumulates over the life of a pursuit, not the week of the deadline. When the customer’s hot buttons, the discriminators you validated, and the past-performance references you plan to cite all live on the same pursuit record in Hitt CRM, the person drafting the summary is writing from captured fact instead of memory. Logged activity from every capture conversation is the raw evidence of what the customer actually said matters, and tasks keep the summary draft, its reviews, and its sign-offs moving against the same deadline the rest of the bid runs on. The summary written from a well-kept pursuit record reads like it was written by someone who was in the room — because the record means they effectively were.
The one-sentence version
The executive summary is the one section decision-makers actually read, so write it first as the argument for why you win — opening with the customer’s hot buttons rather than your features, leading with two or three discriminators you can prove with relevant past performance, and pressure-testing it in color team review — and it will give the whole proposal a spine instead of serving as a tired recap nobody planned.