Sales Territory Design

Territory design is unusual: almost all the work lands in Blueprint. If you do that part right you can

one-shot the whole plan and get a green light in two sessions.

• 1
• Blueprint

Value the market, make the cuts in order, carve three steps ahead, and get every rule of engagement on paper.

• Output The live territory map + rules
• 2
• Build

Territory object or native fields, babysitters and holdouts, hierarchy resolution — then deploy the package.

• Output Live territories & owners
• 3
• Enable

Two working sessions, live edits in the room, and the rules doc shipped alongside the map.

• Output Signed lines
• 4
• Maintain

Alert on drift, revisit on a clock, and expect a full look the week a new C.R.O. walks in.

• Output Territories that stay fair
• Where this sits
• The G.T.M. structure sequence
• Prereq Market Map →
• You are here Sales Territory Design →
• Unlocked next Lead Routing
• This order is not a preference, it's a dependency chain. Market Map produces the

valuations that make an equitable carve possible; territory design produces the owners that routing

assigns to. Sell them in sequence and each one lands. Skip a step and you'll rebuild it later.

Start Here

Don't dig through the GitHub repo. Copy this prompt, drop in the customer name, and send it to your Claude.

It clones the template, reads the AGENTS.md , and walks the checklist with you.

• paste into Claude
• Copy prompt
• # Sales Territory Design — kick off

Clone the LeanScale Sales Territory Design template repo for my customer [Customer Name] .

Then read AGENTS.md and run the kickoff checklist:

1. Confirm the Market Map prerequisite — every account in the C.R.M., with a valuation.

If it's missing, stop and tell me: we scope Market Map first.

2. Pull the account universe (valuation, employee count, industry, geo, hierarchy,

partner-sourced and self-serve flags) plus the current rep roster and manager layer.

3. Build the territory blueprint — firmographic cut, then geographic, round robin

inside the geo, normalized for outliers, carved three steps ahead of headcount.

4. Draft the rules of engagement: named accounts, holdouts, vacancy coverage,

in-flight deals, hierarchies, partner, P.L.G. and government.

Flag anything you can't answer from the data — those are my discovery questions.

What you get

The clone becomes part of the customer's brain — the valuations, the cut

logic, the rules of engagement, and every exception you negotiated. The next re-carve starts warm.

Inside it

The territory designer app to load their data into, the Salesforce and HubSpot

config packages, the rules-of-engagement template, and the checklist that makes kickoff a guided walkthrough.

• 1
• Phase 1

This is the project. Nearly everything that matters

happens before you touch a CRM: value the market, make the cuts in the right order, decide who else besides

sellers gets a line, and pin down every rule people will fight about later. Do it properly and you show up to

the first working session with the answer already built.

1.1 · The Gate

You cannot split a market fairly if you don't know what the pieces are worth. This is the one hard

prerequisite, and it's a qualification question, not a nice-to-have.

• If · they've done the work
• Go
• Every account in the C.R.M., a valuation on each one , and firmographics you

trust. That might be our Market Map or their own — if theirs is genuinely good, use it. You're ready to carve.

• Else · no valuations
• Sell Market Map first
• Running territory design without valuations is drawing lines on a map and hoping the

reps don't notice. Scope Market Map as the prerequisite project — and expect to modify it for territory

purposes : ceilings, floors, and account counts next to the dollars (see §1.4).

1.2 · The Standard

There are five ways to slice a market. They are not equal, and the order you apply them in is the single most

opinionated thing in this playbook. A customer's go-to-market strategy can override it — but make them earn it.

• Apply in this order
• Every account lands in exactly one bucket
• First Firmographic →
• Second Geographic →
• Inside the geo Round robin
• Only if you're out of road →
• Product
• Vertical
• Full randomization
• Firmographic first because you hire a completely different seller for enterprise

than for S.M.B., and run a completely different process. Geography second because coverage and time zone are

real. Round robin third because it's the only fair way to split a metro nobody should be splitting.

Cut 01 · always

Enterprise / mid-market / S.M.B. Different hire, different process, different cycle.

One seller running a 40-person startup and a 60,000-person enterprise in the same week is doing two jobs badly.

Cut 02 · then

Three reps in San Francisco split the inbound round robin and name their own target accounts.

Better results, better traction , and no maintenance burden when someone leaves.

Cut 04 · rarely

Splitting sellers by product almost never works. Where it does is

post-acquisition — a LexisNexis that bought a business with its own motion. Not most of our customers.

