Skip to content
Sales Capacity Planning

Sales Capacity Planning: Turning a Revenue Target Into a Hiring Schedule

A definition you can quote, the formula with every input defined, a full illustrative worked example in productive representative-months, and the assumptions that sink plans.

Free Forever • No Credit Card Required

Capacity model showing ramped representatives, new hires, ramp periods, and productive months against an annual target

Quick answer

Is HelloGrowthCRM right for Sales Capacity Planning?

Yes. HelloGrowthCRM gives Sales Capacity Planning a single system to capture every lead, automate follow-up across phone, WhatsApp, and email, prioritise leads with AI scoring, and forecast revenue — with calling and messaging built in instead of sold as add-ons. It's built for the problems these teams actually hit — like the plan counted heads at year end and the year missed by a wide margin — rather than generic sales busywork.
  • Plain definition: sales capacity planning works out how much selling capacity is needed to reach a revenue target, and when people must be hired for that capacity to exist in time
  • The unit that makes the model honest is the productive representative-month, not the headcount, because a person hired in October contributes almost nothing to that calendar year
  • Productivity per ramped representative should come from your own history, segmented by role and segment, rather than from a figure quoted in an article

See pricingBook a demo

01

Definition

Sales capacity planning is the exercise of working out how much selling capacity is needed to reach a revenue target, and when people must be hired for that capacity to exist in time.

The second clause is where most plans fail. Capacity is not a headcount at year end; it is the sum of months during which people were actually able to sell. Those are very different quantities, and only one of them produces revenue.

02

The formula and its inputs

Required capacity (in ramped representative-years) = annual target ÷ expected annual productivity per fully ramped representative.

Then, in the honest version: required productive representative-months = annual target ÷ (expected productivity per ramped representative ÷ 12).

Productivity per ramped representative

Taken from your own attainment history, segmented by role and segment, expressed as a median rather than a mean so that one exceptional performer does not set the plan for everybody.

Ramp period

Derived from when your past representatives began attaining at a normal rate. It is subtracted from each new hire's contribution, so a hire produces productive months only after ramp ends.

Attrition and replacement lag

An expected departure rate, plus the full gap between a departure and restored capacity: notice period, recruitment, and another ramp.

Hiring lead time

The interval between deciding to hire and someone starting. This determines whether the schedule the model produces is achievable at all.

03

A full worked example (illustrative figures)

These numbers are invented to demonstrate the method and are not benchmarks.

A team carries an annual target of twelve crore rupees. Its own history shows a fully ramped representative closes about one crore per year, which is roughly eight lakh thirty thousand per productive month. Required productive representative-months = 12,00,00,000 ÷ 8,30,000, which is approximately 144 months.

Existing capacity: eight fully ramped representatives present for all twelve months supply 8 × 12 = 96 productive months.

Planned hires: four representatives starting in month one, each with a four-month ramp, are productive from month five onwards. Each supplies eight productive months, so four supply 32. Running total: 96 + 32 = 128 productive months.

The shortfall is 144 − 128 = 16 productive months. Two further representatives hired in month one would add another sixteen, closing the gap exactly, whereas two hired in month five would add only eight each after ramp, which is barely enough and leaves no margin.

Now apply attrition. If history suggests roughly one departure among ten representatives in a year, and the replacement gap is around six months including recruitment and ramp, the plan loses approximately six productive months. Restoring the balance means hiring one more person early rather than discovering the shortfall in the third quarter, when nothing can be done about it.

04

What the model is for

It converts a revenue target into a hiring schedule with dates, which is the only form in which a target can actually be acted upon. It also exposes the moment when a target has become arithmetically unreachable, which is far more useful in November of the prior year than in July of the current one.

Its second function is to force a conversation about pipeline. Capacity and pipeline are two separate constraints, and a plan that adds people without adding qualified opportunities simply distributes the same revenue across more representatives.

05

How capacity plans go wrong

Counting heads instead of productive months

The dominant failure. A plan showing fourteen representatives by December looks robust and may contain very little productive capacity, because the hires arrive late and ramp into the following year.

Borrowed productivity assumptions

Using a productivity figure from an article rather than from your own attainment data makes the entire model an elaborate restatement of somebody else's business.

Assuming nobody leaves

Attrition is not a risk to be footnoted; it is a planned quantity. A departure in the first quarter can remove most of a representative's annual contribution once recruitment and ramp are counted.

Ignoring hiring lead time

A model that requires four representatives productive by April, with a four-month ramp and a two-month recruitment cycle, is really a model that required a decision last October.

Inflating quotas to make the plan balance

When capacity falls short, the easiest adjustment is to raise everybody's quota. This does not create capacity. It converts a resourcing problem into a morale problem and delays the recognition of the same shortfall.

06

What good and bad look like

