Every January, the same ritual plays out in scaling B2B SaaS companies. A VP of Sales pulls up last year’s territory map. A few accounts get shuffled. Someone argues about named accounts. A spreadsheet gets passed around. Territories are “done.”
And then, for the next twelve months, the entire revenue system operates on top of that hastily assembled foundation.
Territory design is not an administrative task you rush through during planning season. It is a structural decision that shapes pipeline quality, rep behaviour, forecast accuracy, and go-to-market execution for the entire year.
I’ve seen territory models break forecasts, tank rep morale, create compensation disputes, and produce coverage gaps so wide that entire market segments go unworked. Not because reps were lazy. Not because the product was wrong. Because the territory architecture was fundamentally flawed.
The damage is structural. And structural problems don’t respond to tactical fixes.
Why Territory Design Is an Architectural Decision
Think about what a territory model actually determines.
It defines which accounts a rep can pursue. Which they cannot. It sets the addressable market for each seller. It determines whether pipeline is distributed evenly or concentrated in a handful of territories. It shapes whether reps spend time on high-potential accounts or waste cycles on accounts that were never going to close.
Territory design sets the ceiling on what a rep can achieve before they make a single call.
If you get territory design wrong, you are not creating a minor inefficiency. You are poisoning the inputs to every downstream system: pipeline generation, forecasting, capacity planning, and compensation architecture.
A CRM is only as good as the data inside it. A forecast is only as good as the pipeline feeding it. And pipeline is only as good as the territory model that governs who works what.
Yet most companies treat territory design as a sales operations chore, something to get through quickly so they can move on to the “real” work of quota setting and pipeline targets. This is exactly backwards. Territory design is the foundation. Everything else is built on top of it.
The Three Failure Patterns I See Repeatedly
Territory design fails in predictable ways. Not because the people involved are incompetent, but because the default approaches are structurally flawed.
Inherited territories
The most common pattern. Last year’s territories are carried forward with minor adjustments. A few accounts get reassigned. A new rep gets a territory carved from an existing one. The fundamental structure remains unchanged.
The problem is that markets shift. Buyer behaviour changes. Product-market fit evolves. Customer segments that mattered last year may not matter this year. An inherited territory model optimises for a market that no longer exists.
I’ve seen companies running territory structures that were designed three or four years ago, by people who have since left the organisation. Nobody remembers the original logic. Nobody questions the assumptions. The territories just persist, like legacy code nobody dares refactor.
Inherited territories are the technical debt of revenue operations. They accumulate quietly and compound over time until the system becomes brittle enough to break.
Rep-driven carving
This is where territories are shaped by rep preferences and political leverage rather than market logic. The top performer gets first pick. The new hire gets whatever is left. A senior rep refuses to give up a named account, so the territory map contorts to accommodate them.
Rep-driven carving optimises for internal politics, not market coverage. It creates territories of wildly uneven potential, which in turn creates misalignment that looks accidental but is actually designed into the system.
When your top rep has a territory with three times the addressable market of your newest hire, you haven’t created a fair system. You’ve created one where quota attainment is largely determined by territory assignment, not effort or skill. And when that becomes visible, it destroys trust faster than almost anything else.
Pure geography
Dividing territories by region, postcode, or state feels clean and objective. It’s easy to explain and easy to administer. It’s also almost always wrong for B2B SaaS.
Geographic territories assume that market potential is evenly distributed across physical space. It isn’t. A single postcode in San Francisco may contain more addressable accounts than an entire state in the Midwest. A geographic split that looks balanced on a map can be wildly unbalanced in terms of actual revenue potential.
Geography is a convenient proxy. It is rarely an accurate one. Companies that rely on pure geographic territories end up with reps who are drowning in opportunity next to reps who are starving, and both of them technically have “balanced” territories.
How Bad Territories Create Downstream Chaos
The consequences of poor territory design don’t stay contained within the sales org. They cascade through the entire revenue system.
Forecast volatility. When territories have uneven potential, pipeline generation becomes inconsistent. Some reps overproduce. Others underperform regardless of effort. The forecast starts swinging because the underlying distribution of opportunity is uneven, not because reps are bad at calling their deals. You can invest in the best forecasting methodology available and it won’t fix a signal problem at the source.
Compensation disputes. Misaligned territories create perceived and real unfairness in compensation outcomes. When one rep hits 140% of quota because they inherited a dense territory and another hits 60% working just as hard in a thin one, you get disputes. You get attrition. You get a cultural narrative that success at this company is about luck, not performance. Incentive structures shape behaviour, but they only work when the underlying opportunity distribution is fair.
Coverage gaps. Bad territory design leaves parts of the market unworked. Accounts fall into cracks between territories. Segments that don’t fit neatly into the existing model get deprioritised. Entire verticals go unaddressed because no rep has clear ownership.
Pipeline quality erosion. When a rep’s territory doesn’t contain enough high-quality accounts, they start working lower-fit prospects. Deal sizes shrink. Win rates drop. Sales cycles lengthen. The pipeline looks full, but conversion rates tell a different story. This is not a coaching problem or a process problem. It’s a territory problem.
Capacity planning breaks. If territories aren’t designed around actual market potential, you can’t accurately plan headcount. You end up hiring into territories that are already saturated while leaving high-potential segments understaffed. The cost of this misallocation compounds quarter over quarter.
Every one of these downstream problems gets treated as its own issue. Forecast accuracy becomes a forecasting methodology project. Comp disputes become an HR conversation. Coverage gaps become a marketing problem. But the root cause is the same: the territory model is architecturally flawed.
What Good Territory Architecture Actually Looks Like
Good territory design starts with the market, not with the current org chart.
Segment-based, not geography-based. Territories should be defined by the characteristics that actually predict buying behaviour: industry vertical, company size, technology stack, growth stage, use case. Geography can be a secondary layer, but it should never be the primary organising principle for a B2B SaaS company.
Potential-weighted, not account-count-balanced. A territory with 200 accounts that have a combined addressable value of $500K is not equivalent to a territory with 200 accounts worth $5M. Good territory design weights by revenue potential, not by raw account count. This requires investing in data enrichment and scoring, which most companies skip because it takes effort.
Governed, not inherited. Territory models should have explicit rules, documented logic, and a regular review cadence. When the assumptions behind a territory change, the territory should change with them. This is not about constant disruption. It’s about treating territories as living architecture rather than fixed infrastructure.
Aligned to capacity. Each territory should be workable by the rep assigned to it. If a territory contains 500 accounts but a rep can meaningfully engage 80 in a quarter, you don’t have a territory, you have a wish list. Territory design must account for realistic rep capacity, which means understanding sales cycle length, deal complexity, and required touch frequency.
Connected to the operating model. Territories don’t exist in isolation. They interact with lead routing logic, marketing campaign targeting, SDR assignment, customer success handoffs, and expansion motions. A territory model that works for the sales team but breaks marketing attribution or creates handoff confusion has not solved the problem. It has moved it.
RevOps Owns Territory Governance. Full Stop.
Territory design is too consequential to be owned by any single functional leader. Sales leadership will optimise for their team. Marketing will optimise for campaign efficiency. CS will optimise for book of business logic. Each perspective is valid. None of them is complete.
RevOps is the only function positioned to design territory architecture that serves the entire revenue system, not just one part of it.
This means RevOps needs to own the territory model, the data that informs it, the rules that govern it, and the cadence at which it’s reviewed. Not as an advisory function. Not as the team that builds the spreadsheet someone else designs. As the architectural authority.
In practice, territory governance through revenue architecture means several things.
Maintaining a scoring model that quantifies account potential using firmographic, technographic, and behavioural data. Running regular territory health checks that identify imbalances before they show up in pipeline or forecast variance. Establishing clear rules for territory changes, including triggers, approval processes, and transition protocols. Ensuring territory logic is reflected consistently in CRM assignment rules, routing logic, and reporting structures. And providing operational design that connects territory architecture to the broader GTM system.
This is not glamorous work. It requires data infrastructure, cross-functional alignment, and the willingness to make decisions that some stakeholders won’t like. But it is some of the highest-leverage work a RevOps function can do.
Stop Treating Territories Like an Annual Chore
The companies that get territory design right share a common trait: they treat it as architecture.
They invest in data before making decisions. They model scenarios before committing to a structure. They build governance mechanisms that allow the model to evolve without creating chaos. They connect territory logic to every other system it touches, from lead routing to compensation to capacity planning.
The companies that get it wrong share a common trait too: they treat territories as a box to tick during annual planning. A spreadsheet exercise that needs to be finished so they can move on to quota setting.
Territory design is not something you do before the real work starts. It is the real work. Every pipeline metric, every forecast, every compensation outcome, every coverage decision flows from the territory model. If that model is flawed, everything built on top of it is compromised.
The next time someone asks you to “just clean up the territories,” recognise the question for what it really is. They’re asking you to redesign the foundation of the revenue system.
Treat it accordingly.