# Sales territory design for a dealer-led field force

> Sales territory design divides a market into areas that one person or team can cover well. How to draw territories, set roles and hierarchy, and review them.

Sales and field teams · The Intellsys team · 18 November 2026 · 6 min read

Sales territory design is the work of dividing a market into areas, each owned by one salesperson or team, so that every dealer and every customer has a clear owner and the workload is fair. For a dealer-led business it has three parts: drawing the areas, deciding who covers each one and who they report to, and agreeing what each role can see. Get those right and routing, reporting and leaderboards follow.

## The short answer

- A territory is an area with one owner, built from units you can count, such as pin codes.
- Balance territories on workload and potential, not on map size or dealer count alone.
- Roles and reporting lines decide who sees which dealers and leads.
- Write the territory map down in the system, not in a spreadsheet beside it.
- Review territories on a fixed rhythm, and move records in bulk when they change.

## What sales territory design has to settle

In many networks the territory map lives in a regional manager's head and a spreadsheet at head office that disagree. Two area managers both believe a growing district is theirs. A new dealer opens and nobody is sure whose numbers it belongs to. Leads from a pin code on the border go to whichever dealer answers first.

Good territory design settles four questions, once, in writing.

- **Where** Which pin codes, districts or towns make up each territory.
- **Who** Which person or team owns each territory, and who covers when they are away.
- **Above whom** Who each owner reports to, up to the national sales head.
- **What they see** Which dealers, leads and numbers each role can open.

*The four questions sales territory design has to answer in writing, before routing, reporting or rankings can work.*

## How to draw territories

Start from small units you can count, then group them. Pin codes or districts work well in India because enquiries, dealers and census figures can all be tied to them.

1. **Pick the unit** Choose pin codes, districts or towns, and use the same unit everywhere.
2. **Count each unit** For each one, record dealers, recent enquiries and recent sales.
3. **Estimate the work** Work out the calls, visits and dealer reviews each unit needs a month.
4. **Group into territories** Combine units until each territory carries similar work and similar potential.
5. **Check travel** Make sure one person can actually reach every dealer in their territory.
6. **Name an owner** Give each territory one owner and one named backup.

*Six steps to draw sales territories from counted units, balancing work and potential rather than area on a map.*

The third step is the one most often skipped. Two territories with the same number of dealers can be very different jobs if one has twice the enquiries. Balance on the work, and check potential separately so nobody is handed a territory that cannot grow.

Territories are also the first rule in [lead routing to dealers](https://intellsys.cloud/blog/lead-routing-to-dealers). If two territories overlap, routing will send the same lead to two places, or to neither.

## Roles and hierarchy for a field force

A territory map is only half the design. The other half is who sits above whom, and what each level can see. A typical dealer-led field force has five or six levels.

- **National** The sales head sees every zone, dealer and lead.
- **Zone** A zonal manager sees the regions in their zone.
- **Region** A regional manager sees their areas and the dealers in them.
- **Area** An area manager or sales officer covers a territory and its dealers.
- **Dealer** The dealer principal sees their own showroom's people and leads.
- **Salesperson** A salesperson sees the leads assigned to them.

*A typical reporting hierarchy for a dealer-led field force. Each level sees what is below it, and nothing beside it.*

What each role can see matters as much as the lines on the chart. A dealer who can open a neighbour's leads will, sooner or later, call them.

| Role | Sees | Does not see |
| --- | --- | --- |
| National sales head | Everything | Nothing is hidden |
| Zonal or regional manager | Their zone or region, all dealers in it | Other zones and regions |
| Area manager or sales officer | Their territory and its dealers | Neighbouring territories |
| Dealer principal | Their own dealership's leads and staff | Other dealers |
| Salesperson | Leads assigned to them | Colleagues' leads, unless shared |

How tightly to set these is covered in our post on [role based access for dealer networks](https://intellsys.cloud/blog/role-based-access-for-dealer-networks).

## Beat plans, visits and what territory design does not cover

Territory design says who owns an area. A beat plan says which dealers or shops a person visits on which day. They are related, but they are different jobs, and the second depends on knowing where people actually are.

In Intellsys OS the two sit on the same record. A business defines territories, roles and hierarchy, and Field Sales builds the beat plan on top of them: each visit planned, recorded with its location, and the order captured on the spot, even without a network.

## Reviewing territories without breaking the record

Territories drift. Dealers open and close, a district grows, a person leaves. A fixed review rhythm keeps the map honest.

- **Monthly** Check for leads arriving from units with no owner, and fix them at once.
- **Quarterly** Compare workload and results across territories; move units where the gap is large.
- **Yearly** Redraw from fresh counts, alongside the annual targets.
- **On any change** Move the affected dealers, leads and open work in bulk, with a record of every move.

*A review rhythm for sales territory design, from monthly gap checks to a yearly redraw.*

When a territory changes, open leads must move with it, or they stay with someone who no longer covers them. Leaderboards need resetting too, or the comparison stops being fair; see [sales leaderboards](https://intellsys.cloud/blog/sales-leaderboards).

## How Intellsys OS handles sales territories

In Intellsys OS a business defines its own territories and roles, and permissions go down to a single record, by role, by reporting hierarchy and by geography. That lets a regional manager see a region, a dealer only its own leads, and a salesperson only what is assigned to them. When territories change or people leave, work can be reassigned one at a time or in bulk, round-robin, with an audit log of each move.

Salespeople work from a day plan and a queue, and leaderboards are included. Field Sales adds beat plans, location-stamped visits and orders taken in the field, online or off. More on our [operations platform](https://intellsys.cloud/platform/operations), and on the network side in [what a dealer management system is](https://intellsys.cloud/blog/what-is-a-dealer-management-system).

> **How Intellsys OS handles it.** Intellsys OS lets a business define its own territories and roles, with permissions by role, reporting hierarchy and geography down to a single record.

## Questions people ask

### What is sales territory design?

It is dividing a market into areas, each owned by one salesperson or team, and setting who reports to whom and what each role can see. Good design balances workload and potential so territories are fair and comparable.

### How do you balance sales territories?

Build them from small counted units such as pin codes. For each unit, estimate the work it needs from its dealers and enquiries, then group units until each territory carries similar work and similar potential, and check that one person can travel it.

### What is the difference between a territory and a beat plan?

A territory says who owns an area. A beat plan says which dealers or shops a person visits on which day. Territory design comes first; beat planning sits on top of it and needs knowledge of where people are.

### How often should sales territories be reviewed?

Check monthly for leads from areas with no owner, compare workload across territories each quarter, and redraw from fresh counts once a year. When anything changes, move the affected dealers and open leads in bulk, with a record.

---

[Request a demo](https://intellsys.cloud/demo) · [Blog](https://intellsys.cloud/blog)

This is the Markdown version of https://intellsys.cloud/blog/sales-territory-design. Intellsys is built by GrowthJockey, a full stack venture architect.
