How does a Sales Operations manager build a territory plan for a growing sales team?

Building a territory plan for a growing sales team requires balancing data-driven market potential with rep capacity and fairness. A well-constructed plan ensures coverage without overwhelming reps or leaving prime accounts untouched.

Here is a step-by-step framework to build an effective territory plan:

1. Analyze and Clean Historical Data
   • Review past performance, win rates, deal sizes, sales cycles, and churned accounts to understand where revenue has historically come from and which segments are most profitable.
   • Audit your CRM data to ensure account records, firmographics (industry, employee size, revenue), and geographic locations are accurate and up-to-date.
2. Define Market Potential and Segmentation
   • Segment your Total Addressable Market (TAM) based on criteria like company size (SMB, Mid-Market, Enterprise), geography, or industry vertical.
   • Calculate the Serviceable Available Market (SAM) to determine the actual volume of accounts your growing team can realistically target and support.
3. Establish a Sizing and Capacity Model
   • Calculate rep capacity by analyzing how many accounts, pipeline opportunities, and active deals a single rep can successfully manage in a given period.
   • Factor in ramp-up time for new hires—newly added reps cannot handle a full quota or a massive territory immediately.
4. Design the Territory Boundaries and Rules
   • Draw the lines using geographic, vertical, or tier-based rules (e.g., Enterprise accounts based on revenue thresholds, or geographic regions split by postal codes/states).
   • Ensure equity (balanced workload and revenue potential) so no single rep feels overloaded while another is under-resourced.
5. Establish Rules of Engagement and Governance
   • Define clear account ownership rules, such as account-scoring thresholds, cross-territory collaboration guidelines, and rules for named accounts vs. inbound leads.
   • Create a transparent process for account rotation, carving out new territories as new reps are hired, and handling named account lists.
6. Align with Compensation and Quotas
   • Tie territory potential directly to quota capacity, ensuring that OTE (On-Target Earnings) and quotas are mathematically aligned with the realistic yield of each territory.
   • Build in buffer zones or adjustments for transitional phases as territories get sliced up to accommodate new team members.

Would you like to dive deeper into any of these areas, such as:

• Formulas and metrics for calculating sales capacity
• Best practices for splitting territories when scaling the team
• Rules of engagement templates for named accounts

Let me know how you'd like to proceed.

A Sales Operations manager should treat territory planning as a capacity-and-coverage problem, not simply drawing geographic boundaries. The goal is to give every rep a reasonable opportunity to hit quota while ensuring the company has enough coverage for its growth targets.

A practical 8-step process

1. Start with the business plan

Before touching account lists, define:

• Revenue/bookings target
• New-logo vs. expansion targets
• Target segments (SMB, mid-market, enterprise)
• Priority industries or markets
• Expected sales-team headcount by quarter
• Rep ramp time and productivity assumptions
• Average deal size, win rate, sales cycle, and pipeline requirements

For example:

We need $24M of new ARR next year, expect 12 productive AEs, and each fully ramped AE should carry roughly $2M of quota. This gives you the capacity requirement before you decide how accounts should be distributed.

Salesforce recommends planning for future hires rather than designing only for the reps who exist today; predetermined future territories can also reduce disruption when new reps join.

2. Build a clean account universe

Pull every addressable account into one dataset and make sure you have reliable fields such as:

• Geography
• Industry
• Employee count / revenue
• Current customer vs. prospect
• Existing ARR
• Historical spend
• Opportunity history
• Buying signals / intent
• Product fit
• Account tier
• Existing owner

Clean the data before using it for assignment. Territory rules shouldn't double as a data-cleaning mechanism.

3. Segment the market

Don't automatically use geography.

Depending on the business, territories might be based on:

• Geography + company size
• Industry
• Named strategic accounts
• Customer lifecycle
• Product specialization
• Account potential
• A hybrid of these

Salesforce, for example, describes segmentation around geography, company size, industry, and customer lifecycle.

A useful segmentation might look like:

4. Quantify territory potential, not just account count

This is one of the most important parts.

Giving Rep A 500 accounts and Rep B 500 accounts does not mean the territories are balanced.

Instead, assign each account a potential-value score.

For example:

Account potential = Revenue potential × fit score × propensity score

Or create a simpler weighted score:

• Enterprise account: +5
• High-growth industry: +3
• Strong product fit: +3
• Existing relationship: +2
• High intent: +2

Then compare the total opportunity available to each territory.

This is why a rep covering a dense urban market can have an economically equivalent territory to someone covering a much larger geographic area.

5. Design territories around rep capacity

Now answer:

"How much territory can one rep realistically work?"

Look at historical productivity:

• Accounts actively worked per rep
• Opportunities created
• Pipeline generated
• Meetings per month
• Travel requirements
• Average deal cycle
• Closed-won revenue
• Expansion workload

Then model capacity.

For example:

A fully ramped AE can effectively work 120 Tier-1/2 accounts and needs ~$6M of qualified pipeline to support a $2M quota. If a proposed territory contains $12M of realistic potential but requires twice the workload capacity of other territories, it isn't actually balanced.

6. Create multiple scenarios

Don't immediately publish the first design.

Build 2–4 scenarios:

Scenario A — Geographic

