The SprintProposal developmentPursuit memoryCaptureGraphicsGraduationCompareAboutResultsLearnDoPricingWorkbenchSecurityFAQBook a call →
‹ frwrd.do

Win theme

Capture · win strategy

One or two sentences that connect a customer hot button to a discriminator you can prove, ending in a benefit and a quiet shot at the alternative. The atom of win strategy — everything in the proposal should trace back to one of these.

When you reach for it. Black hat is done, discriminators are identified, you're building the win strategy before pink team. Also any time a writer asks “what's our message on staffing / transition / cyber?” — the answer should be a win theme, not a feature list.

Take the template

Start it in Word

Copy, paste into your document, fill the brackets.

Because [customer's specific, evidenced hot button],
and because [discriminator — a method a competitor cannot truthfully claim],
proven by [quantified past performance: scope + metric],
you get [benefit, in the customer's terms]
— while [the weakness of the likely alternative, unnamed].
Take the prompt

Draft it in Claude

Copy, paste into Claude, add your own inputs.

You are a capture strategist writing a Shipley-style win theme.

Inputs
- Hot button (with evidence/date): ...
- Discriminator (method or capability): ...
- Substantiating past performance (scope + metric): ...
- Likely competitor approach to ghost against: ...

Write one win theme, 2–4 sentences, that:
1. Opens with the customer's pain, made specific and dated.
2. States the discriminator at the level of method, not adjective.
3. Substantiates it with the quantified proof point.
4. Closes with the benefit in their terms, plus a ghost that makes
   the alternative look risky — without naming the competitor.

No marketing adjectives. Every claim must trace to an input.

Why this works

Hot buttonThe customer's pain, specific and dated. “After the 2024 migration took benefits offline for three days” beats “agencies value continuity.” If it could appear in a competitor's proposal too, it's a platitude.
DiscriminatorWhat you do that a competitor cannot truthfully claim, stated at the level of method, not adjective. “Blue-green cutover that switches traffic only after validation” — not “proven, low-risk approach.”
ProofQuantified past performance that substantiates the discriminator. Named scope, real numbers, the same kind of work. A discriminator without proof is just a claim.
Benefit + ghostThe outcome in the customer's terms, plus a contrast that makes the alternative look risky without naming the competitor.

A worked example

After the 2024 migration took benefits processing offline for three days, your team cannot risk another transition that interrupts citizen services. Our blue-green cutover runs the new environment in parallel and switches traffic only after validation — the method we used to move the FSA 240-workload estate to FedRAMP High with zero unplanned downtime and no Priority-1 incidents. You modernize without a single service interruption, while a maintenance-window cutover leaves you exposed for exactly the hours you can least afford.

Is mine right? The tells

Green flags

A stranger could name the customer's actual pain from your hot button. The discriminator survives “so what / says who.” The proof has a number. The ghost is felt, not stated.

Red flags

Adjectives doing the work (“robust,” “proven,” “best-in-class”). A hot button generic enough to paste into any pursuit. No proof point. A ghost that names or sneers at the competitor. A feature wearing a win theme's clothes.

Want the theory behind it? Write a bid your evaluator can score Learn explains why; this is where you grab it.
Sources & further reading
  • Shipley Proposal Guide — win strategy & win themesthe discriminator-plus-proof structure
  • APMP Body of Knowledge — win themes & discriminators

Or have frwrd run this for you.

Grab it here when you’ve got it handled. When the bid matters more than the afternoon, a senior operator builds it — right, on deadline, as part of the pursuit.

Start with the Sprint