Integration with your ERP is critical for accurate forecasting -- Pwin-weighted pipeline value flowing to financial models, contract award data flowing back to close the lifecycle, and historical outcomes calibrating your Pwin model. Our ERP-connected revenue forecasting guide covers the integration architecture in detail.
---
Pwin Scoring: Making It Quantitative
Most contractors get Pwin wrong because they treat it as gut-feel rather than a quantitative score from measurable inputs.
Building a Pwin Model
Score each opportunity across 8 to 12 weighted factors:
| Pwin Factor | Weight | 5 (Best) | 1 (Worst) |
|---|
| Customer relationship | 15% | Multiple meetings, known by name | No contact, unknown |
| Incumbent performance | 15% | No incumbent or poor ratings | Strong incumbent, exceptional CPARs |
| Past performance fit | 15% | 3+ directly relevant contracts | No relevant experience |
| Technical solution fit | 12% | Proven approach, exceeds requirements | Requires significant development |
| Price competitiveness | 12% | Strong cost position | High-cost, limited flexibility |
| Teaming strength | 10% | Agreements signed, gaps filled | No team, critical gaps |
| Set-aside alignment | 8% | Eligible, correct category | Wrong size/category |
| Shaping completed | 8% | RFI, white papers, influence | No pre-RFP engagement |
| Proposal resources | 5% | Full team, experienced writers | Resource conflicts |
Score mapping: 4.0-5.0 = 60%-80% Pwin; 3.0-3.9 = 40%-59%; 2.0-2.9 = 20%-39%; below 2.0 = no-bid candidate.
Calibrating Over Time
After every award, compare bid/no-bid Pwin to actual outcome. Most firms discover that customer relationship and incumbent performance are the two most predictive factors -- often accounting for 40% to 50% of outcome variance. Technical solution quality matters less than most engineers believe. The capture work that builds relationships before the RFP drops is what moves Pwin most. This is why our capture management guide emphasizes pre-RFP activity over proposal-phase execution.
---
What Separates 50% Win Rate Firms from 25% Win Rate Firms
The patterns are remarkably consistent:
They kill opportunities early. No-bid rates of 50% to 60% at qualification. Ten opportunities at 50% Pwin each beats 30 opportunities at 20% Pwin each -- the expected wins are identical, but the resource investment is dramatically different.
They invest in pre-RFP engagement. For every hour on proposal writing, they spend 3 to 5 hours on capture and shaping. This is the inverse of what most small contractors do.
They use data. They track metrics, calibrate Pwin models against outcomes, and fix bottlenecks using stage conversion data.
They treat BD as investment, not cost. High-performers invest 4% to 6% of revenue in BD; low-performers invest 1% to 2%. The difference compounds year over year. For the broader perspective, see our guide on winning federal contracts.
They have dedicated capture resources. No one who wins consistently does it with a BD director who is also the capture manager who is also the proposal manager. Specialization enables the pre-RFP engagement that drives win rates.
---
Frequently Asked Questions
What is the ideal number of opportunities in a GovCon BD pipeline?
It depends on your revenue targets, average contract value, and win rate. A useful formula: Required pipeline entries = Revenue target / (Average contract value x Win rate x Stage conversion rate). For a firm targeting $30M in new awards with $5M average value, 35% win rate, and 60% conversion, that is roughly 28 to 35 opportunities annually. More importantly, maintain 3:1 to 4:1 weighted coverage against your revenue target.
How do I calculate Pwin with no incumbent intelligence?
Start with the base rate for the procurement type. Full-and-open competitions with 5+ competitors: 15% to 20% base Pwin. Small business set-asides: 25% to 30%. Adjust for past performance fit, customer relationships, and technical differentiators. Track estimates against outcomes and recalibrate quarterly.
When should I no-bid an opportunity?
When you have zero pre-RFP customer engagement, the incumbent has exceptional ratings and a strong relationship, you lack relevant past performance with no teaming solution, or the contract value does not justify pursuit cost. The discipline to no-bid is what separates 40%+ win rate firms from those stuck at 20%.
How early should market research start before an expected RFP?
For recompetes, 18 to 24 months before the expected solicitation. The minimum viable capture timeline is 6 months before RFP release -- anything less means you are writing a reactive proposal without customer engagement or competitive intelligence. The difference between 6 and 18 months of capture is typically 15 to 25 Pwin points.
What should a bid/no-bid meeting look like?
Forty-five to 60 minutes for a single opportunity. The capture manager presents a 5-page bid decision package: opportunity summary, Pwin scorecard, competitive assessment, solution overview, teaming status, resource requirements, B&P estimate, and a clear recommendation. Decision makers review, ask questions, and make a binding decision. Do not let it become a strategy session -- that work should have happened during capture.
How do I build a BD pipeline from scratch as a small business?
Start with three things: a target agency list based on your core capabilities, a SAM.gov registration with the right NAICS codes, and a systematic scanning process (even one person, 2 hours per week). Build your initial pipeline around subcontracting and small business set-asides where past performance requirements are less restrictive. Use every win to build past performance citations that unlock larger opportunities. Within 12 to 18 months of disciplined execution, you should have 10 to 15 qualified opportunities in the pipeline.
---
Start Building a Pipeline That Wins
A GovCon business development pipeline is not built overnight, and it is never finished. It is an iterative system that improves with every opportunity pursued, every gate review conducted, and every win/loss debrief analyzed. The frameworks here -- pipeline stages, gate criteria, Pwin models, metrics, and organizational structures -- provide the engineering blueprint. Execution is what turns that blueprint into revenue.
The firms that dominate federal contracting did not get there by writing better proposals. They got there by building better pipelines -- systems that identify the right opportunities earlier, qualify them more ruthlessly, capture them more thoroughly, and submit proposals that are the natural culmination of months of preparation.
Need help building a data-driven BD pipeline? Contact Cabrillo Club to learn how our platform helps defense contractors manage the full capture-to-proposal lifecycle with CUI-safe infrastructure, integrated pipeline analytics, and AI-powered opportunity intelligence.