Territory planning for sales reps: fair, compact patches that redraw themselves
Territory planning for sales reps works best when each rep gets a compact patch with about the same number of accounts, redrawn as new prospects appear. How to do it.
Part of the guide AI employee for sales prospecting
Good territory planning for sales reps gives every rep a compact patch, so their accounts sit close together, and about the same number of accounts, so nobody is overloaded while a colleague runs out of calls. Draw the patches from where the prospects really are rather than from postcode lines or city districts, put each prospect's rep on its record, and redraw the patches on a regular rhythm as new businesses open and old ones close.
This article is for sales managers and sales operations staff in field teams: distributors, equipment suppliers, payments and telecom sellers, medical reps. It explains what makes a territory fair, how the Split by territory block in xMap Flows draws patches, what happens to accounts with no location, how each rep gets their own list, why and how often to redraw, a made-up example, and the usual mistakes.
What a fair territory looks like
Fairness in a field team has two parts. The first is workload: the number of accounts or prospects in each patch. The second is travel: how far apart those accounts are. A patch with 40 shops spread over a whole region is not equal to 40 shops on six streets, even though the count matches. Districts drawn by a map rarely balance both, because businesses cluster in some districts and thin out in others.
So start from the accounts. Plot every prospect you want the team to work, then cut the map into areas that each hold about the same number and keep their points close together. That is what territory planning tools do, and it is what the Split by territory block does inside a flow.
How Split by territory draws the patches
The block takes the items that reach it, such as new businesses found that morning or the accounts in your table, and shares them out by area. You choose one of two set-ups:
- A number of reps, from 2 to 12. The patches are called Rep 1, Rep 2 and so on, and you map them to people yourself.
- People I name, up to 20, by name or email. Each item then carries that person's name or address.
Every item comes out with three fields added: owner (the rep), territory (named by its direction from the middle of all the items, such as North, South-east or Centre, with numbers when a direction repeats) and territory_size (how many items that rep got in this run). No patch takes more than its share: with 25 items and 3 reps, no rep gets more than 9.
Accounts with no location
Some records arrive without a position, such as a lead typed in with only a company name. They cannot be placed on a map, so the block gives them to the rep with the fewest items, under the territory name No position. Treat that group as a to-do: add an address and the record joins a real patch on the next run.
Getting each rep their own list
Once every result carries its owner, the sending block decides how reps receive it. A Google Sheets step writes a row per account with the owner and territory, so each rep filters to their own name. A Slack message can name the owner and territory on each line. An email can list the results with each one's rep and patch beside it, or go to a manager who forwards the parts. If you name reps by email address, the owner field already holds where their list should go.
For a day's visits rather than a list, put Route planner after the split, set to one route for each rep: it reads the owner field and orders each person's stops from the start you pick.
Redrawing: why monthly works for many teams
Patches drawn from this run's items move a little as new items arrive. That is useful for prospecting, where new businesses keep opening and a monthly redraw keeps workloads even. It is less useful for account management, where a customer expects the same rep for years.
- Prospecting teams: redraw monthly, or weekly for very fast markets, so new openings are shared fairly.
- Account teams: draw once, save each rep's area as a table, and use Match with my table to give new accounts to whoever owns the area they fall in.
- Mixed teams: keep fixed accounts in a table and let Split by territory share out only new prospects.
A made-up example from Johannesburg
Say an office supplies distributor in Johannesburg has five reps, Thabo, Lerato, Pieter, Naledi and Sipho, and wants new offices and co-working spaces found each month and shared between them. The flow finds 140 new places in its first run, 134 of them with a position. Split by territory, set to People I name, shares those into five compact patches of 26 or 27, named North, East, South, West and Centre. The six with no position go to the rep with the fewest, under No position, and he adds their addresses that afternoon.
A month later, a cluster of new offices opens in one district. The redraw shifts the boundary between two patches slightly, so both reps stay near 30 accounts instead of one jumping to 45. All names and numbers here are invented to show how the block behaves.
Mistakes in territory planning
- Balancing on the number of accounts and ignoring how spread out they are.
- Using administrative districts because they are easy to name, then wondering why one rep is always overloaded.
- Redrawing account territories every month and breaking customer relationships.
- Leaving records without a location to pile up in No position instead of fixing their addresses.
- Giving out territories by email attachment and letting them go stale; let the flow redraw and send them.
The flow, step by step
This is the kind of work the AI employees for field operations guide describes: a routine job done the same way each time. For a prospecting team:
- Schedule: the first Monday of the month, 07:00.
- Area of interest: your city or region.
- Nearby places: the kinds of business you sell to.
- Only new: only places the flow has not found before.
- xMap LLM and Filter: score each prospect and keep the good fits.
- Split by territory: People I name, your reps.
- Google Sheets or Email: each result with its owner and territory.
What lands each month is the new prospects, scored, each with its rep and patch, and a count per rep so you can see the balance at a glance. Start from Fair franchise territories for a city or New outlets, graded and routed to each rep.
Questions
How many reps can Split by territory share items between?
From 2 to 12 when you choose a number of reps, or up to 20 people when you name them by name or email.
Do the territories stay the same every run?
Not exactly. They are drawn from the items in each run, so boundaries can shift a little. For fixed patches, save each rep's area in a table and use Match with my table.
What happens to a lead with no address?
It goes to the rep with the fewest items, marked No position, so it is not lost. Add its address and it joins a normal territory next time.
Can it also plan each rep's route?
Yes. Put Route planner after it, set to one route for each rep; it reads the owner field and orders each rep's stops from a start you choose.