A probability, not a feeling
Ask a capture lead how a pursuit is going and you often get a mood: "feeling good about this one," or "it is a long shot but worth a look." Win probability — Pwin — replaces the mood with a number. It is your honest estimate, expressed as a percentage, of the odds you win a specific pursuit if you bid. A 70 percent Pwin and a 20 percent Pwin are different worlds: one deserves your best proposal team, the other deserves a hard look at whether to bid at all. The number forces a conversation that a feeling lets you avoid.
The discipline is not in the precision — nobody can say a bid is exactly 63 percent likely — but in being consistent and honest. A Pwin that is always 80 percent because the team is optimistic is as useless as no estimate at all. The goal is a number that genuinely moves with the evidence and that you are willing to be wrong about out loud, because a Pwin you never check against outcomes never gets better.
What actually moves the number
Pwin rises and falls on a handful of real factors, and naming them keeps the estimate honest instead of optimistic. Do you have a relationship with the customer, or are you a stranger walking in at RFP time? Is there an incumbent, and is it you or someone else — incumbency is one of the heaviest weights on the number in either direction. Do you have clear discriminators and the past performance the evaluation will reward? Did you get to shape the requirement before it was final, or are you reacting to language someone else influenced? How many credible competitors are in the field?
Each factor pushes the number up or down, and writing them down rather than holding them in your head is what makes the estimate defensible. A Pwin of 40 percent that comes with "strong relationship and past performance, but the incumbent is solid and we did no shaping" is a number leadership can act on. A bare "40 percent" is a shrug with a decimal point.
Pwin is a living number, not a one-time guess
The most common mistake is estimating Pwin once — usually at bid/no-bid — and never touching it again. But the whole point of capture is to change the number. You start a pursuit at, say, 25 percent because you have no relationship and no shaping done. Then you build a relationship with the program office, your RFI ideas show up in the draft, a competitor drops out — and your Pwin should climb to 45, then 60, as a direct result of work you did. If it does not move, your capture effort accomplished nothing, and that is worth knowing.
Re-estimating at each gate review turns Pwin into a scoreboard for capture itself. A pursuit whose Pwin refuses to climb despite months of effort is telling you something the optimism in the room will not: this is not winnable, and the capture work is not changing that. A rising Pwin justifies pouring in more resource; a flat one is a quiet no-go forming.
How Pwin drives real decisions
The number is only worth tracking because it drives action. It governs where you spend scarce capture and proposal capacity: a portfolio is won by feeding your best people into the high-Pwin pursuits and starving or killing the low ones, not by spreading effort evenly across everything in the funnel. It feeds pipeline forecasting directly — a weighted pipeline that multiplies each pursuit’s value by its Pwin gives leadership a far more defensible number than a raw sum of everything you are chasing. And it shapes your price-to-win: a high-Pwin pursuit where you hold real discriminators can support a price premium, while a low-Pwin bid you are chasing on price alone should make you ask whether it is worth winning.
Keep yourself honest with history
A Pwin process improves only if you check the estimates against what actually happened. The pursuits you scored at 70 percent — did you win roughly seven in ten? If you win 90 percent of your 70-percent bids, you are sandbagging and probably walking away from winnable work; if you win 40 percent of them, you are fooling yourself and burning proposal teams on long shots. This calibration is the same loop as a good win/loss analysis: the value is not in any single estimate but in the pattern across many, which slowly teaches the team what a 70 actually feels like.
Where the CRM fits
Pwin is only useful if it lives where the pursuit lives and updates as the pursuit changes. When each pursuit is a record in Hitt CRM carrying its current win-probability estimate alongside the logged capture history that justifies it, the number stops being a guess in someone’s head and becomes a field the whole team reads from the same place. A weighted pipeline report multiplies each pursuit’s value by its Pwin to give leadership a forecast it can defend, automations can flag a high-value pursuit whose Pwin has stalled for weeks, and reviewing closed pursuits — what you estimated versus what you won — is how the estimates get calibrated over time. The number drives the portfolio, and the portfolio lives in the system.
The one-sentence version
Win probability is your honest, written-down estimate of the odds you take a pursuit, and its power comes from treating it as a living number that moves as relationships, shaping, and competition change — re-scored at every gate, used to steer capture effort and weight your forecast and set your price, and calibrated against real outcomes so a 70 percent estimate actually means you win about seven in ten.