Go/no-go decision

A go/no-go decision is the formal review where a team decides whether to bid on an opportunity, weighing fit against the mandatory requirements, the likely competition, and what the response will cost in time. It is a decision to protect capacity, not to express confidence.

Why it matters in B2B sales

Bid capacity is the scarcest resource in a sales organization that tenders. Each serious response consumes senior technical time, finance time, and legal review, and none of that is recoverable. A team that bids everything spreads that capacity thin enough that the winnable deals get the same rushed treatment as the hopeless ones.

The other reason is honesty. Sales teams are optimistic by design, and a bid with no realistic path to winning still feels like activity. A formal review makes the reasoning explicit and repeatable, which is what turns a hunch into a decision the team can review afterward against the actual result.

What to assess in a go/no-go review

Start with the disqualifiers, because they end the discussion fastest: mandatory requirements you cannot meet, certifications you do not hold, turnover or insurance thresholds you fall below, references you cannot supply. None of these are arguable, and finding one on day two is far better than finding it in week three.

Then the winnability questions. Did you influence the requirement, or is this the first you have heard of it? Who is the incumbent and how well defended are they? Do the evaluation weightings favor something you are genuinely strong on? Is the price achievable at a margin worth having? Finally the cost: how many people, for how long, and what else those people would otherwise be doing. Work from what capture management already established rather than starting the analysis from the tender document.

How to run the decision

Run it early, within the first two or three days of the documents landing, and run it with someone who can say no. A review chaired by the person whose number depends on the pipeline will approve almost everything.

Write down the reasons, both ways. The value compounds when you compare the reasoning to the outcome six months later: patterns emerge about which signals actually predicted a win. Most teams discover that the strongest predictor is whether they spoke to the buyer before publication, which changes where the effort goes next year. Tracking win rate split by influenced and cold bids makes that visible fast.

A concrete example

A consultancy receives a public tender worth 1.2 million on a Tuesday. The review happens Thursday. They meet every mandatory criterion, but they have never spoken to the buyer, the incumbent has held the contract for six years with no service issues on record, and quality is weighted at only 30 percent against price. The team declines, and puts the four weeks into two smaller bids where they shaped the requirement. Both are won.

How it shows up in a modern proposal workflow

The reason go/no-go reviews get skipped is that the inputs are scattered. Whether you influenced the requirement, what was said on the last call, who the incumbent is, all of it lives in different places and assembling it takes longer than the meeting itself. Cobl keeps the deal and its history in one workspace, so the review starts from what is known about the account rather than from the tender document alone.

The bids you decline are as much a result as the ones you win. They are just harder to see.

Frequently asked questions

What are common go/no-go criteria?

Mandatory requirement fit, whether you influenced the specification, incumbent strength, evaluation weightings against your strengths, achievable margin, resource cost, and strategic value such as entry into a new sector. Most teams score these and set a threshold rather than debating each bid from scratch.

Who should make the go/no-go decision?

A small group with the authority to decline: typically commercial leadership, the bid or capture lead, and someone from delivery who can say whether the work is deliverable. Including delivery early prevents winning contracts the organization cannot staff.

How often should teams say no?

There is no correct ratio, but a team that declines almost nothing is not running a real review. If win rate on cold bids sits far below win rate on influenced ones, the gap is a direct measure of what the review should be filtering.