Pipeline, forecasting and capacity
Sales capacity planning that survives contact with your CRM
Most capacity models are built once, in a spreadsheet, by someone who then goes back to their day job. We build yours inside Salesforce or HubSpot, wire it to the pipeline data that already exists, and keep it current every week. Ramp curves, attrition, quota attainment and coverage, all reconciled against what your reps are actually doing.
Rated 4.9 / 5 on G2 by the teams we operate with. Embedded in the GTM systems of startups backed by the biggest VCs in tech.
Ramp
Modeled as a monthly curve
Cadence
Refreshed every week
Platforms
Salesforce and HubSpot
Engagement
90-day rolling
Definition
What sales capacity planning is, in one paragraph
Sales capacity planning is the work of figuring out how much revenue your sales team can realistically produce, and therefore how many reps you need to hire and by when, to hit a number the board has already set. It is not forecasting. Forecasting asks what will close from the pipeline you have. Capacity planning asks whether the team you have, plus the team you can hire in time, can produce that pipeline at all. The output is a headcount plan with dates on it, a quota structure that adds up to the target, and an honest statement of the gap between the two.
The reason it matters more at Series B than at Series A is that the errors compound. Hire two quarters late and you do not lose two quarters of that rep’s quota, you lose two quarters plus a full ramp period, and the ramp period is longer than most plans assume. Industry benchmarks commonly put the time for a new B2B sales rep to reach full productivity at around seven months. A plan that treats a new hire as productive on day 30 is not optimistic, it is wrong by about six months per head.
Three questions a good capacity plan answers, and a spreadsheet usually does not:
1. How many fully ramped reps will we actually have in each quarter, not how many people will be on payroll.
2. What quota attainment are we assuming, and is that number drawn from our own history or from a benchmark we found on the internet.
3. If hiring slips by one month, what happens to the number, and who finds out.
Why plans break
Why most capacity plans stop being true in week three
The standard failure is not a maths failure. The model is usually fine on the day it is built. It breaks because of where it lives and who owns it.
01
It lives in a spreadsheet
Disconnected from the system of record. The moment a rep leaves, a start date moves, a territory is redrawn or a quota is renegotiated, the spreadsheet is stale and nobody notices until the quarterly business review.
02
It assumes a ramp step instead of a ramp curve
Treating a new hire as zero percent productive for three months and one hundred percent on the first day of month four overstates Q1 capacity and understates Q3. A month-by-month curve, roughly zero in month one, half by month three, full by month six or seven depending on segment, is closer to what actually happens, and it changes the hiring dates materially.
03
It uses a quota attainment number nobody validated
Plugging in one hundred percent attainment produces a plan that has never once been hit. Commonly cited benchmarks put median quota attainment in B2B SaaS around seventy percent, and your own trailing four quarters are a better input than any benchmark.
04
It ignores attrition until it happens
Annual sales attrition commonly runs around thirty percent, which means a team of twenty loses roughly six people a year. A plan without backfills built in is a plan that needs an emergency hiring round every second quarter.
05
It has no owner
Finance owns the headcount budget. Sales owns the quota. Revenue operations (RevOps) owns the CRM data that proves either of them right. If the plan is not assigned to someone who sits across all three, it is nobody’s job to keep it true.
The inputs
The five inputs a sales capacity model needs
Before any formula, get these five numbers from your own data rather than from a benchmark article. Where you genuinely do not have the history, use the benchmark, write down that you used it, and replace it as soon as you have two quarters of your own.
01
Productive quota per rep
Not the quota you assign, the quota a ramped rep actually carries, by segment. Assign quota at roughly five times on-target earnings as a sanity check, then confirm it against what your best two reps have genuinely closed over four quarters.
02
Average quota attainment
Closed revenue divided by assigned quota, averaged across ramped reps only. Including a rep who started six weeks ago drags the number down and makes the plan overhire. Pull the trailing four quarters from the CRM, not from memory.
03
Ramp curve, by segment
Onboarding time plus one average sales cycle is the floor. Express it as a monthly curve, not a single number. SMB and transactional teams ramp faster than mid-market, and mid-market faster than enterprise, because the sales cycle itself is the constraint.
04
Attrition, voluntary and involuntary
Reps who leave divided by average headcount, annualized. Split it if you can: involuntary attrition in months four to eight is a hiring-quality signal, voluntary attrition in month fourteen is a compensation or territory signal, and they need different fixes.
05
Pipeline coverage ratio
How many dollars of pipeline your team needs in a quarter to close one dollar of quota, derived from your own win rate rather than the default 3x everyone quotes. This is the input that connects the capacity plan to the forecast, and it is the one most plans leave out entirely.
The formula
How to calculate sales capacity
Start with the simple form, then correct it for the two things the simple form ignores, which are ramp and attrition.
The correction that matters is that “ramped reps” is not “reps”. In any growing team a meaningful share of the headcount is partially productive at any moment. Calculate ramped-equivalent heads per month by applying the ramp curve to each hire’s start date, then sum. A rep in month three of a six-month ramp counts as roughly half a head, not one.
Then subtract expected attrition and add the backfills, with their own ramp curves, which is why a plan that needs thirty productive reps at year end typically requires somewhere between forty and forty-five total hires and backfills across the year rather than thirty.
The formulas
Sales capacity = Number of ramped reps × Quota per rep × Average quota attainment. Read backwards, it gives the headcount you need: Required ramped reps = Revenue target ÷ (Quota per rep × Average quota attainment).
What the example tells you
The uncomfortable output, and the reason the exercise is worth doing, is that the hiring plan has to be nearly complete by the end of Q2 for a target that is measured in December. Most plans discover this in August. For the full build, see our step-by-step capacity plan walkthrough.
Where it lives
Build the sales capacity model in the CRM, not in a spreadsheet
This is the part no guide covers, and it is the part that decides whether the plan is still true in month four.
The model needs four things from the system of record, and if any of them is unreliable the plan is decorative. Opportunity stages that mean the same thing to every rep. A close-date discipline that is enforced rather than hoped for. Rep records that carry a start date, a segment, a territory and a quota, so ramp state is computable rather than remembered. And a lead source taxonomy clean enough that the pipeline feeding the plan can be attributed to a channel.
When those four exist, the capacity plan stops being a document and becomes a report: ramped-equivalent headcount by month, capacity against target, coverage against required pipeline, refreshed on the same cadence as the forecast. When they do not exist, fixing them is the first phase of the work, and that is ordinary. Many teams need the record layer repaired before any model is worth building.
This is why we are operators rather than advisors. A recommendation to “improve your stage definitions” is not the work. The work is going into the instance, redefining the stages, migrating the historical data so the trend line still means something, rebuilding the reports, and then training the team on the new definitions so they hold. When the whole record layer needs redesigning, that is a GTM architecture engagement.
The loop
Capacity, pipeline and forecast: one loop, not three documents
Capacity planning, pipeline management and forecasting are usually owned by three different people who meet quarterly and disagree. Run as one loop, they check each other every week.
The capacity plan says what the team can produce. The coverage ratio converts that into how much pipeline is required to produce it. The weighted pipeline says how much of that pipeline actually exists and how likely it is to close, weighted by stage, historical conversion and deal health rather than by rep optimism. The forecast says what will land this quarter. When the weighted pipeline falls below the coverage the capacity plan requires, you have a demand problem that no amount of hiring fixes, and you know it in week three rather than week eleven.
Running the loop weekly changes three decisions. Hiring: you stop approving headcount for a quarter that cannot ramp it in time. Quota: you stop setting numbers the coverage maths says are unreachable. Pipeline generation: marketing gets a required-pipeline number derived from capacity instead of a lead target derived from last year.
Revenue and finance
The plan the CRO and the CFO both sign
The capacity plan is the one artifact where revenue and finance have to agree, which is exactly why it tends to fall between them. Sales owns the quota, finance owns the headcount budget and the cost model, and the CRM data that would settle any argument between them belongs to neither.
LeanScale runs four practices, and three of them touch this plan. Revenue Operations owns the CRM, the sales process and the forecast, so it builds the model and keeps the record layer honest. Marketing Operations turns the required-pipeline output into campaign and channel plans. Financial Operations works from the same closed-won record for billing and revenue schedules, so the bookings in the capacity plan and the revenue in the finance system come from one source. Ongoing ownership runs through RevOps as a Service.
Working with us
Embedded operators, on a 90-day rolling subscription
We are not advisors and we are not consultants. We work directly inside your systems, alongside your team, on a 90-day rolling subscription partnership rather than a fixed project with a slide deck at the end. That structure exists because operations work is never finished: the model you build in Q1 needs maintaining in Q2, and a project-shaped engagement leaves exactly when it starts to be useful.
01
Diagnostic
We audit the record layer first: stage definitions, close-date hygiene, rep records, quota assignment, historical attainment. You get a ranked list of what is broken and what it costs you.
02
Repair
We fix the inputs the model depends on. Usually this is stage definitions, quota fields and a clean rep-to-territory-to-segment mapping.
03
Build
The capacity model goes into the CRM as reporting, not a spreadsheet: ramped-equivalent headcount, capacity against target, required pipeline, coverage.
04
Run
We keep it current on a weekly cadence, reconcile it against the forecast, and flag gaps before the quarter closes rather than after.
FAQ
Sales capacity planning questions, answered
01
What is sales capacity planning?
It is the process of working out how much revenue your current and planned sales team can realistically produce, and therefore how many reps you need and by when to hit a revenue target. The output is a headcount plan with dates, a quota structure, and the gap between what the team can produce and what the board has asked for.
02
How do you calculate sales capacity?
Multiply the number of fully ramped reps by the quota each one carries, then by your average quota attainment. To get the headcount you need instead, divide the revenue target by quota multiplied by attainment. Both versions only work if “ramped reps” counts partially ramped hires as fractions of a head rather than whole ones.
03
What is the difference between capacity planning and forecasting?
Forecasting predicts what will close from the pipeline that exists today. Capacity planning asks whether the team can generate and close enough pipeline to hit a target over a longer horizon. Forecasting is a quarter-level question, capacity planning is a year-level one, and they should reconcile against each other every week.
04
What quota attainment should I use in the model?
Your own trailing four quarters, calculated across ramped reps only. If you genuinely do not have the history, around seventy percent is the commonly cited B2B SaaS median, but treat it as a placeholder and replace it as soon as you have two quarters of real data. Planning at one hundred percent attainment is one of the most common ways these models fail.
05
How long does a new sales rep take to ramp?
Industry benchmarks commonly put it at about seven months to full productivity for B2B reps. Your own number is onboarding time plus one average sales cycle, which is why enterprise teams ramp more slowly than SMB teams. Model it as a monthly curve rather than a single switch from zero to full.
06
How much attrition should I plan for?
Annual sales attrition commonly runs around thirty percent, so a team of twenty should expect roughly six departures a year and should carry the backfills, with their own ramp curves, in the plan from the start. If your own attrition is meaningfully lower, use yours.
07
Do I need a sales capacity planning tool?
Not usually, and not first. The constraint is usually data quality in the CRM, not the absence of a planning tool. A tool built on unreliable stage definitions and missing rep records produces a confident wrong answer faster. Fix the record layer, build the model in the CRM, and buy planning software later if the complexity genuinely justifies it.
08
Is there a sales capacity planning template?
Templates are a reasonable starting point for the arithmetic and a poor substitute for the operating cadence. The maths is not the hard part. Keeping the model connected to live CRM data, and having someone accountable for refreshing it, is the hard part. Our documentation includes a step-by-step capacity plan walkthrough.
09
Who should own the sales capacity plan?
Whoever sits across sales, finance and the CRM. In practice that is RevOps, working with finance on the cost side and the CRO on quota. If it is owned by finance alone it drifts from what the CRM says, and if it is owned by sales alone it drifts from what the budget allows.
10
How often should the capacity plan be updated?
Weekly for the inputs that move weekly, which are pipeline, coverage and rep status, and quarterly for the structural assumptions, which are quota, ramp and attrition. A plan reviewed only at the quarterly business review is a plan you find out about too late.
11
What does capacity utilization mean and what is a good number?
It is how much of your theoretical capacity the team is actually producing. Commonly cited research puts functioning B2B teams in the 65 to 75 percent range. Consistently above that suggests quotas are set too low, consistently below suggests a pipeline, territory or enablement problem rather than a headcount one.
12
We are pre-Series B and have six reps. Is this too early?
No, and it is cheaper now. At six reps the model takes days rather than weeks because there is less history to reconcile, and the record-layer decisions you make now determine whether the plan still works at thirty reps. The teams with the worst capacity data are the ones that waited until they needed it.
Customer proof
Teams that let us run this
We’ve owned the GTM systems for 100+ growth-stage B2B SaaS companies, including Mistral AI, Chainguard, AssemblyAI, Clio, Factory.ai, Anrok and Integrate.io. See the case studies.
Selected customers
Mistral AI
Chainguard
AssemblyAI
Clio
Fountain
RunPod
Factory.ai
Ocrolus
Anrok
Act-On
GreyNoise
Integrate.io
CallRail
Patlytics
SpyCloud
Scandit
Coactive
wealth.com
OpenArt
OnBoard
Customer review · G2
Manager, RevOps
“They combine strategic RevOps thinking with hands-on execution — not just high-level recommendations. They help us actually design, document, and implement the systems we need.”
Nicholas B., via G2
4.9 / 5
Get started
Get a capacity plan you can defend in a board meeting
Start with the diagnostic. We audit the data your sales capacity planning actually depends on, tell you what is broken and what it is costing you, and give you a ranked list of fixes.
Powering startups backed by the biggest VCs in tech
Lightspeed
a16z
General Catalyst
Insight Partners
Bessemer
Updata
Sapphire