Three exec summaries I rewrote this week, part 2
Three illustrative before-and-after exec summary openings. The patterns that fail, the edits that work, and why the second sentence is where most exec summaries lose the reader.
The executive summary is the shortest, most consequential document in a B2B proposal. It is also the place I do the most editorial work, because most first drafts spend their first paragraph apologizing for existing.
Here are three openings I rewrote this week. The before-and-afters are illustrative — they’re patterns I see across many drafts, not specific bids — but the failure modes are the ones that actually recur.
One — the throat-clearing opener
Before.
Acme Corp is pleased to submit this response to your Request for Proposal for Enterprise Data Platform Services. We have carefully reviewed the requirements outlined in the RFP and are confident that our solution can meet your needs. With over 15 years of experience and a team of dedicated experts, we are well-positioned to deliver value to your organization.
Three sentences, zero claims. The reader knows the vendor is pleased, has read the RFP, and has 15 years of experience. None of that earns reading the next paragraph.
After.
You are replacing a self-managed Hadoop cluster that has cost your team 1.2 FTE per quarter in operations overhead. We are responding to that, specifically. The platform we propose runs the same workloads at 0.2 FTE of operations cost, with audit trails the security review you ran in March said you didn’t have today.
The first sentence names the buyer’s situation. The second commits to addressing it. The third stakes a specific claim against a specific buyer-side problem the capture work surfaced.
The structural rule: the first sentence is about the buyer, not about the vendor.
Two — the feature-list executive summary
Before.
Our platform offers a comprehensive suite of capabilities including data ingestion, transformation, governance, and analytics. With advanced AI-powered features and an intuitive user interface, our solution provides everything your team needs in one integrated package.
This is product marketing copy in an executive summary slot. It lists capabilities. It doesn’t tell the buyer what they’ll get done that they couldn’t get done before.
After.
The capability you flagged as priority one — schema-on-read across the four legacy sources you listed in Section 3.2 — is in production today for two of your industry peers. The capability you flagged as priority two — automated PII redaction — is what we built last quarter against the same Office of the Inspector General guidance you cite in your security appendix.
The features are the same. The framing is different. Each capability is named against a specific buyer-side priority, with evidence. Win themes don’t show up by being italicized; they show up by being how every paragraph is structured.
The structural rule: every capability claim is a buyer-priority response, not a vendor inventory line.
Three — the win theme that fails the swap test
Before.
Acme delivers integrated, reliable, and adaptable solutions designed to drive operational excellence and deliver value for our customers.
Replace “Acme” with any other vendor name in the bid. The sentence still works. PropLibrary calls this the swap test, and it’s the right gate to put on a win theme. If the swap test passes, the win theme isn’t a win theme — it’s filler the evaluator filters out before the second read.
After.
Our edge: we are the only vendor in this RFP shortlist whose platform was built against the federal data-classification scheme you operate under. Our customer reference list is half DoD. Every capability in this proposal was first shipped against a buyer who reads the same NIST 800-171 controls you do.
Specific. Defensible. Cite-able. A competitor cannot copy this and have it remain true. That is what a win theme is supposed to do.
The structural rule: write the sentence; replace your company name with your competitor’s; if the sentence still parses, rewrite it.
The pattern under all three
Most weak exec summaries fail in the second sentence. The first sentence is a polite hello. The second sentence is supposed to commit. Most second sentences re-state the polite hello in different words and never commit.
The edit I make most often is to delete the first sentence and start with what would have been the third. The rest of the rewrite usually follows from that.
Part 1 of this thread ran in May; Part 3 lands in July with three more, including a federal example where the structural rules fight the boilerplate the contracting officer expects to see.