Capacity is arithmetic: how to build a sales capacity plan that reconciles to the budget

A sales headcount plan is usually an argument between a number sales wants and a number finance will pay for, settled by whoever is more tired. A capacity plan is arithmetic, and arithmetic ends arguments. This guide sets out the two sides of the model and the scenario table that lets the planning meeting move the levers and see the cost.

The two sides

Capacity, per territory:

Capacity = Σ reps (calls per week × working weeks × ramp factor)

Demand, per territory:

Demand = Σ accounts (required calls per year for the account's tier)

Gap, per territory:

Gap = (demand − capacity) ÷ calls per rep per year, expressed in reps

A positive gap is reps short; a negative gap is capacity to redeploy.

The rows you need

• Accounts: one row per account with territory, tier, and revenue or potential.
• Reps: one row per rep with territory, start date, and calls per week if it varies.
• Rules: calls per week by role, working weeks, ramp curve, required frequency by tier, fully loaded cost per rep.

Building the model

1. Demand per territory from accounts and tier frequencies.
2. Capacity per territory from reps, calls per week, working weeks and the ramp curve applied to each rep's start date.
3. Gap in reps per territory.
4. Cost of the plan: reps times loaded cost, per territory.
5. Assert that accounts by territory sum to the account list, and reps by territory sum to headcount.

Σ accounts(territories) = account list, Σ reps(territories) = headcount

Two scenarios can only be compared if both assertions hold in each.

A worked comparison

Plan A is current headcount. Plan B adds two reps in the South and reduces tier-two frequency from quarterly to three times a year.

Plan B closes most of the gap for $0.3m, half from the two reps and half from the frequency change. The remaining 3.7 reps of gap is a decision the meeting can now make with the cost beside it, rather than a feeling that the team is stretched.

Where it goes wrong

Headcount instead of capacity. Counting reps without ramp overstates capacity in a year with turnover. Every rep has a start date; apply the curve.

Frequency by gut. Tier frequencies that were never written down cannot be modelled. Write them down; the scenarios will correct them.

Demand from the whole database. Accounts nobody intends to call inflate demand. Tier them at zero frequency explicitly, so the decision is visible.

Cost as salary. Loaded cost includes tools, travel, management and commission at plan. Use the number finance uses.

Agreed with finance in the room

Mapped once, the account list and the rep list produce the capacity model, and each scenario returns the gap per territory and the cost, reconciled. The plan is agreed in the meeting because both sides are looking at the same arithmetic. Covirage builds scenarios this way and hands the chosen plan to the territory planner. The capacity planning page describes it.