Win themes

A win theme has four parts: the customer's need or hot button, your discriminator that meets it, the proof (past performance, a metric, a named method), and the benefit to the customer. For example: a transition plan that keeps every help-desk seat staffed from day one, proven on two recent transitions with no service gap, so users notice nothing.

Themes come from capture: the capture plan is where the team learns what the customer worries about. A theme written without that knowledge tends to praise the company instead of solving the customer's problem.

Each theme should map to an evaluation factor in Section M, appear in the executive summary, and be carried into the sections that factor scores. Evaluators score against the factors, so a theme that answers no factor earns nothing.

Mistakes to avoid: generic claims any bidder could make ("experienced, dedicated team"), themes with no proof, too many themes, and themes that never reach the technical sections where points are actually given.

A practical test for each theme: could a competitor put its own name on the sentence and still be telling the truth? If so, the theme is generic and needs a sharper discriminator or better proof. Another test is placement: read only the executive summary and the first paragraph of each technical section, and check that every theme appears at least once where the matching factor is scored. Reviewers in a Pink or Red Team often catch missing themes faster than the writers, because they read the way an evaluator does.