• East / Central / West

Scenario B — Segment-based

• Enterprise / Mid-market / SMB

Scenario C — Hybrid

• Enterprise by named accounts
• Mid-market by geography
• SMB pooled or inside-sales coverage

Scenario D — Growth model

• Current territories + prebuilt territories for future hires

Score each scenario on:

• Revenue potential per rep
• Quota attainment opportunity
• Account coverage
• Number of accounts
• Travel burden
• Existing customer disruption
• Ease of administration
• Hiring scalability

Territory-planning systems increasingly support exactly this type of optimization—balancing account value, geographic boundaries, business priorities, and staffing changes.

7. Establish explicit assignment rules

Your territory plan should eventually be executable as rules rather than living in someone's spreadsheet.

For example:

If Segment = Enterprise AND Region = Northeast → Enterprise Northeast If Named Account = Yes → Strategic Accounts If Segment = Mid-Market AND State ∈ {IL, IN, WI} → Central MM Otherwise → Unassigned / pooled queue Assignment criteria can use fields such as industry, annual revenue, employee count, geography, or other business-specific attributes.

Also define exceptions explicitly: named accounts, parent/child companies, channel accounts, house accounts, inbound leads, and accounts undergoing active negotiations.

8. Measure and rebalance

After launch, don't judge the plan solely by revenue.

Create a territory-health dashboard with:

• Quota attainment by territory
• Pipeline coverage
• Pipeline creation per rep
• Account penetration
• Revenue potential per rep
• Accounts per rep
• Unassigned accounts
• Rep capacity/utilization
• Win rate
• Sales cycle
• Ramp performance
• Territory changes

Then establish a governance cadence.

Quarterly: monitor health and identify problems. Semiannually: consider meaningful rebalancing. Annually: perform the major territory redesign.

You don't necessarily want constant changes: frequent reassignment creates disruption. Salesforce specifically recommends minimizing unnecessary changes while still adjusting territories when the existing model is no longer working.

The key SalesOps deliverable

I'd package the final territory plan into five artifacts:

1. Territory model — hierarchy and ownership
2. Account assignment file — every account → territory → rep
3. Capacity model — accounts, potential, quota, and workload per rep
4. Assignment rules — deterministic logic for new accounts/leads
5. Territory scorecard — metrics used to monitor and rebalance

The most important principle is:

Don't optimize for equal numbers of accounts. Optimize for equitable opportunity and manageable workload. That distinction becomes increasingly important as the team grows, because a territory model that works for 5 reps can become badly distorted at 20 or 50 reps. A scalable model should also anticipate hiring and allow new reps to inherit predefined territories rather than forcing SalesOps to redesign the entire organization every time headcount increases.

If you're building this in practice, a territory-planning spreadsheet/model with the exact tabs, formulas, scoring methodology, and example data is usually the best place to start.

• Current territories + prebuilt territories for future hires

Score each scenario on:

• Revenue potential per rep
• Quota attainment opportunity
• Account coverage
• Number of accounts
• Travel burden
• Existing customer disruption
• Ease of administration
• Hiring scalability

Territory-planning systems increasingly support exactly this type of optimization—balancing account value, geographic boundaries, business priorities, and staffing changes.

7. Establish explicit assignment rules

Your territory plan should eventually be executable as rules rather than living in someone's spreadsheet.

For example:

If Segment = Enterprise AND Region = Northeast → Enterprise Northeast If Named Account = Yes → Strategic Accounts If Segment = Mid-Market AND State ∈ {IL, IN, WI} → Central MM Otherwise → Unassigned / pooled queue Assignment criteria can use fields such as industry, annual revenue, employee count, geography, or other business-specific attributes.

Also define exceptions explicitly: named accounts, parent/child companies, channel accounts, house accounts, inbound leads, and accounts undergoing active negotiations.

8. Measure and rebalance

After launch, don't judge the plan solely by revenue.

Create a territory-health dashboard with:

Building a territory plan for a growing sales team requires balancing data-driven market potential with rep capacity and fairness. A well-constructed plan ensures coverage without overwhelming reps or leaving blind spots.

Here is a step-by-step framework to build an effective territory plan:

1. Analyze historical data and company performance

• Internal metrics: Review past win/loss rates, average deal size, sales cycles, and revenue per vertical or region using your CRM Analytics or equivalent reporting tools.
• Baseline establishment: Identify which geographic areas or customer segments historically yield the highest ROI to anchor your baseline expectations.

1. Define and segment the total addressable market (TAM)

• Market sizing: Use data providers like ZoomInfo or LinkedIn Sales Navigator to map out total accounts matching your Ideal Customer Profile (ICP).
• Segmentation logic: Divide the market by firmographics (company size, revenue), geography, industry verticals, or tiering (Enterprise vs. Mid-Market vs. SMB) to ensure equitable groupings.

1. Calculate sales capacity and headcount requirements

• Quota-to-capacity math: Determine your revenue targets and divide them by individual rep quota capacity (Target ÷ Quota = Required Headcount).
• Time allocation: Factor in ramp-up time for new hires, PTO, and non-selling administrative tasks so quotas reflect realistic execution windows.

1. Balance and align the territories

