Setting Expansion Quotas Account Managers Can Actually Hit

Before assigning anything, pull each account manager's book and separate accounts into three buckets: accounts with real unused capacity (seats, usage tiers, or modules they have not adopted), accounts already at or near full utilization, and accounts that are flat-out shrinking. A quota built by inflating last year's total ignores that mix entirely and lands hardest on whoever happens to hold the saturated accounts.

Say one account manager's book is mostly early-stage accounts still ramping toward full seat count, while another's book is mostly mature accounts that adopted everything they are going to adopt years ago. Handing both the same growth target treats two structurally different jobs as if they were identical.

Sort every account in a book into one of three buckets before assigning a number:

• Accounts with real unused capacity, such as seats, usage tiers or modules the customer has not adopted yet.
• Accounts already at or near full utilization, where a straightforward upsell has little room left to run.
• Accounts that are shrinking, which usually need retention work before anyone should count on expansion from them.

Rather than handing someone a single book-wide number, walk through each account and ask what a realistic expansion looks like there in the next planning period: a new department onboarding, a usage tier upgrade, an add-on module tied to a workflow they already run. Summing individually sized targets produces a number the account manager can defend in a pipeline review, instead of a top-down figure they have to reverse-engineer a story for.

This also surfaces accounts nobody had flagged as expansion candidates, since walking every account forces a conscious yes-or-no on each one rather than letting the quiet middle of the book go unexamined until renewal time.

Ambiguity here causes more quota disputes than the target itself. Decide up front whether a flat renewal counts as zero toward the number, whether a downgrade inside one account can offset an upgrade in another, and whether a churned account's lost revenue gets backed out of the manager's total or absorbed elsewhere. Write the rule down before the quarter starts, not after the first dispute comes up.

A rule written after the fact almost always gets read as favoring whoever is arguing loudest in that particular quarter, which erodes trust in the whole system faster than a strict rule applied consistently would.

An account manager holding several fully adopted, flat, healthy accounts should not carry the same expansion target as one holding half-adopted accounts with obvious headroom. Give the saturated-book manager a retention-weighted target instead, credit for keeping renewal rate and satisfaction high, with a smaller expansion component. Forcing an expansion number onto a book with no realistic room to grow just teaches the manager to pad the pipeline with deals that will not close.

Books change: a champion leaves, a big account gets acquired, a module launches that suddenly makes several accounts expansion-ready. A quota set once at the start of the year and never revisited stops reflecting reality by the back half of the year. Build in a short mid-year pass where each account manager and their manager re-rate headroom on the accounts that moved, and adjust the remaining target accordingly, rather than waiting until the annual planning cycle to notice the number no longer makes sense.

A target built from careful per-account math still fails if the account manager only ever sees the final number and has to trust that the work behind it was fair. Share the account-by-account breakdown, not just the total, so a manager who disagrees with one account's headroom rating can raise it before the quarter starts rather than quietly resenting the whole number for the next twelve months.