developing-win-strategylisted

# Developing Win Strategy Turn customer knowledge and competitive analysis into a win strategy: the validated discriminators, the substantiated win themes, the ghosting language, and the plan for the team's own exposures. This is the difference between a proposal that is merely compliant and one that is built to win. Compliance answers every requirement. A win strategy gives the evaluator a reason to pick *this* offer over the others. ## When to use this skill Use this skill late in capture, once customer hot buttons, the competitive field, and the price posture are understood, to set the strategy the proposal will execute. The win strategy is the bridge from capture to proposal development: `outlining-proposals`, `drafting-proposal-sections`, and `writing-executive-summaries` all consume it. Re-run it when the RFP releases and Section M is known, to map themes to the actual evaluation factors and re-test discriminators against the real criteria. ## Inputs **Preferred upstream artifacts:** - `02-capture-plan.md`: customer hot buttons, biases, and the requirement read. - `03-competitive-assessment.md`: competitors' likely themes, the ghosting opportunities, and the team's exposures. - `04-price-to-win.md`: the price posture the strategy must be consistent with. - The solicitation, if released — Section M evaluation factors. **Without the upstream artifacts**, the skill runs from intake, but a win strategy built without a competitive assessment cannot validate the *rar