Win themes are not value props

A win theme is not a value prop. A value prop is what your marketing site says about your company in general. A win theme is what your proposal says about why this specific buyer should pick you for this specific contract. The two are routinely conflated. The conflation is most of why win themes fail.

PropLibrary published a swap test that I have been quoting at proposal teams for years. The test: take your win theme, swap your company name with any competitor’s, and read it back. If the theme still makes sense, it is too generic to be a win theme. It is a value prop in a costume.

I have rewritten win themes for a long time. What follows is six examples, anonymized but drawn from real proposal drafts I have seen. Four fail the swap test. Two pass.

The four that fail

Example 1 — the abstract noun stack

“Acme delivers a powerful, flexible, end-to-end platform that enables your team to achieve operational excellence.”

This is a win theme that has been on a hundred proposals. It is on yours, possibly, right now. Swap “Acme” for any other vendor in the category — Loopio, Responsive, QorusDocs, Upland, PursuitAgent, anyone. The sentence still makes sense. It still says exactly nothing.

The diagnosis: the sentence is built entirely out of category words (“platform,” “operational excellence”) and adjective filler (“powerful, flexible, end-to-end”). There is no buyer-specific noun. There is no proof. An evaluator scoring this sentence has nothing to grade.

This sentence appears in real proposals because somebody on the proposal team, under deadline, stitched together approved corporate language and called it a theme. It is not a theme. It is a description of the company that happens to be filed under “Win Themes” in the document.

Example 2 — the marketing slogan

“Where innovation meets execution.”

This passes for a win theme in a lot of proposal templates. It is a marketing slogan. Marketing slogans are designed to be memorable in isolation. Win themes are designed to be evidence-weighted in context. They are different artifacts.

Swap test: change “Acme” to anyone — except there’s no “Acme” in the slogan to swap. That’s the tell. A win theme that doesn’t even mention the buyer or the bidder by reference is not a win theme. It’s a tagline.

Example 3 — the recycled value prop

“Acme is the proposal-software platform that helps proposal teams win more bids in less time.”

This is the company’s homepage hero, copy-pasted into the executive summary. Same problem: swap the company name and the sentence is unchanged. It also has the secondary problem of being self-evident in a way that insults the evaluator. Every vendor in the category claims to help teams win more bids in less time. Restating the category promise in your win theme is not differentiation; it is fluff that has been reformatted as substance.

Example 4 — the qualified value prop

“Acme is the only proposal-software platform built natively on grounded AI, allowing your team to draft compliant responses without hallucination risk.”

This one is closer. There is a qualifier (“built natively on grounded AI”) and a claim (“without hallucination risk”). It almost passes. The reason it doesn’t: the qualifier is still a category-level claim that any vendor with grounded AI as a feature could put in their own proposal. The “your team” is generic — it does not refer to this buyer’s team or this buyer’s situation. The win theme passes as a piece of category positioning. It does not pass as a thread that an evaluator can follow through the proposal looking for evidence specifically tied to this procurement.

A proposal evaluator reading this theme will not know what to look for in the rest of the document. The theme does not commit the proposal to anything specific.

The two that pass

Example 5 — the buyer-specific theme

“Because the State Health Agency is migrating 17 legacy claims systems on a 2026 federal compliance deadline, Acme’s pre-built FedRAMP High-certified migration patterns — used in 14 state migrations since 2022 — reduce the integration risk that would otherwise concentrate in the final 90 days of your timeline.”

Swap test: change “Acme” to a competitor. The sentence breaks. The “pre-built FedRAMP High-certified migration patterns” and “14 state migrations since 2022” are claims tied to a specific track record. A competitor swapping in their name has to either match the claim (in which case they need their own evidence) or omit it (in which case the theme is gone).

What makes this work: it names the buyer’s specific situation (17 legacy systems, 2026 deadline), it names the bidder’s specific evidence (14 state migrations since 2022), and it names the specific risk being reduced (integration concentrated in final 90 days). An evaluator reading this theme knows exactly what to look for in the technical section: the migration pattern, the 14 case studies, and the timeline analysis.

Notice what this theme is not. It is not punchy. It is not memorable in the marketing sense. It is a long sentence with proper-noun specificity and a number. Win themes are not bumper stickers. They are scoreable claims.

Example 6 — the differentiated process theme

“While the incumbent has staffed this contract with rotating contractors averaging 14 months of tenure, Acme will commit a named team of seven engineers — five with prior experience on the Department’s previous case-management procurement — for the full three-year contract period, with named-staff retention contractually backed.”

Swap test: change “Acme” to a competitor. The sentence breaks because the contractual commitment to named staff with prior agency-specific experience is a specific claim a different vendor would have to substantiate independently. The reference to the incumbent’s contractor turnover is also pointed; a generic competitor’s theme wouldn’t include it because they wouldn’t know the incumbent’s staffing history.

What makes this work: the theme picks a specific weakness in the incumbent’s likely position (contractor turnover), proposes a specific differentiator (named, retained team with prior agency experience), and binds it with a specific contractual mechanism (named-staff retention contractually backed). Three commitments in one sentence, each of which an evaluator can grade.

Why the failures look like wins on the way to the page

The four failed themes don’t look like failures when they get drafted. They look like polished, on-message sentences that have survived a marketing review. The proposal manager nods. The capture lead nods. The senior writer who knows better nods because the deadline is in three days.

The four themes also share a structural property: they were written before the capture work was complete. Generic themes are what a proposal team writes when they don’t yet know the buyer well enough to write a specific theme. Specific themes — the kind that pass the swap test — are downstream of capture work. The capture plan tells you what the buyer cares about, what the incumbent’s weaknesses are, what the buyer’s stated and unstated priorities are. Specific themes assemble themselves out of that material. Without it, you fall back to category language, because category language is the only material you have.

This is why win-theme rewriting at red team is too late. By red team, the proposal is structured around the early themes. Pulling out generic themes and inserting specific ones at red team requires also restructuring the technical section so the themes actually thread through. Most teams don’t have the time. So the generic themes ship.

What good looks like, structurally

Three things, learned the hard way:

1. Win themes get written between bid/no-bid and the start of drafting. Not before bid/no-bid (you don’t know enough), not during drafting (you don’t have time). The window between those two stages is short — a week, maybe two. The proposal manager guards it.

2. Each theme is bound to specific sections of the proposal that will carry the evidence. If theme one is about migration risk, the technical section’s risk-management subsection is the place the theme is proven. Mark it on the outline.

3. Themes get re-tested at gold team with the swap test. The gold-team rubric should explicitly include “swap test: does this theme survive a competitor name swap?” Themes that fail the swap test at gold team get rewritten in the 24 hours before submission. This is uncomfortable. It is also cheaper than shipping themes that the evaluator will skim past.

The honest limit of the swap test

The swap test is a heuristic. It is not a guarantee. A theme can survive the swap test and still fail to win the bid — themes only carry their weight when the proposal that follows actually proves them. A theme can also fail the swap test and still appear in a winning proposal, because the rest of the proposal made up for the theme’s weakness.

What the swap test buys you: a fast, cheap, every-proposal-team-can-do-it test that catches the worst category of failure (generic themes that say nothing) before submission. It does not catch every failure. It catches the most common one.

If your team’s themes fail the swap test, the work to fix them is real. The work to ship without fixing them is also real, just deferred — into a lower win rate that nobody traces back to the themes because nobody ran the test.