Every year, a revenue leader is handed a number and asked how many people it will take to deliver it. The quick answer is to divide the target by what one salesperson produces. The real answer is almost always larger, because that simple division assumes everyone is already productive on the first day of the year, that nobody leaves, and that new hires arrive on time. Capacity planning is the discipline of replacing those assumptions with realistic ones.

The basic calculation

Suppose next year’s new ARR target is ₹40 crore. A fully ramped account executive in this business delivers about ₹3.2 crore of new ARR a year. The team today has eight ramped AEs.

The existing team should deliver 8 × ₹3.2 crore = ₹25.6 crore. That leaves a gap of ₹14.4 crore. New hires do not produce at full capacity in their first year; in this company they deliver about half, or ₹1.6 crore each. Filling the gap therefore needs ₹14.4 crore ÷ ₹1.6 crore = 9 new hires.

Note what the naive calculation would have said. ₹40 crore ÷ ₹3.2 crore is 12.5, so “we need about 13 AEs, we have 8, hire 5”. The ramp adjustment nearly doubles the hiring requirement.

Productivity is not quota

The ₹3.2 crore figure should be what a ramped AE actually delivers on average, not their quota. Quotas are usually set above expected productivity, sometimes well above, so that the company still hits its number when some reps miss. If the average ramped rep achieves 80% of a ₹4 crore quota, productivity is ₹3.2 crore. Planning capacity on quota instead of real productivity is one of the most common reasons a fully staffed team still misses.

Productivity should come from history, ideally the last several quarters, segmented by role and market. Enterprise AEs, mid-market AEs and inside sales reps have very different numbers, and mixing them gives an average that fits none.

When do the hires actually start?

“New hires deliver 50% in year one” quietly assumes they join at the start of the year. In practice, hiring takes time. Finding, interviewing and closing a good enterprise seller can take a few months, and in India notice periods of 60 to 90 days are common for experienced people. A rep approved in January may not start until April or later.

Model it explicitly. Say new hires start at the beginning of the second quarter, produce at 25% of full pace for their first six months, and then reach full pace. In their nine months that year, each produces about (6 months × 25% + 3 months × 100%) of a ramped rep’s monthly output, which comes to ₹1.2 crore. Now the ₹14.4 crore gap needs twelve hires, not nine.

This is why capacity plans often recommend hiring ahead of the year. Reps hired in the last quarter of the current year are partly ramped by January and contribute far more to next year’s number.

People leave

Sales teams have meaningful attrition, both voluntary and performance-related. If one of the eight ramped AEs leaves mid-year, the company loses about half a year of their output, ₹1.6 crore. If that person is replaced, the replacement starts the ramp from zero. The plan needs a buffer.

A practical approach is to apply a historical attrition rate to the team and add backfill hires on top of growth hires. If ramped AEs effectively deliver seven and a half people’s worth of output instead of eight, the existing team produces ₹24 crore and the gap grows to ₹16 crore. Ten hires at the year-one productivity of ₹1.6 crore would be needed, before adjusting for start dates.

The constraints beyond headcount

Adding AEs only works if the rest of the system can support them. A capacity plan should check several dependencies:

  • Pipeline. Twelve new AEs need twelve new territories with enough accounts and pipeline to work. If marketing and SDR capacity does not grow too, new reps compete for the same leads and productivity falls for everyone.
  • Support ratios. Solution engineers, deal desk staff and managers each support a limited number of AEs. A common planning approach is to set ratios, such as one manager per six to eight reps, and add support roles as AEs are added.
  • Onboarding capacity. Hiring many people at once strains managers and enablement teams, which can lengthen ramp time.
  • Market size. If the addressable market in a region is small, adding reps eventually yields diminishing returns.

Turning the plan into a range

Because every input is uncertain, a good capacity plan presents a range, not one number. A base case uses historical productivity, ramp and attrition. A downside case assumes slower hiring, longer ramp or lower productivity. The upside case assumes the opposite. Showing the board that ₹40 crore needs somewhere between nine and fourteen hires, depending on how quickly they can be brought in, is more honest and more useful than a single figure that assumes everything goes right.

The plan should then be tracked monthly. If hires are landing later than planned, or ramp is slower, the revenue forecast for the second half of the year should be adjusted early, while there is still time to respond with other levers such as partner channels, pricing or expansion campaigns into the existing base.

Written by the RP Strativa Team. Figures in the examples are illustrative.

Leave a Reply

Trending