Territory Mapping in India: Drawing Boundaries That Balance Potential and Travel

The most common error in territory design is treating the map as the object. A city is divided into neat zones, each with a similar area, and the design looks equitable. Then one zone turns out to contain three industrial clusters and a wholesale market while another contains largely residential streets, and the two salespeople have entirely different jobs while carrying the same target.

The unit of design should be the working week. How many meaningful contacts can one person make, given travel, in the way your business sells? Build territories that fill that week with worthwhile work, and the map will look untidy while the workloads will be sound.

Four things. Existing customers with pin code and annual value. Prospects with pin code and a rough potential band, which can be as simple as large, medium or small. Realistic travel times between the main clusters, measured at the hours your team actually travels, since morning traffic in most Indian cities makes midnight estimates meaningless. And the visit or call capacity of one person per week.

With those, the exercise becomes arithmetic. Without them, it is intuition, and intuition systematically favours the areas that are easy to reach from the office.

Work upward rather than downward. Group pin codes into clusters that can be covered in a single day including travel. Then assemble clusters into a weekly cycle: a day here, a day there, with a fixed pattern the salesperson can repeat and customers can come to expect. A predictable cycle is worth a great deal in field sales, because customers learn when to expect you and keep questions for that visit.

Write these before anyone needs them. A business with several sites is owned by the person covering the registered office. An existing customer stays with its current owner through a boundary change. Named large accounts belong to individuals, not areas. A new enquiry is routed by the pin code given, and where none is given, by the location of the contact.

Publish the rules where the team can read them. Nearly all territory conflict is about fairness rather than about a specific account, and a visible rule applied consistently removes the sense that outcomes depend on who argues hardest.

Review annually using two measures: revenue against potential per territory, and coverage, meaning the share of identified accounts actually contacted during the period. Coverage is the more useful of the two, because low coverage in a large territory tells you the design is wrong, while low revenue in a well covered territory tells you something about the market or the person.

Redraw only when the evidence requires it. Frequent redrawing is corrosive: it breaks customer relationships, it discourages people from investing in an area, and it signals that success will be taxed. When a redraw is genuinely necessary, involve the incumbents, let them choose where practical, and protect earnings during the transition.

There is a persistent temptation to create more territories than the market supports, usually because headcount is available or because a manager wants more coverage. The result is salespeople with too few worthwhile accounts, spending their week travelling between small opportunities, earning less and eventually leaving. Fewer, properly sized territories almost always outperform more, thinner ones, and the difference shows up in retention as much as in revenue.

Practically, all of this depends on having pin codes on customer records and on being able to see coverage by area. HelloGrowthCRM stores territory assignment against the account, routes new enquiries by pin code automatically and reports contacted against identified accounts per territory, which mainly matters because coverage is the number that tells you whether the map you drew works in practice.

Related reading for field sales teams in India: CRM in India, lead management software, CRM for small business, best CRM for India, industry solutions, and features.