Territory and Quota Model Template
Two documents and four sheets, building quota from scored territory potential and checking workload balance before the kickoff meeting.
Free download · No account needed
Territory Map
Calloway Systems, a fictional B2B SaaS company. Five territories, 240 accounts, $9,000,000 company target. Final state, after one rebalancing move.
| Territory | Accounts | Potential | Workload | Workload / $100k quota |
|---|---|---|---|---|
| T1 - Upper Midwest | 48 | $2,000,000 | 90 | 4.500 |
| T2 - Southeast | 48 | $1,800,000 | 76 | 4.222 |
| T3 - Northeast Metro | 44 | $1,950,000 | 106 | 5.436 |
| T4 - Southwest | 48 | $1,400,000 | 63 | 4.500 |
| T5 - Mountain West | 52 | $1,850,000 | 94 | 5.081 |
Company average is 4.767, band is 4.052 to 5.482. Every territory lands inside it now, after four accounts moved from T3 to T5.
Balance Check
Before the fix: quota already matched each territory's own potential dollar-for-dollar. Workload told a different story.
| Territory | Workload / $100k (before) | Status | After the move |
|---|---|---|---|
| T1 | 4.500 | OK | 4.500 |
| T2 | 4.222 | OK | 4.222 |
| T3 - Northeast Metro | 6.000 | OVERLOADED | 5.436 |
| T4 | 4.500 | OK | 4.500 |
| T5 - Mountain West | 3.667 | UNDERLOADED | 5.081 |
Fix: 4 named accounts (Northfield Health, Vandermeer Logistics, Castlebridge Financial, Ashcombe Manufacturing, $650,000 potential and 50 workload units combined) moved from T3 to T5.
Quota Build by Rep
Quota set bottom-up from each territory's own final potential, reconciled to the company target.
| Rep | Accounts | Quota | % of company target |
|---|---|---|---|
| rep-01 (T1) | 48 | $2,000,000 | 22.2% |
| rep-02 (T2) | 48 | $1,800,000 | 20.0% |
| rep-03 (T3) | 44 | $1,950,000 | 21.7% |
| rep-04 (T4) | 48 | $1,400,000 | 15.6% |
| rep-05 (T5) | 52 | $1,850,000 | 20.6% |
| Total | 240 | $9,000,000 | 100.0% |
The total ties exactly to the $9,000,000 company target. Matching the target was never the hard part; the balance check above is.
Territory planning guidance has mostly converged on one point: balance on opportunity and workload, not on account count or map area. A territory of twenty large accounts is not equivalent to a territory of twenty small ones, even when the account count matches. Quota built proportional to a territory's own potential, rather than split evenly across reps, is the standard fix most guides now recommend.
That fix is necessary and not sufficient. Two territories can carry quotas that both match their own potential dollar-for-dollar and still hand one rep a much harder job, if the accounts behind that potential take more effort to sell and service. This pack scores every account's potential and workload, then builds territories and quota from those scores. It also runs a balance check most plans skip: workload per dollar of quota, tested against a band around the company average, naming any territory that falls outside it before the plan reaches a rep.
On a worked run for Calloway Systems, a B2B SaaS company, five territories held equal 48-account headcounts with quota already proportional to potential. One territory still needed 6.0 workload units per $100,000 of quota against a 4.767 company average, and another needed only 3.667. Moving four named accounts between them brought both within a defined band. The pack pairs with computing required new-business pipeline by segment and with forecasting renewal risk from account usage.
What's in the pack
Assignment Methodology
How potential and workload are scored per account, and how territories and quota get built from those scores.
Fairness Note
The one-pager a rep reads before the kickoff, showing the same math their own territory was checked against.
Territory Map
The final territory split with potential, workload, and the workload-per-quota ratio for every territory in one place.
Account Assignment
Every account's assigned territory, with any moved account's origin, destination, and the specific reason it moved.
Quota Build by Rep
Quota set bottom-up from each territory's own potential, reconciled against the company's top-down target.
Balance Check
Workload per dollar of quota tested against a band around the company average, naming any territory outside it and the fix applied.
How to use it
- 1
Send the account list and target
Accounts with firmographics and historic spend, known deal complexity or service burden, and next year's revenue target.
- 2
Score potential and workload
Every account gets a realistic potential figure and a workload weight, not a geography label or a headcount slot.
- 3
Build territories and quota
Territories assembled from the scores, with quota set bottom-up from each territory's own scored potential, not split evenly.
- 4
Run the balance check
Workload per dollar of quota tested against a band, with any flagged territory fixed by moving named accounts.
Frequently asked questions
Isn't quota proportional to potential already fair?
It fixes one problem and leaves another. Calloway's territories all had quota matching their own potential exactly, and one still needed 64% more workload per quota dollar than another, a gap a potential-only quota build can't see.
What if we don't have clean workload data per account?
Start with whatever proxy exists: number of stakeholders, historical sales cycle length, or a simple complexity tag a rep or manager assigns. An imperfect workload weight applied consistently still catches a territory that's wildly out of line, which a quota built on potential alone cannot.
How wide should the balance band be?
The pack's worked example uses plus or minus 15% of the company average, wide enough to allow for real account-mix differences without letting a genuine imbalance pass. Tighten it if your book is homogeneous enough to support a stricter bar, or widen it slightly for a book with naturally more variance.
What happens if a flagged territory can't be fixed by moving accounts?
Say so directly rather than forcing a move that only shifts the imbalance onto a different territory. The Fairness Note names the alternative for that specific territory instead: added headcount, a workload-adjusted quota, or extra support resource, decided case by case.
Does the bottom-up quota total need to match the top-down company target?
It should, and stating whether it does is part of the build. When it doesn't, that gap is a real planning problem, more pipeline needed or a target that has to move, not something to close by inflating every rep's number until the total works on paper.
How is this different from a pipeline coverage or renewal forecast pack?
Those cover whether enough pipeline exists to hit an already-set number. This pack covers what happens earlier: setting the territories and quotas in the first place, before the year starts and before pipeline coverage becomes the question.
We're restructuring territories mid-year after a wave of churn. Does this still apply?
Yes, though a mid-year rebuild should account for accounts already lost. Run renewal and churn forecasting first to settle which accounts are actually still active, then score and balance-check the territories from that corrected list rather than the original one.
Find the territories a headcount split can't catch
Send your account list, revenue target, and rep count, and get a scored, balance-checked territory and quota plan.
Get the template