The one-line definition
PWin is the probability that you win this specific opportunity. Not the share of bids your company wins on average, and not a measure of how badly you want the work — it is a single number, expressed as a percentage, that answers one question for one pursuit. If you bid this contract as it stands today, against the field that will actually compete for it, how likely are you to be the one the government selects.
That framing matters. A PWin of 35 percent is not a grade on your proposal writing or a verdict on your capability. It is an honest estimate of where you stand on a particular deal, given the customer, the competition, and how much capture work you have done. Treated that way, it becomes the most useful number a capture team produces.
Why PWin drives the bid/no-bid call
A federal proposal is expensive. Bid and proposal — B&P — dollars are finite, and every pursuit you fund is one you cannot spend elsewhere. PWin is how disciplined shops decide where that money goes.
The logic is straightforward. A pursuit with a high PWin and a meaningful contract value deserves real investment. A pursuit with a low PWin, no matter how attractive the ceiling, is a candidate to no-bid or to deliberately under-resource. The bid/no-bid decision is not about whether you could write a compliant proposal — you almost always can — but about whether the expected return justifies the cost of competing.
Across a pipeline, PWin becomes the allocation key. When you rank pursuits by win probability and weight them by value, you can see at a glance where your B&P budget earns the most. The alternative — funding everything that crosses the desk — spreads a small team thin across long-shot bids and starves the pursuits you could actually win. PWin turns a pile of opportunities into a portfolio you can manage.
What actually moves PWin
A small number of factors do most of the work in any honest estimate.
- Incumbency. Holding the contract, or holding adjacent work with the same customer, is the single strongest signal. Incumbents know the requirement, the people, and the unwritten priorities, and they carry transition risk for the government if they lose.
- Customer intimacy. Have you been in the room before the solicitation dropped? Relationships and pre-RFP shaping let you understand what the customer truly needs rather than what the requirements document says on its face.
- Solution fit. How closely your offering maps to the real requirement — not a generic capability, but the specific outcome this customer is buying.
- The competitive field. Who else is bidding, and how strong are they here. A pursuit you would win against three peers is a different bet when a dominant incumbent is defending.
- Price-to-win. Your read on the price the government expects to pay and your ability to get there profitably. A strong technical position does not survive a price that is out of band.
- Past performance. Relevant, recent, well-rated work that the evaluators can point to as evidence you have done this before.
No single factor is decisive. PWin is the synthesis of all of them for one deal.
How to score it honestly
The discipline that makes PWin trustworthy is the gate review. At each milestone in the capture lifecycle, the capture lead presents the pursuit to people who are not emotionally invested in it, and the team reassesses where it stands. PWin is not a number you set once at qualification and carry forward unchanged.
A workable method is a weighted scorecard. List the factors above, weight them by how much they matter for this customer and this competition, score each one against the evidence you actually have, and roll them into a single figure. The structure forces the conversation onto specifics — what do we know about the field, what is our real price position — rather than a show of hands.
The part most teams skip is calibration. Over time, compare the PWin you assigned at each gate against what actually happened. If the pursuits you scored at 60 percent win only a third of the time, your scale is optimistic and your B&P is being misallocated. Calibrating against real outcomes is what turns PWin from a feeling into a forecast.
Where PWin estimates go wrong
Three failure modes recur.
The first is optimism bias. Teams fall in love with pursuits and score the number they hope for. The customer relationship gets inflated, the competition gets discounted, and a 30 percent deal gets carried at 55 percent because no one wants to be the person who calls it. This is exactly what the gate review and an outside reviewer exist to counter.
The second is false precision. A PWin of 47 percent looks rigorous, but the underlying inputs rarely support a number that exact. Treating a rough estimate as a measurement invites bad decisions and false confidence. Bands — low, medium, high, or quartiles — often communicate the real state of knowledge more honestly than a decimal.
The third is scoring once and never updating. A competitor drops out, the incumbent stumbles, the requirement shifts, your price position changes — and the PWin on the books still reflects the day you qualified the deal. A win-probability estimate that does not move as the facts move is not informing decisions; it is decorating them.
How Stratavex Prism calculates PWin
Estimating PWin well is mostly about consistency — the same factors, weighted the same way, scored against real evidence, updated as the pursuit evolves, and calibrated against your own track record. That is exactly the discipline we built Stratavex Prism to enforce. Prism structures each pursuit against the factors that move win probability, keeps the estimate current as the competitive picture changes, and grounds your scale in your actual outcomes — so the number guiding your bid/no-bid calls is one you can trust.