A sound plan is built bottom-up from your own attainment data, expressed in productive representative-months, carries explicit ramp and attrition assumptions, produces hiring dates rather than a year-end headcount, is run as a small number of scenarios, and is reforecast mid-year against actual ramp and attrition.

A weak one is a single number, derived top-down, using borrowed productivity, assuming full contribution from every hire, with attrition mentioned only as a risk. Its distinguishing feature is that when the year misses, nobody can identify which assumption was wrong.

07

The inputs and where they come from

InputWhere it comes fromCommon error
Productivity per repMedian attainment of ramped repsUsing a mean skewed by one top performer
Ramp periodWhen past hires began attaining normallyAdopting a conventional figure untested
Attrition rateYour own departure history by roleExcluding it as too uncomfortable to plan
Replacement lagNotice plus recruitment plus rampCounting recruitment time only
Pipeline coverageQualified pipeline against the targetPlanning capacity without planning demand
08

Building it from records you already keep

Every input above exists in a reasonably maintained CRM: attainment by representative over time, start dates, departure dates, and pipeline by source. A capacity model built from those, in a spreadsheet, is more defensible than a sophisticated model built on assumptions borrowed from elsewhere, and it can be reforecast in an afternoon when the year turns out differently.

Challenges we solve

The problems holding this industry back — and the fix

Every team in this space loses revenue to the same recurring gaps. Here is what they cost you and how HelloGrowthCRM closes each one.

  • The plan counted heads at year end and the year missed by a wide margin.

    Convert every hire into productive representative-months by subtracting the ramp period and counting only the months that remain in the year. A representative starting in October with a four-month ramp contributes zero productive months to that calendar year, however impressive the year-end headcount looks on a slide.Productive months, not heads

  • Productivity per representative was taken from an industry article and the model was wrong from the start.

    Use your own attainment history, segmented by role and by segment, and use a median rather than an average because a single exceptional performer distorts the mean. If you have no history, state the assumption explicitly and plan to revise it after two quarters rather than treating a borrowed figure as fact.Productivity from your own data

  • Attrition was ignored and the team shrank quietly through the year.

    Include an expected attrition rate and model the replacement cycle: departure, recruitment, and a further ramp period before capacity is restored. That total gap is usually far longer than people assume, which is why a plan without attrition allowance runs short from around the middle of the year.Attrition and replacement lag

  • Capacity was added but pipeline was not, and the new representatives had nothing to work.

    Plan the two constraints together. Every additional unit of capacity needs a corresponding increase in qualified pipeline, whether from marketing, outbound, or partners. Adding representatives to a fixed volume of opportunities divides the same revenue among more people and damages morale as well as attainment.Capacity planned with pipeline

What you get

Why teams choose HelloGrowthCRM

AI-powered CRM with the features you need to close more deals.

  • Plain definition: sales capacity planning works out how much selling capacity is needed to reach a revenue target, and when people must be hired for that capacity to exist in time
  • The unit that makes the model honest is the productive representative-month, not the headcount, because a person hired in October contributes almost nothing to that calendar year
  • Productivity per ramped representative should come from your own history, segmented by role and segment, rather than from a figure quoted in an article
  • Ramp time is derived from data on when representatives historically began producing at a normal rate, and it varies by segment and by the complexity of the sale
  • Attrition must be planned rather than hoped away, since a plan that assumes nobody leaves will be short of capacity by the second half of the year
  • Hiring lead time is part of the model. A representative who must be productive by April has to be hired well before April, and recruiting takes as long as it takes
  • Capacity and pipeline are two constraints, not one. Enough representatives with insufficient pipeline miss the number just as reliably as the reverse
  • Territory and account allocation determine whether capacity is usable, because two representatives sharing one thin territory do not produce twice the revenue
  • Managers are part of capacity planning too, since span of control affects how quickly new representatives ramp and how consistently they are coached
  • The model should be run in scenarios rather than as a point estimate, because the inputs carry real uncertainty and a single number hides it
  • Reforecasting mid-year with actual ramp and attrition data is what turns the model from a planning artefact into a management tool
  • In a CRM, the inputs already exist: attainment by representative, start dates, cycle lengths, and win rates, which is what makes a bottom-up model feasible without a planning system

HelloGrowthCRM by the numbers

$12
per user/month list price — $10/user/mo on annual billing, ₹899/user/mo in India
$0
free forever starter plan — no credit card required
14-day
trial included on paid plans
259+
live integrations, from WhatsApp to Tally and QuickBooks
500+
teams worldwide run their pipeline on HelloGrowthCRM

Frequently Asked Questions

Common questions about using HelloGrowthCRM in your industry.

Ready to grow?

Join small businesses that close more deals with HelloGrowthCRM.

Free Forever • No Credit Card Required

Take the next step

Free Forever • No Credit Card Required

Prefer email? Write to sales@hellogrowthcrm.com