A bid/no-bid decision is the structured go/no-go call a firm makes before committing hours to an RFP: you weigh fit, winnability, and the cost of responding against the value of the contract, and you only write when the case holds up. Done well, it’s a scorecard filled in during one careful read, a weighted score, and a threshold you agreed on in advance. Done badly, it’s a gut feeling ratified after someone has already started writing.
Here’s the scorecard: eight weighted criteria, thresholds you calibrate against your own record, and a worked example that lands where these calls usually land — in the uncomfortable middle.
Why the decision matters more than the writing
Every pursuit costs real money before an evaluator reads a word. As an example: a mid-size RFP takes 20–60 hours of response work, so at a blended $125 an hour a single pursuit runs $2,500–$7,500, win or lose (the full math is in our guide to the cost of responding to an RFP). And the odds you’re spending against are roughly a coin flip: the average RFP win rate is 45% as of 2025, up from 43% in 2024, per Loopio’s RFP Response Trends & Benchmarks Report.
The firms that stay above that average are rarely better writers. They’re better pickers. Every weak bid you decline returns those hours to a bid you can actually win — selectivity is the one win-rate lever that costs nothing and works before the writing starts.
What criteria belong on a bid/no-bid scorecard?
Score each criterion 1–5 (1 = bad news, 5 = strong), multiply by its weight, and add up the points. The weights below are a sensible starting framework, not research findings — after a handful of decisions, adjust them to match whatever actually predicted your wins and losses.
| Criterion | The question to ask | Weight |
|---|---|---|
| Relationship with the buyer | Do they know you — or is there an incumbent who does? | 20% |
| Mandatory-requirement fit | Do you clear every "must": certifications, insurance, past performance? | 20% |
| Differentiation | Is there a reason to pick you, stated in their terms? | 15% |
| Competition | How many bidders will show up — and does the spec look wired? | 10% |
| Capacity & deadline | Can you do this well in the time, with the people actually free? | 10% |
| Value vs. effort | Does the contract size justify the hours a real response takes? | 15% |
| Strategic value | Does winning open a market or produce a reference you need? | 5% |
| Terms & risk | Can you live with the liability, payment, and IP terms? | 5% |
Two notes on scoring honestly. Score relationship and competition from evidence, not optimism — "we’d be a great fit" is not a relationship. And a 1 on mandatory-requirement fit isn’t a low score; it’s a disqualification. No weighting rescues a bid you’re not eligible to win.
What score justifies a bid?
Convert the total to a percentage of the maximum — with 1–5 scoring and the weights above, divide your weighted points by five. Then:
- Above ~75% — bid. Strong fit, a real relationship or an open field, and economics that work.
- 60–75% — bid only if you can fix what drags it down. Name the low scores. If they can move before the deadline — a teaming partner covers a gap, the question period clarifies scope — bid; if they can’t, pass. This band is where firms burn the most hours, because a middling score reads as permission.
- Below 60% — skip. Send a polite decline, ask to stay on the bidders list, and put the hours into a stronger pursuit.
Treat the bands as a starting point, not a law. After ten scored decisions, put your scores next to your outcomes: winning at 65% means loosen the middle band; losing at 78% means tighten it. The scorecard’s real product is a paper trail your own history can correct.
A worked example: PipCo scores the Harborlight RFP
An example, with invented numbers. PipCo, a six-person data services firm, is reading a City of Harborlight RFP for a water-usage analytics platform: roughly a $180,000 contract, 62 questions, three weeks to the deadline, and an incumbent vendor whose contract is ending. Line by line (points = score × weight):
- Relationship — score 2, 2 × 20 = 40 points. PipCo has never worked with Harborlight; the incumbent has five years of history there.
- Mandatory fit — score 5, 5 × 20 = 100 points. Insurance, certifications, and two comparable past projects all check out.
- Differentiation — score 4, 4 × 15 = 60 points. The RFP asks for real-time leak detection — PipCo’s specialty, and something the incumbent’s platform doesn’t do.
- Competition — score 2, 2 × 10 = 20 points. Public municipal work draws a crowd, and the incumbent bids from the inside.
- Capacity & deadline — score 3, 3 × 10 = 30 points. Three weeks is workable, but the only free project lead is half-committed elsewhere.
- Value vs. effort — score 4, 4 × 15 = 60 points. $180,000 against an estimated 40 hours of response work is a healthy ratio.
- Strategic value — score 4, 4 × 5 = 20 points. A first municipal reference would open a market PipCo wants.
- Terms & risk — score 3, 3 × 5 = 15 points. Standard city terms, net-45 payment, 10% retainage — livable, not lovely.
Total: 40 + 100 + 60 + 20 + 30 + 60 + 20 + 15 = 345 points of a possible 500, or 69%. Squarely in the borderline band.
The honest call: the drag comes from relationship and competition, and only one can move. Competition won’t change; the relationship picture can sharpen, because the question period is open and every answer becomes public record. So PipCo submits two questions: is the incumbent eligible to rebid, and will evaluation weight leak-detection capability or platform breadth? If the answers read like a spec written around the incumbent, PipCo walks — at a cost of one hour, not 40. If they suggest an open field where the differentiator gets scored, the 69% behaves like a 75% and PipCo bids. That’s what borderline means: not "bid nervously," but "name the thing that must be true, and check it before spending the hours."
Which red flags override any score?
Some findings end the conversation whatever the arithmetic says:
- The spec reads like it was written for the incumbent. Brand-specific requirements, experience criteria only one firm can meet, a scope that mirrors the current contract.
- An impossible timeline. If no one doing honest work could hit the delivery schedule, the buyer either doesn’t know it — or has someone who’s already started.
- Unlimited liability or onerous terms. Uncapped indemnification, assignment of your pre-existing IP, payment terms that make you the bank.
- A budget far below the work. A gap that large isn’t a negotiating position; it’s a loss you’d be volunteering for.
- The buyer won’t answer questions. A silent question period on an ambiguous scope means you’d be pricing a guess.
Any one of these turns a 78% into a no.
Do you need software to decide?
If you bid constantly — a proposal manager on staff, questionnaires arriving weekly — an enterprise platform earns its keep. Loopio- and Responsive-class tools are sold per seat, on annual contracts, through a sales process, and their value comes from a content library someone builds and maintains. Pricing isn’t published, but expect roughly $14,000–$36,000+ a year (approximate, as of 2026 — confirm with the vendor). For a firm that bids a handful of times a year, that model doesn’t fit — the library never fills, and the subscription outlives the enthusiasm. Our small-business RFP software comparison walks the options.
What a low-volume firm actually needs is a cheap go/no-go read — and that’s where the discipline above usually fails. Scoring eight criteria honestly means knowing what’s in the document, and pulling every requirement, the real question count, and the red flags out of a 60-page PDF by hand can eat a day — which defeats the purpose of deciding at all.
Pelican Bid’s free bid/no-bid check does that structured read for you, in minutes: upload the RFP and get the fit read, the red flags, the effort estimate, and the question-count breakdown. No account needed, and the file isn’t stored. With that in hand, the scorecard becomes an hour’s conversation instead of a day’s excavation — cheap enough to run on every RFP that lands.
Frequently asked questions
What is a bid/no-bid decision?
A bid/no-bid decision is the structured go/no-go call a firm makes before committing time to an RFP, weighing fit, winnability, and the cost of responding against the value of the contract. It’s usually made with a weighted scorecard and an agreed threshold, so the call is consistent from bid to bid instead of political.
What criteria should a bid/no-bid checklist include?
Eight cover most cases: relationship with the buyer, mandatory-requirement fit, differentiation, competition, capacity against the deadline, contract value versus response effort, strategic value, and terms and risk. Weight relationship and mandatory fit heaviest — a missed must-have disqualifies you outright, and cold bids against an entrenched incumbent rarely pay off.
What is a good RFP win rate?
The average RFP win rate is 45% as of 2025, up from 43% in 2024, per Loopio’s RFP Response Trends & Benchmarks Report. What counts as good depends on selectivity: bid on everything and you’ll sit below the average; qualify hard and you can sustain a rate well above it. Track your rate on qualified bids — the ones that passed your scorecard — not on everything that hit your inbox.
How do you decline an RFP politely?
Send a short note before the submission deadline: thank the issuer, say you won’t be responding this time, and ask to remain on the bidders list. One honest line of reasoning — scope fit, timing, capacity — is welcome but optional. Declining cleanly costs nothing and keeps the relationship warm for the RFP you do want.
A disciplined no is what pays for a wholehearted yes. When the scorecard says bid, the same rigor carries into the response itself — our guide to how to respond to an RFP walks the process end to end, and the RFP response template gives you a structure to draft against.