Seventy-one percent of sales reps start the fiscal year without an assigned quota. Only 10% say they have a clear path to hitting it. And 39% of ops teams take one to two months to push a plan change live. These aren't edge cases — they're the norm, and they carry a cost that shows up not on a dashboard but in rep behavior, eroded trust, and ultimately, attrition.
In a recent RevOps Co-op webinar, Matthew Volm moderated a panel featuring Johnathan Warren, Director of RevOps at CaptivateIQ; John Houston, Associate Product Marketing Manager at CaptivateIQ; Ruchika Chopra, VP of Revenue and CX Ops and Strategy at Illumio; and Reid Bierly, VP of Revenue Strategy and Operations at Uniphore. The conversation drew on CaptivateIQ's State of Incentive Comp and State of Sales reports — surveying over 500 salespeople — to unpack where quota delays actually live, what they cost, and what closing the gap looks like in practice.
The instinct is to blame the system. It's slower than it should be. The tooling can't keep up. But according to everyone on this panel — practitioners who've collectively run sales compensation across more than a dozen companies — that instinct is wrong.
"It's not a tooling gap. The fast part is executing changes in a system like CaptivateIQ. What stretches it out is the cross-functional decision-making that precedes everything — finance, sales leadership, ops, executives — and every single loop adds days, if not weeks." — Johnathan Warren
Warren's own team experienced this firsthand. Despite entering their most recent planning cycle confident they were further ahead than the prior year, they still missed their targeted plan delivery date. Every step felt accelerated. The decisions still dragged.
Reid Bierly framed the root cause with unusual precision: the decisions that need to be made in Q3 and early Q4 are being made too late. Executives are simultaneously trying to close a year, plan a sales kickoff, and wrap up annual planning — and the temptation to introduce one more "big idea" at the 11th hour is almost irresistible.
"You have to hold back all of these interesting ideas that come up late in Q4 because it really throws off the comp plan, it throws off reps getting launched into the new year correctly. Simplicity doesn't take a lot of time. It's when we all try to introduce complexity that's what throws these things off." — Reid Bierly
Ruchika Chopra added a dimension that often gets overlooked: for organizations with mature planning processes, the delay problem doesn't necessarily live at the start of the year. It lives in mid-year changes. A single territory adjustment doesn't affect one plan — it can cascade across six: the account executive, the SE, customer success, the partner team, geo leadership, and possibly the CRO's rollup. Coordinating that in real time, under pressure, is where even well-run ops teams lose weeks.
This connects directly to the broader challenge of building processes that can absorb organizational complexity without breaking — something RevOps teams at every stage grapple with.
CaptivateIQ's research found that 93% of comp teams field questions every single payout, and reps are still spending an average of 1.6 hours per week checking their own commission math. At one company Bierly worked with, that number was four hours per week — and even after significant improvement, it landed at one hour, which he still described as "horrible."
The math isn't complicated: an hour a week, 48-50 weeks a year, multiplied across a sales org, is a lot of selling time permanently redirected to shadow accounting.
But the more insidious cost is behavioral, and Warren named it clearly:
"The first thing a rep does when they don't trust the numbers is build their own version. Shadow spreadsheets, side math, maybe now an artifact in Claude. You've got multiple sources of truth, and yours is no longer the one they believe. A comp plan exists to steer reps on where to spend their time, and the second they stop trusting it, the plan stops steering that behavior." — Johnathan Warren
He illustrated the point with a real example. CaptivateIQ built a spiff into its mid-market AE plan to incentivize self-sourced pipeline — a bet the business had modeled into its financial operating plan, including headcount and campaign spend decisions. The plans were delivered late. Despite advance communication that the change was coming, reps defaulted to last year's assumptions. The pipe gen program was slow to get off the ground.
The relationship between plan complexity and distrust runs in both directions. Chopra noted that shadow accounting isn't always a sign of distrust in the comp team — sometimes reps genuinely can't do the math without help. Plans that include new logo quotas, expansion quotas, multi-year accelerators, product spiffs, and variable renewal treatments for a single AE create a situation where even a rep who trusts their comp team can't independently verify their own number. The result is a hidden tax on manager time, ops investigation cycles, finance reconciliation, and — most importantly — rep focus.
Bierly's bluntest observation: "The comp plan is too complex, the comp plan is too complex, the comp plan is too complex." He described years when he had genuinely gotten a plan back to simplicity — high attainment, high clarity — and the erosion that followed year by year as one stakeholder after another added "just a little bit more." Fifteen percent more complexity one year, thirty the next.
"Every year it's 15% more, 30% more, 40%... and now it's a bloated comp plan again. I don't think enough executives really appreciate all their little ideas stacked on everybody else's little ideas." — Reid Bierly
This dynamic — the gradual accumulation of complexity until the plan collapses under its own weight — is one of the most persistent patterns in RevOps, and it rarely announces itself.
The attrition dimension adds another layer. CaptivateIQ's research found that 31% of salespeople have left or considered leaving over recurring comp issues. The panel was nuanced on this: no single wrong paycheck, no single late plan, drives a resignation. What drives it is accumulation.
"When the number's late, and then it's wrong, and then they're spending an hour every week doing their own math, and then their territory shifts without warning — no single one of these things on their own leads to a resignation, but they certainly accumulate. Clarity in comp won't make someone stay, but ambiguity absolutely shows up in those exit interviews." — Johnathan Warren
Bierly added texture to the attrition picture: in his experience, territory changes are a more common trigger than comp plan mechanics. A rep who had a productive territory and watched it cut in half has a clearer, more immediate grievance than one navigating a confusing multiplier structure. The trust that gets broken when a quota becomes unattainable — especially after a high-attainment year — is the kind that doesn't come back. This is one reason why compensation plan design and territory management are inseparable problems for any RevOps team serious about retention.
Chopra offered the clearest framework for defining success on the delivery side: four criteria — clarity, simplicity, speed, and trust.
Clarity and simplicity, she argued, travel together. A plan can be technically accurate and still fail if a rep can't understand it, if a manager can't explain it, and if the behavior the plan is supposed to drive isn't obvious. The priorities — new logo growth, expansion, channel-sourced revenue — have to be legible to the field, not just to finance.
Speed matters because a plan change that's been approved but not yet communicated doesn't change behavior. Reps act on what they've seen and signed, not on what leadership has decided in a meeting room.
Trust is the outcome variable. The test isn't whether finance approved the plan or whether ops executed it correctly. The test is whether the rep can see the same thing in the system, whether the manager can coach to it, and whether the commissions team can calculate it consistently.
"The mistake we make is assuming that a planning change is done when leadership approves it. It's not done until the rep understands it, the manager can coach to it, the system reflects it, and the commissions team can calculate it consistently." — Ruchika Chopra
Chopra's process at Illumio starts five months before fiscal year start. The first step: a leadership debrief with the CFO and CRO on lessons learned across plan types. The second: structured feedback collection from GTM leaders — customer success, geo, partner — on what worked and what didn't in the field. The third: a bottoms-up attainment analysis, examining patterns in the haves and have-nots to surface which plan structures actually drove behavior. That combination of top-down, field-level, and data-driven input shapes the plan design before anyone has written a single comp document.
For Bierly, the more fundamental intervention happens even earlier — at the level of organizational alignment across five interconnected variables: the rep profile talent acquisition is targeting, the job architecture those reps are hired into, territory design, comp plan structure, and quota-setting methodology. Getting one of those right while the others remain misaligned produces diminishing returns; getting all five lined up creates durable, compounding performance.
"You get those five things lined up, I will guarantee you they will have a much bigger impact than one more spiff." — Reid Bierly
His point about peanut butter quota distribution is worth dwelling on. Assigning the same quota to a rep covering the Australian market and a rep covering the U.S. enterprise segment ignores market dynamics, product mix, average selling price, and competitive intensity. The math behind a "fair" quota that doesn't account for those differences isn't fair — it's just uniform, and uniformity in the wrong places creates the exact attainability problems that drive attrition.
Even a well-designed plan, delivered on time, with clean system data, can fail if the change management around it is handled poorly. Warren and Chopra both emphasized the critical role of frontline managers — the layer of the organization that is typically not involved in strategic incentive design but is entirely responsible for translating the plan to the field.
Warren described a "breadcrumb" approach to managing this gap. Rather than waiting for a fully finished plan to communicate changes, his team drips directional information to the field in advance — through sales leadership, through enablement — so that by the time the plan is unveiled at SKO, no one is shocked by the overall shape of it. The reveal becomes a details conversation, not a structural surprise.
"By the time we actually unveil the plan at SKO, nobody's shocked by the overall shape of it. The reaction isn't, 'Wait, you're changing what?' It's, 'Okay, I knew this was coming. Now let me focus on understanding the specifics.'" — Johnathan Warren
For the leadership audience, he applies a different set of principles. North Star metrics — the behaviors the plan is meant to influence — need to connect visibly to business priorities. If the company's number one goal is top-line revenue versus services margin versus cash, the plan design will look different, and leadership needs to understand and own that through line. Surfacing a decision to an executive who should have been in the room three weeks earlier is one of the fastest ways to blow a planning timeline.
Bierly extended the change management point into enablement: communication and training are not the same thing. A brown-bag presentation about the comp plan gets forgotten. What actually sticks is structured, self-paced training where reps work through scenarios — how does this spiff calculate? What happens to my quota retirement in a split deal? — and demonstrate comprehension at a meaningful level before the plan is considered "rolled out."
The vocabulary problem is real and underappreciated. Internal acronyms, custom compensation terms invented by individual executives, and ambiguous definitions of concepts like "first year average ACV" or "incremental expansion" create confusion that flows downstream into Salesforce field logic, comp calculations, and rep disputes. Investing in clear, shared definitions before any system is configured is foundational — and often skipped. For a deeper look at how data definitions upstream affect everything downstream, this piece on data management for RevOps teams covers the underlying principle well.
CaptivateIQ's platform perspective, as John Houston framed it at the close of the session, is that solving the quota delay problem requires both the organizational practices the panelists described and a connected technical ecosystem — one where planning, incentives, and forecasting share a common data layer so that decisions can reach the field faster and with greater consistency. You can read more about how CaptivateIQ approaches incentive compensation management for revenue teams, or explore their State of Sales research for the full data behind the statistics discussed in this session.
The message from this panel isn't that quota delays are inevitable — it's that they're a symptom. The underlying condition is misalignment: between leadership decision timelines and the field's need for clarity, between plan complexity and rep comprehension, between what the system can execute and what an executive imagined on a whiteboard in November. Fixing the symptom without addressing the condition is how RevOps teams get stuck in a permanent firefighting posture instead of building the planning infrastructure that prevents the fires in the first place.
The organizations that get this right don't just reduce comp disputes and attrition. They build a field that trusts its numbers, managers who can coach to plan, and a RevOps function that operates as a strategic partner in incentive design — not a help desk for commission calculations.
Check out our blog, join our community and subscribe to our YouTube Channel for more insights.
Learn more about how CaptivateIQ helps revenue teams build, launch, and manage incentive compensation plans — and explore their resources and research to go deeper on the data behind this session.
