01
Fair territories are an efficiency lever, not just a morale lever
Beyond avoiding attrition and hurt feelings, balancing a strong and a weak territory means you're maximizing the use of your sales resources. As Anthony frames it, if you make two lopsided territories fair, the overall system should produce more revenue from the same team.
Why it matters: Sell a territory redesign internally on both fronts: it protects your best people and it raises total output. The business case and the human case reinforce each other, which makes the change easier to defend.
RevOps LeadersSales LeadersRevenue Executives
02
Rep anxiety about imbalance is the hardest part of the job
Whether a sales leader, an in-house ops team, or an outside advisor is doing it, everyone shares the same fear: creating territories where reps feel a peer 'across the aisle' has more to go after. That imbalance drives the morale problems and attrition operators are trying to eliminate.
Why it matters: Treat perceived fairness as a first-class design constraint, not an afterthought. The relationships you protect are key positions in the growth engine, and their trust is expensive to rebuild once lost.
Sales LeadersRevOps Leaders
03
Match the sophistication of your territory design to your growth stage
People's minds jump straight to extremely sophisticated territory design, but the level required depends on where you are and what your sales team looks like. A young team does not need the same machinery as a scaled org.
Why it matters: Don't over-engineer. Resist importing the complex model from your last company; right-size the design to the data and team you actually have today.
FoundersRevOps LeadersSales Leaders
04
There are five main buckets for cutting territories
Cameron's menu: geographic (regions, time zones), product/service specialization, industry/vertical, firmographic tier (enterprise / mid-market / SMB), and — when none of those apply cleanly — a fair round-robin or named-accounts approach. Most designs layer a few of these together.
Why it matters: Start from a known set of segmentation lenses rather than a blank page. Evaluate each bucket against your product and buyer, then combine the ones that actually change how you sell.
RevOps LeadersSales Leaders
05
Firmographic is usually the first and most important cut
Both hosts land on firmographic as the default starting point for B2B SaaS. The enterprise motion — multithreading, stakeholder buy-in, long cycles — is fundamentally different from a high-velocity SMB sale, and it needs different people. Most other skills are coachable; that experience gap is not.
Why it matters: Differentiate enterprise and SMB sellers right out the gate. Putting the wrong profile against the wrong deal size is the mismatch that most reliably wastes a territory.
Sales LeadersRevOps LeadersRevenue Executives
06
Design from data — historicals plus a backfill
The process 'comes down to data, data, data.' Look at historical SQLs and closed-won deals sliced by the segmentation buckets, and if you skipped capturing something, there's real value in going back to populate and backfill it so you can feel confident in the design.
Why it matters: Invest in the data layer before drawing lines. Capturing the right fields on leads and deals is what lets you build intelligent territories instead of guessing.
RevOps LeadersSales Leaders
07
Gather feedback from reps, product, and marketing before you draw lines
Data isn't only numbers. Talk to the reps about what they think would work, ask product what's on the roadmap, and ask marketing how they're targeting campaigns and demographics. Those internal stakeholders make you more confident in the territories you design.
Why it matters: Run territory design as a cross-functional exercise, not a spreadsheet done in isolation. The people closest to the buyer surface constraints your historicals won't show.
RevOps LeadersSales LeadersMarketing Leaders
08
Early-stage teams should make comfortable assumptions, not freeze
If you're early and don't have much sales or pipeline-creation data, don't stall. Take a data dump from a source like ZoomInfo, load it into Salesforce or HubSpot, and at least map where the potential universe is so you can start from something real.
Why it matters: Thin data is not an excuse for no design. Map the addressable universe, make explicit assumptions from what has worked, and refine as pipeline data accumulates.
FoundersRevOps Leaders
09
The rollout is where good plans die — timing and holdover rules
The major pitfall isn't the design, it's the rollout. Cut over at natural calendar breaks (a new quarter or month), and define clear criteria for what reps can and can't hold onto after the reshuffle. Miss the holdover plan and the trickle-down surprises blindside your team.
Why it matters: Plan the change-management as carefully as the segmentation. A 360-degree view of the rollout — holdovers, timing, communication — is what keeps a smart design from becoming a disaster.
Sales LeadersRevOps Leaders
10
Distribute geography by time zone, not by HQ — and don't over-cut
In a distributed-work world there's often no HQ to visit, so Anthony spreads reps across time zones based on what prospects need most: someone available during their business hours. And he warns that slicing a market too many ways creates dry patches and unequal territories, so he keeps bigger buckets with a round-robin inside.
Why it matters: Optimize geography for buyer availability rather than office coverage, and stop cutting once further granularity would starve some reps. Fewer, fairer buckets beat many brittle ones.
Sales LeadersRevOps Leaders