A company can say it wants to focus on enterprise accounts, expand in healthcare, protect strategic customers, or improve speed-to-lead.

Those statements do not become real until territory, routing, and ownership rules change.

This is where strategy gets operational. It is also where a lot of strategy quietly dies.

If the assignment logic does not match the strategic intent, the field will follow the assignment logic. Always.

Ownership rules tell the company what matters

Account ownership is not just who gets credit. It determines who pays attention.

If strategic accounts are scattered across overloaded reps, they will not receive strategic coverage. If expansion ownership is unclear, CS and sales will wait each other out. If inbound leads route to the wrong owner, speed and accountability disappear. If partner-sourced opportunities bypass territory logic, conflict becomes normal.

RevOps should force leadership to answer ownership questions clearly:

  • Does account ownership live with sales, CS, territory, named account list, or segment?
  • Who owns new logo versus expansion?
  • Who owns subsidiaries and parent accounts?
  • What happens when an account changes segment?
  • Who owns dormant customers?
  • Who owns product-led opportunities inside existing accounts?
  • How are partner-influenced deals credited and assigned?

These are not edge cases. They are the rules the field will actually follow.

Routing is a revenue control

Routing often starts as a technical workflow: if lead source equals X and country equals Y, assign to Z.

That is too narrow.

Routing is a revenue control. It determines response time, rep focus, territory fairness, customer experience, and whether strategic segments receive the right coverage.

Good routing design considers:

  • Segment priority
  • Account ownership
  • Existing customer status
  • Territory capacity
  • Language or geography
  • Product interest
  • Partner involvement
  • Named account exclusions
  • Round-robin fairness
  • SLA requirements
  • Conflict resolution

The best routing rule is not the cleverest automation. It is the rule the business can explain and defend.

The damage is measurable when this breaks. An enterprise demo request from a named strategic account sits in a generic round-robin queue for 36 hours, while two SMB reps work smaller leads immediately. By the time the account owner sees it, the buyer has already booked a competitor's call. That is not a CRM inconvenience. It is routing logic contradicting segment strategy and leaking high-intent demand.

Territory design is a strategy argument

Territory planning exposes tradeoffs.

Do we optimize for equal opportunity, geographic familiarity, vertical expertise, account concentration, growth potential, or manager span?

There is no perfect design. There are only designs that make tradeoffs explicit.

A practical territory design worksheet should include:

  • Strategic priority by segment or vertical
  • Total account universe
  • Addressable potential by territory
  • Current customer concentration
  • Rep capacity and ramp status
  • Historical performance
  • Travel or language constraints, if relevant
  • Named account assignments
  • White-space accounts
  • Expected pipeline creation requirement
  • Known conflicts and exception rules

If territory planning is only a spreadsheet exercise, it will miss behavior. Reps work what they believe they own and what they believe can pay them.

Conflict rules matter more than people admit

Ownership disputes consume management energy because the rules are usually incomplete.

Common disputes:

  • Inbound lead from an account owned by another rep
  • Former customer re-enters as a new opportunity
  • Parent company buys for subsidiary
  • Expansion opportunity appears in a customer success-owned account
  • Partner registers a deal already in active sales motion
  • Rep leaves and account reassignment creates credit ambiguity
  • Account moves from commercial to enterprise segment mid-cycle

RevOps should not wait for these disputes to become one-off executive decisions. Create a conflict policy.

A useful policy defines:

  • Default owner by scenario
  • Time-bound protection rules
  • Required evidence for ownership claims
  • Credit split conditions
  • Escalation path
  • Final decision owner
  • Documentation requirements

The goal is not to remove judgment. The goal is to prevent every conflict from becoming a custom negotiation.

Assignment rules should be inspectable

A dangerous routing system is one nobody understands.

When reps and managers cannot explain why something routed a certain way, trust erodes quickly. People start building side channels: Slack claims, manual assignments, spreadsheet lists, and political escalations.

RevOps should maintain a routing rules document that is readable by business leaders.

For each rule, capture:

  • Scenario
  • Assignment logic
  • Business rationale
  • SLA
  • Exception path
  • Field dependencies
  • Owner of rule
  • Date last reviewed

If the rule cannot be explained in plain English, it is probably too fragile.

The artifact: routing rules table

Example:

| Scenario | Rule | Rationale | Exception |

|---|---|---|---|

| Inbound from named account | Route to named account owner | Protect strategic ownership | If owner inactive, route to manager queue |

| Inbound from existing customer | Route to account CS owner and expansion AE | Avoid duplicate outreach | If support issue only, suppress sales task |

| Net-new SMB demo request | Round-robin within SMB pool | Speed and fairness | Exclude reps over capacity threshold |

| Partner registered deal | Route to territory owner with partner tag | Preserve territory accountability | Partner conflict reviewed by channel lead |

This kind of artifact prevents routing from becoming folklore.

Bottom line

Territory, routing, and ownership are not operational afterthoughts. They are the daily expression of strategy.

If leadership says one thing and assignment rules say another, the rules win.

RevOps should make sure the rules reflect the strategy the company actually wants executed.