Pillar 1 covered choosing the right base geography. Pillar 2 is the one most projects underestimate: getting the data right. A territory alignment is only as fair as the numbers under it, and if you balance on bad data, you get precisely balanced unfairness.
Here’s the data a real territory design needs, where to find it, and the quality traps that quietly wreck alignments.
The Four Layers of Territory Design Data
Customer and revenue data (your CRM). The foundation: every account with its location (ZIP code at minimum), current revenue, and segment. Pull 12 to 24 months so one big quarter doesn’t distort the picture. This tells you where your business is.
Market potential data (external). The layer most alignments skip, and the most valuable. Business counts by industry and size, demographics, or syndicated estimates tell you where business could be. Balance on current revenue alone and you reward past coverage while burying greenfield; blend revenue with potential and territories get genuinely fair.
Workload data. Account counts by call-frequency tier, service needs, travel realities. Two territories with equal revenue can carry very different workloads if one has 40 large accounts and the other 400 small ones. Workload is what protects reps from burnout territories.
Structural data. Current assignments, rep home locations, the district and region hierarchy, and any hard constraints (state-boundary rules, contractual carve-outs, account overrides). Without this layer you can design a beautiful alignment that’s impossible to implement.
Formatting the Data for Import
Territory software wants tidy tables, and Excel is the common language. Three sheets cover almost every project. A geography sheet, one row per ZIP code or county FIPS, with the territory assignment and any ZIP-level metrics. An account sheet, one row per account: ID, name, ZIP, revenue, segment, current rep. And a hierarchy sheet mapping territory to district to region, plus rep names and home ZIPs.
Check for the usual traps before importing: ZIP codes stored as numbers (Excel drops the leading zero from 02134), county names instead of FIPS codes, duplicate account rows from a CRM export, and revenue split across columns that need summing first.
Data Quality: The 80/20 Checks
Run a coverage check: what share of revenue has a valid ZIP code? Below about 98 percent, fix the source first, because every unmapped account is invisible to the design. Run a freshness check, since customer lists older than a quarter, or potential data older than a couple of years, will misplace real opportunity. Run an outlier check by sorting accounts by revenue and eyeballing the top 50; one mis-keyed decimal on a big account can tilt a whole territory. And reconcile your sanity totals: do the imported figures match finance’s number for the same period? If not, stop and fix it before you design anything.
How Much Data Is Enough?
Don’t let perfect be the enemy of aligned. A workable design needs accounts with ZIPs and revenue, one potential metric, and current assignments. Everything else refines the picture. Teams that wait for perfect data realign a year late; teams that start with the 80 percent and flag the known gaps realign on schedule and improve the data next cycle. How you’ll judge the design comes next, in Pillar 3: Design Criteria.
Watch: Data Requirements for Territory Design
Frequently Asked Questions
What data do I need to design sales territories?
Four layers: customer and revenue data from your CRM, external market-potential data, workload measures like account counts by call frequency, and structural data such as current assignments, rep locations, and constraints. Revenue plus one potential metric is the minimum viable set.
Where can I get market potential data?
Business-count databases by industry and employee size, census demographics at the ZIP or ZCTA level, and industry-specific syndicated data (prescription data in pharma, for example). Your industry association is often a good place to start.
What file format does AlignMix import?
Excel spreadsheets, and clipboard paste, one row per ZIP, county, or account. A clean file loads in under a minute, and an import can update an existing alignment without rebuilding it.
Continue the series: Pillar 3, Design Criteria, or get our team’s help assembling the data with territory design services.