Key Takeaways
- Account count is not workload. A 50-account territory of strategic enterprise accounts is more work than a 200-account SMB book.
- The formula has six inputs. All six matter. Skipping any of them gives you a number that looks defensible but isn't.
- The output isn't a hour count. It's capacity utilization expressed as a percentage. That's what you compare across reps.
- Healthy capacity utilization is 70-90%. The whole point of the calculation is to land every rep in that band.
- Most teams undercount account complexity. That's why their workload math says "healthy" while reps actually burn out.
Why Workload, Not Account Count
"How many accounts does each rep have?" is the wrong question. A 50-account territory of strategic enterprise accounts is more work than a 200-account SMB book. Counting accounts treats every account as equal — and accounts are never equal.
Workload measures the total time and effort required to cover all accounts at the expected service level. It captures account complexity, travel, prospecting, and the overhead of internal meetings, CRM hygiene, and forecasting reviews — the work that doesn't show up in pipeline reports but consumes real hours.
When you switch from "account count" to "workload" as your balancing metric, two things happen. First, you discover your top-quartile reps usually have more workload than your bottom-quartile reps (which explains why the bottom quartile underperforms — they have lighter books but the wrong accounts). Second, you stop being surprised that 55% of territories are materially imbalanced.
The Formula
(Active Accounts × Service Hours per Account × Complexity Factor)
+ (Prospects × Conversion Hours per Prospect)
+ Travel Hours
+ Non-Selling Overhead
Capacity Utilization (%) = Workload ÷ Available Selling Hours
That's it. Plug in real numbers from your CRM and you get a defensible capacity score for every rep.
The Six Inputs Explained
1. Active Accounts
Closed-won accounts currently being serviced. Pull from CRM. Exclude accounts that haven't had revenue or activity in the trailing 12 months — those are dormant, not active.
2. Service Hours per Account
Time required to keep an active account healthy: QBRs, expansion conversations, support escalations, renewal work. Varies by segment. Typical ranges:
- SMB / Transactional: 4-12 hours/year per account
- Mid-Market: 20-50 hours/year per account
- Enterprise / Strategic: 80-200 hours/year per account
3. Complexity Factor
Multiplier applied to service hours. Standard account = 1.0x. Complex multi-stakeholder = 1.5-2.0x. Strategic with executive sponsorship = 2.5-3.0x. More detail below.
4. Prospects × Conversion Hours
Prospects are open opportunities not yet closed-won. Conversion hours = average sales cycle time × rep involvement %. Pull from CRM opportunity history. For most B2B teams, prospect work consumes 30-50% of total selling hours.
5. Travel Hours
Direct travel time per year — driving, flying, between-meeting travel. For inside sales, this is near-zero. For field sales, can easily exceed 300 hours/year. Travel is where territory geographic design matters most.
6. Non-Selling Overhead
Internal meetings, forecasting, CRM hygiene, training, compensation reviews, all-hands. Salesforce research shows reps spend only 28-30% of their time selling — the other 70% is overhead. Typical overhead: 600-900 hours/year.
Worked Example
Mid-Market Field Rep: Sarah
Sarah covers Wisconsin and Illinois for a mid-market SaaS company. Her book:
| Input | Value | Hours |
|---|---|---|
| Active accounts | 52 accounts × 32 service hrs × 1.2x complexity | 1,997 |
| Prospects | 14 open ops × 28 conversion hrs | 392 |
| Travel | 2 trips/month × 11 mo × 18 hrs/trip | 396 |
| Non-selling overhead | — | 720 |
| Total workload | 3,505 |
Sarah's available selling hours = 1,800. Her workload utilization = 3,505 ÷ 1,800 = 195%.
Sarah is structurally underwater. There aren't enough hours in her year to cover her book at the expected service level — even before factoring in admin, sick days, or unexpected escalations. Quota is unwinnable. The fix isn't motivation. It's territory rebalancing.
Now run this for every rep on your team. The reps over 100% are burning out and missing quota for structural reasons. The reps under 70% are coasting — and probably underperforming because their books are too light to drive engagement.
Complexity Factor: Where Most Teams Get It Wrong
Most workload calculations use a flat service-hours number across all accounts. That's the single biggest mistake in the math. Account complexity varies wildly:
Standard Account (1.0x)
One primary buyer, one product line, predictable annual cadence. Most SMB and lower-mid-market accounts fit here. Service hours match the segment baseline.
Complex Account (1.5-2.0x)
3-5 stakeholders, multi-product expansion path, requires legal/security/procurement reviews. Most upper-mid-market and lower-enterprise accounts. Service hours are 1.5-2x the baseline because every conversation involves more people and more rework.
Strategic Account (2.5-3.0x)
Executive sponsorship required, multi-year contracts, named customer success motion, regular C-level QBRs. True enterprise accounts. Service hours are 2.5-3x the baseline.
Calibrate complexity factors using your actual CRM data — sales cycle length, stakeholder count, deal size — not gut feel. Most teams undercount by 30-50%, which is why workload calculations look "healthy" while reps burn out.
Calibrating the Inputs
Three rules of thumb for getting the numbers right:
- Sanity-check against your top quartile. Your top reps' actual hours should land at 85-95% utilization. If your model says they're at 60%, your service-hour numbers are too low. Adjust.
- Cross-reference with sales cycle data. Conversion hours per prospect should be (sales cycle days / 365) × annual selling hours × rep involvement %. If your CRM says 90-day average cycle and you've set conversion hours at 5, you're underestimating.
- Don't skip overhead. The temptation is to ignore non-selling time because "we want reps selling more." That doesn't make the overhead go away. Subtract it from available hours up front.
Common Mistakes
Four mistakes account for most botched workload calculations:
- Using account count as a proxy for workload. Already covered. Don't do it.
- Flat service hours across all accounts. Apply the complexity factor.
- Forgetting travel for field sales. 300-400 hours of annual travel is normal and dominates the workload calculation in geographically dispersed territories.
- Comparing across segments without normalization. A 90% utilization SMB rep and a 90% utilization enterprise rep are not in the same place. Normalize comparisons to within-segment.
Workload calculation is unglamorous, but it's the foundation of all six territory balance metrics. Get the math right once; everything downstream flows from it.
Want us to run the workload math for you?
Free Territory Fit Assessment — we'll calculate workload utilization for every rep on your team and surface the imbalances. 15 minutes, no obligation.
Request a Territory Fit Assessment →Frequently Asked Questions
What is sales territory workload?
Total time and effort required to cover all accounts in a territory at the expected service level. Sum of account-service hours, prospect-conversion hours, travel, and non-selling overhead. Expressed as hours per rep per year.
What is the sales territory workload formula?
Workload = (Active Accounts × Service Hours × Complexity Factor) + (Prospects × Conversion Hours) + Travel Hours + Non-Selling Overhead. Divide by available selling hours per rep to get capacity utilization as a percentage.
How many hours are in a sales rep's year?
~2,080 working hours. After vacation, sick time, training, and internal meetings, available selling hours are typically 1,700-1,900. That's the denominator in the utilization calculation.
What is a healthy workload index?
70-90% capacity utilization. Below 70% = slack to absorb more. Above 90% = quota unwinnable. The goal of territory design is to land every rep in the 70-90% band.
How do I account for account complexity?
Multiply base service hours by a complexity factor: 1.0x standard, 1.5-2.0x complex, 2.5-3.0x strategic. Calibrate factors against historical close-time data, not guesses. Most teams undercount complexity by 30-50%.