Preview: the field guide to win themes that actually win
A teaser for tomorrow's win-themes pillar. Two worked examples — one theme that fails the swap-name test, one that survives it — and what the difference looks like in the response.
Tomorrow I’m publishing the long version of an argument I’ve been making to proposal teams for a decade: most win themes are not win themes. They are slogans that survived a kickoff meeting because nobody pushed back on them. This post is the warm-up — two examples, one that fails the most basic test, one that passes it.
The test is the swap-name test, popularized by PropLibrary: if you can swap your company name out of a win theme and replace it with any competitor’s name and the sentence still makes sense, the theme is generic. The buyer’s evaluator filters generic themes the same way you filter the third “we partner with our clients” boilerplate paragraph in a vendor pitch deck.
A theme that fails
Acme delivers superior cybersecurity outcomes through best-in-class threat intelligence and a customer-first approach.
Replace “Acme” with “Globex.” Replace it with “Initech.” Replace it with the name of the incumbent. The sentence is identical and just as plausible. There is no claim in this theme that ties to a specific evaluation criterion, no proof point that ties to a specific capability, and no thread the response can carry through the technical, management, and past-performance volumes. It is a press release in a single sentence.
This theme will not move a score. It will not make an evaluator pause on the executive summary. It will not give a champion on the buyer side anything to repeat in the down-select meeting. It does no work.
A theme that survives
Of the three vendors on the shortlist, only Acme has run a 24/7 SOC for a customer in your sector at your scale for more than five years — and our retention rate on those customers is 100%.
Try the swap. “Of the three vendors on the shortlist, only Globex…” — the claim either becomes false or becomes a claim Globex has to back up. The theme is anchored in three specifics: the shortlist (acknowledging the competitive context), the sector and scale match (mapping to the buyer’s evaluation criteria), and the retention number (a verifiable proof point). Each specific is a hook the rest of the response can hang evidence from.
This is what a win theme is supposed to do: name a thing about you that connects to a thing the buyer is grading on, with proof.
The full guide tomorrow
The Day 126 pillar walks through six examples — four that fail, two that pass — and the constructive process for building themes from your capture plan rather than from a brainstorm session. It also covers where themes live in the response (executive summary, each major section, cover letter), and the post-mortem discipline that retires themes that didn’t earn their score bump.
If your team has a kickoff meeting tomorrow with “win themes” on the agenda, save the agenda item for Friday. Read the field guide first. The themes you walk in with will be different.
A reading list of the related shorter posts so far:
- Win themes are not value props — the category mistake the field guide opens with.
- Win themes: the swap test — the original short post on the test PropLibrary popularized.
- Win themes for incumbent defense — a special case the pillar references.