Cut 05 · rarely

Only when it's genuinely a different sale — different buyer, different compliance, different

cycle. Otherwise you've created scarcity in the good verticals and a fight over who gets them.

Anti-pattern

Balances the spreadsheet and destroys everything else. No regional knowledge, nonsense travel,

and two referrals inside one metro landing on different reps. Show them the map — it argues itself.

The exception worth taking

Sales engineers are the one role where a product cut usually works — bring in the S.E. who knows

that product, across account teams. That's a coverage model, not a territory. Don't let it leak into the seller lines.

1.3 · The Floor

The hardest part of a geographic cut is what to do with San Francisco or New York — a single metro big enough

to be its own region. The instinct is to slice it finer. Resist it.

• 1
• Put several reps in the metro and round robin
• Three reps in San Francisco. Split the inbound round robin, let each name their target

accounts, and let the rest sit in the shared pool. The metro stays whole.

• 2
• Don't chase the zip code
• The headquarters usually isn't where the buying team sits . You'll carve a

precise line around a building and route to the wrong rep anyway. Get it to a time zone, a coast, or a general

region, then stop.

• 3
• Zip-code territories are a maintenance trap

The first time someone leaves — or the team drops from three reps to two — you're running a

whole re-equity exercise on lines nobody can hold in their head. It is a nightmare to maintain.

• 4
• And no, not by the first letter of the company name
• One client asked for A–M to one rep and N–Z to another. It's not a perfect science and

round robin still beats it — alphabetical is randomization wearing a lab coat .

1.4 · Normalize

Raw valuations from a Market Map will lie to you the moment one account is an order of magnitude bigger than

the rest. This is the most common way a technically-correct carve gets rejected in the room.

• The Walmart problem
• Running territory design for one client, the central region came back enormous — because

Walmart was in it . If they land Walmart it's a career, so the T.A.M. was real. But the number

of accounts in that region was terrible . One whale and a lot of empty. We had to normalize the

account valuation and balance on account count as well as dollars so the region wasn't over-indexed on a

single logo.

• What to actually do
• Cap the outliers — a percentile ceiling on any single account's contribution to the carve
• Set floors so a thin region doesn't disappear into its neighbour
• Balance on a blend of value and account count, not one or the other

Show both numbers side by side — rich and empty, or poor and busy, are different jobs and reps feel both

• Say the quiet part in the room : "this rep still has to go get Walmart"
• Market Map, modified

You may need a different cut of the Market Map for territory purposes than the one used for

targeting. The raw valuation method is still insightful — keep it close — but the outliers have to be handled or

the plan isn't practical to use.

1.5 · Carve Ahead

The most common failure isn't a bad map — it's a map that's only correct on the day it ships. Every hire, every

departure, and you're back in the room re-negotiating.

• The trap
• One big territory per rep
• "Jim has the west coast." Then they hire, and you have to go slice the west coast while

Jim watches. Every hire becomes a re-carve, and a re-carve is a negotiation.

• The move
• Pre-cut, then assign several to one rep
• Carve West 1, West 2 and West 3 today and assign all three to Jim. When they hire,

Jim keeps West 3 and Susie takes One and Two. A reassignment, not a re-carve — and nobody has to

re-litigate the lines.

Ask it both ways

Two questions, always: what happens if we lose three people, and what happens if we hire ten?

Knowing your next carve while you're making this one is what stops the next change being a fire drill.

1.6 · Account Teams

Broaden it in the first conversation. The unit of coverage is the account team, and every role on it needs a

line — otherwise you've designed half a system and left the rest to be improvised.

A.E.

• The base carve
• Firmographic → geographic → round robin
• Every other role derives from these lines
• Named-account caps live here

S.D.R. / B.D.R.

• Feeds the territory
• Usually lighter than the seller count

How many sit on a region drives the S.L.A.

• Hands straight into Lead Routing
• Sales Engineer
• Shared coverage

Roughly 2 account teams to 1 S.E.

• Product-specialised is fine here
• Pulled in by product, not by geography

C.S.M.

• Owns after the close
• Same firmographic-then-geographic logic
• Product-cut only if truly different products
• Rarely needs its own geography
• If they run pods
• The seller leads . Assign the C.S.M. and the S.E. to the pod and everyone inherits the

seller's lines. Clean to build, clean to explain, and the account team is stable enough that relationships

compound.

If they run hunter / farmer

Each function gets its own cut and you show them side by side. The interesting part is where

