Quota-Setting 1:1 Conversation Script

A manager talk track for defending a quota number to a skeptical rep — using capacity math, not authority. If you can't show the math, don't have the conversation yet.

The Capacity Math (build this before the meeting)

`` Territory Capacity = (Number of realistically workable accounts) × (Average deal size) × (Realistic win rate) ÷ (Average sales cycle length in months) × (Selling months available in the period) ``

Have these five numbers on a single page before you walk in:

1. Realistically workable accounts (not the full list — the number a rep can actually touch meaningfully)
2. Average deal size (team or territory-specific, not company-wide blended)
3. Realistic win rate (this rep's trailing rate, or team average if new)
4. Average sales cycle length
5. Selling months actually available (excluding ramp months, major holidays, etc.)

The Script

"I want to walk you through how we landed on your number — not just tell you what it is. Your territory has [X] accounts we consider realistically workable this year. At an average deal size of $[Y] and a win rate of [Z]%, and assuming you can run about [N] sales cycles in parallel given a [M]-month average cycle length, the math works out to roughly $[Capacity Number] of realistic capacity over [selling months] months. Your quota is $[quota number] — that's [X]% of capacity, which means we're asking you to convert [X]% of what the territory can realistically produce. [State honestly whether that's aggressive, standard, or conservative relative to typical expectations — e.g., 'that's roughly in line with what we ask across the team' or 'I'll be straight with you, that's on the aggressive end, and here's why: ...'] I'm not asking you to just trust the number — I want you to poke holes in any of these five inputs. If the account count is wrong, or the average deal size doesn't match what you're actually seeing in this patch, tell me now, because that changes the math, not just the mood."

Handling the Common Objections

"My territory is worse than [peer]'s."

"Let's actually test that instead of debating it — run the same five inputs for their territory and yours side by side. If yours is genuinely worse on account count or deal size, that's a capacity conversation, and I'd rather fix the input than argue about the output. Let's pull both territories' numbers and look at it properly."

"This number just feels too high."

"Tell me which of the five inputs feels wrong to you — is it the account count, the deal size, the win rate, the cycle length, or the selling months? 'Feels too high' isn't something I can act on, but 'the average deal size you're using is $15k and I'm actually seeing $9k in this vertical' is something we can fix together right now."

"I'm new — I don't have enough pipeline history to know if this is realistic."

"Fair — for your first two quarters we're using team averages, not your own trailing data, which is why your quota is ramped. Once you've got 2 quarters of your own closed-won data, we'll re-run this with your real numbers, and if they're meaningfully different from the team average we used, your number moves too."

"Even if the math works on paper, I don't think I can hit it."

"That's a different conversation than the math — and it's a fair one to have. Let's run a quota-winnability self-assessment together right now — that'll tell us whether the gap is in territory, ramp, or pipeline generation, and we'll know exactly what to fix instead of guessing."

Closing the Conversation

"Here's what I want out of this: not agreement that you love the number, but confidence that the number is fair math, not a guess. If we found a real error in the inputs today, I'll take that back and get it corrected. If the inputs hold up, then our job together for the next 90 days is execution, not renegotiation."

Manager Prep Checklist (before the 1:1)

• Pull the five capacity inputs specific to this rep's actual territory (not company blended averages)
• Cross-check the rep's ramp stage — is this a full or ramped quota?
• Have territory-fairness results on hand if the territory itself was recently redesigned
• Know in advance which input, if any, is genuinely weak — don't get caught defending a number you know has a soft spot
• Decide ahead of time what you're actually willing to adjust if the rep surfaces a legitimate input error