USPs, Win Themes, and Win Strategy

Three distinct concepts that, together, determine whether a proposal is remembered or discarded. This article explains what each one is, how to develop them, and why the order matters.

Most proposals are technically accurate but strategically inert. They describe what an organization does, list relevant experience, and present a methodology. The evaluator reads them, learns something about the bidder, and moves on. Nothing sticks.

Proposals that score well, however, are built differently. Before a word is written, there is a prior document: a short, clear argument for why this organization should win this specific opportunity. That argument is the win strategy. It rests on two prior concepts: USPs and win themes. This article explains all three.

What is a USP?

A unique selling proposition (USP) is not a strength. Every serious bidder has strengths. A USP is a competitive advantage on a dimension that evaluators weight, where your organization outperforms likely competitors, and where that advantage can be substantiated with evidence.

Three conditions must all be true for something to qualify as a USP:

1. Relevant: the advantage must map to something evaluators care about, not just something you are proud of. A 20-year history in public health is irrelevant to an education evaluator assessing curriculum design capability.

2. Unique: the advantage must distinguish you from the other bidders. If every credible organization bidding on this opportunity can make the same claim, it is a qualifying threshold, not a differentiator. "Strong financial management systems" is an expectation. "The only bidder with an existing data-sharing agreement with the Ministry of Health" is a differentiator.

3. Credible: the advantage must be provable. A claim without evidence is an assertion. Evaluators, particularly technical evaluators, discount assertions. The evidence does not need to appear in the USP identification process, but it must exist and be accessible for the proposal.

   
   

The identification process. Start from your competitive assessment, not your organizational profile. List the dimensions on which evaluators will score proposals. Identify where your scores are materially higher than likely competitors. Test each item against the three conditions above. Reduce to two or three. Anything that does not pass all three conditions is not a USP for this opportunity, regardless of how genuine the capability is.

If you cannot identify two USPs that pass all three conditions, the right response is to revisit your competitive assessment, not to proceed with weak differentiators. Proposals built on false USPs produce messaging that evaluators see through immediately.

What a Win Theme Is

A win theme is the donor-facing expression of a USP. The distinction is important. A USP is an internal finding about where you are competitively stronger. A win theme is what you say to the evaluator as a result of that finding. The shift is from your capabilities to their outcomes.

Formula: USP + Evaluator Concern + Specific Benefit = Win Theme

The formula requires knowing what the evaluator is worried about. This is not the same as knowing what the RFP asks for. The RFP states requirements; evaluators have concerns beneath those requirements. A technical evaluator asking whether the methodology is sound is also asking whether it will work in this context, with these communities, given this implementation timeline. A program manager asking about staffing is also asking whether the team can manage coordination across partners without constant escalation.

Win themes are built by connecting your USP to those specific concerns and expressing the result as a benefit the evaluator will receive. The emphasis is on the evaluator, not the organization.

An example:

Not good: We have an established farmer network.

Good: Our existing network of 45,000 farmers enables rapid adoption of climate-smart practices, accelerating results while strengthening long-term sustainability.

The second formulation identifies the same USP but frames it as what the evaluator gets: speed, adoption, and sustainability. Those are the outcomes the evaluator is accountable for. That is why it performs better.

Two to four win themes is the practical range for a proposal. Three is usually sufficient. Fewer than two produces a proposal that feels thin and one-dimensional. More than four produces internal competition between messages, which dilutes all of them. Evaluators remember two or three things after reading a long proposal. Win themes should determine what those things are.

Win Themes Across the Proposal

A win theme is not a tagline for the executive summary. It is an organizing principle that runs through the entire proposal, expressed differently in each section because each section answers a different question for a different evaluator type.

Using the farmer network example, the same theme appears as follows across sections:

Executive Summary

Through an established network of 45,000 farmers, the project will accelerate adoption of climate-smart practices, generating measurable results within the first growing season.

Problem Statement

Previous interventions have struggled to achieve widespread adoption because farmers lack trusted local support structures to sustain behavioral change.

Technical Approach

The project will leverage existing farmer groups to deliver peer-to-peer demonstration plots, reducing mobilization time and increasing participation rates.

Work Plan

Month 1: Mobilization begins immediately through existing cooperative structures.

Sustainability

Because implementation occurs through existing farmer organizations rather than parallel structures, knowledge and practices remain embedded after funding concludes.

