Sales Productivity Calculator
The formula
What the sales productivity tells you
The return test on GTM pay: dollars booked per dollar of loaded rep cost — the single number that decides whether more hiring is an investment or an expense.
Calculation: Productivity index = revenue per rep ÷ fully-loaded rep cost. Enter your inputs and every substitution is shown below the result.
Reading the result
Above 3× loaded cost, each added rep is accretive on the current model; below 2×, fix enablement, leads or pricing before hiring anyone.
Rules of thumb: 3–5× fully-loaded OTE is the accepted healthy band for B2B
Limitations and best practice
Productivity collapses the moment you compare across motions — a mid-market rep at 3.2× may be worse-pulled than an enterprise rep at 2.4× because the ramp and cycle differ. Compare within segment.
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
Does OTE include the SDR that supports the rep?
Why 1.35× on OTE for loaded cost?
Source & methodology
GTM efficiency benchmarking.
How Sales Productivity works — and what your result really means
This page was written for one job: turning your own inputs into a defensible figure, with the working shown. There are plenty of pages about Sales Productivity; 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.
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 Sales Productivity.
Most confusion about Sales Productivity comes from mixing up the input you control with the input you merely observe. The formula treats them identically, but your decisions should not: one deserves measurement, the other deserves a defensible estimate.
What makes a calculation page trustworthy is that its copy is derived from its own arithmetic: here bookings per rep cost = 6.30 ×, recomputed every time a field changes, and the sensitivity section ranks the inputs that move the result — Quota-carrying reps first, at ≈11.1 % 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.
How Sales Productivity is computed, line by line
The engine implements a single stated model: Productivity index = revenue per rep ÷ fully-loaded rep cost. There is no hidden coefficient and no login-gated precision — the formula printed is the formula executed, which is also what makes the result citable.
Total bookings ($) (example value 10,200,000) 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.
Quota-carrying reps (example value 8) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. This input feeds the formula directly; a defensible figure here is worth more than false precision anywhere else.
Average OTE ($) (example value 150,000) is a quantity rather than a category — precision here is cheap and worth having. The example value is there to demonstrate the mechanics, not to describe your situation — overwrite it.
A fully worked Sales Productivity example
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: Total bookings ($), Quota-carrying reps, Average OTE ($). Run to the end, the bookings per rep cost resolves to 6.30 × — Very productive — check quota realism on the bands this tool uses.
- Revenue/rep = $10,200,000 ÷ 8 = $1,275,000
- ÷ loaded cost $202,500 = 6.30× — the classic payback test
Bookings per rep — $1,275,000. Compare it against the main result of 6.30 × before drawing conclusions.
Fully-loaded cost per rep (≈35% on top of OTE) — $202,500. If your inputs change, this is usually the first companion figure to move.
Total GTM pay cost — $1,620,000. 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.
How far Sales Productivity 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?
| Quota-carrying reps setting | Bookings per rep cost |
|---|---|
| 80 % of the example value | 7.87 × |
| 90 % of the example value | 7.00 × |
| example inputs | 6.30 × |
| 110 % of the example value | 5.72 × |
| 120 % of the example value | 5.25 × |
That spread — 5.25 × at the low end, 7.87 × at the high — is what a careful read of Sales Productivity looks like: a band you can state out loud, with the reason for each edge. Reproduce it in the form above by editing Quota-carrying reps alone; the substitution steps will follow your figures exactly.
Where Sales Productivity is fragile — and where it is not
Nobody should have to guess which input matters. The engine was re-run once per field below — ten percent up, ten percent down, everything else frozen — and the results ranked by how far they moved the bookings per rep cost. For Sales Productivity the ranking is measured rather than guessed, and it belongs to these defaults: shift the starting point and the order can shift with it.
- Quota-carrying reps: ten percent up gives 5.72 ×, ten percent down gives 7.00 × — ≈11.1 % of the bookings per rep cost either way
- Nudge Average OTE by ±10 % and Sales Productivity lands between 5.72 × and 7.00 × (sensitivity ≈11.1 %)
- Total bookings +10 % → Sales Productivity = 6.93 × · −10 % → 5.67 × (the bookings per rep cost shifts ≈10.0 %)
Quota-carrying reps is the dominant lever here: ten percent either way moves the result by about 11.1 %, from 5.72 × to 7.00 ×. Measure that input from a document rather than from memory, and Average OTE is effectively tied with it (≈11.1 % 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.
Interpreting the Sales Productivity verdict
A number on its own is trivia; a number against a range is intelligence. On the example inputs the band reads “Very productive — check quota realism”; your own figures place you on a different rung of the same ladder. The sensitivity list shows how far a modest input error moves you along that ladder: for Quota-carrying reps, ±10 % covers 5.72 × to 7.00 ×. The practical reading rules: ask what would have to change to move you one band. If the answer is “a small, plausible input difference”, the band itself is not the finding — the uncertainty is.
Where Sales Productivity sits next to similar measures: this tool answers “how much is the Sales Productivity”, 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 Sales Productivity wrong
Productivity collapses the moment you compare across motions — a mid-market rep at 3.2× may be worse-pulled than an enterprise rep at 2.4× because the ramp and cycle differ. Compare within segment. 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.
Confusing a large number with an important one. Sales Productivity can be dominated by one input whose absolute value looks unimpressive, which is why this page ranks influence separately from magnitude.
One mistake is specific to this engine: assuming every input matters equally. The computation above shows Quota-carrying reps dominating — a careful figure there beats false precision everywhere else.
Another is comparing across contexts: a Sales Productivity 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 Sales Productivity figure
- Record the date and the inputs alongside the number so future-you knows what was assumed.
- Confirm the example values are plausible for your own situation before replacing them.
- Put Quota-carrying reps 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.
- Re-run the calculation with a ±10 % stress on the two most sensitive inputs.
- Confirm the answer against one independent method or published benchmark for Sales Productivity.
Five steps from raw inputs to a figure you can defend
The tool does the arithmetic; the routine below is what makes the arithmetic trustworthy. Five steps, a minute total — and afterwards you will know not just what the number is, but which assumption produced it.
Step 1 — gather before you type. Sales Productivity depends on total bookings ($), quota-carrying reps, average ote ($). 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. Numbers are cheap to produce and expensive to retract; the extra minute is the cheapest insurance available.
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 Bookings per rep cost (6.30 × for the example values), and note the verdict band. The fastest sanity test is to guess the answer first and see how far the calculation disagrees.
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. Half of a good calculation is knowing which input you would hate to be wrong about.
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. Repeating a calculation with the same numbers proves only that the arithmetic is reliable — which is worth knowing.
Step 5 — save the story with the figure. A number without its inputs and its date is unusable within a quarter. Record 6.30 ×, the assumptions behind it, and today’s date; your future self will be auditing a stranger’s arithmetic. Say the answer out loud before you save it; if it sounds wrong, the model did not change, your understanding did.
From calculation to decision: where Sales Productivity earns its keep
Numbers earn their keep in conversations, and Sales Productivity 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 the answer changes your behaviour, it deserves a second run with different assumptions.
The companion outputs — Bookings per rep and Fully-loaded cost per rep (≈35% on top of OTE) — 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. Most surprises in numbers are surprises about inputs, not about formulas.
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. Comparisons are cheap: run the identical calculation for the alternative and look at the gap.
Sales Productivity — frequently asked questions
What affects Sales Productivity the most?
The short answer: Quota-carrying reps. The longer answer is the sensitivity table on this page, where every numeric input was probed by ten percent and the bookings per rep cost recalculated — Quota-carrying reps moved it furthest, by roughly 11.1 % (5.72 × to 7.00 ×).
Do average ote and quota-carrying reps matter equally?
Effectively. Measured on this engine they land at ≈11.1 % and ≈11.1 % for the same ten-percent nudge, so the honest advice is to get both right; chasing precision in only one of them buys almost nothing.
What is a typical Sales Productivity?
There is no honest universal average for Sales Productivity, but there is a reference point: the defaults on this page produce 6.30 × (Very productive — check quota realism). Replace the inputs with your own and compare — that comparison is the useful meaning of “typical”.
How do I calculate Sales Productivity by hand?
Productivity index = revenue per rep ÷ fully-loaded rep cost is the entire method. Work the inputs in that order — Revenue/rep = $10,200,000 ÷ 8 = $1,275,000 — and you will reach 6.30 × on the default figures, the same number this tool prints.
What happens to Sales Productivity if quota-carrying reps changes by 10 %?
Try it in the form above and the printed substitution will follow you; the pre-computed answer for the defaults is 5.72 × to 7.00 × across the ten-percent probe, i.e. ≈11.1 % sensitivity on the bookings per rep cost.
Is the Sales Productivity result of 6.30 × good or bad?
Neither, on its own — the label “Very productive — check quota realism” 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 Quota-carrying reps alone moves it by ≈11.1 %.
Is Sales Productivity accurate?
The arithmetic is exact: Productivity index = revenue per rep ÷ fully-loaded rep cost is evaluated with full floating-point precision and every substitution is printed in the worked example. What limits accuracy is input quality and the model’s assumptions, so treat the 6.30 × result as the correct answer to the question you typed — and check the assumptions section before acting on it.
How do I calculate Sales Productivity manually?
Write down the inputs, then follow the printed steps in order — Productivity index = revenue per rep ÷ fully-loaded rep 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.
Does OTE include the SDR that supports the rep?
If you want the true unit, load the pod: rep OTE plus its share of SDR, SE and manager cost — pod-level productivity is the number that survives org changes.
Why 1.35× on OTE for loaded cost?
Payroll taxes, benefits, T&E and tools typically add 30–40% — swap in your own fully-loaded figure for planning.
Does this Sales Productivity tool store my numbers?
No. The entire calculation runs in your browser session; nothing entered above is transmitted or saved, which is the correct behaviour for sensitive Business & Entrepreneurship figures and the reason you can re-run this page as often as you like.
What the labels on this page mean
- Bookings per rep
- $1,275,000 for the Sales Productivity worked case; it sits next to the main result because it carries context the headline leaves out.
- Fully-loaded cost per rep (≈35% on top of OTE)
- $202,500 for the Sales Productivity worked case; it sits next to the main result because it carries context the headline leaves out.
- Total GTM pay cost
- $1,620,000 in the default Sales Productivity calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Bookings per rep cost
- The primary output of this tool: 6.30 × for the default inputs, computed exactly from Productivity index = revenue per rep ÷ fully-loaded rep cost.
- 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 “Very productive — check quota realism”, and your inputs may not.
- Sensitivity (±10 %)
- How far the Sales Productivity moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
Where the Sales Productivity model comes from
There is no black box on this page — the engine evaluates Productivity index = revenue per rep ÷ fully-loaded rep cost. Source of record: GTM efficiency benchmarking. 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.
Treat the output as a precise answer to the question you typed: exact arithmetic, transparent formula, published source, no hidden rounding. 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
Save the number together with its inputs and today’s date; a Sales Productivity figure without context is unusable the moment an input changes.
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.