• Equitable distribution: Distribute accounts using a tiered workload model—ensuring each territory has a balanced mix of "active pipeline," "warm prospects," and "whitespace" (unpenetrated accounts).
• Avoiding friction: Minimize geographic overlap and account-assignment conflicts between inbound, outbound, and account management teams.

1. Establish governance and rules of engagement

• Account assignment rules: Clearly define rules for account ownership, tenure limits on unworked accounts, and rules of engagement for cross-territory enterprise deals.
• Feedback loops: Create a predictable cadence for mid-year or quarterly adjustments as the market shifts or headcount expands.

Would you like me to dive deeper into how to calculate rep capacity or provide a template for rules of engagement?

A strong territory plan is less about drawing geographic boundaries and more about balancing revenue opportunity, rep capacity, and coverage. For a growing sales team, Sales Operations should build the plan around data and design it so that new reps can slot into the model without repeatedly reshuffling existing accounts.

1. Start with the business objective

Before touching account lists, establish:

• Revenue target for the year/quarter
• New-logo vs. expansion targets
• Number of reps today and expected hiring
• Average quota per rep
• Expected ramp time for new hires
• Target segments, industries, products, and geographies
• Sales motion: field, inside, enterprise, channel, etc.

For example:

"We need $20M in new ARR next year, with 12 AEs today and 6 additional AEs expected by Q3." That immediately gives you a capacity problem to solve—not just a map to draw.

2. Build an account-level opportunity model

Create one dataset containing every addressable account and score each account based on factors such as:

Don't simply divide accounts by count. 1,000 small accounts can represent less opportunity than 50 enterprise accounts. Salesforce similarly recommends using data to make territories equitable rather than assuming equal geographic size or account counts mean equal opportunity.

A simple opportunity score might be:

Territory Opportunity = Σ(account potential × propensity-to-buy × strategic weight)

You can make the formula more sophisticated as your organization matures.

3. Decide what "territory" actually means

Not every sales organization should use geography.

Common models include:

• Geographic: Northeast, Southwest, UK, etc.
• Segment: SMB, Mid-Market, Enterprise
• Industry: Healthcare, Financial Services, Manufacturing
• Named accounts: Specific strategic accounts assigned to specific reps
• Hybrid: e.g., Enterprise Healthcare West
• Book-of-business: A defined collection of accounts regardless of geography

The sales motion should drive the model. A field team may benefit heavily from geographic boundaries, while an enterprise team may be better organized around named accounts or industry specialization.

4. Balance territories against rep capacity

This is the heart of the exercise.

For every proposed territory, calculate something like:

Capacity load = expected selling workload / rep capacity

Then compare:

• Pipeline potential
• Existing ARR
• Number of accounts
• Number of high-value accounts
• Historical bookings
• Expected pipeline generation
• Travel requirements
• Customer complexity
• Renewal/expansion workload

The goal isn't necessarily identical territories. It's roughly equivalent opportunity relative to quota and selling capacity.

For example:

That's much healthier than:

The first version gives each rep a reasonable chance of attaining quota; the second creates a structural performance problem.

5. Design for the team you will have—not just the team you have

This is particularly important for a growing company.

Suppose you have:

• 8 AEs today
• 12 expected next year
• 4 more planned after that

Don't create eight giant territories and figure out later how to split them. Design the 12–16 territory structure upfront, then temporarily leave some territories unassigned.

That lets a new AE inherit a predefined territory when they join instead of forcing Sales Ops to redesign everyone else's books. Salesforce specifically recommends planning for expected hiring and having future territories defined in advance to reduce disruption and ramp time.

6. Establish clear account-assignment rules

You want the CRM to answer:

"Who owns this account?" without a Sales Ops analyst manually deciding every time.

For example:

1. Strategic named accounts → Named Account territory
2. Enterprise healthcare → Enterprise Healthcare
3. Remaining enterprise accounts → geographic territory
4. SMB → pooled/inside-sales territory

Also define exceptions:

• Parent/subsidiary relationships
• Existing customer ownership
• Channel accounts
• Global accounts
• Duplicate accounts
• House accounts
• Inbound leads
• Accounts changing segments

Assignment logic should be deterministic and documented. Salesforce's current guidance also emphasizes keeping assignment rules focused on assignment rather than using them as a mechanism for cleaning bad CRM data.

7. Model several scenarios

Don't settle on the first reasonable-looking map.

I'd normally build at least three:

Scenario A — Minimum disruption Keep existing rep/account relationships wherever possible.

Scenario B — Maximum growth Optimize territories aggressively around future revenue opportunity.

Scenario C — Hiring plan Design specifically around the expected headcount and ramp schedule.

Then compare:

• Quota coverage
• Pipeline coverage
• Revenue potential
• Number of accounts
• Rep capacity
• Customer disruption
• Number of accounts changing owners
• Geographic/travel efficiency
• Hiring requirements

This turns territory planning into a business decision rather than a political negotiation.

8. Get Sales leadership and reps involved—but don't let anecdotes drive the model

A good process is:

Sales Ops → creates data-driven scenarios → Sales leadership reviews → frontline managers challenge assumptions → Sales Ops validates → leadership approves.

