Win Rate Calculator
The formula
What the win rate tells you
The share of decided opportunities that close — the single most leverage-heavy number in a sales model because it multiplies pipeline, headcount and forecast alike.
Calculation: Win rate = wins ÷ (wins + losses). Enter your inputs and every substitution is shown below the result.
Reading the result
A 5-point improvement raises revenue about as much as 20% more pipeline, without the marketing cost — check whether wins are concentrated in one segment before concluding.
Rules of thumb: SMB 15–25% from inbound; mid-market 20–30%; competitive replacements often below 15%
Limitations and best practice
Definition drift is endemic: including no-decisions (blank/no-result deals) in losses depresses the number; cherry-picking qualified-only inflates it. Publish which denominator you use.
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
Should no-decision deals count as losses?
Why does win rate differ so much by segment?
Source & methodology
Sales benchmarking practice; Winning by Design methodology.
How Win Rate works — and what your result really means
You are here because you need a specific number, and you want to see how it was produced before you rely on it. Win Rate is the kind of number people argue about from memory. This page ends that argument with arithmetic you can watch happen: enter your figures, get Win rate in real time, and see every substitution printed below.
A calculation like this one is worth roughly as much as a careful sentence: it forces several vague considerations into one comparable quantity. Once Win Rate is on the table, the argument can stop being about impressions.
Business runs on numbers that are cheap to compute and expensive to ignore. Win Rate in Business & Entrepreneurship is one of those: Win rate = wins ÷ (wins + losses), and the gap between founders who check and founders who hope shows up exactly here.
Every figure in the prose is generated by the engine rather than written beside it — the worked example resolves to win rate = 22.5% on the default inputs, and the sensitivity section ranks the inputs that move the result — Deals lost first, at ≈8.4 % of the headline for a ten-percent error either way in that input. Read the sections in order and you will be able to reproduce every figure by hand.
The Win Rate formula, explained
Here is the complete model this tool runs — Win rate = wins ÷ (wins + losses) — with each input explained below. If a competitor’s page gives you a different answer from the same inputs, this is the text that settles which of you is right.
Deals won (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.
Deals lost (example value 138) is a measured number in the unit named by the label; the formula does not convert for you. This input feeds the formula directly; a defensible figure here is worth more than false precision anywhere else.
Target win rate (%) (example value 24) is a measured number in the unit named by the label; the formula does not convert for you. Enter it exactly as your document states it — quoted annual, monthly and effective rates are three different numbers.
Win Rate with real numbers, step by step
Abstract formulas are hard to trust, so here is the complete substitution using the default inputs, written the way an examiner would want it. Starting figures: Deals won, Deals lost, Target win rate (%). The computed win rate comes out at 22.5%, which the interpretation band labels “Below target: need 3 more wins at this volume”.
- Win rate = 40 ÷ (40 + 138) = 40 ÷ 178 = 22.5%
- At a 24% rate, 24 wins require ≈ 100 decided deals
Total decided deals — 178. If your inputs change, this is usually the first companion figure to move.
Loss rate — 77.5 %. Compare it against the main result of 22.5% before drawing conclusions.
Deals needed for target wins — 166.7. Read next to the headline, this is the figure that shows the shape of the trade-off.
Overwrite any input above and every line of this example updates with it — the substitution is live, not a screenshot of somebody else’s numbers.
How far Win Rate can reasonably move
Read this table as the practical error bar on the headline figure. It answers the question people actually have after seeing a single number: how wrong could this be if the main input is off by ten or twenty percent?
| Deals lost setting | Win rate |
|---|---|
| 80 % of the example value | 26.6% |
| 90 % of the example value | 24.4% |
| example inputs | 22.5% |
| 110 % of the example value | 20.9% |
| 120 % of the example value | 19.5% |
Across 5 settings of Deals lost, the result spans 19.5% to 26.6%. 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 Deals lost alone; the substitution steps will follow your figures exactly.
The levers behind Win Rate, ranked by effect
This list was computed for this specific engine just now: each numeric input was nudged ±10 % while every other field held its example value, and the win rate was recalculated from scratch. For 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.
- Nudge Deals lost by ±10 % and Win Rate lands between 20.9% and 24.4% (sensitivity ≈8.4 %)
- Deals won +10 % → Win Rate = 24.2% · −10 % → 20.7% (the win rate shifts ≈7.9 %)
Deals lost is the dominant lever here: ten percent either way moves the result by about 8.4 %, from 20.9% to 24.4%. Measure that input from a document rather than from memory, and Deals won is effectively tied with it (≈7.9 % for the same nudge), so verify the pair together. Everything below that can stay approximate, which is a licence to stop chasing data that would not change the decision.
What a Win Rate of 22.5% means in practice
Nobody acts on a bare figure — they act on a figure with a comparison attached. The default case lands in the “Below target: need 3 more wins at this volume” band, and bands are deliberately wide because real situations overlap. Before treating the band as fact, note its width: ten percent either way on Deals lost already spans 20.9% to 24.4%. 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 Win Rate sits next to similar measures: this tool answers “how much is the 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.
How people get Win Rate wrong
Definition drift is endemic: including no-decisions (blank/no-result deals) in losses depresses the number; cherry-picking qualified-only inflates it. Publish which denominator you use. 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.
Stopping at the first plausible answer. If the result surprises you, the productive question is which input would have to be wrong for the surprise to disappear — then go check that input.
Attention is also misallocated between fields. Having measured this engine, we can say where it belongs: Deals lost first, everything else second.
Another is comparing across contexts: a 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.
Win Rate verification checklist
- Confirm the example values are plausible for your own situation before replacing them.
- Verify each input against its original source document, not memory.
- Re-verify Deals lost against a source document — ten percent of error there moves the headline by ≈8.4 %.
- Recompute once with the dominant input deliberately set low, and see whether the decision changes.
- Compare the result with one independent method or published benchmark.
- Confirm the answer against one independent method or published benchmark for Win Rate.
Step by step: getting a trustworthy Win Rate out of this tool
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 Win Rate takes a minute to learn and applies to every input above.
Step 1 — gather before you type. Win Rate depends on deals won, deals lost, target win rate (%). Collect them from a source document — a statement, a report, an invoice, a log — rather than from memory, because recalled inputs are the single largest cause of wrong results. A figure nobody can reproduce is a figure nobody will act on twice.
Step 2 — enter the conservative case first. Resist the flattering scenario. Type the inputs you would defend in front of a sceptical reader, read the Win rate (22.5% for the example values), and note the verdict band. If the answer changes your behaviour, it deserves a second run with different assumptions.
Step 3 — change one input at a time. Nudge a single field by ten percent, watch the headline and its companions move, then undo it. Two or three fields will dominate — the sensitivity table above already ranks them for this engine. The point of transparency is that a reader can disagree with a specific line rather than with you.
Step 4 — ask what would have to be true. Take the result you want and work backwards through the inputs until you find the assumption that produces it; then decide honestly whether that assumption is defensible. Most surprises in numbers are surprises about inputs, not about formulas.
Step 5 — record the context, not just the number. Note today’s date and the inputs alongside the 22.5% output. Six months from now the context is what turns this figure into a trend. The point of transparency is that a reader can disagree with a specific line rather than with you.
From calculation to decision: where Win Rate earns its keep
In Sales & Revenue the figure computed here is usually the first one somebody asks to see. Having it — with the formula behind it — changes your position in the conversation from participant to reference. Numbers are cheap to produce and expensive to retract; the extra minute is the cheapest insurance available.
The companion outputs — Total decided deals and Loss rate — exist for the second stage of that screen: the headline sizes the prize, while the companions describe the trade-off you are accepting to get it. A calculation you cannot explain to somebody else is a calculation you cannot defend.
Nothing here is stored or transmitted, so the habit of checking is free: open the page, re-enter current figures, compare with the number you saved last time. A figure nobody can reproduce is a figure nobody will act on twice.
Quick answers: what searchers ask about Win Rate
What affects Win Rate the most?
Measured on this engine, Deals lost is the dominant lever: moving it ±10 % shifts the win rate across 20.9% to 24.4% — about 8.4 % of the headline, with Deals won next at ≈7.9 %. The ranked list in the sensitivity section is computed live, not asserted from a template.
Do deals won and deals lost matter equally?
Win Rate here is co-driven: Deals lost and Deals won produced ≈8.4 % and ≈7.9 % responses, which is a tie for practical purposes. Everything below those two is a rounding error by comparison.
What is a typical Win Rate?
With the example inputs on this page the result is 22.5%, labelled “Below target: need 3 more wins at this volume”. “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 Win Rate by hand?
Three steps: write the formula (Win rate = wins ÷ (wins + losses)), insert your values, and simplify. The worked example section shows exactly that chain for the default inputs; replicating it once on paper teaches you more about Win Rate than any number of calculator runs.
What happens to Win Rate if deals lost changes by 10 %?
The engine was re-run with that field moved by ten percent while everything else stayed fixed: the win rate goes across 20.9% to 24.4%, a swing of roughly 8.4 % around the 22.5% baseline. That ratio is the practical definition of how much this input matters.
Is the Win Rate result of 22.5% good or bad?
Good and bad are comparisons, so the honest test is three questions: where does your own Win Rate sit against the 22.5% reference above, how far would a plausible input error move it (≈8.4 % per ten percent on Deals lost), and what does the alternative option compute to?
Should I use Win Rate before launching?
Yes — a Win Rate run on honest inputs before spending is the cheapest consulting an entrepreneur can buy. Re-run at every pricing change; the number moves more often than founders expect.
How often should I check Win Rate?
Whenever an input changes by more than a few percent, and otherwise on the rhythm of your decisions — before a purchase, a review, a renewal. Win Rate is a snapshot, not a subscription; stale snapshots are the most common silent error in Business & Entrepreneurship planning.
Should no-decision deals count as losses?
Statistically they belong in the denominator — the deal was an opportunity you spent resource on. Some teams report two rates: closed-won share overall, and win rate among deals that ended in a vendor choice.
Why does win rate differ so much by segment?
SMB decisions are one-person and fast; enterprise is committee-based with incumbent advantages. Compare a segment against its own historical band, never against the blended company number.
Is my data private on this page?
Yes — computation happens locally in your browser, with no account, no tracking of your inputs and nothing sent to a server. The printed formula is the whole story of what happens to your figures.
The vocabulary of Win Rate
- Total decided deals
- 178 on the example inputs — a companion figure printed beside the headline of Win Rate so that no result is read in isolation.
- Loss rate
- 77.5 % for the Win Rate worked case; it sits next to the main result because it carries context the headline leaves out.
- Deals needed for target wins
- 166.7 in the default Win Rate calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Win rate
- The primary output of this tool: 22.5% for the default inputs, computed exactly from Win rate = wins ÷ (wins + losses).
- Worked example
- The step-by-step substitution printed above, so the arithmetic can be re-derived by hand or in a spreadsheet.
- Verdict band
- A named zone on the range of plausible results; the example inputs land in “Below target: need 3 more wins at this volume”, and your inputs may not.
- Sensitivity (±10 %)
- How far the 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.
Method, sources and what this tool cannot tell you
There is no black box on this page — the engine evaluates Win rate = wins ÷ (wins + losses). Source of record: Sales benchmarking practice; Winning by Design methodology. Any other implementation of this model should return the same figure for the same inputs. If one does not, the difference is in its assumptions — which this page prints and that one probably does not.
This page is an estimation aid, not professional advice. The design rule is simple: two people entering identical figures must get identical answers. The sensitivity table above is part of that promise rather than a bonus: it lets you see how much of the result depends on how carefully you measured.
After the number: what to do with it
Re-run the calculation with your own figures, stress the two most sensitive inputs by ±10 %, and only then act on the result.
The audience here is people who need one trustworthy number before their next decision. Everything you need to defend the result — formula, substitution, sensitivity, source — is printed above, so the only remaining variable is the honesty of your inputs.