How Many Accounts Should a Sales Rep Have? A Capacity-Based Answer

Most account loads are set by dividing the account universe by the number of reps. That produces a number, and the number is almost always wrong. It assumes every account costs the same amount of selling time and that a rep can work every account they own. Neither holds.

The better approach starts from the seller's calendar and works outward.

How do you calculate the right account load?

Divide available selling hours by the hours one account consumes per period, then apply the touch frequency the segment requires.

Start with the calendar. A rep has roughly 2,000 working hours in a year. Internal meetings, training, travel, CRM work, and administrative time consume a large share of that. What remains is selling time, and it is the only input that matters.

Then estimate what one account costs. A discovery call, follow-up, demo, security review, and procurement cycle add up differently by segment. Multiply the hours per account by the number of times you intend to touch that account in a year.

Here is the calculation on a worked example across three segments. The hour figures are placeholders you should replace with your own time study.

The output is a working load, not an owned load. If your enterprise reps own 300 accounts each while the math says 50, then 250 of those accounts are assigned to nobody in practice.

What is the difference between accounts owned and accounts worked?

Owned accounts sit in the CRM under a rep's name. Worked accounts get contact at the frequency the segment requires. The gap between them is dead coverage, and it distorts every downstream number.

Dead coverage is expensive in two ways. It makes territory potential look larger than it is, so quota gets set against accounts nobody is calling. It also hides real market coverage gaps, because the account technically has an owner and never appears on a gap report.

Measure it directly. Count assigned accounts with no logged activity in 90 days as a share of the total book. Track that share over time. A large and rising share means the account load exceeds capacity, and no amount of activity coaching will fix it.

What happens when the account load is too high?

Selling hours stay fixed, so adding accounts reduces the time spent on each one and conversion falls across the whole book. A rep with twice the accounts does not produce twice the pipeline. They produce roughly the same pipeline with a longer list of accounts they have not called.

Two symptoms appear first. Untouched accounts climb, which shows up as a growing share of the book with no activity. Then stale pipeline climbs. Across ORM customers, 10 percent or more of pipeline typically sits untouched for 12 months. An over-assigned book is one reason records go untouched. Meaningful activity means a change in stage, close date, or amount. Anything else is a note in the record, not progress.

Stale pipeline is not a harmless nuisance. It inflates coverage, which then feeds a forecast built on opportunities that will never close. See deal slippage for how close date movement compounds the same problem.

How do you check the load against actual results?

Compare account load per rep against attainment, then look for the point where more accounts stop producing more revenue.

Plot each rep's worked account count against their closed won revenue for the prior year. In most teams the relationship flattens somewhere, and that flattening point is your practical ceiling. Reps past it are not underperforming, they are over-assigned.

Run the same check on pipeline creation rather than closed revenue if your sales cycle is long enough that closed won lags the assignment change. Pipeline created per rep responds faster.

Should every rep carry the same number of accounts?

Equalize selling hours, not account counts. A rep covering enterprise accounts that each need six stakeholders engaged is carrying the same workload at 50 accounts as a commercial rep at 350. Publishing a single account-per-rep number across segments creates an argument that has no correct answer.

When you do publish loads, publish the hours assumption alongside them. Reps will challenge the hours figure, which is the input worth challenging. That conversation improves the model. A challenge to the account count alone goes nowhere.

How does account load affect the forecast?

Account load sets the ceiling on how much pipeline can be created, which sets the ceiling on the forecast. If the plan requires pipeline creation that the current load cannot support, the shortfall is already determined before the quarter starts.

This is where capacity planning and forecasting meet. The forecast has to account for what will be created and closed inside the period, not only what already sits in the CRM. Teams that model only the visible pipeline miss the in-quarter motion entirely, and account load is the single biggest constraint on that motion.

Build the load calculation into the same model you use for the number. The mechanics of connecting capacity inputs to a revenue projection are covered in how to forecast revenue, and the underlying definitions in sales forecasting.