Why Nobody on Your Team Is Hitting Quota

Quick answer: When almost nobody on a sales team is hitting quota, the cause is one of two things, and they do not get the same fix. Either the org was given more work than it has the capacity to do, or it was given work it does not have the capability to do. A capacity problem is arithmetic: not enough pipeline, not enough sellers, not enough selling hours, too big a number spread across too few people. A capability problem is that the work itself is not being done well, so deals stall in the middle, discovery is thin, the forecast lies, and adding more pipeline or more heads just produces more of the same result. The fastest read is the shape of your attainment. If most reps land in a bunch just under the bar, that’s capacity. If a small handful clear it and everyone else is nowhere close, that’s capability. Cutting the number fixes the first one and hides the second one for about ninety days.

Key takeaways

• A miss across the whole team is either a capacity problem or a capability problem, and most orgs treat both by changing the number.
• Capacity is arithmetic you can fix with heads, pipeline, territory, and time. Capability is the quality of the work, and no amount of arithmetic fixes it.
• The distribution of attainment tells you which one you have faster than any dashboard does. Bunched under the bar is capacity. A few heroes and a long tail is capability.
• A quota built by dividing the board’s number by headcount is not a quota, it’s a wish with a name on it.
• Lowering the number buys a quarter. It also reprices the same broken system, and you will be having this conversation again in two quarters.
• The CRO conversation with the board is different depending on the answer: capacity is an ask for resources, capability is an ask for time.
• The mix matters. Most orgs have some of both, and the mistake is spending on the capacity half because it’s the half you know how to buy.

Why is nobody on your sales team hitting quota?

Because either the number is bigger than what the org can physically produce, or the org cannot do the work the number assumes, and most leadership teams respond to both with the same move. They go at the number.

Every bad quarter ends in some version of the same meeting. The number was too aggressive. The territories were uneven. Marketing didn’t deliver. We’ll recut, we’ll rebalance, we’ll set a realistic number for next year and get everyone back to feeling like they can win.

Sometimes that’s exactly right. Sometimes the number really was fiction and the fastest honest thing a CRO can do is say so out loud.

But here’s what makes it dangerous. Changing the number always looks like it worked, at least for a quarter, because attainment is a ratio and you just changed the denominator. Nothing about how your org sells changed at all. You made the measurement kinder.

Think about a truck at the bottom of a hill that isn’t moving. It’s either loaded past what it can pull, or the engine is shot. From the outside those look identical. Only one of them starts moving when you take weight off.

What’s the difference between a capacity problem and a capability problem?

Capacity is how much work the org can do. Capability is how well it does the work. Capacity is a math question and capability is a competence question, and a CRO who blends them will spend money in the wrong place for two years running.

Capacity problems look like this. You have twelve reps and a number that needs eighteen. Ramp is six months and you hired in month five. Pipeline coverage is thin because the top of funnel never recovered from a cut. Reps are spending most of the week on things that are not selling. Territories are lopsided and four people are sitting on accounts with nothing left in them.

All of that is arithmetic. You can buy your way out of arithmetic. More sellers, more pipeline, fewer non-selling tasks, a better cut of the map.

Capability problems look like this. Win rate has been flat or sliding for a year. Deals die in the middle, after a demo, in a stage nobody can quite name. Reps qualify differently from each other and every manager blesses a different definition of a real deal. The forecast is built on rep optimism and it misses in the same direction every quarter. Ramp is long not because onboarding is long but because there’s nothing to onboard people into.

None of that is arithmetic, and this is the part that costs CROs their jobs. Pour pipeline into an org with a capability problem and you get a bigger pile of deals that die in the middle. Hire six more reps and you get six more people who will produce what your current people produce, which is the thing you were trying to fix.

More of a broken motion is just more broken motion, at a higher cost per unit.

How do you tell which one you have?

Look at the distribution of attainment, not the average. The average tells you that you missed. The shape tells you why.

Line up every rep by attainment and look at the picture.

If most of the team is bunched somewhere just under the bar, say the bulk of your reps landed in the same neighborhood short of the number, the work is happening and there isn’t enough room to do enough of it. That’s capacity. The org knows how to sell, it ran out of runway, hours, or pipeline.