Each section uses the same underlying theme but answers a different evaluator question: Why will this work? Why will farmers participate? How quickly can they start? What happens after the project? The theme reinforces itself across the proposal without repeating the same sentence.

After reading the full proposal, the evaluator who remembers "this is the team with the farmer network, they can mobilize quickly, and the results will last" has absorbed exactly what the win theme was designed to communicate. That is the measure of success.

Matching Evidence to Evaluator Type

Win themes require evidence. A theme without substantiation is a claim, and evaluators treat unsubstantiated claims with skepticism. The type of evidence that is most persuasive depends on the evaluator type.

Evaluator Type	What They Trust
Economic buyer	Track record data, cost-efficiency evidence, budget management outcomes
Technical evaluator	Methodology grounded in peer-reviewed evidence, named experts with qualifications, diagnostic M&E frameworks
Program manager	Operational proof, adaptive management examples, documented communication when implementation encountered problems

Using Competitor Positioning

Win themes become more precise when they are designed with competitors in mind. The goal is not to criticize other bidders. It is to frame the evaluative criteria in terms that favor your position.

If the primary competitor has stronger technical credentials but weaker operational depth, win themes should emphasize operational readiness and on-the-ground delivery. This does not require mentioning the competitor. It simply ensures that the dimensions where you are strongest are the dimensions evaluators are focused on when comparing proposals.

A competitive positioning table, built during capture, maps your position against likely competitors on each evaluatively weighted dimension. Win themes are then drawn from the dimensions where the contrast is most favorable to you.

What a Win Strategy Is

A win strategy is a short document, typically one to two pages, that assembles USPs, win themes, evidence, team positioning, and competitive response into a single coherent argument. It answers one question: why should evaluators choose this organization for this specific opportunity?

A win strategy contains four components:

1. Positioning statement. One to two sentences stating the core claim. Not a description of what the organization does, but the argument for why it wins. This is the sentence that the entire proposal should be able to be reduced to.

2. Win themes. Two to three specific, evidence-based messages, each tied to an evaluator concern and a specific benefit. Each theme is stated clearly enough that a proposal writer can apply it to any section.

3. Evidence plan. For each win theme, the specific evidence that supports it and the proposal section where that evidence appears. This ensures that the substantiation exists before writing begins, not after a section is drafted and found to contain unsupported claims.

4. Competitive response. For each significant competitor advantage, how the strategy addresses it through positioning, framing, or evidence. This does not need to be elaborate. A single sentence per competitor advantage is sufficient if it is specific.

Five Tests for a Win Theme

Before finalizing any win theme, apply these five tests. A theme that fails any one of them needs revision before the proposal is written.

1. So What?

   Is the benefit immediately clear to the evaluator, without explanation? If the evaluator has to infer why this matters, the benefit is not stated explicitly enough.

2. Unique?

   Can competitors make the same claim? If yes, this is a threshold quality, not a differentiator. Rework it to isolate the dimension where you are genuinely stronger.

3. Evidence?

   Does proof exist? Past performance data, named personnel, documented results, third-party evaluations. A theme without accessible proof should not be written into the proposal.

4. Evaluator?

   Does this theme directly address a concern in the Winner Persona (explaination in our capture management course)? A technically accurate claim that is irrelevant to evaluator priorities will not move scores.

5. Competitor?

   Does this theme sharpen the contrast with at least one likely competitor? A theme that is equally true of all bidders offers no comparative advantage.

A theme that scores five out of five is ready. Four out of five requires refinement. Three or below requires a complete rework before it enters the proposal.

Summary

The three concepts are distinct and sequential. USPs come from competitive analysis: where you are genuinely stronger on dimensions evaluators weight, supported by evidence. Win themes translate USPs into evaluator language: what the donor receives as a result of your strength, framed around their specific concerns. Win strategy assembles everything into a coherent argument that guides the proposal team.

None of these emerge from reading the RFP. They emerge from capture work done before the RFP arrives. A proposal written without them may be technically complete and still score below a competitor whose narrative is strategically constructed from the first section to the last.

The evaluator who finishes reading a well-built proposal should be able to summarize it in one sentence. If they can, the win themes are working.

Continue Learning

Capture Management Course

USPs and win themes are one module in a full course covering the complete bid process, from early donor cultivation and opportunity qualification through competitive positioning, team strategy, and proposal management. Each module builds on the last.

Learn More