Territory Management
Define and manage sales territories by geography, industry, company size, or custom criteria for balanced coverage.
Overview
Territory Management in SalesOS provides a structured framework for dividing your total addressable market into manageable segments, assigning ownership to sales representatives, and ensuring balanced coverage across all opportunities. Well-designed territories eliminate coverage gaps, reduce rep conflicts, and create equitable quota distribution that drives predictable revenue.
Whether your organization sells regionally, by vertical, by account size, or through a combination of dimensions, SalesOS territories adapt to your go-to-market model with flexible rules, hierarchies, and automation.
Territory Types
SalesOS supports five territory models that can be used independently or combined into hybrid structures.
Geographic Territories
Geographic territories divide your market by physical location. SalesOS supports multiple geographic granularities:
| Level | Examples | Best For |
|---|---|---|
| Country | United States, Germany, Japan | Global enterprise teams |
| Region | EMEA, APAC, Americas | International mid-market |
| State/Province | California, Ontario, Bavaria | National field sales |
| Metro/City | San Francisco Bay Area, Greater London | Inside sales, SMB |
| Postal Code | 94105, SW1A 1AA | High-density urban markets |
Named Account Territories
Named account territories assign specific high-value accounts to designated reps regardless of geography or industry. This model is common for strategic and enterprise sellers who manage a defined book of business.
Industry Territories
Industry-based territories segment accounts by vertical market. SalesOS uses standard industry classifications (SIC, NAICS) and supports custom industry taxonomies unique to your business.
Company Size Territories
Size-based territories segment by employee count, annual revenue, or a composite scoring model. Common tiers include SMB, Mid-Market, and Enterprise, though SalesOS allows unlimited custom bands.
Hybrid Territories
Hybrid territories combine multiple dimensions. For example, a rep might own "Healthcare accounts with 500+ employees in the Northeastern United States." SalesOS evaluates hybrid rules in priority order and resolves conflicts through configurable precedence logic.
Creating Territories
To create a new territory:
- Navigate to Settings > Territories > Create Territory.
- Assign a name and optional description.
- Select the territory type (geographic, named account, industry, size, or hybrid).
- Define the boundary criteria using the rule builder.
- Set the parent territory if this is a child in a hierarchy.
- Assign one or more reps (primary and overlay).
- Save and activate.
Territory Rule Builder
The rule builder uses a visual interface with condition groups:
- Single conditions: Country equals "United States"
- Compound conditions: Industry equals "Healthcare" AND Revenue greater than $10M
- Nested groups: (State in ["CA", "OR", "WA"]) OR (Metro equals "Denver")
Rules evaluate against account and lead records in real time, automatically routing new records to the correct territory.
Territory Hierarchy
SalesOS supports multi-level territory hierarchies that mirror your organizational structure:
Hierarchies enable roll-up reporting, cascading rule inheritance, and management visibility at each level. A territory can have exactly one parent but unlimited children.
Hierarchy Permissions
| Role | Visibility | Actions |
|---|---|---|
| Rep | Own territory only | View accounts, log activities |
| Manager | Own + direct reports' territories | Reassign within team, adjust rules |
| Director | Full region hierarchy | Create/delete territories, bulk reassign |
| Admin | All territories globally | Full configuration, hierarchy restructuring |
Assigning Representatives
Each territory supports multiple assignment slots:
- Primary Owner: The rep with full quota responsibility for the territory.
- Overlay: Specialists (e.g., solution engineers, product specialists) who support but do not own quota.
- Backup: Designated rep who covers during PTO or transitions.
Assignment Methods
- Manual Assignment: Admins directly assign reps to territories from the territory detail page.
- Bulk Assignment: Upload a CSV mapping reps to territory codes.
- Round-Robin: SalesOS auto-assigns new territories to reps in rotation based on current load.
- Capacity-Based: Assignment considers each rep's existing account count, deal volume, or weighted pipeline value.
Territory Rules and Auto-Assignment
Territory rules determine how new leads and accounts are automatically routed to the correct territory and assigned to the owning rep.
Rule Evaluation Order
- Named account lists are checked first (highest priority).
- Hybrid rules are evaluated in configured priority order.
- Single-dimension rules (geo, industry, size) are evaluated last.
- If no rule matches, the record enters the unassigned queue for manual routing.
Conflict Resolution
When a record matches multiple territories, SalesOS resolves conflicts using:
- Priority ranking: Each territory has a numeric priority; highest wins.
- Specificity: More specific rules (postal code) override broader rules (country).
- Manual override: Admins can lock specific accounts to a territory regardless of rules.
- Split credit: For overlay models, both territories can receive credit with configurable split percentages.
Balancing Territories
Balanced territories ensure equitable distribution of opportunity and workload across your team.
Quota Distribution
SalesOS provides territory-level quota planning tools:
| Metric | Description |
|---|---|
| Total Addressable Market | Estimated revenue potential within territory boundaries |
| Historical Performance | Past quota attainment for the territory |
| Account Density | Number of qualified accounts per territory |
| Pipeline Coverage | Current pipeline relative to quota target |
| Rep Capacity | Factored by experience level, ramp status, and role |
Capacity Planning
The capacity planner visualizes workload distribution across territories and flags imbalances:
- Overloaded territories: Account count or pipeline value exceeds recommended thresholds.
- Underserved territories: Coverage gaps where accounts lack assigned ownership.
- Ramp adjustments: Territories assigned to new hires automatically receive reduced quotas during ramp period.
Rebalancing Suggestions
SalesOS analyzes territory composition quarterly and suggests rebalancing actions:
- Moving specific accounts between adjacent territories.
- Splitting high-density territories into sub-territories.
- Merging underperforming territories to improve efficiency.
- Adjusting boundaries based on market shifts or headcount changes.
Reassignment Workflows
Territory changes require careful orchestration to maintain deal continuity and customer relationships.
Reassignment Process
- Initiation: Admin or manager proposes a territory change.
- Impact Analysis: SalesOS calculates affected accounts, open deals, and pending activities.
- Approval: Configurable approval chain (e.g., both outgoing and incoming managers must approve).
- Transition Period: Optional overlap window where both reps have visibility.
- Execution: Ownership transfers on the scheduled effective date.
- Notification: Automated emails to affected reps, managers, and optionally customers.
Handling Open Deals
During reassignment, open deals can be handled via configurable policies:
- Follow the rep: Deals stay with the original rep regardless of territory change.
- Follow the territory: Deals transfer to the new territory owner.
- Stage-based: Deals past a certain stage stay with the original rep; earlier-stage deals transfer.
- Manual decision: Each deal is individually assigned during the transition.
Analytics and Reporting
Coverage Analysis
The Territory Coverage dashboard shows:
- Accounts with no territory assignment (orphaned).
- Territories with no assigned rep (vacant).
- Accounts matched to multiple territories (conflicts).
- Geographic areas with no territory definition (white space).
Performance by Territory
| Metric | Description |
|---|---|
| Quota Attainment | Percentage of quota achieved per territory |
| Win Rate | Close rate for deals within the territory |
| Average Deal Size | Mean contract value by territory |
| Sales Cycle | Average days from opportunity creation to close |
| Pipeline Velocity | Speed at which pipeline converts to revenue |
| Activity Density | Calls, emails, and meetings per account |
Comparative Analytics
Compare territories side-by-side to identify coaching opportunities, resource allocation needs, and model optimization. Filters allow comparison by time period, territory type, and hierarchy level.
Map Visualization
SalesOS includes an interactive map view for geographic territories:
- Heat maps: Color-coded by revenue, account density, or quota attainment.
- Boundary overlays: Visual territory boundaries with drag-to-adjust capability.
- Pin markers: Individual accounts plotted by headquarters location.
- Clustering: Automatic grouping of dense account clusters at zoom levels.
- Rep location: Optional real-time rep location for field sales teams.
- White space identification: Highlighted areas with potential accounts but no coverage.
The map supports filtering by territory hierarchy level, rep assignment status, and account attributes.
Fiscal Period Planning
Territory planning typically aligns with fiscal year cycles. SalesOS supports:
Annual Planning Workflow
- Data Preparation (6-8 weeks before fiscal year): Export current territory data, account assignments, and performance metrics.
- Modeling (4-6 weeks before): Use the territory simulator to test alternative configurations without affecting live assignments.
- Review and Approval (2-4 weeks before): Share proposed territories with leadership for sign-off.
- Staging (1-2 weeks before): Lock new territory definitions in staging mode; they remain invisible to reps until activation.
- Activation (fiscal year start): One-click activation applies all changes simultaneously on the effective date.
Mid-Year Adjustments
SalesOS tracks mid-year territory changes separately from annual plans, maintaining historical records for accurate year-over-year comparison. Common mid-year triggers include:
- New hire onboarding (carving a new territory).
- Rep departure (merging or reassigning).
- Acquisition or expansion into new markets.
- Product launches requiring specialist territories.
Integration with Other Modules
Territory data flows into multiple SalesOS modules:
- Lead Routing: New leads are auto-assigned based on territory rules.
- Forecasting: Roll-up forecasts aggregate by territory hierarchy.
- Compensation: Territory ownership drives commission crediting.
- Reporting: All reports can be filtered or grouped by territory.
- Coaching: Territory performance informs coaching priorities.
Best Practices
-
Start simple and iterate. Begin with a single territory dimension (usually geography) and layer additional complexity only when your data supports it. Over-engineered territories create maintenance burden without proportional benefit.
-
Review territories quarterly. Markets shift, teams grow, and product lines expand. A quarterly review cadence ensures territories remain balanced and aligned with current go-to-market strategy.
-
Use data to drive decisions. Rely on account density, revenue potential, and historical performance data rather than gut instinct when drawing boundaries. SalesOS provides TAM estimates and balance scores to guide objective decision-making.
-
Document territory rules clearly. Every territory should have explicit, unambiguous rules that any team member can understand. Avoid rules that require institutional knowledge to interpret.
-
Plan for transitions. Always define a transition policy before making changes. Reps need clarity on what happens to their open deals, and customers need continuity in their relationships.
-
Align territories with your sales motion. Inside sales teams benefit from high-volume, smaller territories. Enterprise field teams need fewer, larger territories with deeper account relationships. Match territory design to how your reps actually sell.
-
Monitor white space continuously. Unassigned accounts represent missed revenue. Set up automated alerts when new accounts enter your CRM without territory assignment.
-
Separate territory design from rep assignment. Design territories based on market structure, then assign reps based on capacity and expertise. This separation makes it easier to handle personnel changes without redesigning the entire map.
-
Leverage the hierarchy for reporting. A well-structured hierarchy enables managers to view performance at their level while rolling up cleanly to executive dashboards.
-
Communicate changes proactively. Territory changes affect compensation, relationships, and daily workflow. Announce changes with adequate lead time and provide context on the rationale behind adjustments.