RevOps playbook · AI Employee: Rev

Territory & Account Reassignment

Reassignments done in one pass; comp impact clear

Install this playbookBack to marketplace
The problem

Territory rebalancing happens every fiscal year (and often more) — reps leave, join, get promoted, teams reorganize, ICP shifts. Manual reassignment is a spreadsheet marathon: figure out who has what accounts, what pipeline moves, how comp gets prorated, how quota rebases, how customer relationships continue. It takes weeks; some accounts drop; some reps lose earned commission; some customers realize their AE changed only when the new AE cold-calls.

At a glance
Trigger
Form + cron
Approvals
RevOps + manager approval
What it does
Writes to your systems
Systems
Salesforce · HubSpot · Comp system
How it feels in production

An hour-by-hour walkthrough.

Sales leader announces territory rebalance for FY27: enterprise segment split from mid-market, new AEs joining, ICP focus shifting. Rev coordinates the transition: Plan (2 weeks before effective): - Current-territory mapping: 340 accounts across 8 AEs (avg 42/AE) - New-territory design: 4 enterprise AEs + 6 mid-market AEs - Account-to-territory rules: enterprise = $50M+ revenue OR $250K+ existing ARR; mid-market = below thresholds - Proposed reassignment: 340 accounts → 10 AEs, avg 34/AE, balanced by pipeline + existing ARR - Rep-specific exceptions preserved (strategic-relationship holdouts) AE review (1 week before): - Each AE sees their proposed new book - Accounts leaving: pipeline handoff plan, active-deal transition, comp treatment (retain earned; new AE inherits future) - Accounts inbound: warm-intro from prior AE, prior context, current opportunity pipeline - Objections: escalate to sales leader for adjustments Effective date: - Reassignments execute in CRM + Outreach + comp system atomically - Customer notifications sent (from prior AE, cc new AE) for active-relationship accounts - Quota rebalanced per new territory - Comp system updated with new territory + prorated any earned commissions from transitioning deals Post-reassignment weekly review: transition health, dropped balls, comp disputes. Territory changes stop being year-long disruption.
How it works

Step by step.

  1. 01

    Plan the reassignment with clear rules

    Territory definition rules. Proposed account-to-AE mapping with pipeline + ARR balance. Exceptions preserved.

    Salesforce · HubSpot · Territory design tool
  2. 02

    AE review + adjust

    Each AE sees their proposed book, accounts leaving + arriving, transition + comp treatment. Objections routed to sales leader.

    Web UI · Slack · Sales-leader review
  3. 03

    Execute atomically on effective date

    Reassignments in CRM + cadence tools + comp system. Simultaneous cutover prevents ambiguity about ownership.

    Salesforce · Outreach · Xactly · Effective-date scheduler
  4. 04

    Customer + rep transition support

    Warm-intro email templates for active accounts. Prior-AE + new-AE briefing. Prior-context handoff.

    Email · Slack · Handoff docs
  5. 05

    Post-transition monitoring + comp resolution

    Weekly review of transition health. Dropped-ball detection (accounts with no touch 30d post-transition). Comp disputes routed to comp ops.

    Analytics · Slack digest · Comp ops queue
Systems and wiring

What you connect to make this run.

Salesforce · HubSpot · CRM

read+write

Account ownership + territory + rep-account relationships. Write reassignments effective-dated.

Outreach · Salesloft · Cadence

read+write

Cadence ownership + prospect assignment. Follows CRM reassignment atomically.

Xactly · CaptivateIQ · Spiff · Comp system

read+write

Territory + quota changes. Earned commissions retained; forward attribution to new territory.

Email · Slack · Handoff templates

read+write

Customer + rep coordination during transition. Warm intros + briefings.

What changes

Before and after, honestly.

Time from plan to full execution
Before
6-16 weeks
After
2-4 weeks
% of reassignments with complete handoff
Before
40-70%
After
95%+
Accounts dropped (no touch 30d post-transition)
Before
8-20%
After
Under 2%
Comp disputes from reassignment
Before
10-25 per rebalance
After
0-3 per rebalance
Related

Playbooks that pair with this one.

HR

Manager Change Cascade

Same cascade pattern for sales-org changes.

RevOps

Comp & Quota Q&A

Comp questions spike during / after reassignment.

RevOps

Closed-Won Cascade

In-flight deals need special handling during territory changes.

Frequently asked

Answers about this playbook.

How does it handle in-flight opportunities during reassignment?

Configurable per policy. Common: opportunities past Proposal stay with original AE for close; earlier stages transfer. Comp split reflects the transition.

What about customer objections to the AE change?

Customer-relationship exceptions supported. Sales leader can preserve strategic relationships past the general rules. Explicit override with reason.

How does it handle mid-quarter reassignments?

Prorated quota + comp. New AE gets prorated quota for remaining quarter; original AE keeps prorated. Prevents penalizing either.

Can we do partial reassignments (some accounts move, some don't)?

Yes — hybrid transitions supported. Some accounts move by rule; some preserved for strategic reasons; some moved specifically for rep capacity.

How does it interact with marketing account-based programs?

Marketing sees the new mapping same day. ABM campaigns re-target with new AE + territory context. Prevents customer confusion about who they hear from.

See it run on your data.

Free plan, no credit card. Connect the systems this playbook needs and run it against a past event first.

Book a demoMore RevOps playbooks