All Field Notes

Field Notes · 6 min read

The bid/no-bid decision: a gate that is allowed to say no

Published June 3, 2026

  • Bid/No-Bid
  • Capture
  • Proposal Operations

The most profitable decision most small contractors never make on purpose is the decision to not bid. Bid/no-bid is treated as a formality — of course we're bidding, we found the opportunity — when it should be the most rigorous gate in the entire pursuit. Every proposal you write that you were never going to win is capacity you did not spend on one you could have.

Why the default is "bid" and why that's wrong

Pipeline pressure makes "bid" the path of least resistance. The opportunity is in front of you, the team is anxious about the funnel, and saying no feels like giving up. So shops bid everything that is vaguely in their lane, win a low single-digit percentage, and burn their best people on proposals that were lost the day the solicitation dropped because of an incumbent advantage or a set-aside they did not truly qualify for.

A real bid/no-bid gate inverts the default. The question is not "is there any reason not to bid?" It is "what specifically makes us think we can win this one?" If you cannot answer that with evidence, the answer is no, and no is a win — it returns capacity to the pursuits you can actually take.

The factors that actually predict a win

Score every opportunity on a small set of honest questions before the team falls in love with it.

Customer relationship. Have you done work for this office? Did you shape this requirement, or are you reading it cold for the first time alongside everyone else? Cold opportunities against an entrenched incumbent are the lowest-probability bids you can make.

Fit to the evaluation. Read Section M before you decide. If the evaluation rewards a past performance profile you do not have, no amount of writing fixes the gap. The RFP shred and a quick read of the evaluation factors should happen before the bid/no-bid call, not after.

Realistic competition. Who else bids this, and why do they win? If you can name three competitors who each have a stronger discriminator than you, you are bidding for second place.

Price-to-win reality. Can you be competitive at a price you can actually perform at? A bid you win by underpricing and then lose money executing is worse than a no-bid.

Capacity. Do you have the people to write this well in the time available, without starving the pursuit you are more likely to win? Two mediocre proposals lose to one good one.

Make it a gate, not a vibe

Put the factors in a simple scored sheet, decide a threshold in advance, and hold to it. The value of writing the threshold down before you score is that it stops the team from rationalizing a "bid" after the fact. A pursuit that scores below the line gets a no-bid, and the no-bid is documented so the next time a similar opportunity appears you remember why.

This is the first deterministic gate in a disciplined proposal workflow for a reason. Everything downstream — capture, win themes, the compliance matrix, the writing — is expensive. The bid/no-bid gate is where you protect that spend by only opening pursuits you have a real, evidenced reason to win. The shops that grow are not the ones that bid the most. They are the ones that bid the right ones and put their whole weight behind them.

GovSight is built by federal acquisition practitioners who crossed over from contracting officer roles to industry contracts directors. We ship PursuitWorks for the proposal pipeline, TeamingWorks for the subcontract pipeline, and three supporting tools for the work around them.

The bid/no-bid decision: a gate that is allowed to say no | Field Notes