Measurement
Part of Measure proposal software by revenue or by reply, the choice that changes your numbers
Why proposal software key metrics shift as your team grows
How win rate, cycle time, quote value and revision count change from a five-person team to a fifty-person team, with real tools for each growth stage.
What to take away
- The four core metrics are win rate, cycle time, quote value and revision count. Each has a different normal range at 5, 15 and 50 people.
- Win rate volatility falls as volume risesup to 15 points of swing a month below 5 people, and a 5 to 10 point dip at 16 to 50.
- Median cycle time stretches from 3 to 10 days to 14 to 45 days once review layers join the chain.
- Quote value only becomes comparable once you hold a price book and a discount threshold set in pounds.
- Client satisfaction sits beside the internal numbers, as BSI guidance on customer satisfaction treats measurement as part of consistent delivery.
The four metrics by team size
The same four metrics take different normal ranges as headcount rises.
| Metric | 1 to 5 people | 6 to 15 people | 16 to 50 people |
|---|---|---|---|
| Win rate | swings up to 15 points a month | split by rep, channel and deal size | falls 5 to 10 points while reps ramp |
| Cycle time (median) | 3 to 10 days | 7 to 21 days | 14 to 45 days |
| Quote value | one order moves the average | drifts as discounts creep in | needs a price book and GBP thresholds |
| Revisions per proposal | 1 to 2 | 2 to 4 | 3 to 6 |
Metrics by team size
1-5 people
- Win rate
- swings 15 points
- Cycle time
- 3-10 days
- Quote value
- single order
- Revisions
- 1-2
6-15 people
- Win rate
- split by rep
- Cycle time
- 7-21 days
- Quote value
- discounts creep in
- Revisions
- 2-4
16-50 people
- Win rate
- falls 5-10 points
- Cycle time
- approval chains
- Quote value
- drifts
- Revisions
- rises
Why each metric changes shape
At five people, one order is a large share of the quarter. One win or loss swings the win rate by up to 15 points, so a monthly figure means little.
At fifteen people, approval chains appear for discounts and non-standard terms, stretching median cycle time to 7 to 21 days.
At fifty people, legal, security and finance review every large bid. Cycle time can reach 14 to 45 days, and revisions climb to 3 to 6 as more approvers edit.
Software and licence terms at each stage
Most tools price per seat, usually in US dollars. Convert to pounds and add VAT at 20%, as set out by GOV.UK.
- PandaDoc: per-seat plans with approval workflows and e-signature.
- Proposifytiered plans with template controls for design-led teams.
- Better Proposalsmonthly proposal limits on lower tiers.
- Qwilrper editor per month, with web-based quotes.
- HubSpot Sales Hubper seat, quotes inside a CRM.
- Salesforce CPQper user, for complex product sales.
- DocuSigne-signature plans with envelope limits.
- Responsive and Loopioannual enterprise contracts, pricing on request.
Licence terms, not the feature list, decide most of your three-year cost. Our comparison of proposal software business models sets out which clauses matter at each team size.
Example: a revision count that moved with the template
Illustrative figures. In March, an eight-person team counted every resend as a revision, giving 2.4 per proposal. In April a new template forced a first-pass rewrite, and the figure rose to 3.1. Client behaviour had not changed.
Redefine a revision as a client-requested change to scope, price or timing. Record the old wording, the new wording and the date.
Definition drift is easy to miss. Two managers can count the same event in different ways, and the dashboard shows only one number.
Test the new definition against last quarter's closed deals. If the count barely moves, keep it. If it jumps, the old wording was hiding activity.
Benchmark before you compare
Record your own baseline first. A sector average turns into a target the moment there is nothing to compare it with. Compare like with like, or the gap you find is a gap in method.
Match the definition, the deal band and the sales stage first.
The benchmark research in England explains how sample choice changes the numbers you read, so check the method before quoting an average.
Averages drawn from enterprise bid teams rarely describe a five-person agency, so match the sample to your own band.
A sector average tells you where you sit. It does not tell you what to do.
Where AI features score or draft proposals, the ICO guidance on artificial intelligence covers the data protection duties that apply.
Reporting rhythm
Set a monthly review and a quarterly reset. Monthly reviews catch drift in cycle time early, and quarterly resets let you change a definition when the sales motion changes. Put the reset date in the calendar and give it a named owner.
Record the reason for every change, along with the date and the old wording. Keep one owner for the dashboard. A change made quietly mid-quarter breaks every comparison you have.
If the CRM and the quoting tool disagree, decide which one the dashboard reads from. Settle that once and the numbers stay reconcilable. The measurement and reporting guide sets out the cycle these definitions feed into.
Reporting rhythm
- Monthlyreview catches cycle-time drift
- Quarterlyreset definitions and record why
- Alwaysone owner for the dashboard
- Alwaysname the system of record
A first-quarter checklist
- Define sent, decided and signed in writing.
- Record median cycle time rather than the average.
- Split win rate by deal size band and channel.
- Set a discount threshold that needs approval.
Common questions
How many metrics should a small team track?
Four is enough to start: win rate, cycle time, quote value and revisions. Add more only when someone acts on the data.
Should win rate include proposals the client withdrew?
No. Withdrawn proposals never reached a buying decision, so counting them understates performance.
How often should definitions change?
Rarely, and never mid-quarter. Change them at a quarterly reset, and record the old wording and the date so comparisons stay honest.
