What a win theme is, and what it isn't
A win theme answers one question for the evaluator: why should we pick you over the others for this particular need? It is not a slogan, a company value, or a list of features.
Compare these:
- Not a win theme: "We are committed to customer success."
- Not a win theme: "Our platform has 200+ integrations."
- Win theme: "Your team can go live on the new system without pausing month-end close, because we run implementation in parallel with your existing process. We did this for three regional banks last year, all live within one close cycle."
The first is something every bidder says. The second is a feature with no link to the buyer. The third names a buyer concern, a specific approach, and proof.
Most responses need three to five themes. More than that and none of them stick. Fewer than three and you usually leave major evaluation criteria without a clear argument.
Start with the buyer, not your brochure
Themes that come from your marketing deck tend to miss. Build them from what the buyer has told you, directly or indirectly.
Gather these inputs before writing anything:
- Evaluation criteria and weightings. If the RFP says technical approach is 40% and price is 20%, your strongest themes belong in the technical approach.
- Stated requirements and pain points. Read the background and scope sections closely. Phrases like "previous implementation exceeded timeline" or "limited internal IT capacity" are hot buttons.
- Q&A responses and addenda. The questions other bidders ask, and how the buyer answers, often reveal what worries them.
- Capture intelligence. Notes from discovery calls, the incumbent's known weaknesses, and anything the buyer said informally about past vendors.
- Your honest competitive position. Where are you clearly better, where are you equal, and where are you weaker?
Write each buyer concern as a single line in the buyer's own words. That list is the raw material for your themes.
Use a simple formula: need, discriminator, proof
Every win theme should have three parts.
- Buyer need or benefit: what the buyer gets, stated in their terms.
- Discriminator: the specific thing you do that competitors don't, or do less well.
- Proof: evidence the evaluator can check, such as a case study, reference, metric from a past project, certification, or named team member.
A working template:
[Buyer] will [achieve outcome / avoid risk] because [our specific approach or asset], as shown by [verifiable proof].
Example for a facilities management bid:
The county will maintain response times during the transition because our mobilization team has already mapped all 14 sites and pre-hired two supervisors from the local area. We completed a similar 60-day transition for a neighboring county with no missed SLAs.
Write the long version first to make sure all three parts exist. Then create a short version of 10 to 15 words you can use in headings, callout boxes, and the executive summary. For the example above: "Zero disruption during transition, with a team already on the ground."
Test every theme before you use it
Run each draft theme through this checklist. If it fails more than one test, rewrite it or drop it.
- Buyer-focused: Does it lead with the buyer's outcome, not your company?
- Tied to criteria: Can you point to the evaluation criterion or requirement it addresses?
- Discriminating: Could a competitor paste this into their response unchanged? If yes, it's not a discriminator.
- Provable: Is there specific evidence, and is it in the response or an appendix?
- Credible: Would a skeptical evaluator believe it? Overstated claims cost points.
- Specific: Does it include numbers, names, timeframes, or places where possible?
A useful exercise is the competitor swap. Replace your company name with your main competitor's name and read the theme aloud. If it still sounds true, you haven't found your discriminator yet.
Also check for ghosting opportunities. If a competitor has a known weakness, such as offshore support or a history of turnover, a theme that highlights your strength in that area lets the evaluator draw the comparison without you naming anyone.
Place themes throughout the response
A theme that appears only in the executive summary gets lost. Evaluators often score sections separately, sometimes with different people reading different volumes. Each section needs to make its own case.
Where to put them:
- Executive summary. Introduce all themes briefly, usually one short paragraph or bullet each, mapped to the buyer's top priorities.
- Section openers. Start each major section with a one or two sentence theme statement relevant to that section before answering the requirement.
- Headings and callout boxes. Use the short version of the theme in headings or sidebars so a skimming evaluator still picks it up.
- Graphics captions. Captions are read more often than body text. Make each caption state a benefit, not just describe the image.
- Pricing narrative. Connect cost to value themes, for example lower total cost from reduced rework.
- Conclusion or transmittal letter. Restate the themes as a final reminder.
Keep a theme matrix: a simple table listing each theme against each section, showing where it appears and what proof supports it. Reviewers can use it to spot sections with no theme or themes with no proof.
| Theme | Exec summary | Technical | Management | Past performance | Pricing |
|---|---|---|---|---|---|
| Fast transition | Yes | Mobilization plan | Named team | County reference | Transition cost |
| Local support | Yes | Staffing model | Supervisor bios |
Common mistakes to avoid
- Writing themes after the draft. Themes should shape the outline and the writing. Adding them at the end produces bolted-on sentences that don't match the body text.
- Using the same themes for every bid. Reusable themes are usually generic ones. Content can be reused; themes should be built for each buyer.
- Claiming without proof. "Industry-leading" and "best-in-class" with no evidence get ignored or marked down.
- Ignoring weaknesses. If you're the higher-priced option or new to the sector, evaluators will notice. Address it with a theme that reframes it, such as lower lifetime cost or a dedicated senior team.
- Too many themes. If you have eight, merge related ones or cut the weakest.
- Company-first language. Count how often a theme starts with "We" versus the buyer's name or outcome. Aim for the buyer first.
Let pingpong sharpen your bid
Paste the RFP and pingpong maps every requirement, finds your win themes, flags gaps and risks, and drafts the full response and buyer follow-ups, reviewed by five AI models before you see them. $100 for the first month, then $799 a month.
Common questions
How many win themes should an RFP response have?
Three to five is the common practitioner range. That is enough to cover the heavily weighted evaluation criteria without diluting the message. If you have more, look for themes that can be merged under a single buyer benefit.
What is the difference between a win theme and a value proposition?
A value proposition usually describes your company's overall offer to a market. A win theme is specific to one buyer and one bid, tied to their evaluation criteria, and includes a discriminator and proof. Your value proposition can inform themes, but it shouldn't be pasted in as one.
When should win themes be developed in the RFP process?
Ideally during capture, before the RFP is released, and finalized at the kickoff meeting once the RFP is in hand. Writers should have the approved themes and the theme matrix before they start drafting sections, so the themes shape the content rather than being added at the end.