Quota Allocation Agent

The agent runs when a new year starts or a territory changes. This keeps quota allocation tied to the planning decisions that affect the team, rather than recalculating quotas continuously.

• Trigger: A new year starts or a territory changes
• Runs: When quotas need to be proposed, not continuously

To understand what each territory could produce, the agent pulls its account count, segments, and installed base. This gives the allocation a view of territory potential instead of treating every patch as equal.

• Fields: Account count, segment, and installed base by territory
• Scope: Accounts assigned to each territory

Next, the agent pulls what each rep has historically attained, along with last year's quota. This connects the potential in each territory with the person carrying the number and gives the next step a basis for comparing the new proposal with last year.

• Scope: Attainment history by rep
• Include: Last year's quota for each rep

The agent ranks the territories by sales potential using their account count, segments, and installed base. It does not use team headcount, so a territory's position reflects what the accounts could produce rather than how many reps cover it.

The agent distributes the team number across reps using the territory rankings and each rep's attainment history. It flags any proposed quota that is more than 20% above last year's quota, so leadership and RevOps can see where the largest increases sit before setting the final numbers.

Finally, the agent emails leadership and RevOps the proposed quota for each rep and the working behind it. The proposal shows how territory potential and attainment history shaped the allocation, while the decision on the final numbers stays with them.

• Recipients: Leadership and RevOps
• Include: Proposed quotas, territory potential, attainment history, and flags for increases above 20%
• Status: A proposal, not the final quota allocation