they differ — that's where coverage gaps hide, and it's the view that makes a C.R.O. sit up.

1.7 · Altitude & Management

Two decisions people forget until they're stuck. Both are easier to raise while you're already drawing lines.

• 1
• Decide the altitude before the U.S. carve
• Regions first — North America, E.M.E.A., A.P.A.C., LATAM — or countries first? Most teams
• under about forty sellers should run one N.A.M. carve with a named E.M.E.A. lane and keep

A.P.A.C. and LATAM as overlay coverage. Cutting a region you can't staff is how you get a territory nobody

works.

• 2
• Then break the big ones down
• East coast and west coast inside the U.S., then finer only if the headcount justifies it —

and never below the metro.

• 3
• Assign management territories too
• Twelve sellers and no director is a finding, not a detail . Who's keeping a

pulse on this — is the C.R.O. really checking in with all twelve? Assign directors to groups of territories

the same way you assign reps to territories, and show it on the same map.

1.8 · Discovery

The map is what people look at. The rules are what they argue about. Every row here that you leave unanswered

becomes somebody's political fight in month two — and by then it's an escalation, not a decision.

Rule

A checkbox on the account . Reps nominate their five by a deadline, you filter

them out of the carve, and you build a report so nobody quietly takes fifteen. It's manual, and it works — the

rep has to tell you which ones somehow.

Rule

One client protected anything past stage four . Pick the line in discovery —

whatever it is, it has to be written down before the map is announced or it becomes a negotiation with every

rep individually.

Rule

The McDonald's headquarters and the operator running fifteen locations in South Carolina are

not the same territory . And the hard part is inference: is this a franchisee, or is this Ronald

himself?

Rule

Two motions wear the same word — recruiting partners is its own territory

design; working deals through them is a rule on the direct team. Decide which, then write who

gets credit. This is the one that goes political fastest.

Rule

A self-serve account converts in someone's region — is it a lead they don't get paid on until

there's a contract, does C.S. own conversion on a quota, or do they get paid regardless? We don't have a

strong opinion, so you have to get theirs.

Rule

Divisions rolling up to one parent agency, procurement cycles that look nothing like

commercial. Carve it out — but push for one instance with role-based access over a second CRM.

The Deliverable

Blueprint's output is an interactive territory map . Bubbles sized by the value in each metro.

Equity anyone in the room can check at a glance. A headcount slider that re-carves the whole plan live. And the

rules of engagement in the same place as the lines, exporting as one document.

Imagine a new C.R.O. walking in on day one and getting this instead of a stack of Salesforce reports.

That's the bar. Load the customer's Market Map into it and you can drive a decision in two sessions.

• leanscale-territory-designer-270.netlify.app
• Open ↗
• ▶
• Load the Territory Designer
• The live blueprint artifact, running on demo data. Or open it in a new tab ↗
• Feature

Drag from ten reps to twenty and watch the territories carve themselves. It's the fastest way

to make "carve three steps ahead" obvious to someone who has never thought about it.

Feature

Every territory indexed against the average inside its own segment , with the

account count next to the dollars. Nobody has to take your word for whether Sarah got the juice.

Feature

The good news: this is the most packageable build in the

library. The names of the territories change from customer to customer; the infrastructure barely does. The one

real decision is how much structure their team size actually needs.

2.1 · The Decision

In Salesforce you get a real choice, and picking wrong in either direction costs you. Team size and territory

complexity decide it — not preference.

• If · small and simple
• Native fields on the account
• Series A shape: two or three territories, ten to fifteen reps . Perfectly

manageable. If Jim leaves and he had the whole west coast, reassigning Jim's accounts is a five-minute job.

Most teams graduate out of this eventually — that's fine, it's not a mistake to start here.

• If · approaching one territory per rep
• A custom Territory object
• Fifty territories and fifty reps, San Francisco logic and New York logic, deep carves

you can't hold in your head. One client went straight to the custom object out of the gate because they

were hiring like crazy — if they'd waited they'd have rebuilt it inside a year.

The threshold, stated plainly

It's team size and territory complexity . Once you're carving finely enough that one rep is

roughly one territory — and especially once other systems reference the assignment — go custom object. Below

that, native is honest.

2.2 · Why It's Worth It

The usual argument for the object is reporting. That's the smallest reason. The real one is the number of

places you have to remember to change when a person moves.

• 1
• Change the owner once, cascade everywhere
• Update the owner at the territory record and every associated account

follows. No custom report to scroll through wondering whether you missed a holdout.

