RFP Win Rate Calculator
The formula
What the rfp win rate tells you
Government and enterprise procurement conversion — usually far below proposal rates because the field was pre-shaped before you saw it.
Calculation: RFP win rate = wins ÷ responses; bid value = rate × deal − loaded hours cost. Enter your inputs and every substitution is shown below the result.
Reading the result
The break-even rate is the whole point of this metric: any RFP below your expected-value line is charity work for the incumbent’s evaluation committee.
Rules of thumb: 8–15% typical for open RFPs; 30%+ for client-invited, shape-phase responses
Limitations and best practice
Win rates rise by declining bad-fit bids, and teams that never decline hide 8–12% blended rates while their good-fit segment runs 35% — report by pre-scored bid tier.
This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Frequently asked questions
What bid-to-lose ratio should trigger a no-bid review?
Do win-back bids after a loss perform better?
Source & methodology
Bid-management practice (APMP benchmarks).
RFP Win Rate: what this tool answers
You are here because you need a specific number, and you want to see how it was produced before you rely on it. There are plenty of pages about RFP Win Rate; almost none of them show the working. This one does: the formula, every input, a fully computed example, and a sensitivity analysis calculated live from this engine’s own defaults.
A calculation like this one is worth roughly as much as a careful sentence: it forces several vague considerations into one comparable quantity. Once RFP Win Rate is on the table, the argument can stop being about impressions.
People rarely disagree about arithmetic; they disagree about assumptions that were never written down. Printing the substitution and the sensitivity ranking removes that category of disagreement for RFP Win Rate.
Nothing below is stock text pasted around a number: the worked example computes RFP win rate = 15.0% from this tool’s own defaults, and the sensitivity section ranks the inputs that move the result — RFPs responded to first, at ≈11.1 % of the headline for a ten-percent error either way in that input. Work down the page and by the end you could re-derive the result in a spreadsheet from memory.
How RFP Win Rate is computed, line by line
One formula, published in full: RFP win rate = wins ÷ responses; bid value = rate × deal − loaded hours cost. Anything you can read, you can reproduce in a spreadsheet, and that reproducibility is the whole point of printing it rather than hiding it behind a button.
RFPs responded to (example value 40) is a plain measured quantity — the unit shown in the label is the unit the formula expects. Replace the example with the figure from your own records — the tool recomputes instantly and the printed steps follow your numbers.
RFPs won (example value 6) is a plain measured quantity — the unit shown in the label is the unit the formula expects. This input feeds the formula directly; a defensible figure here is worth more than false precision anywhere else.
Average hours per RFP (example value 60) is a plain measured quantity — the unit shown in the label is the unit the formula expects. If the period is partial, decide whether you mean elapsed or planned time and keep that meaning across every field.
Average deal size ($) (example value 180,000) is a plain measured quantity — the unit shown in the label is the unit the formula expects. Keep every length field in the same unit; the formula assumes a consistency it cannot check for you.
RFP Win Rate with real numbers, step by step
Rather than describe the calculation, here it is end to end — every substitution in order, starting from the inputs above. Starting figures: RFPs responded to, RFPs won, Average hours per RFP, Average deal size ($). Run to the end, the RFP win rate resolves to 15.0% — Each bid costs $6,600 loaded and returns $27,000 expected value — accretive at the margin on the bands this tool uses.
- Rate = 6 ÷ 40 = 15.0%
- EV/bid = 0.15 × $180,000 = $27,000 vs cost $6,600
Expected value per bid — $27,000. Compare it against the main result of 15.0% before drawing conclusions.
Loaded cost per bid — $6,600. Read next to the headline, this is the figure that shows the shape of the trade-off.
Break-even win rate for this deal size — 3.7 %. This is the number experienced users quote when the headline alone would mislead.
Keep this worked example open while you enter your own figures: matching the shape of the substitution is the fastest way to spot a unit or convention mistake.
Scenario table: RFP Win Rate at ±10 % and ±20 % of the key input
Single-point answers invite false confidence, so the same engine was run across a band around the input that matters most here. Each row is a full recalculation of RFP Win Rate, not an interpolation.
| RFPs responded to setting | RFP win rate |
|---|---|
| 80 % of the example value | 18.8% |
| 90 % of the example value | 16.7% |
| example inputs | 15.0% |
| 110 % of the example value | 13.6% |
| 120 % of the example value | 12.5% |
Across 5 settings of RFPs responded to, the result spans 12.5% to 18.8%. A decision that only works at one row of this table is a decision waiting for an input to move. Reproduce it in the form above by editing RFPs responded to alone; the substitution steps will follow your figures exactly.
What actually moves your RFP Win Rate
Generic advice says “it depends on your inputs”; this section says exactly how much. Each field was perturbed by ±10 % in isolation and the RFP win rate recomputed, so the ranking below is measured rather than asserted. For RFP Win Rate the ranking is measured rather than guessed, and it belongs to these defaults: shift the starting point and the order can shift with it.
- RFPs responded to +10 % → RFP Win Rate = 13.6% · −10 % → 16.7% (the RFP win rate shifts ≈11.1 %)
- RFPs won +10 % → RFP Win Rate = 16.5% · −10 % → 13.5% (the RFP win rate shifts ≈10.0 %)
RFPs responded to is the dominant lever here: ten percent either way moves the result by about 11.1 %, from 13.6% to 16.7%. That is where a careless figure does the most damage, so check it against a source, and treat RFPs won as the second priority (≈10.0 % per ten percent). The remaining fields can sit at safe defaults without materially changing the answer — knowing which is which is what separates a careful calculation from an anxious one.
Reading the result: bands, zones and thresholds
A number on its own is trivia; a number against a range is intelligence. The verdict attached to the default calculation — “Each bid costs $6,600 loaded and returns $27,000 expected value — accretive at the margin” — is one band on a ladder your own figure may sit somewhere else on. Before treating the band as fact, note its width: ten percent either way on RFPs responded to already spans 13.6% to 16.7%. The practical reading rules: compare against your own history before comparing against other people; treat band boundaries as zones, not walls — one point on the wrong side of a threshold rarely changes a real outcome; and when a companion output contradicts the headline, believe the pair.
Where RFP Win Rate sits next to similar measures: this tool answers “how much is the RFP Win Rate”, while the related calculators answer “what do I do about it”. Reading the result alone tends to over-weight a single snapshot; pairing it with the companion tools above turns the number into a decision.
Why RFP Win Rate results go wrong — and how to prevent it
Win rates rise by declining bad-fit bids, and teams that never decline hide 8–12% blended rates while their good-fit segment runs 35% — report by pre-scored bid tier. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Leaving a line out of the input. An omitted fee, tax or headcount is not a rounding error — it is a structural optimism bias.
Attention is also misallocated between fields. Having measured this engine, we can say where it belongs: RFPs responded to first, everything else second.
Another is comparing across contexts: an RFP Win Rate computed with one set of conventions should never be lined up against a figure computed with another. Check the inputs behind both before ranking them.
A quick check for any RFP Win Rate figure
- Recompute once with the dominant input deliberately set low, and see whether the decision changes.
- Re-run the calculation with a ±10 % stress on the two most sensitive inputs.
- Put RFPs responded to under a magnifier; the sensitivity table above is the reason why.
- Note the date and the inputs beside the number so the figure can be audited later.
- Verify each input against its original source document, not memory.
- Run the ±10 % stress on the top two levers and check that your conclusion survives both.
How to use the RFP Win Rate tool properly
Using a calculator well sounds trivial, but the difference between a decision-grade figure and a throwaway one lives entirely in the routine. The routine for RFP Win Rate takes a minute to learn and applies to every input above.
Step 1 — collect, then type. Everything this tool asks for is listed above (rfps responded to, rfps won, average hours per rfp, average deal size ($)). Pull each figure from something you can point at — paperwork, a dashboard, a label — before touching a field. Guesswork at the input stage cannot be repaired at the interpretation stage. When in doubt, prefer the boring input: the interesting one is usually the one you misread.
Step 2 — baseline before exploration. Get one defensible RFP win rate on screen before you start nudging numbers. Without a baseline, every variation looks interesting and none of them means anything. One decimal place more than your data supports is one decimal place of fiction.
Step 3 — measure what deserves measuring. The ranked levers above tell you where a careful figure pays off. Everything else can stay approximate, which is a licence to stop hunting for data you do not need. Write the figure down before moving on; memory flatters whichever number you saw last.
Step 4 — run the scenario trio. Expected, pessimistic, optimistic. The gap between pessimistic and expected is the number to plan against; the optimistic result is useful only as a ceiling. Rounding early is the quietest way to introduce a permanent error.
Step 5 — save the story with the figure. A number without its inputs and its date is unusable within a quarter. Record 15.0%, the assumptions behind it, and today’s date; your future self will be auditing a stranger’s arithmetic. One decimal place more than your data supports is one decimal place of fiction.
The real-world conversations RFP Win Rate settles
Numbers earn their keep in conversations, and RFP Win Rate is no exception. In Business & Entrepreneurship discussions around Sales & Revenue, this figure decides whether an option stays on the table: it converts an opinionated debate into an arithmetic one, and arithmetic is the only referee both sides accept. If a result feels obviously right, that is the moment to check the inputs hardest.
Used properly this is a five-minute filter that saves weeks. Compute RFP Win Rate, reject what fails, and only then bring in the expensive analysis for the survivors. Half of a good calculation is knowing which input you would hate to be wrong about.
Re-running this page costs nothing and catches the slow drifts that never announce themselves. In Business & Entrepreneurship the expensive mistakes are rarely sudden; they are small changes in RFPs responded to that nobody recalculated for a year. Suspiciously tidy answers deserve the same scrutiny as untidy ones.
Quick answers: what searchers ask about RFP Win Rate
What affects RFP Win Rate the most?
The short answer: RFPs responded to. The longer answer is the sensitivity table on this page, where every numeric input was probed by ten percent and the RFP win rate recalculated — RFPs responded to moved it furthest, by roughly 11.1 % (13.6% to 16.7%).
Which matters more: rfps won or rfps responded to?
By the numbers, RFPs responded to: a ten-percent change in it moves the result ≈11.1 %, versus ≈10.0 % for RFPs won. Spend your measuring effort in that order — precision on the weaker lever buys almost nothing.
What is a typical RFP Win Rate?
With the example inputs on this page the result is 15.0%, labelled “Each bid costs $6,600 loaded and returns $27,000 expected value — accretive at the margin”. “Typical” varies with situation, which is why every result here ships with its verdict band and its sensitivity list: they turn one figure into a range you can locate yourself inside.
How do I calculate RFP Win Rate by hand?
RFP win rate = wins ÷ responses; bid value = rate × deal − loaded hours cost is the entire method. Work the inputs in that order — Rate = 6 ÷ 40 = 15.0% — and you will reach 15.0% on the default figures, the same number this tool prints.
What happens to RFP Win Rate if rfps responded to changes by 10 %?
Try it in the form above and the printed substitution will follow you; the pre-computed answer for the defaults is 13.6% to 16.7% across the ten-percent probe, i.e. ≈11.1 % sensitivity on the RFP win rate.
Is the RFP Win Rate result of 15.0% good or bad?
Neither, on its own — the label “Each bid costs $6,600 loaded and returns $27,000 expected value — accretive at the margin” is the band this figure falls in for the example inputs, and your own inputs will place you elsewhere on the same ladder. Judge the number against your history and your alternatives, and remember that a ten-percent error in RFPs responded to alone moves it by ≈11.1 %.
How do I calculate RFP Win Rate manually?
Write down the inputs, then follow the printed steps in order — RFP win rate = wins ÷ responses; bid value = rate × deal − loaded hours cost. A spreadsheet replicates it with two or three cells. The manual route is worth doing once to build intuition; after that the calculator saves time and eliminates transcription slips.
What affects RFP Win Rate the most?
Sensitivity depends on where you start, but the inputs RFPs responded to and RFPs won typically move RFP Win Rate further than the rest because they enter the formula multiplicatively. If you can only measure two things well, measure those and hold the others at conservative defaults.
What bid-to-lose ratio should trigger a no-bid review?
Three consecutive losses with no feedback, or any bid scoring below the break-even line above — both are market signals that the qualification gate is too polite.
Do win-back bids after a loss perform better?
Occasionally — a second bid into the same evaluation team reuses their stated requirements, which historically lifts rates 5–10 points when the first loss was close.
Can this tool see the numbers I type?
It cannot. There is no submission step: the calculation happens in your browser and the result disappears when you close the page. Treat the fields above as a scratchpad rather than a form.
Key terms on this page
- Expected value per bid
- $27,000 on the example inputs — a companion figure printed beside the headline of RFP Win Rate so that no result is read in isolation.
- Loaded cost per bid
- $6,600 on the example inputs — a companion figure printed beside the headline of RFP Win Rate so that no result is read in isolation.
- Break-even win rate for this deal size
- 3.7 % in the default RFP Win Rate calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- RFP win rate
- The primary output of this tool: 15.0% for the default inputs, computed exactly from RFP win rate = wins ÷ responses; bid value = rate × deal − loaded hours cost.
- Worked example
- The calculation written out in full so that nothing on this page has to be taken on trust.
- Verdict band
- The plain-language label — here “Each bid costs $6,600 loaded and returns $27,000 expected value — accretive at the margin” — mapping the computed figure onto experience-based ranges for Business & Entrepreneurship.
- Sensitivity (±10 %)
- How far the RFP Win Rate moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
Methodology, sources and limits
The model is published arithmetic implemented exactly as written: RFP win rate = wins ÷ responses; bid value = rate × deal − loaded hours cost. Source of record: Bid-management practice (APMP benchmarks). Where a professional version of this calculation differs, it differs in inputs and jurisdiction-specific coefficients, not in the algebra — which is why re-checking your inputs beats hunting for a second calculator.
This page is an estimation aid, not professional advice. The design rule is simple: two people entering identical figures must get identical answers. What that buys you is reproducibility — two people, two browsers, the same arithmetic, and a printed trail from inputs to result that either of them can audit.
What to do with your RFP Win Rate next
Save the number together with its inputs and today’s date; an RFP Win Rate figure without context is unusable the moment an input changes.
This page was written for people who need one trustworthy number before their next decision, and the promise is that nothing above required trust. Bookmark the tool, re-run it whenever an input moves by more than a few percent, and keep the date with the number.