The most expensive proposal is the one you should never have written. Every bid consumes senior time, subject-matter expertise and capacity that cannot go to a better opportunity. Yet teams under deadline pressure respond to bids they cannot win, then wonder why the win rate sits where it does.

A go/no-go decision is the discipline that prevents this. It is a short, structured decision made early, with clear criteria and a single decision point, so that effort flows to the opportunities worth pursuing. Done well, it is the fastest lever a firm has for improving its win rate – because the bids you decline were dragging the average down.

Every no-bid decision is a bet on a better bid later. Make it deliberately, with evidence, not by default.

Why selectivity raises win rate

The link between selectivity and results is documented. In Loopio’s 2026 RFP Response Trends and Benchmarks Report (1,500+ teams), 75% of teams use a go/no-go process, and teams reported responding to roughly 55% of the RFPs they received. AutoRFP.ai’s 2026 Proposal Win Rate Report found that 71% of high-win teams have a formal go/no-go qualification step, versus fewer than half of low-win teams.

The mechanism is arithmetic. If you can only produce a fixed number of quality responses each month, every weak bid you accept displaces a stronger one. Selectivity does not reduce effort; it redirects it. That is why the go/no-go decision sits at the very start of the process – it is the step that makes every later step worth doing.

For the full response process this feeds into, see How to Respond to an RFP.

The four questions

A disciplined qualification answers four questions, in order. If any answer is clearly no, stop.

  • Is it real? Is there a funded, defined need with a decision that will actually happen? A bid with no budget, no decision-maker or no urgency is a no-bid regardless of how attractive the scope looks.
  • Can we win? Do we understand the requirement, have a credible differentiator, and have any relationship or incumbency advantage? Head-to-head win rates are highest where the buyer already trusts you.
  • Can we deliver? Do we have the capability, the capacity and the resources to deliver what the RFP asks, on the terms it implies? A win you cannot serve is worse than a loss.
  • Is it worth it? Does the expected value and margin justify the cost of bidding and the opportunity cost of the senior time it consumes?

These four map cleanly onto the go/no-go model below, which turns the answers into a score you can compare across opportunities.

A weighted go/no-go model

Use a weighted score rather than a gut feel, so decisions are consistent and defensible. Score each criterion, weight the total, and apply thresholds.

Criterion Weight What good looks like
Capability fit and delivery feasibility 20 We can deliver the requirement without stretching beyond competence
Past performance and proof readiness 15 We have relevant, referenceable evidence ready to cite
Competitive position 15 We know who else is bidding and where we genuinely differ
Capacity and timeline realism 15 We can produce a quality response by the deadline without harming live work
Compliance burden 15 Requirements are clear and manageable, not an unmapped maze
Commercial quality (margin and bid cost) 10 The economics work after bid and delivery cost
Contract and risk 10 Terms are acceptable; no disqualifying liabilities

Apply simple thresholds: a strong score is a bid, a marginal one is a conditional bid, a weak one is a no-bid. Document the score so the decision can be reviewed later against the actual outcome. See the free RFP Go/No-Go Scorecard for a ready-to-use version.

Hard gates that override the score

Some factors are disqualifying, and no aggregate score should be able to rescue them. Treat these as gates, not criteria:

  • A mandatory requirement the firm cannot meet.
  • A conflict of interest or an existing commitment that bars participation.
  • Terms, insurance or certifications the firm cannot lawfully accept.
  • A deadline that cannot be met with the review gates intact.

If a hard gate fails, the answer is no, however attractive the rest of the opportunity looks. The purpose of the gate is to prevent a strong score on the soft criteria from overruling a fatal flaw.

Who decides, and how fast

A go/no-go process fails when it has no owner. Assign the decision to a single accountable person or a small council, and set a service level for how quickly they decide – often within 48 hours of the RFP landing.

  • Give the decision-maker visibility of the data: fit, estimated bid cost, expected margin and win probability.
  • Align incentives. A decision-maker compensated only on revenue will over-bid; one with no stake in growth will under-bid.
  • Make the decision final. The value of the gate is that it stops the debate, so the team can commit or move on.

