Territory design is a map problem, not a spreadsheet exercise.

Scoring the accounts

What usually happens: Books get balanced on account count because it is the only number everyone has. Two hundred accounts in a saturated region is treated as equivalent to eighty in a growing one, and it is not.

What we build instead: Every account scored on firmographic fit and live intent, then potential summed per territory. The target is every book within a few percent of the same opportunity, not the same headcount.

Drawing the boundary

What usually happens: State lines are an administrative boundary, not a market one. Drawing on them is how a book ends up looking tidy on a map and being wildly uneven in practice.

What we build instead: ArcGIS and four years of customer and demographic movement, so the boundary falls where the buyers actually concentrate. Zones cross state lines when the data says they should.

Making it hold

What usually happens: A territory map that lives in a slide drifts within a quarter. Someone reassigns an account manually, then someone else does, and by Q2 the balance you designed is gone.

What we build instead: Assignment written into the CRM as rules evaluated on record creation, so a new account lands with the right owner without anyone thinking about it. The map is a system, not a document.