If two or three people cleared the number and everybody else is at a fraction of it, that’s capability. Your top performers have a method and nobody wrote it down. This is the heroic org, and the number is not the problem, the number is just where the problem shows up.

Then pressure test with four things that don’t lie:

• Win rate over the last four quarters. If it’s flat while pipeline grew, you have a capability problem and you’ve been paying for it with volume.
• Where deals die. Late-stage death after a good demo is almost always a discovery problem wearing a pricing costume.
• Forecast accuracy by manager. If they miss in the same direction every quarter, nobody is inspecting against a standard, because there isn’t one.
• Ramp, measured in weeks, as a number someone actually knows. If nobody knows it, that answer is itself the finding.

Most orgs have some of both. That’s fine and it’s normal. What’s not fine is spending all your money on the capacity half because that’s the half you know how to buy.

How do you know if your quota is too high?

Build the number from the bottom and see if it survives. Take your actual win rate, your actual average deal size, your actual cycle length, and the actual amount of qualified pipeline a rep can get in front of in a quarter, then multiply it out. That’s what the org can produce with the org you have today.

If the quota you handed out is meaningfully above that, the number is too high and everybody in the building already knows it.

Most quotas are not built this way. Most quotas are built by taking the board’s growth number, subtracting what you think renewals will cover, dividing the rest by heads, and adding a cushion because attainment is never one hundred percent. That’s not a plan. That’s a wish with names attached to it, and it gets discovered in week eleven of Q1.

The bottom-up number does something else for you too. It shows you exactly which input has to move. If the math only works when win rate jumps eight points, you have not set a quota, you have quietly assumed a capability improvement nobody scheduled, funded, or is accountable for.

Write that assumption down. If your plan requires the org to get better at something, name the something and name who owns it. Otherwise the plan is that everyone tries harder, and we’ve all watched how that ends.

What percentage of reps should hit quota?

Whatever percentage you designed the comp plan around, and the real problem is that most orgs never decided. There is no universal law here. Some companies build plans where the majority of sellers should clear the bar and the top end is paid heavily for going past it. Some build stretch plans where hitting is genuinely hard and the accelerators are the point. Both are defensible. Not choosing is not.

So make it a decision. Pick the share of the team you expect to hit, tell finance, tell the board, and then measure against that instead of against a benchmark you read somewhere.

What matters more than the percentage is the shape underneath it, and this is where a CRO earns the room. An org where a wide middle of reps lands close to target has a system. An org where the number gets made by three people and the rest of the team is decoration has heroics, and heroics has a price you pay in retention, in ramp, in margin, and in the forecast nobody believes.

Same attainment percentage. Completely different company.

What happens when you lower the number?

You buy one quarter, and you reprice the exact same system. Attainment goes up because you changed the denominator, comp gets paid, the room exhales, and none of the reasons deals were dying in the middle got touched.

Then it comes back. It usually comes back with interest, because now the board has a lower number and expects it to be hit, and the next miss is much harder to explain.

Lowering quota is the right call when the number was arithmetic fiction. If the plan required capacity you never hired and pipeline you never had, fix it and say so plainly. That’s leadership, not retreat.

Lowering quota when the real issue is capability is where it turns expensive:

• Reps who were struggling to qualify still can’t qualify. – You’ll see it again in a soft forecast.
• Managers who inspect deals but don’t develop anybody still don’t develop anybody. – Nothing improves between this quarter and next.
• Ramp still runs long with nothing to ramp into. – You pay full salary for months of nothing, twice a year, every year.
• Your best reps notice the bar moved. – Some of them leave, and they’re the ones who were carrying it.

That last one is the bill nobody puts in the deck.

What do you do about a capability problem?

Define the work, then hold the org to the definition. Capability problems are not fixed with motivation, a new tool, or a kickoff. They’re fixed by writing down how selling gets done here and making it the same for everybody.

Start narrow, because a CRO trying to fix everything in a quarter fixes nothing.

One definition of a real deal. Written down, not a slide. What has to be true before a deal advances, and what a manager has to see before they approve it. Everything downstream depends on this: what the forecast counts, what coaching looks at, what a new rep learns first.

One way to run discovery. If you ask ten reps how they do discovery and get ten answers, you don’t have a discovery approach, you have ten people improvising. Deals that die in the middle almost always died in discovery and took four months to show it.

