A Pwin score is a forecast, not a verdict
A Pwin score is a forecast of the probability of winning a specific federal contract opportunity. It is a quantitative input to the GO/NO-GO decision, not the decision itself. A 65% Pwin does not mean you will win. A 25% Pwin does not mean you will lose. Both are weighted estimates of the structural conditions surrounding the pursuit at the moment the score was generated.
The score answers one question: given everything we know about the opportunity, the incumbent, the competitive landscape, your firm's qualifications, and the agency's likely evaluation behavior, what is our best estimate of your win probability if you bid? It does not answer whether you should bid. That is a separate decision involving strategic priorities, capacity, and capability development goals — none of which the Pwin model captures.
Reading a Pwin score well requires understanding what is in the score and what is missing from it.
The factors a rigorous Pwin model considers
A weighted Pwin model evaluates multiple factors. Each factor receives a score, weights are applied, and the result is a percentage. The exact weights vary by methodology, but a defensible model considers:
- Customer relationship — Has the contractor met with the program office? Is there an existing relationship that surfaces requirements early?
- Incumbent advantage — Is the contractor the incumbent? If not, what is the incumbent's structural position on past performance, technical familiarity, and pricing?
- Technical capability — Does the contractor have demonstrated past performance in the required NAICS codes and at the required scale?
- Price competitiveness — Is the contractor's pricing aligned with the government's budget and historical spend on this requirement?
- Teaming strategy — Does the contractor have a teaming arrangement that fills capability gaps the agency cares about?
- Set-aside alignment — Does the contractor qualify for the contract's set-aside requirements (SDVOSB, 8(a), HUBZone, WOSB)?
- Contract vehicle access — Does the contractor hold the required GWAC, BPA, or GSA Schedule? Or does the procurement vehicle exclude the contractor entirely?
- Competitive landscape — How many qualified competitors are expected to bid? What does the competitive density look like in this NAICS at this scale?
Each factor combines into the score. A high incumbent advantage with a weak customer relationship can still produce a middle Pwin. A perfect set-aside alignment with no teaming strategy can fall short. The score reflects the joint condition.
Reading a high score (60% and above)
A high Pwin score means the structural conditions favor your firm. The incumbent position, set-aside fit, vehicle access, customer relationships, and pricing posture all align. A 60%-plus Pwin says: if you bid competently, you have a real chance.
What it does not say: that you will win. Execution risk remains. A high Pwin can be lost through a weak proposal, a teaming partner that drops out, an aggressive competitor, or an evaluation surprise. Treat a high Pwin as license to commit resources to the pursuit, not as a guarantee. The capture work — incumbent profiling, win themes, compliance, color teams — is still required to convert the structural advantage into a win.
What you should do: prioritize. A high-Pwin pursuit deserves your best people, your tightest schedule, and your sharpest pricing. Run all three color teams. Invest in the customer relationship. Do not let a high Pwin lull the team into a thin proposal.
Reading a middle score (30% to 60%)
Most pursuits land here. A middle Pwin says the structural conditions are mixed: some factors favor you, some do not. The pursuit is winnable but requires deliberate strategy.
What you should do: look at the factor breakdown, not just the headline number. A 45% Pwin driven by strong incumbent advantage and weak customer relationship is a different pursuit than a 45% Pwin driven by strong relationship and weak past performance. The first calls for relationship-building investment in the months before the RFP drops. The second calls for teaming with a firm that brings the missing past performance.
Middle-Pwin pursuits are where capture discipline matters most. The high-Pwin ones largely take care of themselves; the low-Pwin ones get cut. Middle-Pwin pursuits require the team to actively shape the conditions — build the relationship, identify the right teaming partner, refine the pricing strategy, sharpen the win themes — before the proposal phase begins.
Reading a low score (under 30%)
A low Pwin does not always mean a no-bid. Some low-Pwin pursuits are worth pursuing for reasons the model does not capture:
- Strategic positioning — bidding signals to the agency that you are a serious player in this market, even if you do not win this specific opportunity.
- Capability development — the proposal effort itself develops a capability statement, builds teaming relationships, or produces past-performance citations you will use later.
- Customer relationship — bidding maintains a relationship with a program office you want to keep warm.
- Recompete preparation — losing this competition with a credible bid positions you for the next one.
What you should do: be explicit about why you are bidding a low-Pwin pursuit. If the answer is "because we always bid this kind of thing," that is not strategy — that is habit, and it is expensive. Document the strategic reason in the GO/NO-GO record. If you cannot, the answer is no-bid.
What to do with the recommendation
The score is one input. The decision is yours. In a Shipley-aligned capture process, the GO/NO-GO meeting is where the score, the strategic context, and the firm's capacity come together. Read the score, read the factor breakdown, read the strategic context, and then decide. Communicate the decision with the reasoning attached — "we are bidding this 35% Pwin because the customer relationship is worth maintaining and the proposal effort produces a past-performance citation in NAICS 541512" — so the team understands why and the firm builds institutional learning over time.
A Pwin score is a tool. Used well, it sharpens decisions. Used badly, it becomes a number that justifies bidding pursuits the team should walk away from. The discipline is in reading the factors, not just the percentage.
Closing
Prime Recon Labs delivers Pwin scoring against your competitive profile in every weekly pipeline digest, with the factor breakdown and a GO/NO-GO recommendation for each matched opportunity. The number is the surface; the reasoning is what makes the recommendation actionable.