Territory design is easiest to compare when you stop asking, “Which map should we draw?” and start asking, “Which rule should own an opportunity when two legitimate sellers could claim it?”

Four approaches cover most programs: geographic territories, named accounts, opportunity registration and hybrid rule stacks. Each can work. Each can also fail when it is used to solve a problem it was not designed for.

The right choice depends on selling motion, customer geography, service requirements, channel maturity and the amount of administration the supplier is willing to maintain. The five questions below expose the trade-offs.

Question 1: Is geography actually the best predictor of who can win and serve the account?

Geographic territories are simple when customers buy locally and service is local. A dealer in Phoenix can own a defined area; routing is fast, sales teams understand the boundary and the supplier can visualize white space.

But geography becomes blunt when:

  • customers operate in multiple states;
  • buying decisions are centralized at headquarters;
  • e-commerce creates demand outside the partner’s physical selling area;
  • one partner has specialized vertical expertise that matters more than distance;
  • installation and sales coverage are handled by different organizations.

U.S. Census County Business Patterns can help size a territory before assigning it. The 2023 CBP data provides establishment counts and other economic statistics by detailed industry and geography. Census Business Builder adds a map-oriented way to examine industries and locations. Those sources do not tell you which dealer should own an account, but they can prevent one common error: drawing equal-looking territories over very unequal opportunity pools.

Counterexample: two territories contain the same population. One contains three times as many establishments in the target NAICS and far shorter service travel. Equal map size is not equal commercial capacity.

Question 2: Do strategic customers need continuity across locations?

If yes, named-account ownership can outperform geography.

A national retailer, property manager, enterprise buyer or multi-location contractor may prefer one commercial owner even when work is fulfilled locally. Named accounts keep pricing, forecasting and executive relationships coherent.

The disadvantages are equally real:

  • the named-account list can grow until geography becomes meaningless;
  • partners may resent headquarters taking attractive accounts;
  • local sellers may stop supporting service if they receive no economic credit;
  • account hierarchies can be difficult to maintain after acquisitions or rebrands.

The solution is not simply to publish a list. Define what “named account” means:

  • parent company only or subsidiaries too?
  • new locations?
  • franchisees?
  • distributors buying on behalf of the account?
  • inbound web orders using a corporate email domain?
  • projects specified centrally but purchased locally?

Counterexample: headquarters negotiates the deal, but each branch requires local installation. Giving 100% credit to the national team can destroy the local partner’s incentive to execute.

A better model can split commercial ownership from fulfillment or service credit.

Question 3: Does the business need to reward partner-created demand?

Then opportunity registration becomes useful.

Registration protects a partner that identifies and develops a specific opportunity. It can work across geographic boundaries and can reward actual selling effort rather than mere presence on a map.

A credible registration program needs:

  • a qualification threshold;
  • evidence that the opportunity is active;
  • a protection start date;
  • an expiration rule;
  • renewal criteria;
  • duplicate-account handling;
  • a dispute owner;
  • audit history.

Without those controls, registration turns into land-grabbing. Partners register every account they can find, then wait.

Counterexample: a distributor uploads 500 company names to “protect” them. There is no contact, project, budget signal or sales activity. A true opportunity-registration system should reject that behavior rather than reward it.

Time matters. A protection window appropriate for a 30-day transaction may be useless for a 12-month capital project. Use the actual sales cycle.

Question 4: How much administrative complexity can the company support?

This is where hybrid rules win or lose.

A mature rule stack might say:

  1. named account overrides normal geography;
  2. active registered opportunity receives temporary protection;
  3. national-account policy determines multi-site ownership;
  4. service territory decides installation/support responsibility;
  5. geography handles unclaimed local demand;
  6. a documented exception owner resolves the remaining edge cases.

This can be far more accurate than any single method. It also requires reliable CRM fields, hierarchy data, timestamps, route logic and people who will actually maintain exceptions.

If the business has no clean account IDs, no partner manager and no one willing to adjudicate disputes, a sophisticated hybrid model can become worse than a simple map. Complexity does not create fairness by itself.

Use the simplest rule stack that correctly handles the majority of valuable opportunities.

Question 5: Are protection terms aligned with the commercial investment and legal context?

