How B2B sales teams build territories across several cities
When a team sells in many cities, some reps get a whole city and others share one. How to count prospects city by city and draw patches that stay fair.
Part of the guide Workflow automation
A B2B team selling in several cities builds territories in two layers. First it counts the prospects in each city and gives small cities to one rep each, grouping nearby small cities together when one alone is too thin. Then it splits only the big cities, by where the prospects actually are, so each rep in a shared city gets a compact patch of about the same size. Counting comes first; maps of districts come last.
This is for sales managers whose team covers a region or a country rather than one metro: software firms selling to clinics or shops, equipment suppliers, payment providers, distributors opening new markets. It walks through counting prospects city by city, deciding which cities to share, splitting the big ones, and keeping the whole thing up to date without a quarterly spreadsheet exercise.
Start with a prospect count for every city
Territory arguments usually come from guessing. One manager thinks the capital is worth three reps, another thinks two; neither has counted. The count you need is not population or company registrations but the businesses that match your ideal customer: the kind of place, open, perhaps independent, perhaps above a rating.
xMap's places database gives that count in minutes. As a sense of scale, it lists 830 dentists within 10 km of the centre of Toronto, 768 around the centre of Sydney and 638 around the centre of London (November 2026). A dental software company looking only at those three cores already sees that Toronto and Sydney are close in size and London's core is smaller, which is not what most people would guess from the size of the cities.
| City core | Dentists listed | Chains among the nearest |
|---|---|---|
| Toronto | 830 | 13 of 460 |
| Sydney | 768 | 18 of 465 |
| London | 638 | 33 of 462 |
Dentists within 10 km of each city centre, xMap's places database, November 2026. Chains are counted among the nearest places to the centre, as shown.
Run the same count for every city on your list, with the same distance or the same Area of interest drawn around each, and you have one table to argue over instead of opinions.
Decide which cities a rep owns outright
With counts in hand, sort the cities into three groups. The cut-off depends on how many accounts one rep can actually work in a quarter, which only your own records can tell you; use that number, not someone else's.
- Cities a single rep can cover. One owner, no splitting. Everyone knows whose city it is.
- Clusters of small cities. Two or three towns an hour apart that together make one rep's load. Group them by travel, not by the region's name on a map.
- Big cities that need several reps. These are the only ones worth splitting, and the split should follow where the prospects are.
Keep remote or inside reps out of this geography altogether. If a rep works by phone, giving them a patch only adds hand-offs; give them accounts by kind or size instead.
Split the big cities by the prospects, not by districts
Inside a big city, the Split by territory block shares the businesses a flow found between the reps you name, or between a number of reps from 2 to 12. It draws compact groups of nearly equal size from the positions themselves and labels each by its direction from the middle, so a rep's list says North-east or Centre rather than a postcode they have to look up.
Because it works on the list it receives, you choose what counts as a prospect before the split. Put a Filter in front to drop chains or anything under your rating line, and the split shares only the businesses worth visiting.
A worked example
A made-up example shows the two layers together. A company selling booking software to physiotherapy clinics covers Mexico: one rep for Mexico City, one for Guadalajara and one shared between Puebla and Queretaro. Mexico City has far more clinics than the others, so the manager hires two more reps there.
- One flow with an Area of interest holding all four cities, and Nearby places searching physiotherapy types in each.
- A Filter keeps independent clinics that are open.
- A Branch sends Mexico City's clinics one way and the rest another.
- On the Mexico City side, Split by territory between the three reps named; on the other side, a Calculated field sets the owner from the city.
- Both sides meet again at a Google Sheets step that writes each clinic as a row with its owner and territory, so the CRM import is one paste.
Each Monday the sheet grows by the new clinics found that week, each already with its rep. The manager reviews it once rather than sorting it.
Keep territories steady while the list changes
Territories that move every week make reps nervous and customers confused. Three habits help:
- Split once, then match. Draw the big-city patches from a full list one time, save who owns which patch, and afterwards give new prospects to the patch they fall in.
- Review twice a year, not weekly. Recount each city every six months; move a city between groups only when its count has clearly moved.
- Watch only what is new. Only new means each week's list holds the businesses never seen before, so reps get fresh names in their own patch instead of the same list again.
What the AI employee does each week
Set up as a flow, this becomes an AI employee with one job: find new prospects in every city you cover and put each one in front of the right rep. A common shape is Schedule on Monday, Area of interest with your cities, Nearby places, Only new, Split by territory, then Email or a Slack message naming each rep, and Route planner after the split if your reps drive.
Each rep reads a short list of new businesses in their patch, with type, rating, phone and a map link, and the manager gets the whole picture. The Split my city into fair sales territories and New businesses in my territory, researched, into HubSpot templates are good starting points.
Questions
How many reps should a big city get?
Divide the city's prospect count by the number of accounts one rep can actually work in a period, using your own team's history. The places count gives the first number; only your records give the second.
Can one flow cover all my cities?
Yes. An Area of interest holds several cities, and every business found keeps its city, so later blocks can treat each city differently.
Will Split by territory follow city boundaries?
It follows where the businesses are. If you want splits inside one city only, send that city's businesses to it on their own, for example with a Branch on the city field.
Can I name the reps instead of Rep 1 and Rep 2?
Yes. Give up to 20 people by name or email, and each business carries its rep's name in the owner field.