Win Probability Engine — Bayesian pWin with 8-Factor Model
Calculates a 0-100 Win Probability (pWin) score for any federal opportunity by weighing 8 quantitative factors. Outputs a GO/NO-GO recommendation, ranked strengths and gaps with mitigation strategies, and a confidence indicator.
Overview
Most federal contractors over-invest in proposals they have little realistic chance of winning. The Win Probability Engine produces a defensible bid/no-bid signal by evaluating 8 factors that historically predict federal source selection outcomes — turning the bid/no-bid call from a judgment exercise into a data-supported decision gate at Phase 02 of the 9-Phase Win Loop.
Why a pWin Engine
The economics of federal proposals are unforgiving. A typical mid-complexity capture and proposal effort costs tens to hundreds of thousands of dollars in capture investment, proposal labor, and opportunity cost. Pursuing low-pWin opportunities wastes that investment. Failing to pursue high-pWin opportunities leaves revenue on the table.
The Win Probability Engine forces explicit bid/no-bid discipline. Opportunities below a threshold pWin generate a NO-GO recommendation. Opportunities above the threshold get the full Phase 03 qualification treatment and feed into capture investment.
The 8-Factor Model
The pWin calculation weighs 8 factors that historically predict federal source selection outcomes. Weights are agency-adjusted because the same factor predicts differently at different agencies (some weight past performance heavily; others weight technical capability or price).
8-Factor Model
Technical capability match
How closely the client's technical capability set maps to the solicitation's technical requirements
Past performance relevance
Relevance, recency, and complexity of past performance to the solicitation's specific requirements
Incumbent vulnerability
Score from the Incumbent Vulnerability model — how vulnerable is the current contract holder?
Pricing position
Where the client's likely bid falls in the Pricing Intelligence engine's recommended band — Aggressive, Competitive, or Conservative
Set-aside eligibility
Whether the solicitation set-aside category matches the client's certifications (8(a), HUBZone, SDVOSB, WOSB, EDWOSB)
Customer relationship
Strength of pre-existing customer relationships at the agency — CO, COR, PM, and end users
Teaming strength
Quality and fit of teaming partners — both subs that fill capability gaps and primes who might team the client in
Competitive landscape density
Expected number of credible competitors based on the NAICS, set-aside, and agency historical patterns
Outputs
- 0-100 Win Probability (pWin) score
- GO/NO-GO recommendation based on score threshold
- Ranked list of strengths and gaps per factor
- Mitigation strategies for each identified gap
- Confidence indicator reflecting data completeness and the strength of underlying signals
Frequently Asked Questions
What is the Win Probability Engine?
The Win Probability Engine is the bid/no-bid decision-support component of the Aliff Solutions platform. It calculates a 0-100 Win Probability (pWin) score for any federal opportunity by weighing 8 factors that historically predict federal source selection outcomes. Output includes a GO/NO-GO recommendation, ranked strengths and gaps with mitigation strategies, and a confidence indicator.
What are the 8 factors weighed for Win Probability?
The 8 factors are: technical capability match, past performance relevance, incumbent vulnerability, pricing position, set-aside eligibility, customer relationship, teaming strength, and competitive landscape density. Weights are agency-adjusted — the same factor predicts differently at different agencies based on historical source selection patterns.
How does the engine produce a GO/NO-GO recommendation?
The engine calculates a pWin score by combining the 8 factor scores using agency-adjusted weights, then compares the score to a client-configurable threshold. Opportunities above the threshold receive a GO recommendation; below receive NO-GO. The threshold is typically set at the pWin level where expected proposal investment ROI turns positive given the client's proposal cost structure and historical win rate.
What mitigation strategies does the engine suggest for low pWin?
Mitigation strategies are tied to specific gaps identified per factor. Low past performance relevance might trigger teaming recommendations with partners holding the missing past performance. Weak customer relationship might trigger customer engagement plan recommendations. High competitive density might trigger price strategy recommendations from the Pricing Intelligence Engine. If multiple factors are weak simultaneously, the engine surfaces NO-GO and the recommendation is to redeploy capture investment to a higher-pWin opportunity.
What confidence levels does the engine provide?
Each pWin score carries a confidence indicator reflecting the completeness and reliability of the underlying signal data. High-confidence scores come from data-rich situations — established NAICS at familiar agencies with multiple data sources confirming each factor. Lower-confidence scores indicate data gaps — newer NAICS, unfamiliar agencies, or sparse historical pattern. Low-confidence scores trigger additional Phase 03 qualification work before final GO/NO-GO commitment.
How is pWin different from win-rate forecasting?
pWin is opportunity-specific — it predicts the probability of winning a specific opportunity given its specific characteristics. Win-rate forecasting is portfolio-level — predicting the percentage of pursuits that will win across a pipeline. Both are useful: pWin drives individual bid/no-bid decisions; portfolio win-rate forecasting drives capture investment budgeting and pipeline sizing decisions.
Why is incumbent vulnerability a factor in pWin?
Federal recompete data shows that approximately 63% of services recompetes retain the incumbent. Pursuing well-performing entrenched incumbents is a low-yield use of capture investment. Pursuing vulnerable incumbents — where the Incumbent Vulnerability Scoring model surfaces 4+ visible weakness signals — substantially improves challenger win probability. The factor links the two engines so vulnerability evidence directly raises pWin.
How does set-aside eligibility affect the pWin score?
Set-aside eligibility is binary at the threshold (you either qualify or you don't) but binary changes can produce large pWin swings. A client with valid SDVOSB certification competing in an SDVOSB set-aside has a substantially smaller eligible competitor pool than the same client in a full-and-open competition. The engine credits the set-aside advantage explicitly and surfaces the implication for capture strategy.
See Win Probability Engine on a live opportunity
Schedule a 30-minute walkthrough. Bring an active pursuit and we'll run it through Win Probability Engine live so you can see the methodology applied to your specific opportunity.
Related Methodology
Incumbent Vulnerability Scoring
Generates a 0-100 displacement potential score for any federal incumbent by analyzing CPARS proxies, protest records, modification history,
Pricing Intelligence Engine
Calculates federal Price-to-Win targets by benchmarking your bid against historical award values, 450,000+ GSA CALC labor rate data points,
Recompete Prediction Engine
Forecasts when federal contracts will recompete by analyzing contract end dates, modification histories, option year patterns, and agency ac
9-Phase Win Loop
A 9-phase, 4-stage continuous capture methodology that blends quantitative AI analysis with expert human judgment across the federal contrac
Win Probability Calculator (Free)
Try the pWin model on a real opportunity — no login required.
State of GovCon Recompetes 2026
Underlying research on federal recompete patterns and incumbent vulnerability.