Managers who coach against that standard. Not “where is it and when does it close.” That’s inspection. Inspection tells them what happened. Coaching changes what happens next, and it’s the only real multiplier a CRO has, because it’s the only thing that touches every rep every week.

Ramp as a measured number. Weeks to first deal, weeks to full productivity. If you can’t say it, you can’t plan capacity, which means your capability problem is also quietly a capacity problem.

Pick one of these, change it deliberately, write down what you expect it to move and where that metric stands today, and check in ninety days. A quarter where you kept the gain is a different quarter than one where you just made the number.

What do you tell the board when the team misses?

Tell them which of the two problems it is, because it determines what you’re asking them for. A capacity miss is an ask for resources. A capability miss is an ask for time. Boards will grant both, but they will not grant either to a CRO who can’t tell them which one they’re funding.

Capacity sounds like this: here’s the bottom-up math, here’s the gap between what the org can produce and the number, here’s what it costs to close it in heads or pipeline, here’s when it lands given ramp.

Capability sounds like this: our win rate has been flat for four quarters while pipeline grew, deals are dying in the same place, here’s the specific thing we’re changing, here’s the metric it should move, here’s the ninety-day checkpoint.

The second conversation is harder and it’s the one that saves the year. A CRO who walks in asking for six more reps to fix a win rate problem is asking the board to fund a bigger version of the miss.

And going back to the truck at the bottom of the hill: take weight off a truck with a blown engine and all you’ve got is a lighter truck that still isn’t going anywhere.

How do you get an honest read on your own org?

Get an outside look at how much of your current performance is system and how much is force, before you set next year’s number. The Four Orgs Assessment and the PCOS Capability Assessment at salesgrowth.com take about twenty minutes and they’ll tell you whether you’re arguing about the quota or about the org.

Frequently asked questions

What is quota attainment?

The percentage of a rep’s assigned quota they actually closed in a period, and the percentage of the team that cleared their number. Both get called attainment, which is part of why these conversations go sideways. Ask which one somebody means before you react to it.

Should you lower quota in the middle of the year?

Only if the number was built on capacity you never got, and only if you say plainly why. Mid-year cuts made to protect comp in an org with a capability problem teach the team that the bar moves when it’s hard, and your best reps are the ones who read that signal fastest.

Is high sales turnover a capacity or a capability problem?

Usually capability, showing up as a capacity problem. Reps leave when they can’t see a path to the number, and constant backfilling keeps a chunk of your headcount permanently in ramp, which then reads on the dashboard as not enough capacity.

Can you fix a capability problem by hiring better reps?

Not at scale. Hiring talent works when you need two people and you have a great brand. It stops working when you need twenty, because you end up back at the same distribution, a few strong performers and a long tail, and now you’ve paid a premium for it.

How much pipeline coverage do you actually need?

Your own win rate tells you, plus a margin for slip. Coverage ratios get repeated as fixed rules, but a ratio borrowed from another company with a different win rate and a different cycle length is just a number you’re comfortable with, not one you can plan on.

Should every rep carry the same quota?

Only if every territory can produce the same amount, which is rarely true. Uneven territories with even quotas is one of the most common capacity problems and one of the easiest to fix, and it often gets misread as a performance problem in the people sitting on the thin patches.

How long does it take to fix a capability problem?

Longer than a quarter, shorter than most leaders fear, because the first move is narrow. Defining what qualifies a deal to advance and what a manager must see before approving it can be put in place inside a quarter, and it changes what the forecast counts almost immediately.

About the source

This article comes from A Sales Growth Company (ASG), the creator of Gap Selling and Problem-Centric® Selling and the architect of the Problem-Centric Operating System (PCOS™). It builds on the Four Orgs model described in The Modern Sales Org, where the heroic org, the random org, the peacock org, and the compounding org each miss for different reasons. To see where your org stands, visit salesgrowth.com.

Sources

• The capacity versus capability distinction, the Four Orgs model, and PCOS are ASG frameworks.
• No third-party statistics are cited in this article. The attainment distribution test, the bottom-up quota build, and the four diagnostics are offered as diagnostic practice, not as findings from a specific study.