Saying no without damage

A no-bid is a business decision, not a rejection of the person who brought the opportunity in. Communicate it well:

  • State the specific reasons against the qualification criteria, not a vague “we are too busy.”
  • Cite the evidence – the score, the capability gap, the commercial math.
  • Credit the relationship work that surfaced the opportunity.
  • Flag whether a future version of the opportunity would qualify.

Handled this way, a no-bid preserves the relationship and improves the quality of the next opportunity that reaches the gate.

Run the decision in 48 hours

A go/no-go process that takes a week to produce a decision has already failed. The value is speed, so set a short, predictable window and hold to it.

  • Day 0: the opportunity is logged and skimmed for hard gates, so a disqualifier is caught immediately.
  • Day 1: the seven criteria are scored with the best available data, and unknowns are flagged rather than guessed.
  • Day 2: the decision is made – go, no-go, or conditional with a named condition and a revisit date.

Keep the record to one page. The score does not need to be perfect; it needs to be consistent and defensible. A fast, documented no-go frees the team for the next opportunity, which is the real prize. The most common failure is escalating every marginal bid to a senior meeting, which reintroduces exactly the delay and politics the process was meant to remove.

Common mistakes

  • Scoring after the decision. Deciding on gut feel, then rationalizing a score to fit. Decide from the score, not toward it.
  • No hard gates. A strong soft score rescues a bid with a fatal flaw. Gates must override the total.
  • Too many decision-makers. Committees delay and diffuse accountability. One owner or a small council decides.
  • No revisit trigger. Conditional bids drift into full bids by default. Set a date.
  • Ignoring opportunity cost. The cost of a bid is not only money; it is the better bid you could have run instead.

Frequently asked questions

What is a go/no-go decision?

A structured, early decision on whether to pursue an opportunity, made against defined criteria with a single decision point. It is also called a bid/no-bid decision.

When should the go/no-go decision be made?

As early as possible – ideally within the first day or two after the RFP arrives, and before significant effort is committed. The later it is made, the more sunk cost builds up and the harder it becomes to say no.

What is the difference between a go/no-go and a bid/no-bid?

They are the same thing. “Bid/no-bid” is more common in proposal and capture teams; “go/no-go” is used more broadly in business development.

Who should make the go/no-go decision?

One accountable person or a small council with clear authority, supported by data on fit, cost, margin and win probability. Avoid decision-by-committee, which produces delay rather than discipline.

How do you decide when you are genuinely unsure?

Treat the uncertain cases as conditional bids: proceed only if a specific condition is met (a partner is secured, a clarification confirms scope, a resource frees up). Set a date to revisit; do not drift into a full bid by default.

What if we need the revenue and the bid is marginal?

Need is not a qualification criterion. Bidding on a marginal opportunity because revenue is tight usually produces both a loss and a missed better bid. Score the opportunity on its merits, and treat pressure to bid as a reason to scrutinize the score, not to override it.

Next step

If you are bidding on too many opportunities you cannot win, the fix starts here. Use the free RFP Go/No-Go Scorecard to screen your next opportunity objectively, then see how qualification feeds the rest of the process in How to Respond to an RFP. If you would rather have the decision run for you, book an RFP triage call.

Sources

  • Loopio, 2026 RFP Response Trends & Benchmarks Report (1,500+ teams, developed with APMP): 75% of teams use a go/no-go process; teams respond to roughly 55% of RFPs received.
  • AutoRFP.ai, 2026 Proposal Win Rate Report (94 bid professionals): 71% of high-win teams use a formal go/no-go qualification step.
  • APMP, Body of Knowledge: opportunity assessment, preliminary bid/no-bid decisions, and the cost of qualifying opportunities poorly.

Numbers are cited from their sources and dated; no statistic in this article is invented. Verify figures against the primary sources before republication.