Territory model is a coverage decision that gets treated as an org chart decision. The three standard options distribute the same account universe in different ways, and each one trades a different thing for a different gain. Picking the wrong one shows up as uneven attainment, accounts nobody owns, and a forecast that swings for reasons nobody can explain.
What are the three territory models?
Geographic territories split accounts by location, vertical territories split by industry, and named account territories assign a fixed account list to each rep. Everything else is a variation or a hybrid of those three.Geographic is the default for volume motions. It is simple to administer, easy to explain, and produces clean rules of engagement, since an account's location rarely changes.
Vertical assigns reps to industries. Reps develop domain fluency, reference stories accumulate inside a segment, and discovery gets sharper because the rep already knows the buyer's operating problems.
Named accounts hands each rep an explicit list, usually the largest or highest-potential companies. Assignment is deliberate rather than rule-based, and the list is stable across periods.
How do the three models compare on the things that matter?
Geographic wins on administrative simplicity, vertical wins on conversion rate, and named accounts wins on forecast stability. No model wins on all three.| Dimension | Geographic | Vertical | Named account |
|---|---|---|---|
| Setup and maintenance | Low effort | High effort | Medium effort |
| New-rep ramp speed | Fast | Slow | Slow |
| Coverage gaps | Rare | Common at vertical edges | By design, non-named accounts are uncovered |
| Win rate lift from specialization | None | High | High |
| Forecast stability | Low | Medium | High |
| Rules-of-engagement disputes | Rare | Frequent | Rare |
| Scales past 50 reps | Yes | With pods | Requires tiering |
When should you use a geographic model?
Use geographic when your win rate is roughly flat across industries and your deal cycle is short enough that rep specialization does not pay for itself. That describes most commercial and SMB motions.Three conditions favor it. Deal sizes are similar across the account base, so a location split produces balanced books without heavy adjustment. The sales motion is transactional enough that industry knowledge adds little to conversion. Headcount is growing fast, and the model needs to absorb new reps without a redesign, which a geographic split does by subdividing regions.
Its weakness is account potential variance. Two territories with equal account counts can have very different revenue ceilings, and rep attainment will diverge for reasons that have nothing to do with rep quality. Balance on modeled potential rather than on account count.
When does a vertical model earn its complexity?
Use vertical when win rate varies meaningfully across industries and the gap traces to buyer knowledge rather than to product fit. A useful test is whether the spread between your best and worst verticals is large enough to survive a change in one quarter's mix.Run the diagnostic before restructuring. Pull two years of closed opportunities, group by industry, and compare win rate, average deal size, and cycle length. If financial services closes at 32 percent in 90 days and manufacturing closes at 19 percent in 140 days, a vertical split is defensible. If every industry sits within a few points of the mean, the specialization gain will not cover the coverage gaps.
Vertical models create three recurring costs. Accounts that span industries generate ownership disputes. Ramp gets slower because new reps learn a domain along with the product. And a downturn in one industry concentrates its damage on a small group of reps, which distorts attainment and makes territory-level sales forecasting noisier at the pod level.
When are named accounts the right structure?
Use named accounts when a small number of companies represent most of your revenue potential and the sales motion requires multi-quarter relationship development. Enterprise motions with long cycles and large committees sit here.The design question is list length, and the answer comes from touch math rather than tradition. Decide how many meaningful interactions per quarter an account needs to progress, then divide a rep's available interaction capacity by that number. A motion requiring six quarterly touches per account and a rep capable of 150 meaningful interactions per quarter supports roughly 25 named accounts. Doubling that list does not double coverage. It halves the touch frequency and pushes every account below the threshold where progression happens.
Named accounts also concentrate risk. When one rep carries eight accounts, a single departure or a single stalled deal moves the segment forecast. Watch for concentration in your forecast composition. A quarter that depends on two large deals in one territory carries different risk than the same dollar amount spread across 30 opportunities, which is a point covered further in why the 3x pipeline coverage rule is wrong.
How do you switch models without breaking the quarter?
Sequence the change so account moves land at the start of a period and no in-quarter opportunity changes hands. The transition cost is real and it is routinely left out of the business case.ORM sees this pattern across its customer base. A company changes territories, coverage ratios hold at the usual 3x to 5x, pipeline volume looks fine, and sales execution degrades anyway because reps are absorbing new account sets instead of working deals. The coverage metric misses it entirely, since coverage measures dollars in the pipeline rather than the relationship continuity that moves those dollars.
Four rules that limit the damage:
1. Freeze any opportunity with a close date inside the current quarter. It stays with the originating rep through close. 2. Move accounts at period boundaries, never mid-quarter. 3. Publish the assignment logic before the assignments. Reps accept an unfavorable territory built on visible rules and resist a favorable one that appears arbitrary. 4. Hold quotas flat for one period after the change, then reset on the new territory model.
Measure the transition rather than assuming it went well. Stage-progression speed and meeting volume per rep both degrade before bookings do, which gives you a quarter of warning instead of a post-mortem.
Frequently Asked Questions
Which territory model produces the most predictable forecast?
Named accounts, because the account set is fixed and the same opportunities are tracked period over period. Geographic territories with open account universes produce more forecast variance, since new logos arrive from a pool that has no defined size.
When does a vertical model beat a geographic one?
When your win rate varies across industries and the sales motion requires domain fluency that takes months to build. A useful test is whether the spread between your best and worst verticals is large enough to survive a change in one quarter's mix. Below that, the specialization gain rarely covers the coverage gaps a vertical split creates.
Can you run a hybrid territory model?
Yes, and hybrids are common once a single model stops covering the whole account base. The common structure is named accounts for the top tier, vertical pods for the two or three industries with distinct buying processes, and geographic coverage for everything else.
How many named accounts should a rep carry?
It depends on required touch frequency rather than a fixed number. Work backward from how many meaningful account interactions a rep can sustain per quarter and how many the sales motion requires per account, then divide.
Does changing territory models hurt the forecast?
Yes, in the transition period. ORM sees teams keep their 3x to 5x coverage ratio through a territory change while sales execution degrades, because reps are distracted by new account sets. Plan for a productivity dip in the transition quarter.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo