Skip to content

Territory design

Unbalanced territories overload some sales reps and leave others with too little to do, and nobody reaches their sales target. Territory optimisation fixes the cause: how customers are split between reps.

  • Free 30-minute call
  • No commitment
  • You own the code
Typical industries
Logistics and transport, Field service management
Problem type
Routing
You receive
A documented model, run on your data

In short: A sales territory optimisation divides the customers and regions your field sales team covers into territories. Each territory gets a similar workload and similar possible revenue. Each rep gets one connected, compact area with a fair share of travel, visits and revenue opportunity.

The problem

One rep has the dense city centre and hasn’t cleared her visit list in weeks. Another covers three rural counties and spends half the day driving. Both missed their sales target last quarter. You drew the territory borders by postcode, by habit, or to suit the rep who argued hardest at the last planning meeting.

Signs your territories are out of balance

Territories drawn by hand drift out of balance almost at once. You see it in missed sales targets, uneven service and tired people. Some customers get a visit every week, others once a quarter. When a rep leaves, their customers go to whoever has the least to do that month. All of it has one cause: the customers are split unevenly between reps.

Why redrawing the map by hand fails

Redrawing territories looks like a job for a map and a marker. Yet every line you move shifts work, revenue and travel time from one rep to another. Even out only the revenue in a spreadsheet, and each territory ends up as scattered pieces that nobody can drive sensibly. Draw tidy shapes on the map, and the numbers drift apart again. Balanced numbers and tidy shapes work against each other: when one gets better, the other gets worse. That’s what makes it a hard optimisation problem.

What changes

Today, you redraw territories once a year in a long meeting, and the arguments start the week after. Our model proposes territories balanced on workload, revenue and customer count, each in one tight area. You set how much each of the three counts, see the new map and the numbers side by side, and decide. When someone joins or leaves, you move a handful of accounts instead of redrawing the whole map.

What you get

We build one model of your territories. It holds what you want to balance and how much each point counts. It also holds the rules for the shape of a territory and what it costs to hand a customer to another rep. The method is the same one we use in vehicle routing optimisation, applied to your field force territory design. You measure the result on four numbers: how evenly work and revenue are spread, how long each rep drives, and how many customers change rep. We test it on your own accounts before a single account moves, and the model is yours.

  • A model written around your own territory design rules.
  • Results measured in the numbers you already track.
  • It slots into how you already work, and you can check every answer it gives.

How it works

We write your depots, your customers, your fleet and your rules into one model. You get the routes that cost the least and keep every rule. You still have the last word: you check the result and send it out.

What territory design solves

Territory design divides customers, stops or zones among a team. The result is sales territories, service zones or delivery areas. The goal is a fair workload and territories that a person can cover in a normal working day. So the model answers two questions at once. What does balanced mean for your team, and does each territory work on the map?

Territory balancing on more than one number

Balance by customer count alone, and you ignore account size. A hundred small accounts aren’t the same job as a hundred large ones. Balance by revenue alone, and one rep gets a handful of very large customers while another gets a long list of small ones. Both bring in the same revenue, but their working days look very different.

Balance by workload alone, and you count visits, service time and travel. You capture the effort, but you miss how much revenue each customer brings. Sales territory optimisation balances workload, revenue and customer count together. A territory balancing algorithm weighs the three, and you decide how much each one counts.

Contiguity and compactness

A balanced territory also has to work on the ground, which brings two rules about shape. Contiguity means each territory is one connected area, with no islands. Compactness means that area is tight rather than long and stretched. A rep then spends most of the day with customers.

A design that balances the numbers but ignores shape looks fair in a spreadsheet and falls apart in the field. Our territory design software solves balance and shape together, on the map of your own customers. A split that looks fair on paper then also gives each rep a day they can actually drive.

Patch the map or start again?

Territories don’t stay fixed. You hire two reps into a growing region, or you lose one and have to absorb their accounts. Re-zoning, redrawing the map for a changed team, is its own optimisation problem. Rerun the full design from scratch, and the new map can look nothing like the old one. Every reassigned account costs a handover and puts a relationship at risk.

So we work at two speeds. When someone joins or leaves, a smaller model moves only some customers. It limits how many customers each rep loses and how far a territory may stretch. Most customers keep the rep they know. After a few such changes, the territories lose their compact shape. That’s when you rerun the full design. How often you do that depends on how much the shapes suffer and how much the changes bother your reps.

Common questions.

Something else? Ask us directly.

Don’t redraw everything at once. A fresh design can move territories around far more than the change in headcount needs. Instead, move a limited set of accounts, with caps on how many each rep loses and how far an area stretches. After a few such small changes, redo the whole territory design. Do it when territories overlap or the routes inside them get long.

Rarely. Equal counts ignore account size, visit frequency and travel. A rep with forty large accounts in a city and one with forty small ones across a valley have very different weeks. Spread workload and revenue evenly as well, and decide how much each counts. Then look at each territory on the map. Its customers should be close together, so the routes stay short.

Usually not in one run, because the two change at different speeds. Territories stay the same for months, while routes change every day. But the territory model needs a good estimate of the travel time inside each area. Otherwise the workload numbers are only guesses. So when we design territories, we estimate travel time from the visits each area typically gets in a week. Daily routing then works inside the lines you drew.

Sometimes it can, and if that’s the case, we’ll tell you. Standard software is built for an average operation, though. Yours runs on its own rules: your contracts, your exceptions, the things you know by heart. A custom model writes those rules in, and that’s where the better plan comes from.

You don’t need either to start. We build the model from the data you’ve already got, even if it lives in three spreadsheets and one person’s head. You get a system you run yourself. We train your team until they no longer need us.

You see a first result with the prototype, before you commit to anything bigger. We start with a free 30-minute call about your operation and the model that would fit it. Then we build a working prototype and run it on your numbers.

Tell us what you’re planning.

In a free 30-minute call with a specialist, you find out whether optimisation can help.

  • Free, no commitment
  • You talk to a specialist directly
  • A clear go or no-go