• 2
• Routing references the territory, not the person
• This is the one that bites. With a custom field on the account, a rep change means editing
• the field and the routing rule and whatever else points at them. With the object, the flow
• just asks "who owns this territory?" — one place, no leaks. It's a level of complexity

proportional to how many other systems are involved.

• 3
• Babysitters and placeholders have somewhere to live
• A babysitter field on the territory, or a placeholder owner — an integration user, the

hiring sales director — holds the seat open. It stops the existing team quietly working accounts that were

carved for a rep who hasn't started yet, and a new rep walking into an

inequitable situation on day one .

• 4
• The territory snapshot
• Open a territory and see everything related to it. You can get there with custom

reports — but this is the view a sales director will actually open, and that matters.

2.3 · The Config Package

Different shapes, same outcome: an account knows its territory, a territory knows its people, and changing a

person is one edit.

• Salesforce
• Territory__c — name, region, segment, owner, babysitter, status
• Account → Territory lookup, set by the assignment logic
• Holdout checkbox + holdout expiry date on the account
• Named-account flag and the per-rep cap report
• Owner-change automation that cascades from the territory down
• Account team roles for S.E. and C.S.M. coverage
• Territory snapshot reports + an equity dashboard by owner
• HubSpot
• It's workflow-driven — there's no equivalent object to lean on

A mapping data table : this A.E. → this B.D.R., this S.E., this C.S.M.

• Everything cascades off the account owner — set that, the rest fills in
• Territory and segment as company properties for reporting
• Holdout and named-account properties, same as Salesforce
• Accept more manual maintenance; keep the mapping table as the source of truth
• 2.4 · Hierarchies

Same rule as Market Map: you want a market map, you use Clay. You want hierarchy-aware territories, you use a

tool built for it.

• The tools
• Traction Complete or Kernel for hierarchy resolution — both expensive, both

worth it when the business model depends on it. Get the parent-child structure mapped, then take a position on

whether the corporate level or the local operator owns the relationship. Our default: the operating

location owns it, because that's who buys.

• Where it gets dicey
• Fed and public sector. Divisions of the army rolling up to a main army account, agencies

inside agencies. And in resell-heavy channel models you may have no visibility into who is actually using the

product — a single master account paying for everything. At that point you're treating the reseller as the

customer, and the territory rule has to say so out loud.

2.5 · Deploy

• 1
• Deploy the package
• On the Salesforce side this is genuinely rinse and repeat — the object, the

assignment logic, the cascade automation, the reports. The names of the territories and which accounts fall

into them change; the infrastructure doesn't.

• 2
• Claude writes the assignment logic from the approved blueprint

The blueprint already encodes the cut order, the boundaries and the exceptions. Have Claude

turn it into the assignment rules and the data load, then an engineer reviews the diff before

anything touches production.

• 3
• Load holdouts and placeholders first
• Holdout flags go in before the mass assignment, or you'll reassign the accounts a rep

was promised and have to walk it back. Same for babysitters and open seats.

• 4
• Reconcile before you announce

Every account has exactly one territory. Every territory has an owner or a named babysitter.

Nobody exceeds their holdout cap. Run the report, fix the gaps, then send the email — a rep

finding their own missing account is how the whole plan loses credibility.

• 3
• Phase 3

Enable is short on this project, because you show up

with the blueprint already built. Two sessions is usually enough to drive a decision — the first to react, the

second to sign.

• Session 1
• Show up with it built
• Walk the map, the equity chart and the carve-ahead view. Don't present options — present a

recommendation and let them push on it.

• Between
• Adjust and close the rules

Fold in their feedback and finish the rules of engagement — the holdout and vacancy answers

usually come out of session one.

• Session 2
• Edit live, then sign
• Change it in the room. Being able to move a slider and re-cut in front of them is what

turns a review into a decision.

• Then
• Build, reconcile, announce

Hand the rules doc over with the map. They are one deliverable, not two.

3.1 · The rules doc ships with the map

Whatever else you hand over, hand over the rules of engagement . The map is what people look

at; the rules are what they argue about, and a rule that only exists in a call recording isn't a rule.

Every exception you negotiated goes in it — the holdout window, who babysits a vacancy, what stage protects an

in-flight deal, how a franchisee gets treated. When the first dispute lands, you want to be pointing at a

document rather than reconstructing a conversation.

• 3.2 · Say the boundary out loud
• Routing is not part of this project. Territory design defines the lines and