Rep feedback is extremely valuable because reps know things that CRM data may not capture—for example, a major account undergoing an acquisition or a region that's unusually difficult to penetrate.

But avoid:

"John says he needs California because he's been working it for three years." The response should be:

"Let's look at the revenue, pipeline, relationships, and strategic value associated with those accounts." Salesforce also recommends getting salespeople and leadership bought in before rolling out territory changes.

9. Lock the plan and define change rules

One of the biggest mistakes is changing territories constantly.

A rep can't effectively prospect if they don't know whether an account will still belong to them next month.

Establish rules such as:

• Annual territory redesign
• Quarterly review
• Mid-quarter changes only for defined exceptions
• New hires receive predefined territories
• Existing opportunities remain with the current owner
• Named-account changes require leadership approval

Salesforce notes that minimizing midyear changes reduces disruption, while still allowing adjustments when a territory is genuinely out of balance.

10. Measure whether the plan actually worked

After rollout, track territory health—not just overall sales performance.

I'd build a dashboard containing:

Coverage

• Accounts per rep
• TAM per territory
• % of TAM assigned
• White-space accounts

Opportunity

• Pipeline $
• Pipeline/account
• Pipeline/quota
• Win rate
• Average deal size

Capacity

• Quota per rep
• Attainment
• Ramp time
• Active opportunities per rep

Balance

• Opportunity/quota by territory
• Attainment distribution
• Pipeline distribution
• Top-account concentration

Change

• Accounts reassigned
• Open opportunities reassigned
• Customer ownership changes
• Territories above/below capacity

The key metric I'd watch is opportunity relative to quota, rather than simply the number of accounts assigned to each rep.

A practical Sales Ops workflow

You can turn the whole process into a repeatable operating cadence:

1. Define goals → Revenue, quota, segments, headcount

2. Clean the data → Accounts, ownership, geography, segment, potential

3. Score the accounts → TAM + propensity + strategic value

4. Define territory architecture → Geography / segment / industry / named account / hybrid

5. Calculate capacity → Opportunity and workload per rep

6. Build 2–3 scenarios → Compare quantitatively

7. Review with leadership + managers → Challenge assumptions

8. Finalize assignment rules → Make ownership deterministic

9. Publish + communicate → CRM, maps, quota, account lists, FAQs

10. Monitor quarterly → Identify under/over-covered territories

The mental model

Think of territory planning as an optimization problem:

Maximize revenue opportunity and coverage while keeping territories sufficiently balanced for reps to achieve quota and minimizing unnecessary disruption. That's the core job of Sales Operations. A good territory plan isn't the one with the prettiest map—it is the one where the right accounts are covered by the right reps, at the right capacity, with a structure that can absorb growth.

If you're building this for an actual sales org, I can also give you a territory-planning spreadsheet/template with the exact columns, scoring formulas, capacity model, and scenario analysis I'd use in Excel or Google Sheets.

A Sales Operations manager builds a territory plan by analyzing market potential, segmenting accounts based on data, and aligning rep capacity with revenue goals to ensure balanced, equitable workloads.

According to strategic guides from revenue operation platforms like Gong and Xactly , building a scalable territory plan requires a structured, multi-phase operational workflow.

1. Define the Ideal Customer Profile (ICP) and Market Potential

• Analyze historical data : Review CRM records to identify which customer segments yield the highest win rates, shortest sales cycles, and largest deal sizes.
• Map Total Addressable Market (TAM) : Use third-party data providers and firmographics to quantify the total number of target accounts available in your expansion regions.
• Segment accounts into tiers : Group accounts into Tier A (high-value, perfect ICP fit), Tier B (moderate potential) , and Tier C (low-fit/nurture) to prioritize rep focus.

2. Segment and Design Territories

• Move beyond geography : Structure territories using multi-dimensional criteria like company headcount, revenue, industry vertical, or technographic data rather than just zip codes or states.
• Balance workload capacity : Ensure the aggregate quota potential in each territory matches a representative's carrying capacity without overloading individual reps.
• Eliminate overlap : Define unambiguous boundary rules in your CRM to prevent internal channel conflict and account bickering.

3. Align Reps with Territory Needs

• Match skills to segments : Assign enterprise-level "hunters" to high-complexity Tier A accounts and account-manager personalities to high-volume, lower-touch SMB segments.
• Account for tenure and ramp time : Adjust capacity expectations for newly hired reps who are still ramping up compared to seasoned quota-bearers.

4. Establish Governance and Rules of Engagement

• Define rules of routing : Program explicit lead-to-account assignment rules inside your CRM automation layer.
• Build an exceptions process : Create a transparent, fast-response dispute resolution protocol for crossed wires or disputed account ownership.

5. Implement, Communicate, and Iterate

• Communicate change context : Share the data-driven "why" behind the new alignment with the sales team to secure buy-in before rollout.
• Build real-time dashboards : Set up BI and CRM tracking views to monitor territory-level quota attainment and pipeline generation.
• Treat it as a living plan : Review performance metrics quarterly rather than annually to rebalance coverage before gaps impact company revenue targets.

If you'd like, let me know:

• Your current team size and structure (e.g., SMB vs. Enterprise)
• The primary segmentation model you are currently using (geographic vs. vertical)

