Most founders have no idea if their RFP win rate is good or broken, because nobody tells them what normal looks like. The honest answer: a normal RFP win rate for B2B SaaS startups sits between 30% and 45%, with most teams landing closer to 35-39% once you measure over a full year instead of a single quarter.
That number is almost useless on its own, though. Your win rate depends entirely on which kind of RFP you're responding to, and lumping every deal into one average is why most founders think they're underperforming when they're actually fine, or think they're fine when they're quietly bleeding deals they should be winning.
The benchmark numbers, and why the average lies
30-45% is the blended average across every RFP a B2B SaaS company responds to. But that blend hides three very different games.
Incumbents defending an existing contract win 60-80% of the time. Vendors with a warm relationship who helped shape the requirements before the document existed win 60-90%. Cold RFPs, the ones that land in your inbox from a buyer you've never spoken to, win 10-20%.
If your overall number is 35% and you're mostly responding to cold, unsolicited RFPs, you're actually outperforming benchmark. If that same 35% comes from a mix that's supposed to include warm relationships, you're underperforming badly and don't know it yet.
The one signal that predicts your win rate before you write a word
The single biggest predictor of whether you win an RFP isn't your proposal quality. It's whether someone from your team talked to the buyer before the RFP existed.
Buyers who write the requirements almost always write them around the vendor they've already talked to, whether they realize it or not. That vendor's product terminology ends up in the spec. Their pricing model becomes the assumed structure. Their case studies become the implicit bar.
If you're seeing the RFP for the first time when it lands in your inbox, you're not competing on equal footing. You're competing against a document that was quietly written to describe someone else's product.
How to benchmark your own number correctly
Two mistakes make founders distrust or misread their own win rate.
The first is measuring quarterly. A team that responds to 4-6 RFPs a quarter doesn't have a real sample size. One large deal swings the percentage 15-20 points either way. Track win rate on a rolling 12-month basis instead, and only start drawing conclusions once you've closed or lost at least 15-20 RFPs.
The second is not segmenting by relationship type. Before you calculate anything, tag every RFP in your pipeline with one label: warm (you talked to the buyer before the document existed) or cold (you didn't). Calculate win rate separately for each bucket. A blended number across both tells you almost nothing actionable.
If you're under 20%, don't fix your writing first
Founders who see a low win rate usually reach for the proposal. They rewrite the executive summary, add more case studies, hire a proposal consultant. That's rarely the actual problem.
If your win rate is under 20%, the issue is almost always qualification, not writing quality. You're responding to RFPs you were never going to win: deals where an incumbent is entrenched, where the requirements were written around a competitor, or where the buyer has no real budget approved. No amount of proposal polish fixes a deal that was decided before you were invited to bid.
Before improving how you write RFP responses, fix which RFPs you respond to. A hard go/no-go filter, applied before your team spends a single hour, will move your win rate more than any template.
What to track starting this quarter
Three fields, added to whatever you're already using to log RFPs:
- Relationship type: warm or cold, based on whether you spoke to the buyer before the document existed.
- Deal size band: RFPs behave differently at different contract values, and blending them hides which band you're actually strong in.
- Outcome and reason: won, lost, or no-decision, with one line on why, pulled from debrief when you can get it.
After 15-20 tracked RFPs, you'll have a real number instead of a guess, and you'll know whether the fix is your qualification process or your response quality, not just a feeling that something's off.
Frequently asked questions
What's a good RFP win rate for a B2B SaaS startup? 30-45% blended is normal. Above 20% on cold, unsolicited RFPs is solid. Above 60% only makes sense if most of your pipeline is warm relationships or incumbent renewals.
Why is my RFP win rate so low? Almost always qualification, not proposal quality. Check whether you're bidding on deals where an incumbent is entrenched or the requirements already favor a competitor before rewriting anything.
Should a startup respond to every RFP it receives? No. Cold RFPs with no prior buyer relationship win at 10-20%. Run a quick go/no-go check before committing team hours to any RFP that lands cold.
How many RFPs do I need before I trust my win rate number? At least 15-20 closed outcomes, tracked on a rolling 12-month basis. Quarterly samples in B2B SaaS are almost always too small to mean anything.
Does talking to the buyer before the RFP actually move the number that much? Yes. Relationship-based pursuits win at 60-90% versus roughly 15% for cold bids. It's the single largest lever available, larger than anything you can change in the document itself.
A win rate is only useful once you know which game you're actually playing. Segment warm from cold, track outcomes for a full year, and the number stops being a mystery and starts being a filter for where your team's time actually pays off.