the owners; routing decides what happens when a lead shows up. They're related enough that a customer will

assume they're the same scope, and different enough that mixing them sinks both.

Land this plane, get the lines signed, then open Lead Routing as the next project. It's

an easier sell after this one anyway — you've just built the prerequisite.

Tell them what changes for them

Reps don't care about the object model. They care about three things: which accounts are mine, how many

can I name, and what happens to the deal I'm already working. Answer those three in the announcement and

most of the noise never starts.

• 4
• Phase 4

There is a lot of maintenance on this one. That's not a

flaw in the design — it's the nature of the object. People move, whales land, and the lines that were fair in

January aren't in July.

4.1 · Triggers

Two account universes, two hierarchies, two sets of named accounts, and reps on both sides

convinced the overlap is theirs. Treat it as a new blueprint, not a patch.

4.2 · Monitoring

Territory value swing — flag any territory whose T.A.M. moves more than ~40%, in either direction

Equity spread — track richest-to-thinnest across the team; when it drifts past ~2× it's time to revisit

Unassigned accounts — new accounts landing with no territory is the most common silent failure

• Expired holdouts — the 90-day window closed and nobody released them
• Territories with no owner and no babysitter — an open seat nobody is covering
• Named-account overruns — a rep quietly holding sixty when the cap is fifty
• 4.3 · Cadence

• Event-based
• The real trigger
• New C.R.O. or V.P. of Sales — immediately
• Rep joins or leaves — reassign and re-check the rules
• A whale lands or a segment changes shape
• A hiring wave against the plan
• Time-based
• Quarterly if they'll have you, every half at minimum
• A full review at least once a year, no exceptions. Resist over-refreshing though — the

churn has a cost of its own, and reps need the lines to sit still long enough to build something on them.

What You Hand Over

The team gets this page, the brief, and a one-paste prompt. The client gets an app they can poke at, a rules

document they can point to, and territories that survive the next three hires.

For the team

The playbook overview and the audio brief — the front door for anyone running a territory

project, and the fastest way to get into the right mindset before the first call.

For the team

The exported rules doc, the deployed Salesforce or HubSpot config, and the monitoring that

tells them when the lines have drifted.

The bet

Most companies re-cut territories in a spreadsheet once a year and argue about it for a month. Show up with the

market already valued, the cuts already made, the next three carves already drawn, and every rule already

written — and you've turned the worst meeting of their year into two sessions and a signature .

• ✓
• Closeout

When a Sales Territory Design engagement wraps, spend sixteen

minutes with the debrief agent. Teamwork already knows what got built and when. This is for the

part none of our systems can see — the call that could have gone either way, the thing the customer

wanted that you refused, the near-miss that never became an incident, and above all the places

this playbook turned out to be wrong. What comes out of it gets written back into this page.

Two minutes of thinking beats sixteen minutes of recall. Have these in your head —

you don't need notes, and you definitely don't need a script.

The cut order — what you actually cut on and in what order, and what forced it if it wasn't firmographic then geographic.

The metro line — where the smallest boundary in your plan landed, and who pushed to go finer than that.

Structure and the rules — Territory object or fields on the account, and which rule of engagement you had to invent on the spot.

Sixteen minutes, one sitting. It's a voice conversation, so your browser will

ask for microphone access — use headphones or the agent will hear itself. Chrome is the safer bet

over Safari.

It's a craft debrief , feeding straight back into this playbook.

It is not an assessment. Nothing here goes near performance review.

It's attributed — Anthony reads it with your name on it.

"This took two weeks longer than it should have because of X" is the most useful thing

you can say . Say it.

No mic prompt? Check the padlock in the address bar — the browser may have blocked it.

Agent talking over you? Headphones. It's hearing itself through your speakers.

Still stuck? Message Anthony rather than burning fifteen minutes on it.

The transcript takes a moment to generate after you hang up. You'll get a recap

emailed to you.

• The debrief asks what you built that's worth reusing. This is where you actually hand it
• over — dashboards, field maps, flows, templates, scripts, spec docs. Files land in the

project's Drive folder; links go into the artifact register so the next person can find them.

Thirty seconds, and do it while the project is still in your head.

“I'll upload it later” is exactly how assets end up trapped on an account.

• Add an artifact →
• LeanScale · Delivery OS

The Sales Territory Design playbook — the internal standard for carving a valued market into books of business

that are equitable, coverable, and still correct three hires from now. Blueprint, Build, Enable, Maintain. Audio brief

generated with ElevenLabs.