Sales territory design: principles, steps and examples

Quick answer

To design sales territories:

1. Pick a coverage model: geographic, named accounts, industry, or a hybrid.
2. Choose a building block: ZIP codes, counties, states or custom-drawn areas.
3. Choose a balance measure: account count, revenue potential or workload.
4. Draw a first design around your accounts and reps' home bases.
5. Test it against shape rules: compact, contiguous, sensible borders.
6. Rebalance and document exceptions before rollout.

Territory design, planning and alignment

These terms overlap, and teams use them loosely. A useful distinction:

Decision 1: Choose a coverage model

Even named-account and industry teams benefit from a map: it shows travel load, clusters worth a visit trip, and accounts nobody owns. A map is essential for geographic and hybrid models.

Decision 2: Choose the geographic building block

Pick the smallest block your systems can handle. Finer blocks make balancing easier, because you can move a ZIP code instead of a whole county.

Decision 3: Choose how you'll measure balance

Territories should offer similar opportunity and a workload one person can cover, not identical account counts. Most teams balance on revenue potential or workload and use account count and travel as checks. Whatever you choose must be a column in your account list so the map can total it. The territory balancing guide explains each measure and how to set a tolerance band, such as every territory within 15% of the average.

Decision 4: Apply shape rules

• Contiguous: one connected piece. Detached islands are tolerable only for named-account exceptions.
• Compact: roughly round or square rather than long and thin, so drive times stay short.
• Anchored: the rep's home base or office sits near the middle.
• Sensible borders: follow highways, rivers and mountain ranges that affect travel, rather than cutting across them.
• Whole markets: avoid splitting a small city or a single large customer's campus between reps.

Decision 5: Decide how to handle exceptions

Write the rules down before drawing, or every edge case becomes a negotiation:

• Named and house accounts that stay with a specific rep regardless of location.
• Overlaps: whether shared coverage is allowed, and who owns the account when it is.
• Multi-location customers: owned by headquarters location, or by each site.
• Unassigned areas: covered by inside sales, a partner, or nobody yet.
• Account continuity: when an account moves territories, whether the relationship moves with it.

Step by step: design territories on a map

1. Map accounts and reps

   Import your account list into the map builder with latitude, longitude and your balance measure. Add rep home bases as a second point layer so you can see where each territory should center.

2. Draw or build a first design

   Draw one shape around the whole market and split it with Line cut so neighbors share borders exactly. If your building block is ZIP codes or counties, import those boundaries and merge them into territories instead.

3. Measure every territory

   In Analytics, choose your accounts under Dataset and your territories under Territories, then set the measure to the sum of potential or workload. Add a breakdown by segment to check the account mix.

4. Adjust the extremes

   Move the border between the heaviest territory and its lightest neighbor, one change at a time. Totals update after each edit.

5. Check shape and exceptions

   Look for stretched shapes, detached pieces, accounts in two territories and accounts in none. Fix them or record why they're intentional.

6. Document and share

   Export point membership so every account has a territory value for your CRM, and share the live map with reps and managers. See assigning accounts to territories.

Three territory design examples

These examples use illustrative numbers to show how the decisions above play out. Adapt the structure, not the figures.

Example 1: Four field reps, one state, county-based

A building-products distributor covers one state with four outside reps. Contracts and reporting are by county, so counties are the building block. The planner imports county boundaries, merges them into four territories around each rep's home city, and balances on annual potential.

The average is $4.0M per territory. Metro has the most accounts in the fewest counties because travel is short. Metro and South both sit outside a ±8% band, so the planner moves a suburban county worth about $0.4M from Metro to South, which brings both to roughly $4.0M.

Example 2: Metro and rural split

A medical-supply team has a dense metro area and a large rural region. Instead of equal areas, the design gives the metro two small territories with many accounts and the rural region one large territory with fewer, higher-value accounts. Workload, measured as visits per year times hours per visit, is the balance measure, so the rural rep's drive time counts.

Example 3: Hybrid with named accounts

A software company assigns its 25 largest customers to two key-account managers as named accounts, wherever they are. Everyone else is covered by five geographic territories built from ZIP codes. On the map, named accounts are a separate point layer, so they don't distort the geographic totals, and the planner checks that no geographic rep has more than their share of the remaining potential.

Common territory design mistakes

• Balancing on account count alone. A rep with 150 small accounts and a rep with 150 enterprise accounts don't have the same job.
• Designing around current reps' preferences. Design for the market first, then assign people.
• Ignoring travel. Equal potential is meaningless if one territory takes three hours to cross.
• Redesigning too often. Customers and reps lose relationships. Most teams realign yearly and make small mid-year fixes only for hires and departures.
• Leaving gaps. Every unassigned account is revenue nobody is chasing.

FAQ

Related guides