I can help you outline specific optimization metrics or design a custom tiering matrix for your accounts.

A Sales Operations manager should treat a territory plan as a capacity-and-revenue allocation problem, not simply a map-drawing exercise. The goal is to give each rep a reasonable opportunity to hit quota while ensuring the company has complete market coverage and can scale as headcount grows. Salesforce similarly recommends using data and company goals to create fair, balanced territories and revisiting them as conditions change.

1. Start with the business strategy

Before touching territories, define what the company is trying to accomplish.

For example:

• Grow ARR 30%
• Enter two new verticals
• Increase enterprise penetration
• Expand into a new geography
• Improve new-logo acquisition
• Grow existing-account revenue

Your territory design should follow those priorities. A geography-based model isn't necessarily appropriate if your sales motion is primarily vertical-, segment-, or account-based.

2. Build the market data set

Create one account-level dataset containing, at minimum:

Clean the data before using it to assign territories. Salesforce specifically recommends keeping data cleansing separate from territory-assignment logic.

3. Decide what makes a territory "balanced"

This is the most important step.

Don't define balance as "each rep gets 500 accounts." One rep's 500 accounts could be worth $2M while another's are worth $20M.

Instead, create a territory opportunity score.

For example:

Territory potential = 40% TAM + 25% historical revenue + 20% pipeline + 15% strategic-account value You can modify the weights based on your GTM strategy.

Then compare each proposed territory on:

• Revenue potential
• Number of accounts
• Number of high-value accounts
• Historical bookings
• Open pipeline
• New-logo potential
• Expected sales workload
• Geographic/travel burden
• Rep capacity

The objective is roughly:

Opportunity available ≈ quota × realistic attainment factor

So if an AE has a $1M quota, you generally don't want to give them a territory with only $1.1M of realistic opportunity and expect them to perform like someone with $4M of opportunity.

4. Calculate rep capacity

Next ask: How much territory can one rep actually cover?

For example:

• 1 AE can actively manage ~100 strategic accounts
• or ~300 commercial accounts
• or ~600 SMB accounts

Those numbers are illustrative; your historical productivity should determine them.

Also account for:

• Ramp time for new hires
• Existing customer management
• Travel
• Sales-cycle length
• SDR support
• Sales engineering requirements
• Manager span of control

This is where Sales Ops turns territory planning into headcount planning.

For example:

$50M addressable revenue ÷ $2.5M addressable revenue per AE = 20 AE capacity Then you can model what happens at 15, 20, or 25 reps rather than redesigning the organization reactively every time someone is hired.

5. Choose the territory model

Common models include:

Geographic

Example:

• Northeast
• Southeast
• Central
• West

Best when location and field coverage matter.

Segment-based

Example:

• SMB
• Mid-market
• Enterprise

Best when sales motions differ substantially by customer size.

Vertical-based

Example:

• Healthcare
• Financial services
• Manufacturing
• Technology

Useful when industry expertise materially improves conversion.

Named-account

Specific strategic accounts are assigned to specific reps regardless of geography.

This is common for enterprise sales.

Hybrid

Often the best model for a growing organization:

Region → Segment → Industry → Named accounts Salesforce notes that territories can be based on combinations of geography, company size, industry, product, and customer lifecycle rather than geography alone.

6. Build several scenarios

Don't immediately publish the first territory design.

Create 2–4 scenarios, such as:

Scenario A — Geographic

• Simple
• Easy to understand
• Good field coverage

Scenario B — Revenue balanced

• Equalizes opportunity more aggressively
• May create non-contiguous territories

Scenario C — Segment + geography

• More complex
• Better alignment with differentiated sales motions

Then compare:

The important thing is to make the tradeoffs visible to leadership.

Modern territory-planning approaches explicitly use scenarios and metrics to identify coverage gaps and distribute workload more fairly.

7. Assign reps to territories

Don't assume the best territory automatically goes to the best rep.

Consider:

• Rep experience
• Industry expertise
• Existing relationships
• Product knowledge
• Geographic location
• Historical performance
• Ramp status

A senior enterprise rep may be capable of handling a significantly more valuable or complex territory than a new hire. Salesforce likewise recommends considering experience, expertise, relationships, product knowledge, and location when matching people to territories.

8. Establish rules for edge cases

This is where many territory plans fall apart.

Document rules for:

• House accounts
• Strategic/named accounts
• Parent/subsidiary relationships
• Existing opportunities
• Account ownership changes
• Inbound leads
• Partner-sourced accounts
• New geographic markets
• M&A
• Reps joining/leaving
• Temporary coverage
• Account reassignment

For example:

"Existing open opportunities remain with the current AE through close; new opportunities generated after the effective date follow the new territory assignment." That single rule can prevent enormous internal conflict.

9. Stress-test the plan

Before launch, ask:

Coverage

• Is every target account assigned?
• Are there uncovered markets?
• Are there overlaps?

Fairness

• Is territory potential reasonably comparable?
• Does one rep have disproportionately many strategic accounts?
• Are quotas proportional to opportunity?

Capacity

• Can reps actually work the accounts assigned?
• Are managers overloaded?

Growth

• What happens when we hire 5 more reps?
• What happens when we enter a new vertical?
• What happens if a territory grows 50%?

