Win rate: the number that sets your prices
Win rate is the percentage of decided proposals you win, and it is the closest thing a B2B service firm has to a live price signal from its market. When your rolling win rate sits above 60%, raise prices 15% — the market is saying yes too easily. When it sits well below 30%, the problem is usually qualification rather than price, and discounting will make it worse, not better.
What is a win rate you can actually trust?
A trustworthy win rate has three properties. It is rolling — computed over your last 20 or so decided proposals, not a calendar year that mixes last year's pricing with this year's. It is decided-only — the denominator counts proposals that received a yes or a no, never the open ones still floating in someone's inbox. And it is logged — every win and every loss recorded as a stage change in the CRM at the moment it happens, because a percentage cannot be reconstructed from memory three months later.
Most firms fail on the third property. Wins get logged because invoices follow them; losses quietly evaporate, and dead deals sit "open" indefinitely. The result is a flattering number nobody can act on. Win rate is one of the core instruments on the founder's screen — the full build, including how each number arrives without anyone compiling it, is in The MD Dashboard Blueprint.
Why does win rate set prices?
Because every proposal is a price test that a real buyer either accepted or declined. Survey your clients about pricing and they will be polite; send them a proposal and they will tell you the truth. Read over 20 decisions, the pattern is hard to argue with:
| Rolling win rate | What the market is saying | The move |
|---|---|---|
| Above 60% | You are priced below what buyers will bear | Raise prices 15% |
| Roughly 30–60% | Healthy tension between price and demand | Hold; keep refining qualification |
| Well below 30% | The wrong deals are reaching proposal stage | Fix qualification, not price |
The 60/15 rule works because it is mechanical. A founder who waits until raising prices "feels right" typically waits years; a founder with a threshold raises them the month the number crosses it.
How do you track it without compiling anything?
The mechanism is four steps, none of which is a spreadsheet:
- When a proposal goes out, the deal moves to a "proposal sent" stage with a value and a date attached.
- When the prospect decides, the deal moves to won or lost — and lost requires a reason picked from a short fixed list, so the stage change takes ten seconds.
- The dashboard computes won ÷ decided over the last 20 decisions, refreshing the moment any stage changes.
- When the rolling figure crosses a threshold you set in advance, the pricing decision fires — no meeting, no debate, no compiling.
If step 2 is skipped even occasionally, the number rots. This is why lost-reason capture belongs in your first wave of CRM automation, not your tenth.
What ruins the number?
Four things, in rough order of frequency. Zombie deals — opportunities that died months ago but were never marked lost, which inflate the win rate by shrinking the denominator. Unqualified proposals — quoting anyone who asks drags the rate down and tells you nothing about price. Moving definitions — if "proposal" means a formal document one month and a two-line email the next, the trend is noise. And small denominators — below about ten decisions the percentage jumps around, so hold your nerve until the sample fills out.
What do you do with the number once it's clean?
Three things. First, apply the pricing rule above. Second, feed it into your revenue forecast — win rate is the conversion assumption that turns pipeline value into an expected number, which is the subject of Forecasting revenue from pipeline, honestly. Third, treat it as one of the four levers that determine how fast your pipeline turns into cash — the full frame is in Pipeline velocity: the four levers.
One habit makes all of this stick: write the thresholds down before you need them. "Above 60% for 20 decisions, raise 15%" is a standing rule, decided once and applied automatically — the same logic I apply to my own recurring decisions in The Personal Operating System. Rules made in advance get followed; judgements made in the moment get postponed.
Next step: the Growth System Audit — £450, seven days, credited against any build — maps whether your win rate is a number you can trust, where your growth system leaks, and what to build first.
Total Format builds the systems UK B2B service firms grow on — AI-powered outbound, automation, and reporting — so growth stops depending on the founder's time.
Map your growth system. The £450 audit takes seven days and is credited against any build.
BOOK THE AUDIT