The RFP go/no-go decision is the cheapest thing a bid team can get right and the most expensive thing it can skip. Every hour spent on a tender you were never going to win is an hour taken from one you might have.
Why the RFP Go/No-Go Decision Matters Right Now
Loopio’s 2026 RFP Response Trends & Benchmarks Report puts the average organisation at 166 RFPs a year, at roughly 33 hours each, and names bandwidth as the number one challenge respondents face. Those figures describe a capacity problem rather than a writing problem. When the constraint is hours rather than ideas, the highest-leverage moment in the whole process arrives before anyone opens a document.
The same report finds that 81% of top-performing teams run a formal go/no-go process. That is the clearest signal in the data. The teams doing best are not the ones answering the most tenders. They are the ones who decided early which tenders to leave alone, then put the recovered hours into the bids they kept.
For a small firm the stakes are sharper. A twelve-person proposal department can absorb a bad call. A firm where bid work is a second job carried by two people cannot. One badly chosen tender does not simply lose; it crowds out the two winnable ones sitting behind it in the same fortnight.
What an RFP Go/No-Go Decision Actually Looks Like
A useful go/no-go is short, written down, and run at a fixed point in the calendar rather than whenever someone remembers. Most workable versions come down to five questions. Do we meet the mandatory criteria without a stretch? Do we have a relationship with this buyer, or are we cold? Have we delivered work of this type and scale before, and can we evidence it? Is the commercial shape something we would actually want to deliver? And do we have the hours between now and the deadline to submit something we would not apologise for?
Score them, set a threshold, and hold the line. The discipline is not in the scoring model, because any sensible model works. It is in agreeing beforehand that a low score means no, then saying no when a low score arrives attached to an appealing logo.
The failure mode is almost always evidence, not judgement. The RFP go/no-go decision gets made on optimism because the honest inputs are hard to reach in the twenty minutes anyone has for it. Nobody can remember whether the firm has bid this kind of scope before, what was promised on delivery, or whether the last three attempts at this buyer went anywhere. So the team defaults to yes, because yes feels like ambition and no feels like giving up.
How BrandWagon Approaches the RFP Go/No-Go Decision
Better go/no-go calls come from better recall. QuoteForge+ RFP makes a firm’s past bids, CVs and boilerplate searchable section by section and ranks what it finds by which bids won. Before committing to a tender, a team can see in minutes what it has previously submitted for comparable scope, what the winning versions of those sections said, and how often bids of that shape converted.
That is evidence, not a verdict. QuoteForge+ RFP does not score tenders and it does not draft responses. It finds, organises and ranks what the firm already wrote, and every result traces back to the real submission it came from. The decision stays with the people who have to deliver the work. They simply get to make it against the record instead of against memory.
There is a second-order benefit worth naming. Teams that can see their bid history honestly tend to say no more often, because the pattern of what has not worked becomes visible. You can see how the section-level search behaves on the QuoteForge+ RFP page.
Writing the No Down
The part most teams skip is recording the decision. A no that leaves no trace teaches the firm nothing, and the same tender shape comes back next quarter to be argued about from scratch. Two lines is enough: what the score was, which criterion failed, and who made the call. Over a year that record becomes the most honest picture of the firm’s bidding that anyone has.
It also changes the conversation with the client-facing side of the business. A decline backed by a written criterion is a position; a decline backed by a feeling is an argument waiting to be reopened by whoever is most senior in the room that day.
Frequently Asked Questions
Who should make the RFP go/no-go decision in a small firm?
Whoever carries the delivery risk, with input from whoever owns the client relationship. In firms of this size that is usually a principal and an operations lead. What matters more than seniority is that the same two people make the call every time, against the same criteria.
How early should the go/no-go happen?
Within the first day or two of the tender landing, before anyone has invested effort that will make walking away feel wasteful. A decision made after twelve hours of drafting is not really a decision.
Does saying no more often reduce the number of bids we win?
Loopio’s 2026 report associates a formal go/no-go process with top performers rather than with lower volume, and separately finds that teams with RFP tooling submit ten more bids a year. We would not put a number on your own outcomes, but the mechanism is straightforward: hours not spent on unwinnable tenders become available for winnable ones.
Getting Started
If your RFP go/no-go decision currently happens in a hallway conversation, the first fix is evidence rather than process. Make your own bid history easy to check before the call gets made. Talk to BrandWagon and we will walk through what your last two years of submissions look like once they are searchable.