Win themes and the swap-name test
If you can swap your company name with a competitor's and the win theme still makes sense, the win theme is fluff. Six examples of themes that fail the test, six that pass, and what evaluators actually score.
The PropLibrary team has a test for win themes that I steal shamelessly. It is one sentence long: if you can swap your company name with another company’s and the win theme still makes sense, the win theme is too generic.
I have read thousands of proposals across my career as a proposal lead. The single most consistent pattern in losing proposals is win themes that fail the swap-name test. The single most consistent pattern in winning proposals is win themes that fail spectacularly when you try the swap.
This post walks through six concrete examples of each. Real-feeling but not real — I’m not allowed to publish the actual win themes from any specific bid, mine or otherwise. The shapes are the truth. The text is constructed to illustrate the shape.
Why the swap test works
A win theme is supposed to do one job. It is supposed to give the evaluator a reason — a specific, defensible reason — to score your proposal higher than the next one in the stack. The evaluator is reading 5 to 50 proposals. They are tired. They are looking for any signal that lets them rank the responses against each other.
If your win theme reads like every other vendor’s win theme, the evaluator gets no signal from it. They score every proposal the same on whatever criterion the theme was supposed to win. The theme was rendered, but it didn’t do the job.
The swap test catches this. Take the sentence. Replace your company name with a plausible competitor’s. Read it again. If it still makes sense, the sentence wasn’t about you — it was about a category of vendors, and the buyer can’t grade you against a category.
Six themes that fail the swap test
These are paraphrased patterns I see constantly. Read each one with our company name, then with three competitor names you can think of off the top of your head.
Fail 1 — The adjective stack.
“Acme Corp delivers superior, proven, and innovative solutions purpose-built for the modern enterprise.”
Swap Acme for Globex. Or Initech. Or Pied Piper. The sentence is identical in meaning. The adjectives — superior, proven, innovative — are not differentiators. PropLibrary explicitly calls adjective stacks like this out as evaluator filter words. They contain no information.
Fail 2 — The capability list as theme.
“With over 15 years of experience, 200+ certified consultants, and presence in 40 countries, Acme is uniquely positioned to deliver.”
Swap. Every competitor in this RFP has tenure, headcount, and a global footprint. The “uniquely positioned” claim is not supported by the evidence in the same sentence. This is a fact dump dressed as a theme.
Fail 3 — The buyer-side flattery.
“Acme understands that [Buyer Name]‘s mission to advance public health requires a partner who shares your commitment to innovation and excellence.”
Swap. Every vendor in this bid is going to write that sentence. The evaluator has read it five times before yours. The buyer’s mission isn’t differentiating you — you’re using it to mirror them, which is fine in a relationship-building meeting and useless in evaluator-graded text.
Fail 4 — The reverse-superlative.
“Unlike other vendors, Acme provides truly customized solutions tailored to your unique requirements.”
Swap. Every competitor will write the same “unlike other vendors” sentence. The phrase has been so overused that evaluators read it as a flag for boilerplate. “Truly customized” is not a claim — it’s a denial of a charge nobody made yet.
Fail 5 — The buzzword cascade.
“Acme’s AI-powered, cloud-native, end-to-end platform delivers transformational outcomes for our partners.”
Swap. The sentence has zero specific claims. It is a list of category labels. Every word in it appears in every competing vendor’s marketing. The evaluator who scores this section has nothing to grade.
Fail 6 — The trust-me theme.
“Acme has a proven track record of success delivering mission-critical projects on time and on budget.”
Swap. “Proven track record” is not a fact. “Mission-critical” is not a fact. “On time and on budget” is a fact only if specific bids are named with their delivery dates. The sentence claims a pattern without showing the data.
Six themes that pass the swap test
These are the same kinds of claims, rewritten so that swapping the company name breaks the sentence. The mechanic each one uses is what makes the swap fail.
Pass 1 — Named, dated, datapoint.
“Acme’s deployment at the State of Vermont migrated 42,000 case files in 11 weeks, six weeks ahead of the State’s compliance deadline. (Public award announcement: VT-DHHS-2024-RFP-117.)”
Swap to Globex. The sentence breaks because Globex didn’t do that deployment. The theme is anchored in a specific, citable past performance. The dates and counts are not adjectives — they’re load-bearing.
Pass 2 — Methodology with a named name.
“Acme’s clinical-data ingest pipeline uses the FHIR R4 conformance harness Acme contributed to the HL7 working group in 2023. The harness is open-source and the test suite is public.”
Swap. Acme is the contributor of the named, public artifact. A competitor can run that harness, but they can’t claim to have built it. The theme is anchored in a verifiable artifact, not a vibe.
Pass 3 — Personnel-anchored.
“The Acme team for this engagement is led by Dr. M. Patel, who served as Director of Clinical Informatics at [public-record-prior-employer] from 2018 to 2023 and led the analogous deployment described in case study A-3.”
Swap. The named lead and her record do not transfer. The theme says: this person, who has a public record of doing exactly this, will lead exactly this. PropLibrary calls this “people as proof” and rates it among the strongest win-theme constructions.
Pass 4 — A counter-intuitive operational detail.
“Acme runs every customer’s data plane in a single-tenant VPC. Multi-tenant cost-optimizations were rejected after the 2022 incident review (public post-mortem). The cost difference is reflected in our pricing schedule, line 14.”
Swap. The architectural choice and the documented incident review are specific to Acme. The theme is making a virtue of a cost choice and showing receipts.
Pass 5 — Limit acknowledged.
“Acme does not currently support FedRAMP High. We support FedRAMP Moderate, ATO’d 2024, registry ID FR-XX-2024. If FedRAMP High is a hard requirement, Acme is not a fit; if it’s a 24-month roadmap requirement, our published roadmap commits to ATO by Q3 2026.”
Swap. The named ATO and the explicit honest limit are both Acme-specific. Evaluators do not score “we do everything” higher than “we do this and not that, and here’s the registry ID.” Honesty is a differentiator in a category where every competitor claims everything.
Pass 6 — The buyer-tied measurable outcome.
“Based on the requirements in section 3.4 and 3.7, Acme commits to migrating [Buyer]‘s 18,400 legacy records in 9 weeks against the 12-week deadline. The 9-week figure is tied to throughput from Acme’s three most recent comparable migrations (A-3, A-7, A-9).”
Swap. The tied outcome — 9 weeks against a 12-week deadline, anchored to three named past performances — does not survive a name change. The theme is committing, not asserting.
What evaluators actually score
The swap test is a heuristic. The mechanism behind it is more specific.
A buyer-side evaluation panel is graded against a scoring rubric. Each section of the proposal has a maximum score and a set of criteria. When an evaluator reads a paragraph, they’re looking for evidence that maps to a criterion. “Superior, proven, innovative” maps to no criterion. “42,000 case files in 11 weeks at the State of Vermont” maps to “demonstrated past performance on comparable engagements,” which is on every public-sector rubric I’ve ever seen.
The swap test is a fast way to ask: does my paragraph contain evidence that maps to a criterion, or does it contain language that fits a category? Evidence breaks under name swaps because evidence is specific to actors, dates, places, and numbers. Category language survives name swaps because category language describes a category, and the category contains every competitor.
The takeaway
Run the test on every win theme in your active proposal. Print the section. Cross out your company name. Write a competitor’s name in. Read the paragraph aloud.
If it still makes sense, you don’t have a win theme. You have a paragraph that takes up space.
The hard part is not the test. The hard part is having the conversation with the SME or executive whose paragraph fails it. The conversation goes better when the test is a checklist than when it’s an opinion.