How should the reassignment framework differ between a founder-led early-stage org (where the founder knows reps personally) vs. a scaled 50+ rep team (where reassignment is mostly data-driven)?

Reassignment Framework: Founder-Led (≤10 Reps) vs. Scaled (50+ Reps)

The core difference is the decision currency. In a founder-led org, reassignment runs on judgment, relationship context, and qualitative rep reads — the founder knows *why* Rep A is struggling on Account X. At 50+ reps, that intuition doesn't exist; every reassignment decision must be defended by CRM data, quota attainment curves, pipeline coverage ratios, and a written governance process.

---

THE DETAIL

#### Stage 1: Founder-Led (≤10 Reps)

In early-stage B2B tech companies, founders often lead sales efforts initially, using their deep industry knowledge and personal relationships to land first customers. Reassignment at this stage is essentially a direct conversation — no committee, no scorecard.

How to handle reassignment here:

1. Relationship-first triage. Before moving any account, the founder asks: what's the customer relationship risk? In a 5-rep org, losing a strategic account mid-reassignment can be a $200K ARR miss.
2. One-sales-cycle patience. Not every rep will have a great first month or two. Give it a full sales cycle before making an initial assessment — especially on complex, longer-cycle deals.
3. **Document the *why* immediately.** Salespeople won't understand how to replicate your process if you don't share the details. Be open about how you speak to prospects, any challenges your company is facing, and why each account matters. Reassignment logic becomes playbook material.
4. Assign new reps to lower-complexity accounts first. Assign new reps to less complex, shorter-cycle territories at first. Move them up as they prove velocity.

Key risk: The founder possesses capabilities reps do not — the deepest understanding of product value, the ability to adjust pricing and messaging based on direct feedback, and established industry credibility. Reassignment without a warm handoff breaks deals.

---

#### Stage 2: Scaled Org (50+ Reps)

As teams grow, relying on spreadsheets or other manual methods for territory planning becomes impractical — it leads to errors and inefficiencies, especially when planning at scale.

The scaled reassignment operating model:

1. Define the trigger set. Reassignment fires on objective signals: quota attainment <70% for 2 consecutive quarters, pipeline coverage below 3x, win rate dropping >10 points vs. segment peers, or rep departure.
2. Score territories, not reps. Balance territories by revenue potential — total ARR available — and account complexity, since enterprise deals require more touches than SMB.
3. Run a formal governance layer. No informal override process — informal exceptions accumulate silently and surface only at quarter end when someone's compensation doesn't match expectations. Every reassignment needs a deal desk ticket and RevOps sign-off.
4. Version every change. Not versioning territory changes makes prior-period reporting unreliable and compensation disputes difficult to resolve. Use Fullcast, Xactly, or Salesforce Maps for audit trails.
5. Act fast on top-performer departures. When a top performer leaves, reassign their high-value accounts to your strongest available rep immediately — don't let them go cold.
6. Dynamic reviews, not annual resets. Companies that dynamically adjust territories see up to 30% more revenue per rep than those using static models.

---

Benchmark Comparison Table

---