Territory rules are commercial policy, but material restrictions and exclusivity can have legal implications that vary by arrangement and jurisdiction.

FTC guidance on manufacturer-imposed requirements says reasonable territory and customer restrictions can be lawful under federal antitrust principles while noting that facts, competitor coordination, state law and international regimes can change the analysis. FTC guidance on exclusive dealing similarly explains that these arrangements are commonly evaluated in context and can support investment while also raising concerns in some circumstances.

That is not a template for every contract. It is a reason to avoid treating “exclusive territory” as a casual sales promise.

Before signing, define:

  • what is protected;
  • from whom;
  • for how long;
  • what performance or investment supports the protection;
  • what alternate channels remain open;
  • what happens to active opportunities after a boundary change;
  • what law governs the agreement.

Material legal terms should be reviewed by qualified counsel for the applicable market.

Speed comparison

Geography: fastest to explain and route. Good for local demand. Slow to adapt when accounts cross boundaries.

Named accounts: fast for strategic customers once hierarchy data is clean. Slow when names and ownership change.

Registration: fast to reward active selling. Administrative burden rises with duplicates and renewals.

Hybrid: slower to design, fastest at handling complex real-world edge cases once data and governance are mature.

Do not confuse configuration speed with selling speed. A rule that takes one week to design but saves months of recurring dispute can be efficient.

Cost comparison

The visible cost is software or partner-management time. The hidden costs matter more:

  • duplicate selling effort;
  • discount escalation on conflicted deals;
  • manager hours spent arbitrating ownership;
  • partner churn;
  • uncovered markets;
  • bad lead routing;
  • local service performed with no compensation;
  • protected territories that stop other capable sellers from investing.

Track those costs before deciding the current design is “free.”

Control comparison

Geography gives high routing control but low precision for multi-location customers.

Named accounts give high control over strategic relationships but can centralize too much power.

Registration gives partners control over opportunities they create but requires anti-hoarding rules.

Hybrid systems give the supplier the most control — and therefore create the biggest governance obligation. Every override should leave an audit trail.

Risk comparison

The main risks differ by model:

Model Operational risk Partner-behavior risk Data risk
Geography dead zones, cross-border accounts local monopolies stale boundaries
Named accounts local execution gaps cherry-picking bad parent-child hierarchy
Registration duplicate claims account hoarding weak timestamps/evidence
Hybrid rules collide exception lobbying inconsistent CRM logic

This table is why one universal “best practice” does not exist.

Use a scenario test before rollout

Take twenty real opportunities from the last year, including the ugly ones:

  • national account with local branches;
  • inbound website lead;
  • partner-created deal outside normal territory;
  • existing customer opening a new location;
  • e-commerce order into a protected area;
  • project requiring local installation;
  • duplicate lead from two partners.

Route them through the proposed rules without changing the rules mid-test.

If managers repeatedly need to say “we would probably make an exception,” write that exception class into policy before launch.

A practical selection rule

Choose geographic territory when customers and service are local and the market can be sized meaningfully by geography.

Choose named-account ownership when relationship continuity across locations has more value than local routing.

Choose opportunity registration when the program primarily needs to protect partner-created demand and active selling effort.

Choose a hybrid stack when the business has multiple partner types, direct sales, national accounts, digital demand and enough data/governance to maintain precedence rules.

The objective is not a beautiful map. It is a routing system that puts one accountable owner around an opportunity quickly, preserves the incentive to invest, and makes exceptions rare enough to learn from.

Add a second lens: market density versus service intensity

Two territories with equal account potential can still need different designs because the cost to serve is different.

A software reseller may support customers remotely and can tolerate a wide geography. A physical-product dealer that provides site visits, installation or warranty response may need much tighter service radii. This means territory design should model both commercial density and service intensity.

For each segment, estimate how often a normal sale creates travel, installation, training, returns or on-site support. Then ask whether the proposed owner can absorb that work without degrading response times. If not, create a separate service-credit rule rather than pretending the sales boundary solves fulfillment.

This lens is especially useful when a partner looks underproductive on revenue alone but carries a disproportionate service load. A routing model that ignores service can reward the team that sells and penalize the team that makes the promise work.

Sources

Related Reading