Operationally

• Can the CRM assign accounts automatically?
• Can Finance calculate quota correctly?
• Can RevOps report performance by territory?
• Can leadership forecast by territory?

Territory hierarchies are particularly useful for reporting and forecasting, while assignment rules should be explicit rather than relying on assumptions about hierarchy inheritance.

10. Launch with a governance process

A good territory plan isn't a spreadsheet that gets updated once a year.

Set up:

• Annual: major territory redesign
• Quarterly: health check and capacity review
• Monthly: exceptions and staffing changes
• Ad hoc: major acquisitions, market changes, or organizational changes

Track:

• Quota attainment by territory
• Pipeline coverage
• Win rate
• Average deal size
• Sales cycle
• Revenue per rep
• TAM per rep
• Accounts per rep
• Territory penetration
• Rep productivity
• Territory changes/exception volume

Salesforce recommends regularly optimizing territories as staffing, goals, products, and market conditions change rather than treating the original design as permanent.

A practical Sales Ops framework

If I were building this from scratch, I'd structure the project as:

1. Strategy → What markets are we trying to win?

2. Data → What does the addressable market actually look like?

3. Capacity → How much opportunity can each rep realistically handle?

4. Segmentation → Which accounts belong together?

5. Territory design → How do we distribute that opportunity?

6. Rep assignment → Who is best suited to each territory?

7. Quota → Does quota reflect the opportunity assigned?

8. Rules → What happens when accounts, reps, or markets change?

9. Validation → Are territories fair, complete, and operationally workable?

10. Governance → How will we continuously rebalance them?

The key principle is don't optimize for equal territories; optimize for equitable opportunity. Two reps can have very different numbers of accounts or geographic footprints while still having roughly comparable chances of achieving quota. That is the real job of Sales Operations in territory planning.

Building a territory plan for a growing sales team requires a data-driven approach that balances market potential with rep capacity, ensuring equitable workloads and maximum revenue.

Here is a step-by-step framework for a Sales Operations manager to build an effective, scalable territory plan:

1. Analyze Historical Data and Market Potential
   • Data Audit : Review past performance, win rates, average deal size (ACV), sales cycles, and churn rates by region, industry, and company size.
   • TAM/SAM/SOM Slicing : Evaluate Total Addressable Market (TAM) using third-party data or internal CRM enrichment tools to see where the highest density of ideal customer profiles (ICPs) resides.
2. Segment and Categorize Accounts
   • Tiering Model : Group accounts into tiers (e.g., Tier 1 Enterprise, Tier 2 Mid-Market, Tier 3 SMB) based on revenue potential, employee count, or strategic value.
   • Account Scoring : Implement a predictive lead/account scoring model to dynamically flag high-propensity accounts.
3. Calculate Sales Capacity and Quota
   • Ramp-Up & Capacity : Determine the realistic capacity of your reps, factoring in onboarding time, ramp schedules, PTO, and non-selling administrative tasks.
   • Coverage Ratio : Aim for a total market quota coverage of 3× to 4× the team's cumulative quota target to account for pipeline erosion and lost deals.
4. Define Geographic, Vertical, or Named Account Boundaries
   • Balancing Strategy : Choose a structure—geographic (zip codes/states), vertical (industry/NAICS code), or enterprise named-account lists—that minimizes overlap and channel conflict.
   • Fairness Check : Ensure the "weight" of each territory is roughly equal in terms of pipeline potential, not just raw number of accounts.
5. Establish Rules of Engagement and Governance
   • Account Ownership Rules : Clearly define what happens when an account moves tiers, how inbound leads are routed, and how cross-territory collaboration (e.g., global enterprise deals) is credited.
   • SLA and Hygiene Standards : Set strict CRM data hygiene rules so reps keep account statuses updated, enabling seamless territory audits down the line.
6. Iterate and Optimize
   • Continuous Monitoring : Track leading indicators like pipeline generation, activity volume, and attainment velocity monthly rather than waiting for quarterly post-mortems.
   • Feedback Loop : Solicit feedback from Sales Directors and Account Executives to identify friction points or starved patches.

If you'd like to dive deeper, let me know:

• What industry or business model (SaaS, manufacturing, B2B services) you are planning for
• The current size of your sales team
• Whether you prefer a geographic or vertical-based split

I can help tailor the sizing formulas or tiering criteria to your specific situation.

A Sales Operations manager should treat territory planning as a capacity-and-revenue optimization problem, not simply as drawing geographic boundaries. The goal is to give each rep a realistic opportunity to hit quota while maximizing customer coverage and making the model scalable as the team grows.

A practical territory-planning framework

1. Start with the business strategy

Before touching account lists, clarify:

• Revenue and bookings targets
• Growth rate expected next year
• New markets or industries being prioritized
• Existing-customer expansion vs. net-new acquisition
• Sales motions: enterprise, mid-market, SMB, channel, etc.
• Planned headcount and hiring timing

A useful question is:

“If we achieve our company plan, what sales coverage will we need to support it?” Importantly, plan for future reps, not just today's headcount. A territory can temporarily carry extra accounts and then be split cleanly when a new rep joins.

2. Clean and segment the account universe

