The Do's and Don'ts of Sales Territory Planning

Sales territory planning works when you split the market by where revenue sits, encode the split in properties your CRM reports on, and review the model on a fixed cadence.

It fails when you split by headcount, store the territory somewhere unreportable, and leave the model untouched for a year. Below are the do's and don'ts, the HubSpot build behind each one, and the point at which a scaling team needs territories at all.

Most startup territory plans get built around the org chart instead of the data. You hire two more AEs, split the patch in half, and hope. Six months later one rep is drowning and the other has nothing to work, your pipeline reporting offers no explanation, and nobody trusts the numbers going to the board.

Territory planning at scale stage is a decision about who owns what, why, and whether your CRM proves the split is working. Get it wrong and you bake misallocation into your revenue engine. Get it right and you have a routing model that scales with every new hire.

Territory problems are rarely the first thing to break. They surface once the operational debt underneath has been building for a while. Click here to read more about why startups delay RevOps and what it costs them.

Here is what works and what does not.

The do's and don'ts at a glance

First, do you need territories yet?

Worth asking before you draw anything. A large share of the teams who raise territory planning with us do not have a coverage problem yet.

With three or four AEs running one motion, a rotation rule and a clean owner field does more for your numbers than any map. Territories earn their place at three specific triggers:

• Reps collide on the same accounts. Two people working one buying group is a coverage problem, and it shows up as awkward calls rather than in a report.
• You run more than one motion. Self-serve alongside enterprise, or inbound alongside outbound, needs different ownership rules.
• Someone needs to specialise. A vertical, a region with its own procurement norms, or a product line with a different buyer.

Until one of those bites, territory design adds governance you have no reason to maintain. If the coverage question feels premature, the gap costing you more is probably elsewhere in the funnel. Click here to read more about the 7 GTM process gaps hurting scaling tech companies.

Do: rank patches by revenue potential before you count heads

The instinct is to divide accounts evenly so everyone feels treated fairly. Even splits feel fair and produce uneven results. Accounts vary widely in value, and an equal share of accounts is rarely an equal share of opportunity. Zoltners and Lorimer's work on territory alignment put the cost of imbalance in the millions for large sales forces, and the mechanism is the same at twelve reps as at twelve hundred.

Start with where the revenue sits:

• Segment your base first. Pull closed won deals from the last 12 to 18 months and group by industry, company size and region. Patterns show up fast. In the portals we audit, two or three segments usually carry the bulk of revenue.
• Rank by TAM and customer value. Score each segment on addressable market and average deal value, then layer in retention or expansion data if you hold it. A segment with smaller deals and high expansion outranks one with big logos that churn.
• Pilot before you commit. Carve out a test patch, assign it, and run it for a quarter before rolling the model out. You learn which parts survive contact with a real quarter.

In HubSpot this lives on your deal and company records. Build a custom company property for segment tier, then a deal-based report grouped by that property and Deal stage to see win rate and average deal size per segment. That single report tells you where to point your reps.

Don't: design territories your CRM has no way to measure

A territory model your reporting has no way to measure is a model nobody reviews. If win rate, pipeline coverage and conversion by territory take more than two clicks, the review stops happening, and an unreviewed sales territory design drifts inside a quarter.

Before you allocate anything, make sure the data foundation holds:

• Set the properties first. You need a clean owner field, a territory or segment property, and consistent lifecycle stages. In the portals we audit, inconsistent lifecycle stage definitions are the most common reason pipeline reporting fails the board's first question. Resist the urge to add five properties where one dropdown does the work. Click here to read more about why the right CRM fields beat more fields.
• Fix routing at the point of entry. Lead routing in HubSpot runs on a workflow triggered by form submission or lifecycle stage change, using Rotate record to owner with branches on Country, Industry or Company size to match your territory rules. Manual assignment is where leakage starts. Note the tier requirement: Rotate record to owner needs Sales Hub Professional or Enterprise, or Service Hub Professional or Enterprise. On Starter you route with a static owner assignment per branch instead. Routing by territory sits on top of the same workflow carrying your marketing to sales handoff, so the two get built together. Click here to read more about the MQL to SQL handoff most HubSpot portals get wrong.
• Build the dashboard before you need it. Pipeline by owner, conversion by segment as a custom funnel report, and deal velocity. You spot a failing split in weeks rather than at the next QBR.

This is the part most engagements skip on the way to the interesting work. The data layer is what makes the strategy real.

Do: store territory where it reports

