A territory plan is only useful if the system refuses to let two reps work the same account by accident. The goal is boring: every account has one owner, every rep has a book they can finish, and nobody is arguing about who gets credit.
Territory management is the practice of defining and governing which sales reps work which accounts, so coverage is fair, conflict is prevented, and every prospect has a clear owner. Territories can be carved by geography, industry, account size, named-account list, or a hybrid of those. A CRM enforces the model through assignment rules, routing, and access permissions so the plan on paper matches what reps actually see.
What a territory actually is, why every revenue team ends up building one, and the five models most companies pick from.
A sales territory is a bounded slice of the total market that a specific rep or team owns. Territory management is the governance around those slices: how they are drawn, how accounts are assigned, how conflicts get resolved, and how the lines are redrawn when the team or the market changes.
Without a territory model, high-value accounts get worked by three reps and the long tail gets ignored. With one, every account has a defined owner, every rep has a book they can realistically cover, and comp disputes have a defensible answer instead of a Slack argument.
Five patterns dominate: geography (ZIP codes, states, regions), industry or vertical (SaaS, manufacturing, healthcare), account size (SMB, mid-market, enterprise), named-account lists (specific logos per rep), and hybrid models that combine two or three of the above. Most mature teams end up on a hybrid.
A good carve starts from rep capacity (how many accounts one person can realistically touch per quarter), weighs each account by potential (revenue, fit, buying signals), and then balances the resulting books so no rep is set up to miss quota by geography alone.
Accounts change hands when a rep leaves, a region grows, a prospect becomes an enterprise logo, or an inactive account gets a new owner. Written reassignment rules (triggers, timing, pipeline carve-outs) prevent every change from becoming a three-way negotiation between the two reps and their manager.
The territory lives in the CRM as assignment rules, routing logic, and record-level permissions. If territory is managed in a spreadsheet that only RevOps updates, the plan on paper always drifts from what reps see in the pipeline. Enforcement in the system is what makes the model real.
There is no single right way to carve a market. The right model is a function of how customers buy, how the product sells, and how big the sales team is. Most companies cycle through two or three models before they land on one that fits, and most mature teams end up blending patterns rather than picking one.
The oldest pattern. A rep owns everything in a bounded geographic area. Works best for field-sales motions, outside sales, or products where in-person meetings matter. Weak when the buyer is remote and geography has nothing to do with how deals get worked, which is most SaaS.
Also called vertical territories. A rep owns every account in one or more industries, regardless of where they are. Lets reps build real domain expertise and speak the customer's language. The downside is uneven total addressable market by vertical, which has to be balanced in the carve.
A rep owns all accounts in a revenue or headcount band. Pairs with specialized motions: SMB on inbound and high-velocity, mid-market on blended, enterprise on named-account outbound. The challenge is defining where the bands start and stop, and what happens when an SMB account grows into mid-market.
Each rep is handed a specific list of 20 to 200 logos they own, built from strategic value rather than any formula. Common in enterprise and account-based motions. The strength is total clarity. The weakness is the list has to be curated and refreshed by someone who knows the business, which is a real workload.
The pattern most mature teams end up on. Enterprise is named-account, mid-market is split by vertical, SMB is round-robin by geography. Each segment uses the model that fits how it buys. The complexity goes up, which is why hybrid only works when the CRM can enforce it.
The anti-pattern teams fall back to when they cannot or will not carve a market. Every new lead goes to the next rep in line. Works at the earliest stage of a team, breaks the second one rep is better at a specific vertical, size, or geography than the others.
Carving a territory is not a one-afternoon spreadsheet exercise. The repeatable version is a sequence: measure what reps can cover, score what the accounts are worth, balance the resulting books, publish the rules, and schedule a review. Teams that skip any of the five steps usually find themselves re-carving mid-quarter.
Start with how many accounts one rep can realistically touch per quarter at the required depth. The number is almost always smaller than the manager thinks. Count meetings, follow-ups, prep time, and admin, then subtract vacation and ramp. The output is the account count per book.
Not every account is worth the same effort. Score each one on revenue potential, ICP fit, buying signals, and strategic value. The score drives who gets named-account treatment, who sits in a vertical book, and who ends up in the long-tail round-robin pool.
Each rep's book should sum to roughly the same total potential, with a similar mix of high-, medium-, and low-score accounts. Imbalanced books create disputes before quota is even set. The output is a draft map of accounts to reps that comp can be built against.
Reps need to know the carve rules, not only their current list. Document how new accounts get assigned, what counts as "working" an account, how long an account sits before it is reclaimable, and what happens when an account splits into two. Rules outlast lists.
Markets drift. Reps leave. New segments open. The carve should be revisited at a known cadence (annual with mid-year checkpoints is typical) rather than reactively. A scheduled review stops the plan from decaying into an argument every time a big account changes hands.
None of the above is real until it lives in the system reps actually use. Assignment rules, routing logic, permission scopes, and reports all need to reflect the carve. If reps are checking a spreadsheet to know who owns an account, the plan is already drifting.
Reassignment is where most territory plans fail. The carve looks clean on day one, then a rep quits, a prospect gets acquired, a named account goes cold for three quarters, and the manager starts making one-off calls that erode the whole system. Written reassignment rules keep the plan honest when reality moves.
When a rep leaves, their book, their open pipeline, and their accrued credit all have to be reassigned. The clean version splits these: the book goes to the territory's successor, open deals in late stage stay credited to the departing rep, and early-stage pipeline resets with the new owner.
Accounts a rep has not touched in a defined window (90 or 180 days is common) become reclaimable. The rule is time-based, not a manager's discretion, so the policy applies equally to everyone. Reps hoarding accounts they will not work loses to the written clock.
An account that was SMB when it was carved can grow (or shrink) into a different segment. The rule defines the trigger (headcount, revenue, product usage) and the hand-off: who owns the transition conversation, how pipeline credit splits, and when the new owner picks up the next renewal.
Named-account territories need a formal trade mechanism. Two reps can swap accounts with manager approval, but the trade is logged with date, old owner, new owner, and reason. The trade log prevents the slow drift of informal handoffs that nobody can reconstruct a year later.
The thorniest question in reassignment: a lead that was worked by rep A, handed to rep B after a reassignment, and closed by rep C. Written rules on splits (percentage by stage, time, or activity) remove the dispute. The CRM stores the activity history that the splits are calculated against.
Most teams freeze reassignment inside the final six to eight weeks of a quarter. Mid-quarter changes break forecasts, break comp, and create resentment. The freeze window is explicit, agreed in advance, and overridden only for rep departure or an executive escalation.
A territory plan written in a slide deck is a suggestion. A territory plan embedded in the CRM is a constraint. The system has to do three things: route every new record to the right owner the moment it lands, prevent reps from working accounts they do not own, and show leadership the coverage picture without a RevOps analyst rebuilding the view each week.
When a lead, account, or deal is created, the CRM applies the assignment rule and sets the owner automatically. Rules can read ZIP, country, industry, revenue, named-account list membership, or any combination. The record never sits unassigned, and nobody has to remember who covers what.
Territory tells you the pod. Routing tells you the rep inside the pod. The engine picks the next rep by round-robin, capacity, or workload, respecting out-of-office and skill tags. A new SMB lead in the Northeast goes to the next available Northeast SMB rep, not to a shared inbox.
Record-level permissions hide accounts a rep does not own from their default views. Reps still see counts and firmographics in rollups, so leadership can report on coverage, but working data (contacts, activity, notes) is scoped to the owner. Permission scope is what stops cross-territory poaching.
In Strkr, a named-account list is a tagged attribute on the account record, visible in reports and routable by assignment rules. Reps see "my named accounts" as a saved view. When a logo is added or removed from the list, the ownership follows automatically.
When a book changes hands, the CRM runs a reassignment flow: update owner on all matching accounts, hand open opportunities with configurable splits, notify the old and new owners, and write the change to an audit log. Not a spreadsheet exercise with a bulk-import at the end.
Dashboards show accounts per rep, pipeline per territory, dormant accounts, and segments with no owner at all. Leadership stops asking "do we cover Texas mid-market?" and starts seeing it answered on the same screen as the forecast. The reporting layer is what turns a plan into a system.
Strkr runs assignment rules, routing, named-account lists, and record-level permissions against the same accounts your pipeline is built on. The carve lives in the system, so reps see their book, leadership sees the coverage, and reassignment is a logged flow instead of a bulk-import exercise.
Territory management defines who owns which accounts. Lead routing is the real-time act of handing a new lead to a specific rep. The two work together: territory sets the pod a lead belongs to, routing picks the individual rep inside that pod. In most CRMs they share an engine, but the two concepts answer different questions.
Most teams run an annual re-carve with a mid-year checkpoint. More frequent changes break forecasts and erode trust. Less frequent changes let the plan drift out of alignment with the market. The written reassignment rules handle the between-review drift so the carve itself does not have to move every month.
A named-account territory is a hand-picked list of specific companies that one rep owns, regardless of geography, industry, or size. It is the dominant pattern in enterprise sales and account-based motions. The list is curated for strategic value, maintained by sales leadership or RevOps, and enforced through assignment rules in the CRM.
Both. Sales leadership owns the strategic choices (which segments to cover, how to split enterprise and SMB, which logos sit on named-account lists). Revenue operations owns the mechanical work (building the carve, balancing books, writing the assignment rules in the CRM, running the reports). The best plans come from the two groups iterating together, not from one handing a finished plan to the other.
Clean practice splits the question: late-stage open deals usually stay with the original rep through close, early-stage pipeline resets to the new owner, and credit is governed by a written policy that reads the deal's activity history. The CRM runs the owner change in bulk and logs it, so comp and forecasting can both reference the same source of truth.
Yes, if the assignment rules support compound conditions. Hybrid models mix dimensions (segment and vertical, geography and size, named-account and round-robin), which requires a rules engine that can read multiple fields on a record and route accordingly. Strkr's assignment rules support this pattern directly, so a hybrid carve lives in the system rather than a spreadsheet.
Leaving the plan in a spreadsheet instead of putting it into the CRM. The second a territory lives only in a document that RevOps maintains, every new record becomes a judgment call, every reassignment becomes an argument, and the lines drift from what reps actually see in their pipeline. Enforcement in the system is what makes the model real.
Comp plans are built against the carve. Quota is set per rep based on the potential of their book, accelerators are calibrated against expected book performance, and splits on reassigned deals pay out based on the written policy. A clean territory plan makes comp admin boring. A messy one turns every quarter-end into a reconciliation project.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
