Every territory alignment stands on five pillars: the right base geography, the right data, clear design criteria, a sound process, and a disciplined rollout. Get the first one wrong and the other four can’t rescue it, because the base geography is the unit every territory is built from, every account is assigned through, and every report rolls up by.
This is Part 1 of the series, on choosing that foundation. (Then come Pillar 2: Data Requirements and Pillar 3: Design Criteria.)
What Is a Base Geography?
The base geography is the smallest block you assign to a territory. In the US that usually means five-digit ZIP codes or counties; internationally it’s postcode areas or administrative districts. A territory is just a named collection of these units: “Territory 14 equals these 187 ZIP codes.”
Why not draw free-hand lines on a map? Because a territory made of standard units is unambiguous. Your CRM, comp plan, reporting, and reps all read it the same way. A line through the middle of a suburb is a permanent argument waiting to happen.
The Three Main Options
ZIP codes: the default for most US sales forces
With 30,000-plus mappable ZIP areas, ZIPs are granular enough to balance finely, they already sit in every customer record you own, and demographic data attaches to them cleanly. If your reps work metros or your accounts are dense, start here. (New to how ZIP boundaries work? Read what a ZIP code boundary really is.)
Counties: for large, lower-density territories
About 3,100 counties cover the US. When a single territory would otherwise hold hundreds of ZIP codes, agricultural equipment, industrial distribution, rural healthcare, counties keep the alignment manageable and the market data is often better. Just key your file on FIPS codes, not county names; our guide to county-based sales territories explains why.
Account-level: when geography isn’t the organizing idea
Named-account and vertical models assign specific customers rather than areas. Even then, most teams use a geographic base for the broad market and layer account overrides on top for the exceptions, which gives you both.
How to Choose: Four Questions
How dense is your customer base? Hundreds of accounts per metro points to ZIP codes; a handful per state points to counties or whole states grouped into multi-state territories. What resolution does your data support? If market-potential data only exists at county level, a county base may serve you better than false ZIP-level precision. Where do your constraints live? If territories must respect state boundaries for licensing, both ZIPs and counties work, though counties never cross state lines, which removes a class of edge cases. And will you mix? Many alignments run ZIPs in the metros and counties in the countryside; purpose-built software handles both in one alignment, spreadsheets handle neither well.
Common Base-Geography Mistakes
Splitting the atomic unit is the big one: assign half a ZIP to one rep and half to another and you’ve reintroduced every ambiguity the base geography exists to remove, so handle true exceptions as account overrides instead. Using ZCTA and ZIP interchangeably causes quiet errors, since Census ZCTAs only approximate ZIP codes and some ZIPs have no ZCTA at all. And choosing finer resolution than you can maintain backfires: every unit is an assignment someone has to own and update, so if your ops team can’t keep 30,000 ZIP assignments current, 3,100 accurate county assignments beat ZIP-level precision that rots.
Watch: Picking the Right Base Geography
Frequently Asked Questions
What is the best base geography for sales territories?
ZIP codes for most US sales forces with dense coverage, counties for large rural or multi-state territories, and postcode areas internationally. Many alignments mix ZIPs in metros with counties elsewhere.
Can I change base geography later?
Yes, but it’s a project, since every assignment, report, and comp reference is keyed to the base unit. Choosing well up front is much cheaper than converting later.
What does AlignMix support?
US five-digit ZIP codes and counties (FIPS), plus postcode geographies for the UK, Canada, Germany, France, Australia, Japan, and more, all included with the software.
Next in the series: Pillar 2, Data Requirements. Or see all five applied in a live alignment: book a demo.