Bid/no-bid decision
The go/no-go call on whether to respond to an RFP at all — made once, on the record, against consistent criteria, before any response work begins.
Also called: go/no-go, pursuit decision, qualification gate
A bid/no-bid decision is the call on whether to respond to an opportunity at all. It happens before any response work begins, and in a governed process it is made once, by a named owner, against the same criteria every time.
Most teams have this decision. Very few have it as a decision. It usually happens by default — someone opens the email, the deadline looks tight, a meeting gets booked to talk about capacity, and by the time anyone asks whether the deal is winnable the response is already underway.
Why it matters more than response speed
Organizations submit around 166 RFPs a year on average, up roughly 9% year over year, against an average win rate near 45% (Loopio, 2026). That means a typical team loses somewhere near ninety responses annually.
The instinct when a response team is drowning is to add capacity. But bandwidth is now the number one constraint proposal teams report — for the first time on record — and more capacity applied to an unfiltered queue buys you more losses, delivered faster, at higher cost.
A bandwidth problem is usually a qualification problem wearing a bandwidth costume.
What a real decision weighs
Seven things, in two groups.
Can we win it? Fit (do you actually win deals shaped like this, not could you serve them) · access (a champion who acts, a route to the signer, permission to ask questions before the deadline) · timing (a real forcing event with an owner) · incumbency (can you name the specific failure the buyer will say out loud).
Do we want it? Cost to compete (whose senior hours, and what they’re not doing instead) · complexity (what delivery actually takes — a deal that wins then costs double to deliver is a slow loss) · growth potential (a ceiling or a floor).
Most published frameworks stop at the first group. The second is where an operator’s gate differs from a template.
The governed version
Four elements, and none are complicated. One named owner who can say no and have it hold. One moment, before any response work starts. Consistent criteria, so the answer doesn’t depend on who opened the email or how the quarter is tracking. And a written record of what you believed at intake — which is what lets you check, six months later, whether you were right.
That last one is what turns a filter into a system that improves. Without it you get faster at answering. With it you get better at choosing.
Deeper: You’re not bidding. You’re donating. · From Reactive to Proactive
Rob Roberts is the founder of Widenine Solutions. In B2B SaaS and life sciences since 2011, running Deal Desk and Sales Operations since 2018 — including a Deal Desk built from scratch governing a $25M+ pipeline, and a 2,000+ vetted Q&A library behind 5,000+ responses built and audited.