How do I set territories and quotas that the team does not immediately game?
Build the number bottom up first, then reconcile it against the top down target, and show the team both. Bottom up means rep capacity times realistic ramp times historical productivity per rep, which is a number you can defend. If the top down target is meaningfully higher, the gap is a hiring plan or a pipeline plan, not a quota increase. On territories, balance on account potential rather than account count, publish the rules, and freeze them for the year so nobody spends December lobbying for a reshuffle. Gaming almost always traces back to one of two things: a plan that pays on something the rep can manufacture without creating value, or a plan complicated enough that only the ops team understands it. If a rep cannot compute their own commission on a napkin, simplify it.
Go deeper
5 resources, 2 India-specific, 5 link-checked.
📄 Article
✓ Link checkedIndiaFreeAdvanced
The practical method for combining top down targets with bottom up rep feedback, and the attainment bell curve to aim for: 60 to 70 percent around quota, 15 to 20 percent above, 10 to 15 percent short.
A nine step territory design framework that ends where it should, with tying territories to quota and compensation. The step most teams skip is exactly the one that causes the arguments.
The operating cadence rather than the design theory: review quarterly, change annually, roll out in phases, and the line worth quoting back to anyone defending a complicated plan, that if a rep needs a spreadsheet and a half hour meeting to understand it, it is already too late.
Splits the RevOps hiring decision into three company phases and says plainly when to outsource instead of hiring. It is the clearest answer we found to the question founders actually ask.
Territories are the half of this question people hand wave, and this session treats them as a design problem with fairness of earning opportunity as the test. That fairness test is what stops the team gaming the plan.