Account allocation and ownership

Account allocation works when every account has a clear destination, the assignee can carry the load, and a rule covers changes. Before outreach starts, each person should be able to answer three questions: which accounts are mine, why are they mine, and who takes over when the boundary moves. A consistent rule beats a more accurate rule that keeps shifting. Territory data can remain imperfect, but it has to stay consistent or people spend time disputing assignments.¹ When setting territories, leaders should prioritize consistency over accuracy.²

Run the allocation in order

1

Define the account set

2

Set the load

3

Set the rule

4

Name ownership

5

Test exceptions

1. Define the account set
2. Set the load
3. Set the rule
4. Name ownership
5. Test exceptions

Use the same sequence whenever you divide an account pool. It makes you decide scope, capacity, routing, ownership, and exceptions before outreach begins.

Stage	What you are trying to learn	Example question
Define the account set	which accounts belong in the current allocation	"What accounts are they going to go after?"3
Set the load	how much demand the pool creates and how much each assignee can carry	How many accounts do we need, and how many can each person handle?
Set the rule	which fields determine ownership and when the rule changes	Which fields decide ownership?
Name ownership	who handles outreach, follow-up, and handoff	Who answers for this account today?
Test exceptions	what happens when an account crosses a boundary	What happens when its segment or status changes?

Define the account set

Start with a workable CRM subset that is already reasonably organized around accounts, such as past customers and opportunities, then prioritize and assign it.⁴

In an account-based model, assign SDRs and AEs to a list of target accounts.⁵ Set the tier before distribution when tiers are part of the plan, then automate account distribution by tier.⁶ The result should be a named pool with a reason each account belongs there.

After ownership is assigned, do not let the list grow by accident. For each new account, apply the same inclusion and priority rules before sending it to a person. That keeps the allocation explainable when someone asks why an account landed with them.

Set the load

Account count should reflect both the work the business needs and the work the team can absorb. Check both before deciding how many accounts each assignment can hold.

Do not use an industry average to decide how many target accounts a rep should carry.⁷ Look at the particulars of the business and calculate the number that fits those conditions.⁸

Run two calculations. The sales model asks how many accounts are needed to hit the target.⁹ The capacity model asks how many accounts one rep can handle.¹⁰ Use the sales target as a top-down calculation for the account requirement,¹¹ then compare that requirement with the available capacity.

The two calculations involve trade-offs, so the answer requires a business decision.¹² Balance the split around each person's preference, current workload, and capability.¹³ A balanced split can carry different loads, capacities, and responsibilities when each person owns work they can succeed at and that contributes to the team goal.¹⁴

Choose the routing pattern

Pick the simplest routing pattern that fits the team and the way accounts are worked. The routing method should follow the operating model so people do not debate the method account by account.

Start with round-robin routing when several reps share an incoming flow.¹⁵ Until there is a team of reps, route leads automatically in order rather than by territory.¹⁶ Territories fit field reps who visit customers in person.¹⁷ Territories can also make sense for inside sales, and most larger companies organize teams into patches even when those patches are far from their geographic location.¹⁸

For outbound account allocation, assign the target account list itself. Route each account to its owner, then keep its contacts and activity under that account. This gives the team one place to see who is responsible when several people work at the same company.

Write the ownership rule

A routing method tells you where an account goes. An ownership rule tells you who keeps responsibility when the account changes.

Set the territory with an objective method.¹⁹ Use employee counts and segment lines in the rules, and define what happens when one of those conditions changes.²⁰ Choose the ownership trigger before the team faces a disputed account. One workable trigger is the account's status when the deal is received and qualified.²¹

Write the rule in plain language. Include the fields that decide the assignment, the event that can change it, and the person who makes the call when the record is unclear. Keep the rule stable across comparable accounts. If the team cannot reach the same decision from the same fields, the rule is too loose.

Make ownership visible

An account assignment is incomplete when the owner is known but the work around that owner is vague. Record responsibility for outreach, follow-up, relationship coverage, and handoff in the account plan.

Each account should have one directly responsible individual and one owner, the account manager.²² The account executive's plan should assign relationship ownership, timing, and communication type.²³ Store those fields where the team works so a handoff does not depend on memory.

When requests keep flowing to one owner, introduce a backup contact and move smaller clients to that contact over time.²⁴ Assigned owners should share updates so other reps know whom to ask when they need context.²⁵ This creates a visible path for questions without turning every request into an ownership debate.

Test changes before launch

Run the uncomfortable cases before the first allocation goes live. Settle decisions while the team can still change the rule, before two people are working the same account.

Identify possible account-assignment problems early and role-play what to do in each scenario.²⁶ Test a segment change, an employee-count change, a qualification event, and a request that arrives through the backup contact. Record the decision for each case, then use the same wording in the operating rule.

What not to do

Before publishing the assignments, check these warnings.

• Do not move an account to another rep solely because its employee count changed modestly.²⁷
• Do not use an industry average to set the account load.⁷
• Until you have a team of reps, do not route leads by territory. Route them automatically in order.¹⁶
• Do not wait for an ownership dispute to discover how an exception should work. Identify possible problems early and role-play the response.²⁶