RFP Go/No-Go Decision: A Checklist for Small Businesses
Should You Bid on That RFP? How to Make a Smart Go/No-Go Decision
An RFP go/no-go decision is the choice to pursue or pass on a request for proposal before your team invests time in a response. Small businesses make it by scoring each opportunity against a short checklist covering fit, relationships, capacity, competition, and realistic odds of winning. If an RFP fails the checklist, walking away is a strategic win.
Key takeaways
Treat every RFP as a choice, not an obligation.
Score each opportunity against the same 10 questions before anyone starts writing.
Walk away from any RFP where you can't meet a mandatory requirement, no matter how good the rest looks.
Build relationships before an RFP drops, since many public agencies restrict vendor contact once it's released.
Reinvest the hours you save into fewer, stronger proposals.
What Is an RFP Go/No-Go Decision?
A go/no-go decision, also called a bid/no-bid decision, is a short, structured review your team completes as soon as an RFP lands. Instead of asking "Can we respond?" you ask "Can we win, and is winning worth it?"
Every review ends in one of three calls:
Go: The opportunity fits, you have an edge, and you have the capacity to write a strong response.
Conditional go: The opportunity is promising, but you need to close a gap first, such as confirming a teaming partner or getting an answer during the Q&A period.
No-go: The fit, the odds, or the economics don't justify the effort.
Most teams skip this step because saying no feels like leaving money on the table. It isn't. Every hour spent on a long-shot bid is an hour taken from a proposal you could have won.
Why Do Small Businesses Lose by Bidding on Everything?
Small businesses lose by bidding on everything because every response costs real hours, and spreading those hours across weak-fit bids lowers the quality of every proposal. When your pipeline feels thin, every RFP looks like an opportunity. The math rarely works.
Teams spend an average of 33 hours on a single RFP response and win 39% of the RFPs they submit, according to Loopio's 2026 RFP Response Trends & Benchmarks Report. At those numbers, every contract you win costs about 85 hours of proposal work. For a small business where the people writing proposals also deliver client work, those hours come straight out of your capacity.
Top performers are more selective. The same research found that 81% of top-performing teams, those winning 50% or more of their bids, use a formal go/no-go process, compared with 75% of teams overall. The average organization already responds to only 55% of the RFPs it receives. The question isn't whether to say no. It's whether you're saying no to the right ones.
Bidding on everything hurts you in three ways:
Dilutes quality. Stretched teams copy and paste, and evaluators notice generic answers.
Burns out your team. Rushing from deadline to deadline wears down the people you need most.
Hides the real problem. When you lose, you can't tell whether the proposal was weak or the opportunity was wrong.
As Lisa Rehurek, founder of The RFP Success® Company, puts it:
"You're not losing because you're unqualified. You're losing because you're undisciplined."
A go/no-go process is where that discipline starts.
What Questions Should Your Go/No-Go Checklist Include?
Answer these 10 questions for every RFP, and answer them as a team: the person who will manage the response, someone who will deliver the work, and whoever owns the budget. Each question is written so that "yes" counts in favor of bidding.
Fit
1. Does this work match what we do best? If you have to stretch your services to fit the scope, evaluators will see the stretch too.
2. Can we meet every mandatory requirement? Check licenses, certifications, insurance, bonding, required experience, and vendor registration. Mandatory requirements are pass/fail.
Relationships and Insight
3. Did we know this RFP was coming before it was released? If the RFP is your first contact with the agency, a competitor likely has a head start.
4. Do we understand the buyer's real problem? The scope of work tells you what they're buying. You also need to know why, and what went wrong last time.
Competition
5. Can we compete with the incumbent, or is there no strong incumbent? A satisfied agency with a well-performing incumbent is a hard seat to take. If the incumbent is doing well, score this one low.
6. Is the RFP written neutrally, not around someone else's solution? Requirements that mirror a competitor's product or approach are a warning sign.
Capacity
7. Can we write a strong response by the deadline without dropping client work? A rushed proposal rarely scores well.
8. Can we deliver if we win? Consider staffing, cash flow, and the required start date.
Value
9. Is the contract worth the cost to bid? Weigh the contract value and margin against the hours and people it will take to respond.
10. Does winning move us toward a bigger goal? A strategic win might open a new agency, a new state, or a strong reference for future bids.
Want a guided way to apply these criteria? The Go/No-Go Assessment training shows you how to evaluate opportunities strategically so your time goes to best-fit bids.
How Do You Score an RFP Before You Commit?
A checklist only works if it ends in a decision. Here's a simple way to score one:
Score each question: 2 = yes, 1 = partly or unsure, 0 = no.
Add up the total, out of 20.
Apply one knockout rule: if you can't meet a mandatory requirement (question 2), it's a no-go regardless of the total.
Make the call based on your total:
16 to 20 (Go): Assign roles, set your timeline, and build your compliance checklist.
11 to 15 (Conditional go): Name the gaps, set a date to close them, and decide again.
10 or below (No-go): Decline, send a no-bid notice if the agency requests one, and log the reason.
A lot of 1s means you need more information before you decide. Use the Q&A period to get it.
Adjust the thresholds as you learn. After every award, win or lose, compare your score to the outcome. The Debrief Process training shows how to gather that feedback and turn it into better decisions next time.
What Does a Go/No-Go Decision Look Like in Practice?
Here's a hypothetical example. A 15-person IT services firm finds a county RFP for help desk support on a bid board, two weeks before the deadline. The team scores it together:
Question 1, fit (2): Help desk support is the firm's core service.
Question 2, mandatory requirements (2): The firm holds the required certifications and insurance.
Question 3, advance notice (0): The bid board was the first the team heard of it.
Question 4, the buyer's real problem (1): The scope mentions slow ticket response, but not why.
Question 5, the incumbent (1): The incumbent has held the contract for six years, but the scope hints at service problems.
Question 6, neutral requirements (2): The requirements don't point to any one vendor.
Question 7, writing capacity (1): Two key writers are on another deadline the same week.
Question 8, delivery capacity (2): Staffing and cash flow cover the start date.
Question 9, cost to bid (1): The contract value is modest for the effort.
Question 10, bigger goal (2): It would be the firm's first county client.
The total is 14 out of 20, and the knockout rule doesn't apply, so the call is a conditional go. The gaps are specific: no relationship, an unclear incumbent situation, and tight writing capacity. The team gives itself three days to attend the pre-proposal conference, submit questions during the Q&A period, and free up one writer. If those gaps close, it's a go. If they don't, the team declines and logs the reason.
That's the real value of the process. It turns a gut reaction into a short list of specific things to find out.
When Should You Walk Away From an RFP?
Walk away when a red flag makes winning unlikely or unprofitable. Walk away when you:
Can't meet a mandatory requirement before the due date.
Found the RFP on a bid board with a short deadline and no prior contact with the agency.
Recognize a competitor's product or approach written into the requirements.
Would have to price below a healthy margin to compete.
Can't staff the response without pulling people off paying client work.
Still can't make sense of the scope after the Q&A period.
Saying no is a strategic decision, not a failure. Some agencies ask vendors on their bid list to submit a no-bid response, so check the RFP instructions. A short, professional note keeps you in good standing for the next opportunity.
Still tempted to chase a long shot? The True Cost of Losing an RFP white paper breaks down the lost revenue, sunk bid cost, and team toll behind every lost bid.
What Mistakes Do Teams Make With Go/No-Go Decisions?
Even teams with a checklist can undercut it. Watch for these five mistakes:
Deciding after writing starts. Once people have invested hours, sunk cost makes "no" much harder to say. Score first.
Letting one person decide alone. The person who found the RFP is rarely the most objective voice in the room.
Treating a conditional go as a go. If you never close the gaps you named, you're chasing the same long shot with extra steps.
Skipping the log. Without a record of why you bid or passed, you can't spot patterns or improve your thresholds.
Never revisiting the criteria. Compare scores to outcomes after every award, and adjust the thresholds to match what actually wins.
How Do State and Local Government RFPs Change the Decision?
State, local, and education (SLED) procurement follows its own rules, and those rules shape your go/no-go call:
Build relationships before release. Many public agencies name a single point of contact and restrict vendor communication once an RFP is out, so the groundwork has to happen earlier. The Relationship Building training covers how.
Read the evaluation criteria first. Public evaluators score against published criteria and weights. If the heaviest-weighted criteria play to your weaknesses, count that in your score.
Research past awards. Many agencies post award notices and bid tabulations, and in many states you can request past proposals through a public records request. Use them to size up the incumbent and see what won last time.
Use the pre-proposal conference and Q&A period. Attendee lists can show who else may bid, and the questions reveal what the agency cares about most.
For a deeper look at how state evaluators think, Lisa's newest book, Winning in State Government, walks through her 4x4 Framework™ and the evaluator's perspective.
Make Your Next Go/No-Go Decision With Confidence
Run the checklist on the next RFP that lands, before anyone opens a blank document. The goal isn't to bid less for its own sake. It's to put your best effort behind the bids you can win.
Ready to build the habit?
Start with the Go/No-Go Assessment training to evaluate opportunities with clear criteria.
Learn the full process in RFP Response 101, from evaluating opportunities to organizing your team.
Grab The RFP Success® Playbook for the templates and checklists that take a "go" to submission.
FAQ: RFP Go/No-Go Decisions
How long should an RFP go/no-go decision take?
For most small businesses, a go/no-go review should take less than an hour and happen within a few days of the RFP's release. A fast, documented decision gives your team the full response window if you bid, and frees them to move on if you don't.
What is the difference between go/no-go and bid/no-bid?
There is no real difference. Go/no-go and bid/no-bid are two names for the same decision: whether to invest time and resources in responding to a specific RFP. Use whichever term your team already knows.
What should an RFP go/no-go checklist include?
A go/no-go checklist should cover six areas: fit, mandatory requirements, relationships, competition, capacity, and value. Score every question the same way each time, apply a knockout rule for mandatory requirements, and set clear score ranges for go, conditional go, and no-go.
What is a good RFP win rate?
Teams won 39% of the RFPs they submitted on average in Loopio's 2026 benchmark, and 45% on average from 2019 to 2026. Top performers win 50% or more. A formal go/no-go process is one of the habits that sets them apart: 81% of top performers use one.
Should you bid on an RFP if you have no relationship with the buyer?
Usually not, unless every other factor scores high. Without a relationship, you have less insight into the buyer's real priorities, and competitors who did that groundwork start ahead. If you do bid, request a debrief afterward to start building the relationship.
Is it bad to say no to an RFP?
No. Declining a poor-fit RFP protects your team's time for bids you can win. If the agency asks vendors to submit a no-bid response, send a short, professional one to stay in good standing for the next opportunity.
Who should be involved in the go/no-go decision?
Include the person who will manage the response, someone who will deliver the work if you win, and the person who owns the budget. In a small business, that may be two or three people, or the owner making the call with input from the team.
About the Author
Lisa Rehurek is the founder of The RFP Success® Company, with 30+ years of experience responding to, developing, and evaluating RFPs. She has written 11 books, including five on RFP strategy, and hosts The RFP Success® Show, the longest-running podcast dedicated to government proposals. Her company is a two-time Inc. 5000 honoree (2023, 2024), and its clients have won more than $500M in contracts. Read Lisa's full bio.
Last updated: September 2026
