Here's a number that should bother every BD director in GovCon: the average win rate for federal proposals is around 30-40% for well-run teams, and below 20% for most. That means the majority of proposals your team writes — each one representing 100 to 500 hours of effort — produce nothing.
The instinct is to blame the proposals. "We need better writers." "Our technical approach wasn't strong enough." "The incumbent had an unfair advantage." Sometimes that's true. But more often, the real problem happened weeks earlier, in a conference room where someone said "let's go for it" without a disciplined framework for evaluating whether the opportunity was worth pursuing in the first place.
The bid/no-bid decision is where win rates are actually determined — not at proposal submission, but at the moment your team commits resources to a pursuit. This guide gives you a framework for making that decision consistently, so you stop wasting proposal resources on opportunities you were never going to win.
The real cost of a bad "go" decision
Let's make the math tangible. A moderately complex federal proposal — say, a 50-page technical volume with past performance, staffing plan, and price — takes roughly 200-300 staff-hours to produce. At a fully burdened rate of $75/hour, that's $15,000 to $22,500 per proposal. If your win rate is 20%, you're spending $75,000 to $112,500 in proposal costs for every contract you win.
Now imagine you improve your win rate to 35% by being more selective about which opportunities you pursue. The same $75,000 in proposal investment now produces nearly twice the revenue. You didn't write better proposals — you chose better opportunities.
That's the leverage in the bid/no-bid decision. It's not about saying "no" more often. It's about saying "no" to the right opportunities so you can say "yes" with full commitment to the ones you're most likely to win.
The three-gate framework
Every opportunity your team evaluates should pass through three gates, in order. The gates are designed so that obvious disqualifiers surface immediately, saving your most expensive resource — senior leadership's time and attention — for the opportunities that actually deserve it.
Gate 1: Eligibility (30 seconds)
These are binary. If any answer is "no," the opportunity is dead. Don't rationalize, don't speculate about waivers, don't say "maybe we could partner with someone who's eligible." Just move on.
- Set-aside: Are we eligible for the socioeconomic set-aside (8(a), SDVOSB, WOSB, HUBZone, small business)?
- Vehicle access: Do we hold the required contract vehicle?
- Clearance: Can we meet the facility and individual clearance requirements?
- NAICS/size: Are we eligible and small (if applicable) under the specified NAICS code?
With a standardized opportunity summary in front of you, Gate 1 takes 30 seconds. Without one, it takes 30 minutes of hunting through the solicitation to find these four data points — and we've seen teams spend an hour on a solicitation before discovering they don't hold the required vehicle. That's an hour of senior staff time producing zero value.
Gate 2: Strategic fit (2-3 minutes)
These aren't binary — they're judgment calls. But they should be informed by specific data, not gut feel.
- Customer relationship: Have we worked with this agency/office before? Attended their industry days? Met the program manager? A cold pursuit against an entrenched incumbent is a fundamentally different competitive situation than a warm pursuit with a known customer.
- Scope alignment: Is this our core work, or would we be stretching? The further you stretch from your primary capabilities, the harder it is to demonstrate convincing past performance and technical approach.
- Value fit: Is the contract value worth the proposal investment? A $300K task order that requires the same proposal effort as a $5M opportunity is a bad use of resources unless there's a strategic reason to pursue it.
- Geographic reality: Can you actually staff the place of performance? "We'll figure it out" is not a staffing plan.
- Incumbent intelligence: Who has this contract now? Is their performance strong? Displacing a well-performing incumbent is the hardest thing in GovCon — you need a genuine discriminator, not just a competitive price.
Gate 3: Competitiveness (3-5 minutes)
This is where most teams either rubber-stamp a "go" or get mired in debate. A structured assessment keeps it focused.
- Key personnel: Do you have the required people, by name, available and committed? "We'll recruit someone" is a risk factor, not a staffing plan. If the proposal is due in 21 days and you haven't identified your Program Manager, your probability of fielding a competitive team is low.
- Past performance: Do your references meet the dollar value, recency, and relevancy thresholds? If the solicitation requires $5M+ annual contract value and your best reference is $3M, evaluators will notice.
- Evaluation alignment: Are the evaluation criteria weighted toward your strengths? If past performance is the dominant factor and you have five directly relevant references, that's a strong signal. If technical innovation is the dominant factor and you're proposing a standard approach, you'll score in the middle of the pack. For more on how evaluation criteria should drive this assessment, see our guide: How to Read Section M Like a Winning Capture Manager.
- Competitive landscape: How many firms are likely bidding? Are any better positioned than you? On a vehicle like OASIS+ with hundreds of holders, the competition for any given task order might be 5 firms or 50 — that dramatically changes your Pwin calculation.
- Teaming readiness: If you need a partner, do you have one committed? Teaming arrangements assembled under deadline pressure produce weaker proposals and weaker teams than established partnerships.
A real-world example: the mistake and the smart play
A mid-size IT services contractor we know was on three GovCon vehicles and evaluating 15-20 opportunities per week. They had no formal framework — the BD director would read each solicitation, form an opinion, and present to leadership. Their pursuit rate was around 60% (they said "go" to most things), and their win rate was 12%.
The problem wasn't proposal quality. The problem was that they were routinely pursuing opportunities where they had no customer relationship, marginal past performance, and key personnel gaps they hoped to fill during proposal development. Each losing proposal consumed 200+ hours that could have gone to strengthening the pursuits where they actually had a competitive advantage.
After implementing a structured gate review (using a simple spreadsheet with the criteria above), their pursuit rate dropped to 25% and their win rate climbed to 38% within two quarters. They wrote fewer proposals, won more contracts, and their proposal team stopped burning out on Thursday-night writing sessions for opportunities they were never going to win.
The three mistakes that quietly kill your win rate
Sunk cost reasoning: "We've already spent 20 hours reading this RFP and talking to teaming partners, so we should bid." The 20 hours are gone whether you bid or not. If the framework says no-go after a thorough evaluation, honor the framework. Throwing 200 more hours at a bad opportunity doesn't recoup the 20 you already spent.
Revenue desperation: "We need to win something this quarter." This is the most dangerous bias in BD. Bidding on weak opportunities because you're desperate for revenue leads to losing proposals that consume the resources you needed for next quarter's stronger pipeline. It's a downward spiral.
The "we can figure it out" fallacy: "We'll find a key person." "We'll partner with someone." "Our rates will be competitive if we reduce margin." Every one of these statements is an unvalidated assumption masquerading as a plan. If your path to competitiveness requires assumptions you can't verify before committing proposal resources, the honest call is "conditional no-go pending confirmation."
Making it practical
The framework works with a paper checklist, a spreadsheet, or a structured opportunity summary. The format matters less than the consistency — the same questions, in the same order, for every single opportunity. The moment you start making exceptions ("this one's different, we don't need the full review") is the moment the framework stops protecting your win rate.
For a step-by-step guide on extracting the data these gates require, see: How to Rip Through a Government RFP in Under 10 Minutes.