Territory Realignment Modeling After a Sales Team Restructuring
I run sales operations for a company that went through a full sales team restructuring last year, splitting a single generalist sales org into segmented teams by account size, and rebuilding the territory model from that reorg taught me things about territory design that no planning spreadsheet template ever warned me about.
The Old Territories Were Never Actually Balanced
Before the restructuring, our territories were geographic, drawn years earlier and adjusted piecemeal every time someone left or a new rep got hired. When I pulled the actual account data to start the realignment, I found some reps carrying territories with three times the total addressable revenue potential of others, not because anyone planned it that way, but because the geographic boundaries had never been revisited against how the market had actually grown. One rep in a fast-growing metro area was sitting on a territory that had organically tripled in potential, while a rep in a flatter region was working just as hard for a fraction of the opportunity.
This became the first real lesson of the project. You cannot model a fair realignment on top of an unfair baseline and expect the math to fix itself. I had to throw out the assumption that the old territory boundaries represented any kind of equilibrium and start from raw account potential instead.
Segmenting by Account Potential Before Geography
The new model needed to reflect the segmented team structure, enterprise, mid-market, and a new SMB team, each with different account ownership logic. I built the potential model first, independent of geography or headcount, scoring every account on firmographic signals, current spend where we had it, and estimated total addressable spend based on company size and industry. Only after that scoring existed did I layer geography and team assignment on top of it.
Doing it in this order mattered because it separated two questions that are easy to accidentally conflate: how much opportunity exists in an account, and who should own it. Skipping straight to territory boundaries without first establishing potential led to an early draft that looked reasonable on a map but was wildly unbalanced in actual revenue potential once we checked the numbers, because visually equal geographic slices rarely translate to equal opportunity.
Rep Capacity Assumptions Need to Be Honest, Not Aspirational
Every territory model needs an assumption about how many accounts or how much total potential a single rep can effectively cover, and I initially used our sales leadership's stated target capacity, which turned out to be more aspirational than realistic based on what reps were actually managing to do with their current workload. I pulled twelve months of actual activity data, calls, meetings, proposals, and cross-referenced it against close rates by account tier, and found that reps working the highest potential accounts were maxing out well below the theoretical capacity leadership had been using in planning.
I rebuilt the capacity assumptions using observed performance rather than target performance, which produced a model calling for more headcount than leadership had originally budgeted for. That was an uncomfortable conversation, but presenting it with the actual activity data behind it made the case far more persuasive than a generic industry benchmark would have, because it was our own team's real behavior, not an assumption borrowed from a consulting deck.
Transition Rules Matter as Much as the End State
Designing the ideal future-state territory map turned out to be only half the project. The other half was figuring out how to move from the old territories to the new ones without destroying in-flight relationships and pipeline. We had deals in active negotiation that would have crossed territory boundaries under the new model, and a rigid cutover would have handed a rep's nearly-closed deal to someone else with zero context, right at the worst possible moment in the sales cycle.
I built explicit transition rules into the rollout: any opportunity above a certain pipeline stage stayed with its original owner through close, regardless of which territory it fell into under the new map, with a defined sunset date after which unclosed deals would transfer regardless. This protected momentum on live deals while still moving the whole org onto the new structure within a defined window, rather than letting exceptions drag on indefinitely.
Compensation Implications Have to Be Modeled in Parallel
A territory realignment that isn't paired with compensation plan review creates a mismatch almost immediately, since moving accounts between reps changes each person's realistic earning potential even if the comp plan structure itself doesn't change. I worked closely with our compensation team throughout the modeling process rather than handing them a finished territory map at the end, because a rep who loses their best account in a realignment needs to see, concretely, what their new territory's earning potential looks like, or the realignment reads as a demotion regardless of how sound the underlying logic was.
We built individualized territory potential summaries for every rep as part of the rollout communication, showing the account list, the estimated potential, and how it compared to their prior territory. This transparency reduced pushback significantly compared to an earlier internal pilot where we'd rolled out a smaller realignment with just a list of accounts and no context, which generated a wave of anxious questions we could have avoided by leading with the data.
Ongoing Rebalancing Beats a One-Time Fix
The old territory model failed partly because it was treated as a set-once decision rather than something that needed periodic revisiting. I built a lighter-weight quarterly rebalancing review into our new process, not a full realignment, but a check against account potential drift, new account creation, and win rate patterns that might signal an emerging imbalance before it becomes as severe as what we inherited. This is a much smaller, less disruptive process than the full restructuring, and the goal is specifically to avoid ever needing another full realignment project like the one we just went through.
What I'd Tell Someone Starting This Kind of Project
Don't trust your existing territory boundaries as a fair starting point, verify potential independently first. Separate account potential scoring from territory assignment as two distinct modeling steps. Use observed rep capacity data instead of aspirational targets, even when the resulting headcount ask is uncomfortable. Build explicit transition rules for in-flight deals before you announce anything. And loop in compensation planning throughout the process, not after the territory map is finalized, because the map and the plan have to make sense together for reps to actually trust the outcome.
