-
1
1. Diagnose why you are realigning
Before you touch a carve, write down the specific problem you are solving. Realignments typically trace to one of three drivers: growth (new segment, new product, new region, or a headcount expansion the current plan cannot absorb), underperformance (one or more territories missing number because the carve is wrong, not because the rep is), or churn and shift (lost reps, lost logos, or a market move that stranded coverage). The driver dictates the scope. A growth realignment adds territories without disturbing existing ones where possible. An underperformance fix touches the specific carves that broke. A churn response rebalances load and reassigns orphaned accounts. Pick the one driver that explains the most pain and name it in the plan artifact. Mixed-driver realignments quietly become redesigns, which is the wrong tool for a mid-cycle move.
- Pull attainment, pipeline, and account movement data for the last four quarters and look for the pattern
- Interview three to five managers and ask what they would change about their current carve
- Write a one-paragraph problem statement and share it with the executive sponsor before you plan the fix
Tip: If the honest answer is more than one driver, you are planning a redesign. Wait for the annual cycle or scope the realignment down to the single most urgent cause.
-
2
2. Define the principles that will govern the change
Realignments live or die on the rules you set before you draw a line. Lock three principles up front and refuse to break them under pressure: fairness (no rep ends up materially worse off than peers for the same effort), continuity (reps keep the deals they built and the relationships they own unless there is an explicit reason to move them), and revenue potential (every new carve has to show equal or better weighted potential than what it replaces). Publish these principles with the problem statement so every decision from here has a frame. When a manager pushes to grab a hot account for their rep, you reference the principles, not your opinion. Teams that skip this step spend the whole realignment relitigating one account at a time, and the plan ships late and bruised.
- Translate each principle into a measurable test you can run on any draft carve
- Document the one or two tradeoffs you will tolerate (for example, a short-term potential dip for a long-term coverage gain)
- Get the sales leader and finance lead to sign off on the principles in writing before draft work starts
Tip: If you cannot measure a principle, you cannot defend it in the review. Write the test alongside the principle or drop it.
-
3
3. Build the new carves
Work from the current plan outward, not from a blank slate. Mark every account that must stay with its current rep (active deal in late stage, named-account hold, strategic relationship) and freeze those first. Everything else is movable. Apply the diagnostic driver to the movable set: if the driver is growth, add new territories by pulling the lowest-touch accounts from the busiest existing carves. If the driver is underperformance, rewrite only the carves that failed the balance test and let the rest stand. If the driver is churn, reassign the orphaned accounts across neighbors by weighted potential, not raw count. Keep every change in a line-by-line log so you can roll back a bad move without starting over.
- Export the current carves to a working sheet with weighted potential, active opp count, and ARR per territory
- Freeze the untouchable accounts and compute the movable pool before any assignment logic runs
- Draft two alternatives (conservative and aggressive on the diagnostic driver) so leadership picks between real options
Tip: Realignment carves fail when they chase elegance. Choose the plan that fixes the stated problem with the fewest account moves, not the one that looks tidiest on a map.
-
4
4. Model the expected impact
Run three models before you call a draft done: a potential model (what weighted TAM does each rep now carry versus before), a pipeline continuity model (how much open ARR follows each rep versus moves with the account), and a quota attainment model (given the new carves and the current pipeline, what is the realistic attainment range per rep for the remaining quarter and the next one). Compare each rep's new state to their old one and flag any case where the delta is worse than minus 10 percent on potential or minus 15 percent on pipeline. Those are the conversations that need special handling. Model the comp impact too: if a change pushes a rep off an accelerator they would otherwise hit, decide now whether you true them up, grandfather the quota, or absorb the risk.
- Compute old-vs-new weighted potential, open pipeline, and attainment projection per rep
- Flag reps whose model shows a material downgrade and prepare a specific remediation per case
- Share the aggregate model with finance so comp exposure and quota math are known before launch
-
5
5. Communicate to reps individually
Every rep whose territory changes gets a one-on-one conversation with their manager before any group announcement. Hand managers a prepared packet: what is changing, why it is changing, what is staying the same, how pipeline and comp will be handled, and the escalation path if something feels wrong. Lead with continuity (what the rep keeps) before change (what moves). Reps do not react to the map, they react to feeling like the plan was done to them. The one-on-one, done well, is what turns a realignment from a morale event into a strategy event. Never, under any circumstance, let a rep learn their new territory from a shared sheet or a Slack post.
- Build a per-rep summary showing old versus new territory, retained accounts, moved accounts, and quota impact
- Script the manager conversation with the three answers every rep will ask (comp, deals in flight, named accounts)
- Hold the one-on-ones in a tight window (ideally one to two days) so the news does not leak before the field hears it
Tip: Give managers a decision tree for the handful of questions that will come up repeatedly. Freelance answers in these conversations create inconsistencies you will spend weeks cleaning up.
-
6
6. Handle in-flight deal transitions
This is the step most realignments botch. Set the deal-transition policy in writing before the cutover. The common pattern that works: deals past a stage threshold (usually proposal or later) stay with the original rep through close, deals earlier than that transfer to the new owner with a credit-split rule, and any deal with a named-account conflict goes to sales leadership for a one-call decision. Write the rules down, apply them mechanically, and resist case-by-case negotiation. Build a transition tracker that lists every active opportunity touched by the realignment, its stage, its new owner, its credit split, and its transition date. Review the tracker weekly for the first month so nothing slips.
- Publish the stage-based transition policy and the credit-split formula at the same time as the new territory map
- Stand up a transition tracker with new owner, old owner, split percentages, and target close date for every open opp
- Run a weekly transition review for four weeks and close out each row to a known state (closed, transferred, or escalated)
-
7
7. Launch with a hard cutover date
Pick one date and move everything on that date. Soft launches, where territories change in theory but not in the CRM, teach the field that the plan is optional. On the cutover date, push the new territory rules into the CRM so account creation and reassignment auto-apply them, update quotas in the comp system, repoint reporting dashboards, and send the one-page territory summary to every affected rep. Communicate the cutover a week ahead and again the day of, so no one is surprised when the dashboard changes under them. Keep the old mapping snapshotted somewhere searchable for 90 days in case a crediting dispute needs the pre-cutover state.
- Encode the new territory rules in the CRM so routing is automatic, not spreadsheet-driven
- Snapshot the pre-cutover state (ownership, pipeline, quota) for every rep before the switch
- Send a one-page per-rep summary on cutover day with new territory, new quota, retained deals, and the escalation contact
Tip: If your CRM cannot express the new carve as a routing rule, your rule is too complex. Simplify until the system can enforce it without manual reassignment.
-
8
8. Instrument tracking and run a 90-day retro
A realignment is not done at cutover. Instrument the metrics you need to know whether it worked, and hold a retrospective at 90 days with the data in hand. Track four things weekly: pipeline velocity per rep (is the new coverage producing meetings and opps), attainment projection versus plan (are the modeled numbers holding), rep sentiment (short pulse survey, three questions, every two weeks), and transition exceptions (how many deal or account disputes are still open). At 90 days, bring the sales leader, finance lead, and a sample of managers and reps together to review what the data says and what the field feels. Decide explicitly whether the realignment solved the diagnosed problem, created new ones, or needs a follow-on move at the next planning cycle.
- Define the four tracking metrics and the dashboard that reports them before the cutover goes live
- Run a biweekly pulse (three questions, under two minutes) with every affected rep for the first 60 days
- Hold a structured 90-day retro with a written outcome and a decision on what to carry into the annual plan