Build a single territory-planning dataset containing, at minimum:

• Account/company
• Geography
• Industry
• Employee/revenue band
• Current customer vs. prospect
• Current ARR/revenue
• Historical bookings
• Open pipeline
• Opportunity stage
• Buying propensity/intent, if available
• Parent/child account relationships
• Current owner
• Strategic-account designation

Then segment accounts according to how your sales team actually sells. Common dimensions are geography, company size, industry, and customer lifecycle.

3. Calculate territory potential

Don't balance territories based simply on number of accounts.

For example, suppose you have:

Territory C has the most accounts but may actually be the least valuable and easiest to overburden operationally.

Create a territory-potential score, for example:

Territory Potential = Existing Revenue + Weighted Pipeline + Estimated TAM

You can weight the components according to your business model.

4. Model rep capacity

This is where Sales Ops can add significant value.

Estimate how much work one rep can realistically handle:

Rep capacity = selling time × activities per account × account mix

For example, an enterprise AE might handle 40 strategic accounts, while a commercial AE might handle 150 smaller accounts.

Don't assume equal account counts = equal workloads. A territory with 50 complex enterprise accounts may require substantially more effort than one with 200 SMB accounts.

5. Design the territory structure

Choose the primary assignment logic:

• Geographic: state, country, ZIP/postal code, region
• Vertical: healthcare, financial services, manufacturing, etc.
• Company size: SMB, mid-market, enterprise
• Named accounts: strategically important customers assigned individually
• Hybrid: geography + segment + named accounts

For a growing organization, a hybrid model is often practical.

For example:

Americas → Enterprise → Healthcare → Northeast The structure should be predictable enough that Sales, Marketing, Finance, and Customer Success all understand who owns an account.

6. Balance opportunity—not just workload

A good territory model tries to give reps a reasonably equitable chance of achieving quota.

Compare each proposed territory on metrics such as:

• Revenue potential
• Historical bookings
• Pipeline
• Number of qualified accounts
• TAM
• Existing customers
• Average deal size
• Win rate
• Sales-cycle length
• Rep capacity

Salesforce similarly emphasizes using data to give reps an equitable opportunity to attain quota rather than simply dividing territories evenly.

7. Run scenarios before committing

Don't immediately publish the first model.

Create scenarios such as:

Scenario A — Current headcount 10 reps, current market coverage.

Scenario B — Planned growth 12 reps, with two new territories created.

Scenario C — Aggressive growth 15 reps, with smaller territories and additional specialization.

Then compare:

• Revenue potential per rep
• Quota-to-potential ratio
• Account coverage
• White-space coverage
• Rep workload
• Hiring requirements
• Number of accounts that change owners

This lets leadership make a deliberate tradeoff rather than discovering problems after territories are deployed. Territory-planning systems are designed around this type of modeling and comparison before assignments are activated.

8. Map quotas to territory potential

This is an important—and frequently mishandled—step.

Don't start with a quota and force territory potential to fit it.

Instead:

1. Estimate territory potential.
2. Estimate realistic capture/conversion.
3. Determine expected bookings.
4. Set quota based on the resulting opportunity.
5. Check whether the aggregate quotas support the company target.

For example:

$10M territory potential × 15% realistic capture = $1.5M expected bookings If the rep's quota is $3M, you may have created a territory that is structurally impossible to cover.

9. Define ownership and exception rules

Document things like:

• Who owns subsidiaries?
• Who owns global accounts?
• What happens when an account moves headquarters?
• How are inbound leads assigned?
• Who owns partners?
• What happens when a rep leaves?
• Can reps sell outside their territory?
• How are strategic accounts handled?
• What happens to open opportunities during a territory change?

This prevents the inevitable “But who owns this account?” firefights.

10. Build a governance cadence

Territories shouldn't change every time someone complains about an account.

A strong model might use:

• Annual: major territory redesign
• Quarterly: territory-health review
• Monthly: staffing, exceptions, and major coverage issues
• Ad hoc: defined triggers such as acquisition, major hiring, market entry, or significant territory imbalance

There's a useful balance here: frequent optimization is valuable, but unnecessary changes create disruption. Salesforce specifically recommends planning ahead and minimizing unnecessary territory churn.

The Sales Ops deliverable

I'd make the final territory plan a single operating document/dashboard containing:

1. Territory hierarchy Who reports to whom and which territories exist.

2. Account assignment file Account → Territory → Rep → Segment

3. Territory scorecard

4. Rules and exceptions Clear documentation of ownership logic.

5. Hiring plan Which territories split when reps #11, #12, #13, etc. join.

6. Health dashboard Track attainment, pipeline coverage, account penetration, capacity, and territory imbalance.

The core principle

Think of the territory plan as:

Company strategy → market segmentation → territory potential → rep capacity → territory design → quota → assignment rules → ongoing optimization

If you get those dependencies in the right order, the territory plan becomes a scalable operating system for the sales organization, rather than a spreadsheet exercise.

A Sales Operations (Sales Ops) manager builds a territory plan by turning the company’s growth strategy into a repeatable system for assigning markets, accounts, quotas, and sales resources. The goal is not just to divide accounts evenly—it is to create territories where each rep has a realistic opportunity to succeed while maximizing revenue coverage.

