Win themes and discriminators: how to write them, with examples
Short answer: A win theme is a short statement, repeated through a proposal, that links a buyer's most important need to a benefit only you can deliver, backed by proof. A discriminator is the feature or fact behind it that sets you apart from competitors. Write two to four win themes per bid with this formula: buyer's need → your discriminator → the benefit to them → proof. Put them in the executive summary, the section openings that map to the highest-weighted criteria, and the cover letter.
In Iris: Insights (beta) shows your strong suits and capability gaps by topic, drawn from your approved answers and win/loss data, which helps you see which discriminators hold up.
Who this is for: proposal managers, capture managers and sales leads preparing a competitive RFP or proposal.
On this page
- What's the difference between a win theme, a discriminator and a feature?
- How do you write a win theme?
- Win theme worksheet
- Win theme examples: weak vs strong
- Where do win themes go in a proposal?
- Common mistakes
- FAQ
What's the difference between a win theme, a discriminator and a feature?
A ghost is the mirror image: a statement that highlights a competitor's weakness without naming them ("Unlike approaches that require on-premises servers…"). Use ghosts only when they're factual and the weakness is real.
How do you write a win theme?
- List the buyer's hot buttons. Read the RFP's background, evaluation criteria and weights, and your discovery notes. What worries them? What gets someone promoted?
- List your discriminators for this bid, honestly. Ask: would a competitor say the same thing? If yes, it's not a discriminator.
- Match them. Each hot button gets the discriminator that best addresses it. Drop hot buttons you can't answer better than others, and drop discriminators the buyer doesn't care about.
- Add proof. A reference, a metric from a comparable project, a certification, a demonstration. No proof, no theme.
- Write the sentence in the buyer's words, leading with their benefit, not your name.
- Test it: if you swapped in a competitor's name, would it still be true? If so, rewrite.
Formula: [Benefit to buyer] because [discriminator], as shown by [proof].
Win theme worksheet
Fill in one row per theme. Stop at four.
Win theme examples: weak vs strong
All three bids are fictional.
1. Incumbent rebid: facilities maintenance for a county
Why: incumbency isn't a benefit by itself; continuity and data are. The strong version also pre-empts the evaluator's worry about complacency by naming what carries over.
2. New logo: SaaS platform for a mid-size insurer
Why: "cutting-edge" and "best-in-class" are claims any vendor can make. The strong theme names a moment in the buyer's workflow and backs it with proof from a comparable customer.
3. Public sector: case management for a state agency
Why: every bidder is "committed to security." The strong version gives a checkable fact, points to evidence, and links it to the agency's real concern: schedule.
Where do win themes go in a proposal?
Consistency matters: evaluators who read the same theme in the executive summary, the technical approach and the orals remember it.
Common mistakes
- Too many themes. Seven themes are no themes. Two to four.
- Themes about you ("We are proud to…") instead of the buyer.
- No proof. An unsupported theme is just a slogan.
- Discriminators the buyer doesn't value. Unique isn't the same as important.
- Themes invented at the end and pasted into the executive summary, but missing from the body.
- Ghosting with claims you can't verify about a competitor.
How Iris helps
Iris is AI software for RFPs, security questionnaires and proposals.
- Insights. Topic clustering of your approved Q&A, with trends, win/loss by topic, and capability gaps and strong suits, so you can see which topics appear in wins vs losses.
- Requirements against your content. The RFP Analyzer evaluates each requirement against your Knowledge Map (met, partial or likely not met, with sources), a fast way to spot where you can credibly discriminate.
- Proof at hand. Every drafted answer links to its sources, so the proof behind each theme is easy to find and check.
- Tone set once. Custom instructions apply tone, length and modifiers like "sales positioning" or "no marketing fluff" across a project, section or question.
Iris is rated 4.9/5 on G2 from 85 reviews (October 2026). Try Iris free on an RFP you've already answered.
FAQ
How many win themes should a proposal have?
Two to four. Enough to cover the highest-weighted criteria, few enough to remember.
What's the difference between a win theme and a value proposition?
A value proposition is general to your company. A win theme is specific to one buyer and one bid, and is built on what they told you.
What is a discriminator in a proposal?
A feature or fact that the buyer values and that competitors can't match or can't prove.
When should win themes be developed?
Before writing starts, ideally during capture or at kickoff, so writers build sections around them.
Can I reuse win themes across bids?
Reuse discriminators and proof. Rewrite the themes for each buyer's hot buttons.
See it live
Respond to RFPs
without the grind.
Book a demo and see your real auto-fill rate on a translation
RFP from your pipeline.
