The Bid/No-Bid Decision: A Framework for Stopping Bad Pursuits Before They Start

The federal government awarded $179 billion in prime contracts to small businesses in FY2025 — nearly 28% of all federal prime contract spending. That's a massive pie. The problem isn't the opportunity. The problem is that most small contractors try to grab too many slices at once and end up dropping all of them.

Industry data puts proposal development costs between 1% and 4% of the total contract value. On a $500,000 contract, that's $5,000 to $20,000 in staff time, consultant fees, and writing effort — spent before you know whether you won. On a $2 million contract, the upper end reaches $80,000.

Now factor in win rates. First-time bidders win roughly 3% of their proposals. Even seasoned contractors with strong past performance and agency relationships typically win 15–25% of what they bid. That means your average federal proposal has a one-in-five shot at best — and your proposal cost is being multiplied by the number of losing bids.

The contractors who grow consistently aren't the ones who bid the most. They're the ones who bid selectively on opportunities where they have a real advantage, and pass on everything else without guilt or second-guessing.

A bid/no-bid framework is a structured scoring tool that evaluates each opportunity against a fixed set of weighted criteria before you commit resources to a response. You score the opportunity, compare the total against a threshold, and make a documented decision.

That sounds clinical. Here's why it matters in practice: without a framework, the loudest voice in the room wins the argument. Someone sees a big dollar value and gets excited. Leadership doesn't want to "leave money on the table." The business developer who found the opportunity pushes for it. A framework replaces those political dynamics with a repeatable, defensible process.

It also creates a paper trail. When a no-bid decision leads to a competitor winning a contract you could have bid, you can look back at the scorecard and see why you passed — instead of spending weeks second-guessing a call that was actually correct.

The framework also forces early action. You can't fill out a scorecard without knowing your incumbent situation, your teaming arrangements, and your relationship with the contracting officer. If you don't know those things by RFP release day, you're already behind — and the scorecard exposes that gap before it's too late to close it.

There's no universal standard for bid/no-bid criteria — every company tweaks the list based on their market, their size, and their strategy. But the following ten factors show up in almost every serious framework, and they cover the questions that matter most.

You don't need all ten. Most effective scorecards use 7–9 criteria. The goal is consistency: use the same criteria for every opportunity so you can compare scores across your pipeline and spot patterns over time.

Not all criteria are equal. Strategic fit matters more for some businesses than profit margin. For a company trying to break into a new agency, relationship strength might be the single most important factor. For a company at capacity, resource availability becomes the deciding criterion.

The standard approach: assign each criterion a weight from 1 to 3 (or 1 to 5 for more granularity). Multiply the weight by the score (1–5) for each criterion. Sum the weighted scores. Divide by the maximum possible total to get a percentage.

In this example, the weighted score is 70 out of a possible 95 — a 74% score. That's above the typical 60–70% bid threshold, so this opportunity is a strong pursuit candidate.

Your threshold is the minimum score required to justify bidding. Most government contractors set this at 60–70% of the maximum possible weighted score. The right number for your business depends on two things: your capacity and your strategic situation.

A few practical adjustments to consider. If you're new to federal contracting and still building past performance, raise your threshold — your margin for error on a bad bid is thinner. If you're at full capacity and your current contracts are profitable, raise it even higher. The opportunity cost of a weak proposal isn't just the proposal cost; it's the distraction from work that's already paying.

Conversely, if you're in a slow pipeline period and need to generate activity, you might lower the threshold temporarily — but be deliberate about it and set a review date. "We're bidding more aggressively until Q3, then reassessing" is a strategy. "We bid everything because the pipeline is dry" is a panic mode that compounds the problem.

Some signals are so reliable that they don't need to survive a scoring process — they should immediately trigger a no-bid decision regardless of how the other criteria score.

These aren't pessimistic takes. They're pattern-matched from decades of federal contracting data. The contractors who recognize these signals early — and act on them — preserve their energy for pursuits where they actually have a shot.

The hardest part of a bid/no-bid framework isn't the scoring — it's delivering the decision to people who are invested in the opportunity. The business developer who found the lead. The executive who was excited about the agency. The program manager who already told someone you were interested.

A few things that make the no-bid conversation easier:

The best contractors in any market use no-bids strategically. Saying no to a weak opportunity frees you to debrief the contracting officer, update your capability statement, and position your company better for the recompete. That's not losing — it's playing a longer game.

Large defense contractors have dedicated capture managers, BD analysts, and price-to-win specialists who run formal gate reviews. You probably don't. That's fine. The principles scale down.

The single best thing you can do to support bid/no-bid discipline is invest in better intelligence before opportunities hit the street. When you've been monitoring an agency's spending patterns, tracking the incumbent's contract expiration, and building a relationship with the program office over six months — the scorecard almost fills itself. You already know the answers.

That's the goal of capture intelligence: arrive at the RFP already informed. The capture management process is how you build that knowledge systematically, and the sources sought response is often your first real intelligence-gathering opportunity on a new pursuit.

For more on how to manage the full lifecycle from opportunity identification to award, read our guides on government contract pipeline management and calculating your probability of win. And when you're ready to evaluate a specific opportunity against your eligibility criteria, CapturePilot's matching engine surfaces the right contracts and tells you which set-asides apply to you automatically.