A practical process looks like this:

1. Start with the business strategy

Before drawing territories, align on:

• Revenue target and growth goals
• Sales motion (SMB, mid-market, enterprise, channel, field, inside sales)
• Priority industries or segments
• New logo vs. expansion focus
• Planned hiring and headcount growth

Example:

“We need to grow enterprise revenue by 40%, expand into healthcare, and hire 5 new AEs.” That strategy determines whether territories should be organized by geography, industry, account size, named accounts, or a hybrid model.

---

2. Define the Ideal Customer Profile (ICP)

Create a clear definition of accounts worth pursuing.

Typical attributes:

Then classify accounts:

• Tier 1: Strategic accounts with high revenue potential
• Tier 2: Strong-fit accounts with scalable opportunity
• Tier 3: Lower-touch or nurture accounts

This prevents territories from being built around arbitrary account counts.

---

3. Build a complete account universe

Pull data from:

• CRM
• Marketing automation
• Customer database
• Intent data providers
• Market research sources

Create a master account list containing:

• Account name
• Industry
• Location
• Employee count
• Revenue estimate
• Existing customer status
• Current opportunities
• Historical win rates
• Expansion potential

Clean the data first:

• Remove duplicates
• Resolve parent/subsidiary relationships
• Standardize industries and regions

---

4. Score accounts by opportunity

A common mistake is balancing territories by the number of accounts.

Instead, assign opportunity scores.

Example scoring model:

A territory with 50 excellent accounts may be more valuable than one with 300 weak accounts.

---

5. Model sales rep capacity

Territories must match what reps can realistically cover.

Consider:

• Number of accounts a rep can actively work
• Average sales cycle
• Required customer touches
• Travel requirements
• Ramp time for new hires
• Rep experience level

For example:

• Enterprise AE: 25–50 strategic accounts
• Mid-market AE: 50–150 accounts
• SMB AE: hundreds of accounts

The exact numbers depend on your selling motion.

---

6. Choose the territory model

Common models include:

Geographic territories

Example:

• East Coast
• West Coast
• EMEA

Best when:

• Travel matters
• Accounts cluster geographically

Industry vertical territories

Example:

• Healthcare
• Manufacturing
• Financial services

Best when:

• Buyers and sales motions differ by industry

Named-account territories

Example:

• Rep A owns Microsoft, Adobe, Oracle

Best when:

• Enterprise accounts require deep relationships

Hybrid model

Example:

• Enterprise accounts assigned by name
• Remaining accounts split by region or segment

Many growing B2B companies use hybrid models.

---

7. Balance territories

Evaluate each proposed territory against:

• Total addressable market (TAM)
• Pipeline potential
• Existing revenue
• Number of accounts
• Historical win rates
• Rep capacity
• Strategic importance

The objective is fair opportunity, not identical territories.

A good test:

“If two equally capable reps swapped territories, would both have a reasonable chance to hit quota?”

---

8. Align quotas and compensation

Territory design and quota setting should happen together.

For each territory define:

• Annual quota
• Pipeline coverage target
• Account targets
• Activity expectations
• Expansion goals

Example:

---

9. Create rules of engagement

Avoid ownership disputes by defining:

• Who owns inbound leads?
• Who owns subsidiaries?
• How are global accounts handled?
• What happens when a customer expands regions?
• How are channel partners involved?
• When can ownership change?

Document these rules in CRM.

---

10. Launch, measure, and rebalance

A territory plan is not a one-time spreadsheet.

Review:

Monthly

• Pipeline creation
• Coverage gaps
• Account engagement

Quarterly

• Territory health
• Rep capacity
• Hiring changes
• Market changes

Annually

• Full redesign

Track:

• Quota attainment by territory
• Pipeline coverage
• Win rate
• Sales cycle length
• Account penetration
• Revenue per rep

Frequent random changes can create confusion, so changes should be governed by clear triggers and communicated carefully.

---

A simple Sales Ops territory planning workflow

1. Export all accounts from CRM
2. Clean and enrich data
3. Define ICP and segmentation
4. Score account potential
5. Estimate rep capacity
6. Design territory scenarios
7. Review with Sales, Finance, and Marketing
8. Assign quotas
9. Load ownership rules into CRM
10. Monitor and adjust

A strong territory plan becomes the foundation for hiring plans, quota setting, pipeline expectations, and sales productivity—not just a map of who owns which accounts.

• Full redesign

Track:

• Quota attainment by territory
• Pipeline coverage
• Win rate
• Sales cycle length
• Account penetration
• Revenue per rep

Frequent random changes can create confusion, so changes should be governed by clear triggers and communicated carefully.

A Sales Operations manager builds a territory plan for a growing sales team by analyzing market data, balancing workloads, and aligning rep capacity with revenue targets.

For a comprehensive guide on building equitable and productive sales coverage, review the strategies outlined by Highspot's Sales Territory Management Guide and Fullcast's Territory Planning Framework.

Core Steps to Build a Territory Plan

If you'd like, I can:

• Break down how to calculate rep capacity
• Provide advice on geographic vs. vertical segmentation
• Share tips on managing rep pushback during territory rollouts