Territory management in HubSpot fails most often on storage rather than strategy. Someone types "UK North" into a free text contact property, three spellings appear within a month, and the report nobody trusts gets rebuilt by hand.

Three rules hold up:

• Territory belongs on the Company record. It describes an account, not a person. A single company property, dropdown select, with a closed list of values you own.
• Inherit it downward. Use a workflow with the Copy property value action to push the company's territory onto associated contacts and newly created deals, so reporting works on every object without anyone typing anything twice.
• Never let two systems write to it. If an enrichment tool or a Salesforce sync also populates territory, name one system of record and set the sync direction to match. Two writers on one field produces data everyone trusts and nobody should.

Free text costs you the reporting you built the property for.

Do: let CRM evidence shape the model

Most territory designs get built on what the founder believes about the market. The CRM usually tells a different story.

• Find the patterns in what already closed. Analyse won deals by geography, industry and company size. Your best-converting segment is rarely the one you assumed.
• Score lead quality by territory. Conversion from MQL to SQL to closed won varies widely across segments. A territory thick with leads nobody converts costs you a rep's quarter.
• Test the cut. Geographic and vertical splits produce different results depending on your product. Run both as a small test before committing the whole team to one model.

In HubSpot, a contact attribution report combined with Original source on the deal shows which territories produce qualified pipeline rather than volume. Volume flatters. Conversion tells the truth.

Don't: design the patch and ignore the rep working it

A territory is only as good as the rep working it. Building the perfect data-driven split and dropping an SMB-velocity rep into a complex enterprise patch wastes both.

• Match reps to territory type. Enterprise selling and SMB velocity are different skills. Align the patch to the rep's strength rather than their seniority.
• Set KPIs to territory maturity. A new territory and an established one should not carry the same target. Mature patches get conversion and expansion goals. New ones get coverage and activity goals.
• Review with the reps rather than at them. Your reps know where the model breaks before the dashboard does. Build a quarterly review where their input adjusts the plan.

Track this with a deal owner performance report segmented by territory tier, so you read rep performance in the context of the patch they were given rather than against a flat target.

Don't: re-cut without a plan for open deals

Here is the part that derails most re-alignments. The model is sound, the properties are clean, and then somebody asks what happens to the 40 open deals sitting with the wrong owner.

Handle it deliberately:

• Freeze open deals with their current owner. Deals past a qualification stage stay with the rep who opened them until close. Reassigning a live deal mid cycle loses the relationship and the context, and it teaches your team that ownership is arbitrary.
• Apply the new model to new records only. Change the routing workflow, leave history alone. Set a cut-over date and note it, so the reporting reads correctly either side of the line.
• Handle the exceptions by hand. Name them, list them, agree each one with both reps. A short list of deliberate exceptions beats a blanket rule nobody accepts.
• Protect the comp. A rep losing an account they sourced needs the commission position agreed before the announcement. Territory changes fail on compensation more often than on logic.

Log the change. HubSpot records deal owner history, so a report split by close date either side of your cut-over date tells you whether the new model performs.

The order that matters

Most teams run sales territory planning backwards: split the patch, then try to report on it. The sequence that holds up:

1. Segment your existing revenue to find where value sits.
2. Fix the data foundation. Properties, lifecycle stages, routing.
3. Design the model on CRM evidence rather than assumption.
4. Match reps to territories and set maturity-appropriate KPIs.
5. Agree the transition plan for open deals and the comp position.
6. Build the dashboard, then review it quarterly with the team.

Treat territory planning as an operating cadence. The teams getting compounding returns tune the model every quarter with data they trust. The quarterly review only holds if it sits inside an operating cadence the team already runs. Click here to read more about a RevOps framework that works for B2B SaaS.

Territory coverage feeds straight into the number you commit to the board, so the two reviews belong in the same meeting. Click here to read more about what good forecast accuracy looks like.

B2B sales territory planning stops being a spreadsheet exercise at the point your CRM proves which split works. If your pipeline reporting has no answer on which segments convert, start there, before you redraw a single line.

A RevOps Audit maps your current routing, data foundation and reporting gaps, then hands you a prioritised plan to fix them, quick wins first. You finish knowing which three fixes matter this quarter and which four wait.

If you would rather have senior RevOps support embedded in the team to build and tune the model with you, Fractional RevOps is the right-sized way to do it. Click here to read more about what to expect in your first 90 days with a fractional RevOps partner, including what gets diagnosed in the first thirty.

Book a RevOps Audit and get a clear view of where your coverage leaks, and the order to fix it.

FAQs