Bid/no-bid
Bid/no-bid decisions that protect revenue
A strong RFP program is defined as much by what it refuses to chase as what it pursues. Saying no creates room for the opportunities that can actually change the business.
Key takeaways
- Decide before the draft. A bid/no-bid call made after writing starts is a sunk-cost ratification, not a decision.
- Score six factors: fit, value, proof, timing, buyer context, and competition.
- Use three outcomes, not two. Monitor is a real decision that keeps marginal opportunities visible without consuming response effort.
- Make the tradeoff explicit: every weak pursuit crowds out a stronger one.
- Track outcomes by decision reason. That feedback loop is what makes the model smarter each quarter.
Score the pursuit before the draft
The bid/no-bid decision should happen before the team burns time writing. Use fit, value, timing, proof, buyer context, and competitive posture to decide whether to proceed.
- Fit: the requirements match your strongest capabilities.
- Value: the contract size and expansion path justify the work.
- Proof: your team can show credible outcomes or past performance.
- Timing: the deadline supports a response worth submitting.
- Context: the source trail explains why this buyer is moving now.
- Competition: the team understands the incumbent or likely field.
The 15-minute bid/no-bid meeting
The decision meeting should be short because the inputs were gathered before it started. A workable agenda: two minutes on the opportunity summary and source trail, five on the six factors above, three on what the pursuit would displace, and five to commit to a decision and an owner. If the meeting needs an hour, the problem is missing qualification work, not insufficient discussion.
Three outcomes keep the decision honest: bid, no-bid, or monitor. Monitor means the opportunity stays on a watchlist with a named trigger — a draft posting, a budget vote, an incumbent stumble — that would flip it to a bid. Without a trigger, monitor is just a polite no that clutters the pipeline.
Make the tradeoff explicit
Every weak pursuit crowds out a stronger one. Leaders should be able to see what the team is choosing, what it is passing on, and why the decision protects revenue.
- What work will this pursuit displace?
- What would make the opportunity worth pursuing?
- What proof is missing?
- What buyer context is still unknown?
Protect the team from false urgency
A deadline can make every RFP feel important. That does not mean every RFP deserves the same effort. A healthy motion separates urgent from valuable and prevents the team from treating low-fit opportunities like strategic pursuits.
Turn decisions into learning
When outcomes are connected back to source signals and response quality, the bid/no-bid model improves. The team learns which signals were predictive, which proof mattered, and which assumptions were wrong.
The practical mechanism is simple: record the decision reason at decision time, then review win-loss against those reasons quarterly. If pursuits justified by strategic value never convert to follow-on revenue, the model needs a higher bar for that factor. If no-bids keep getting won by competitors you could beat, the bar is too high.
What good looks like
A good bid/no-bid decision is fast, source-backed, and visible. It leaves the team with a clear yes, no, or monitor decision, plus the reason behind it.
Frequently asked questions
What is a bid/no-bid decision?
It is the explicit, recorded choice to invest or withhold response effort on a specific solicitation, made against fixed criteria before drafting starts. Done well it protects win rate and capacity; done late it just ratifies work the team already started.
What criteria should a bid/no-bid decision use?
Six factors cover most situations: requirement fit, contract value and economics, available proof and past performance, timeline runway, buyer context from the source trail, and the competitive field including any incumbent. Score them consistently and record the reasons.
What no-bid rate should an RFP team expect?
There is no universal number, but a team that almost never says no is qualifying too late, and a team that declines nearly everything has criteria detached from its actual capabilities. The more useful metric is trend: as qualification moves earlier, no-bids should happen faster and cheaper, and win rate on pursued opportunities should rise.
Who should own the bid/no-bid decision?
One named owner with input from sales, delivery, and proposal — commonly a revenue or BD leader. Committees without an owner default to yes, because no one wants to be the person who killed a deal. The owner's job is to enforce the criteria, not to win arguments.
Keep reading
- How winning teams spot pre-RFP signals — How winning RFP teams identify buyer intent before a public RFP is posted, and how to turn early signals into qualified pursuits.
- What a great RFP opportunity looks like — A practical framework for deciding which RFP opportunities are worth serious pursuit, and which ones will pull the team away from better revenue.
- Federal vs. commercial RFP motions — How federal, state, local, education, and commercial RFP motions differ, and where the workflow should stay consistent.