Base salary, target variable and the number they handed you. We'll tell you where the plan sits against what's normal, and what it asks of your patch. These are example numbers; type yours over them.
Divide your quota by your on-target earnings. That one number tells you more about the plan than the plan will.
Somewhere between 4 and 6 is the usual range for mid-market SaaS and cloud reps: the company expects to pay you roughly a fifth of what you bring in. Below 3 is unusual, and usually means a ramp quota, an overlay role, or a plan with a catch in it. Six to eight is enterprise at a big CSP, and it needs a strong pipeline behind it. Eight to ten is strategic and named-account territory, where you'll need three to four times coverage and a patch that can produce it. Above ten, the plan is asking the territory for something it may not have.
The second number that matters is variable as a share of OTE. Under 40% and the quota matters less than it looks; over 60% and it's most of your pay, so treat it like one. And if you closed last year, the growth the new number implies is the honest measure of how much harder this year is.
None of this says the number is wrong. It says where it sits. Whether the patch can produce it is Territory Check, and how much pipeline it takes is Pipeline Check.
I've spent a lot of years helping customers buy complicated technology. For six of them I led partner sales teams at AWS. Before that F5, Red Hat, and a couple of storage companies you've probably forgotten. Before all of that, 20 years as a Marine.
Along the way I've been the seller defending the deal, the partner trying to help, the manager asking annoying questions, and the guy one level up explaining why the forecast moved again.
QuotaBird is where I put the things I've found useful. Most of the tools are free. Most take a few minutes. None of them require you to adopt a new sales religion. Use whatever helps.
Rarely just one of them. Usually a couple at the same time, quietly making each other worse.
The forecast call has become the job. Your manager wants a status on everything by noon, the CRM wants a next step on every line, and the customer is the last person you talk to each day.
The pipeline looks better than it really is. Plenty of opportunities in the CRM, but once you ask about budget, timing and who actually wants the thing, the number gets smaller fast.
The partner likes you, but nothing is happening. Plenty of meetings, maybe a joint deck. Nobody can point to the accounts where the two companies are actually trying to win something together.
The team is busy, but there isn't much rhythm. The forecast call happens. The one-on-ones happen. Nobody is sure what the team should do differently this week to make next quarter better.
The number from above doesn't match what you see below. Leadership has a growth number. Your team has a pipeline. You're the one who has to explain why they disagree without sounding like you've already given up.
A team can be behind plan for a lot of reasons. One seller needs help getting in front of customers. Another is doing fine and wants you to stay out of the way. Someone else thinks the year is already gone. Sometimes the rep is fine and the territory, the comp plan or the pipeline they inherited isn't. The useful part is figuring out which one you're dealing with before you fix the wrong one. That's what the tools here do, one deal, one rep, one territory at a time. It's also most of what I do.
Sometimes a calculator isn't enough. If you're stuck on a deal, an account, a partner, a territory, a QBR or a federal problem, I'm happy to look at it with you. Here's exactly how it works:
If I don't think I can help, I'll tell you.
If it's something that takes more than a conversation, we can figure that out too. I also build fedhoo, a federal market research tool.