Why territory design is more art than science, and how to get it right.
RevOps leaders often describe territory design as something that should take a meeting. In reality, it's one of the most consequential, multidimensional decisions a growing sales organization makes. Get it right, and you create a foundation for sustainable growth, fair compensation, and scalable operations. Get it wrong, and you're managing turnover, missed quotas, and organizational chaos for years.
I recently sat in on a comprehensive territory redesign meeting for a mid-market SaaS organization managing thousands of customers across multiple global regions. What began as a straightforward account-to-rep assignment exercise quickly became a 90-minute exploration of interconnected strategic, operational, and human challenges. The conversation revealed why territory design is so often bungled, and how to approach it systematically.
This article explores the hidden complexities of territory design, the critical questions you must answer, why you need diverse stakeholder input, and a practical framework for getting it right.
When most people think of "territory design," they imagine a simple division: draw lines on a map, assign customers, set quotas. But effective territory design actually requires you to simultaneously solve for multiple, often competing variables.
Let's look at how you should group industries into sales territories. On the surface, this seems like a data exercise. But it forces a fundamental strategic choice.
The Revenue-Based Approach prioritizes historical performance. You analyze which industries generate the most ARR (Annual Recurring Revenue), then group the highest-revenue industries into one territory, the next tier into another, and so on. The logic is appealing: your best reps focus on your most profitable segments.
But this approach often creates heterogeneous territories. In one organization, this method resulted in pairing manufacturing with retail, industries with completely different sales dynamics, buyer personas, and technical requirements. A rep who understands how manufacturing companies purchase software faces a steep learning curve when suddenly asked to sell to a retail organization.
The Expertise-Based Approach prioritizes industry coherence. You group industries that share similar characteristics: financial services with insurance (both regulated, compliance-heavy), media with communications (both infrastructure-focused), retail with food and beverage with logistics (all fast-moving, supply-chain-driven). There's clear on-paper benefits here: reps develop deep expertise, knowledge transfers within teams become meaningful, and hiring becomes strategic (you can recruit someone with retail experience knowing they'll also succeed in food and beverage).
The cost? Revenue distribution becomes unequal. Financial services might generate 40% of a region's revenue while another territory (e.g. nonprofits and education) generates 15%. Now your quota-setting becomes unfair.
The Real Problem: You can't optimize for both simultaneously. You must choose which variable drives your decision, then manage the downstream consequences.
Once you decide how to group industries, you face another uncomfortable truth: some territories will inherently be more valuable than others.
In technology sales, this is almost universal. Financial services and telecommunications territories typically outperform healthcare, nonprofits, or government. It's not a random occurence, it reflects market dynamics, deal sizes, and buyer complexity that exist independent of your territory design.
The Question You Must Answer: How much variance in territory potential is acceptable?
In this discussion, leadership initially thought all territories should generate roughly equal revenue. But the data told a different story. The highest-potential territory could generate 40% more revenue than the lowest-potential one, even with identical rep performance. Forcing artificial balance would mean either:
The pragmatic answer they landed on: accept 25-30% variance between segments, acknowledging that some territories are legitimately "king territories" while others are tougher slogs. Then compensate fairly for this reality through quota calibration and career development support.
Here's a deceptively simple question that turned into a 20-minute debate: How many accounts should each rep own?
The math seems straightforward. If a rep needs to close 10 deals at $25K average contract value to hit a $250K quota, and your organization converts 5-10% of accounts to customers, a rep needs roughly 200-500 accounts in their pipeline.
But there's a critical distinction between needed and sustainable.
A rep might need 500 accounts to hit quota, but releasing all 500 at once creates several problems:
The Overwhelm Factor: With 800 accounts to review, even with detailed briefs, reps don't know where to start. Paradoxically, more options can lead to less focus and lower activity on the highest-potential accounts.
The Quality Problem: Reps working through massive account lists tend to focus on easy-to-reach, lower-quality prospects rather than strategic targets. The sheer volume creates a perverse incentive toward shallow outreach rather than deep research.
The Onboarding Reality: New territories require actual work—territory mapping, account research, buying committee identification, personalized outreach strategy. You can't do this at scale across 800 accounts.
The Cascade Effect: If reps are overwhelmed, your BDRs and marketing team become reactive instead of strategic. Lead routing breaks down, and account-based marketing becomes impossible.
One alternative that's gaining traction: staged account releases. Release the top 125-250 accounts (A-graded accounts with highest ICP fit) in quarter one. After the rep demonstrates focus and results on this core set, release the next batch. This approach:
The Trade-off: Staged releases require more operational overhead and coordination. But the alternative (paralyzed reps with undifferentiated account lists) is costlier.
We often view sales reps as interchangeable and easy to replace, but the data behind deal cycles, win rates, and territory revenue generation all show that rep disruption hurts all of these metrics. Even with data backing this, territory assignment processes still often treat them that way.
Different territories require different skill sets. An upper mid-market territory (dealing with companies generating $500M+ in revenue) requires reps who can navigate complex sales cycles, manage multiple stakeholders, and handle sophisticated procurement processes. An SMB territory requires high-velocity specialists who can move deals quickly, handle smaller deal sizes, and prioritize volume over complexity.
Yet most organizations hire generic "account executives" and assume they'll thrive anywhere. When territory redesigns happen, reps are randomly assigned based on availability rather than capability fit.
The consequence: Top performers end up in mismatched territories and underperform. Underutilized reps are placed in high-value territories, frustrating management. Team dynamics fracture as some reps feel punished while others feel inappropriately elevated.
With this specific revenue leadership team, they estimated they knew with ~30% confidence where top performers should be assigned. The other ~70% required deeper conversations about individual strengths, aspirations, and expertise.
This matters not just for current assignments but for future hiring. Once you lock in territory definitions, you can shift from hiring generic AEs to recruiting specialists: "We need someone with financial services mid-market experience." "We're looking for a high-velocity SMB closer." "We need someone who can handle complex enterprise sales."
Territory design, done right, becomes a catalyst for more strategic talent management.
Effective territory design requires asking, and answering, a series of interconnected questions. These aren't yes/no questions; they're decision frameworks that shape everything downstream.
The Core Issue: Opportunity isn't distributed evenly by nature. Some regions have more customers. Some industries have higher deal values. Some accounts have more growth potential. How do you account for these natural imbalances?
Sub-Questions to Explore:
Practical Framework: Rather than trying to make all territories perfectly equal, establish a fairness principle. For example: "Territories will vary by up to 30% in revenue potential, with quotas calibrated to reflect this difference. Reps in lower-potential territories have more flexibility to develop adjacent markets."
This explicit framework prevents the resentment that comes from opaque territory assignments.
The Core Issue: "Territory size" can mean several things:
Using the wrong metric creates obvious unfairness. One rep might have 300 high-value accounts while another has 500 low-value ones. On raw account count, the second rep looks like they got more; in reality, they got significantly less.
Better Approach: Define territory size using TAM or revenue potential as the primary metric, adjusted for workload reality.
Example: "Each rep will manage territories with approximately $10-12M in TAM. Within that TAM, they might have 300 large accounts or 500 small accounts. The mix varies by industry and geography, but the total opportunity is held relatively constant."
This requires more sophisticated territory modeling but prevents obvious inequities.
Territory design isn't just about accounts; it's about markets. And markets have different characteristics.
Geographic Considerations:
Demographic and Economic Variables:
In the meeting I observed, the organization was designing territories primarily based on their Germany operations, which was the most mature market with the most customer density. The plan was to adapt this "template" to other countries by adjusting for local conditions. This is smart territory design: you establish a clear principle in your strongest market, then deliberately adapt it rather than recreating it from scratch elsewhere.
The Core Issue: You have historical performance data. Some of your top reps have closed enormous deals. Some industries have generated disproportionate revenue. Should this data drive territory design, or should you ignore it and start fresh?
The Nuance: Historical data reveals what's possible and what's not. But it can also embed past mistakes or over-index on specific rep strengths that won't transfer.
Better Approach: Use historical data as input, not as gospel. Ask:
Then balance this historical perspective with forward-looking strategy. You might discover you've underinvested in industries with high white space, or that your top reps succeeded despite suboptimal territory design, not because of it.
The Core Issue: Once you assign territories, inbound leads don't respect those boundaries. You'll have situations where:
The Problem with Round-Robin Routing: It seems fair but creates misalignment. Different BDRs will get vastly different inbound volumes. Different reps end up specializing in unintended industries. Data integrity deteriorates because routing rules are invisible.
Better Approach: Create "ghost territories"—explicitly defined unassigned segments. Designate specific reps or teams to handle inbound from these ghost territories. This creates visibility, prevents misalignment, and makes it easy to transition ghost territories into formal assignments when you hire.
Example: "Segment 5 (Nonprofits/Education) is currently unassigned. All inbound from Segment 5 routes to Sarah, who focuses on developing this market. When we hire for a Segment 5 AE, Sarah transitions all accounts to the new hire."
This is operationally cleaner and prevents the data chaos of hidden territories.
Here's where territory design moves from academic exercise to organizational reality: you cannot design territories in isolation. You need input from at least five constituencies, each with legitimate but different perspectives.
Sales leaders bring market understanding and rep capability insight. They know:
In the organization I observed, sales leadership estimated 30-40% confidence in initial rep assignments, acknowledging that the other 70% required deeper exploration. This honest assessment was valuable—it prevented leaders from over-confidently assigning reps to mismatched territories.
Key Input: "Based on rep profiles and aspirations, here's where I think our top performers should be positioned. But I need territory definitions locked first."
RevOps brings data rigor and quota realism. They understand:
In the meeting, RevOps pushed back on oversimplified thinking with data. When territory design discussions were purely theoretical, RevOps grounded them in reality: "Our account-to-win rate is 5-10%. Here's what that means for required account counts."
Key Input: "Here's what the data says about rep capacity, conversion metrics, and the white space in each potential territory."
This team manages the mechanics: routing, assignment, and territory execution. They see:
In the discussion, BDR leadership highlighted a critical point: if you assign territories to AEs without considering BDR alignment, you create misalignment in the go-to-market motion. BDRs end up supporting multiple unrelated territories, and account research becomes fragmented.
Key Input: "Here's what's operationally feasible to implement and sustain. Here's what creates problems in our systems."
Marketing often gets overlooked in territory design, but they're a critical piece of the puzzle. They understand:
When territories are designed without marketing input, you often end up with misalignment between revenue teams. Marketing is generating inbound in Segment A while you've assigned Segment A to your weakest rep. Meanwhile, Segment C (your strongest rep's territory) receives zero marketing support.
Key Input: "Here's where we're generating demand. Here's where we should be investing. Let's align territories with our go-to-market strategy."
Finance brings quota calibration and compensation expertise. They understand:
In the organization I met with, finance played a crucial role in validating that 25-30% variance in territory potential was acceptable as long as quotas were calibrated accordingly. This financial modeling informed the territory design and prevented unrealistic quota expectations.
Key Input: "Given these territories and quota assumptions, here's what we need from each segment and here's the financial impact of the design."
The core reason to involve multiple stakeholders isn't to create consensus (you won't). It's to surface hidden assumptions and downstream consequences. When sales leadership designs territories alone, they optimize for rep satisfaction and may ignore operational feasibility or data quality issues.
When RevOps designs territories alone, they optimize for mathematical fairness and may ignore sales strategy or market dynamics.
When operations designs territories alone, they optimize for system cleanliness and may ignore business opportunity or growth potential.
The magic happens when these perspectives collide. Conflicts force you to ask harder questions: "Why does marketing think Segment A is low-priority when sales thinks it's high-opportunity?" "Why can't operations route inbound to this territory if it makes strategic sense?" "What data quality issues are preventing fair territory assignment?"
These are signals pointing to genuine organizational misalignment.
Here's what makes territory design genuinely strategic: it doesn't exist in isolation. Every choice cascades into multiple downstream decisions.
Once you lock in territory definitions, you can shift from generic hiring to strategic recruiting.
Instead of: "We need two senior account executives."
You can say: "We need someone with three years of financial services mid-market experience who's based in the London region and comfortable with complex multi-stakeholder deals. We also need a high-velocity SMB specialist in the NorthEast region who can handle deal cycles under 90 days."
This is infinitely more precise and makes it possible to actually find the right person rather than hiring a generic AE and hoping they fit. More importantly, it allows you to build career paths. A rep who's excelling in SMB might develop into a mid-market specialist. Someone who's thriving in a high-competition territory might be ready for an enterprise stretch role. Territory-based hiring creates visibility into development paths.
Territory quality should be reflected in quota and compensation design.
If one territory has 40% more opportunity than another, individual quotas should reflect this. Otherwise, you're setting one rep up to earn significantly more than their peer for equal performance, or you're setting one rep up to fail because their quota is unrealistic for their territory.
More sophisticated organizations might use territory-adjusted quotas: "Your base quota is $500K, but your territory potential is $600K. Your stretch target is $750K." This creates fairness while maintaining upside incentive.
If you have a Sales / BDR or SDR partnership and assign AEs to territories without aligning BDRs, you break the go-to-market motion.
BDRs need clear lines of sight into which rep they're supporting and what that rep's territory is. When BDRs support multiple unrelated territories, account research becomes fragmented. When BDRs are assigned to territories but inbound routing is separate, they're demoralized by irrelevant leads.
Diving deep with this same revenue team, this was explicitly addressed: "We're assigning BDRs to specific AEs and their territories. Inbound from those territories routes to the paired BDR unless it's already being worked by that AE. This creates alignment and accountability."
Some products skew toward specific territory types. If your Product "A" is upper mid-market and enterprise focused, but your Product A Specialists aren't assigned to those territories, they become orphaned overlay functions without clear sponsorship.
Better design: "Product A Specialists are floating resources who support upper mid-market and enterprise AEs. When an opportunity is identified, the specialist joins the deal. Attribution is shared. There's a clear communication protocol between territory AEs and specialists."
Doing this requires explicit design; otherwise, tax specialists end up as disconnected resources chasing deals rather than integrated revenue drivers.
How you design territories fundamentally determines whether your data will be clean or chaotic in two years. If territories are clearly defined with explicit rules for new prospects, your system remains coherent. Months from now, you can look at an account and quickly identify the responsible rep.
If territories are fuzzy or implicit, with informal routing rules, you end up with accounts scattered across multiple reps, prospects assigned based on who "found them," and data that's essentially unusable for analysis.
This matters more than it seems. In mature organizations, territory design affects your ability to do territory-based analytics, quota forecasting, and performance management for years.
If you're embarking on territory design or redesign manually, here's a structured approach that accounts for each stage of this process:
Goal: Make explicit decisions on key variables before doing any design work.
If you design territories without input from sales, operations, marketing, and finance, you'll build something theoretically sound but practically broken. Get alignment early on decision-making principles, or you'll waste months redesigning based on feedback you should have gathered upfront.
Territory assignment should reflect rep capability, not just availability. A top performer assigned to a weak territory is demoralized. An underperformer assigned to a king territory creates frustration elsewhere. Get specific about rep-to-territory fit.
You can't make all territories perfectly equal, and trying to often creates worse problems. A rep with 300 accounts might be miserable. A rep with 500 accounts might be more focused. Define fairness clearly (usually around opportunity/TAM), but accept natural variation.
If your customer data is messy, territory design will surface this painfully. Clean your data before you design territories, or your territories will be built on a broken foundation.
Territories should be strategy-driven but operationally flexible. Leave room for rebalancing. If a rep identifies a new market segment within their territory, let them pursue it. If two reps can justify territory sharing, make it possible. Rigid territories often create misalignment with actual market opportunity.
If you're designing territories without considering marketing, BDR alignment, and product specialization, you're solving the wrong problem. Territory design should reflect your end-to-end go-to-market motion, not just rep-to-account assignments.
Territory design is unglamorous work. It doesn't generate revenue directly. It doesn't close deals. It doesn't move metrics visibly, but it affects everything.
Get territories right, and you create conditions for sustainable growth. Reps understand their market. Quotas are achievable. Marketing can create relevant demand. BDRs support territories coherently. New hires know what they're being hired for. You can measure performance meaningfully and develop talent systematically.
Get territories wrong, and you manage dysfunction for years. Reps are demoralized by unfair assignments. Marketing creates demand that doesn't align with rep territories. BDRs support multiple unrelated segments. Every new hire requires months of informal onboarding because no one really knows what the territory is. You can't compare reps fairly because territories are incomparable.
The investment to get territory design right, explicit stakeholder alignment, clear decision-making, rigorous design, and iterative refinement pays compounding returns.
If you're leading a sales organization, territory design deserves real time, real thought, and real investment. It's not something to delegate or rush. It's foundational infrastructure for everything that comes next.