Sandbagging in sales: Why your forecast is missing and how to fix it

43% of sales organizations miss their forecasts by 10% or more. If that number describes your last two quarters, the usual suspects get blamed: territory coverage, competitive losses, macro headwinds.

The one that rarely gets named is sandbagging.

The deal is real, the buyer is ready, but the rep has a reason to wait.

For sales leadership, the cost compounds fast. A sandbagged forecast doesn't just create a one-quarter miss. It breaks financial planning, erodes board confidence, and forces reactive decisions on headcount and budget that should have been made weeks earlier.

What follows is how to identify it, understand what's actually driving it, and fix the system rather than the symptom.

TLDR

• What it is: Reps deliberately delay or underreport deals to protect comp, avoid quota hikes, or carry wins into the next period.
• Who does it: Reps in high-stakes quota environments with comp caps, accelerators, or quarterly resets. It's more common in enterprise and SaaS sales where deal sizes are large and cycles are long.
• How to detect it: EOQ deal concentration (35%+ of monthly revenue in the final week), deal velocity anomalies by rep, wide forecast accuracy variance across the team, stage churn, and low activity-to-deal-size correlation.
• Root causes: Comp caps that kill incentive after 150% attainment, quota compression from overperforming, quarterly resets, and stage definitions that let reps park deals without detection.
• The fix: The comp plan, stage definitions, and pipeline review format. Audit the comp plan, redefine stages around buyer actions, run pipeline reviews that ask "what changed" instead of "what's closing," and measure forecast accuracy as a leadership competency.
• How Avoma helps: Conversation intelligence automatically captures deal signals from every call, making it harder for reps to misrepresent pipeline status because the conversation record exists independent of what they log.

What is sandbagging in sales

Sandbagging in sales is when a rep intentionally delays closing a deal or underreports its pipeline stage to protect their comp, manage quota pressure, or avoid a target hike next year.

A rep who closes a deal but delays the signature by two weeks so it lands in next quarter's numbers is sandbagging. A rep who has a deal at verbal agreement but keeps it marked as "proposal stage" in the CRM is sandbagging. Both know what they're doing.

Separating this from conservative forecasting matters because the two are unfairly lumped together. A rep who says, "I think this deal is 60/40 because the champion hasn't confirmed budget," is reading the uncertainty accurately. A rep who says "this deal is maybe a Q3 thing" when the buyer asked for an invoice last week is sandbagging. The difference is whether the rep is sharing their honest read or managing what leadership sees.

SaaS and enterprise sales see more of it than other segments. The reasons are structural. Deal sizes are large enough that the timing of one signature can meaningfully affect a rep's quarterly comp. Sales cycles are long enough that a rep can credibly claim a deal "just wasn't ready" without raising flags. And quota mechanics in enterprise orgs give reps multiple period boundaries to exploit every year.

The anonymized scenario plays out constantly: An enterprise rep has a $200K ARR deal that's ready to sign in week 3 of Q2. Their Q2 quota is already covered. If this deal closes in Q2, it signals to leadership that their Q3 target should be higher. So the rep delays the contract by 10 days. The deal lands in Q3, it seeds the new quarter strong, and the rep avoids a quota hike. Leadership forecasted a Q2 shortfall and then saw an artificial Q3 spike. Forecast credibility takes the hit.

Why reps sandbag (and it's not always greed)

Sandbagging looks like a trust problem between a rep and their manager. It's a signal that the comp plan has a design flaw.

Quota compression is the most common driver. When a rep hits quota early in the quarter, leadership interprets it as evidence that the target was set too low. Next quarter’s number goes up. Reps who've seen this pattern learn to pace themselves. Sandbagging becomes insurance against a target that punishes overperformance.

Comp caps make it worse. Many SaaS comp plans cap accelerated earnings at 150% of quota. Once a rep hits that ceiling, every additional deal they close this period generates zero incremental comp. The math is obvious: Hold the deal, let it count next quarter when the accelerator resets, start the new period ahead. It's rational, not malicious.

Quarterly resets create the same incentive from a different angle. A rep who closes in week 2 of Q1 starts Q2 at zero with a potentially higher target. A rep who holds that deal until week 1 of Q2 starts the quarter with a win on the board. Most reps will take the outcome that doesn't leave them starting Q2 at zero.

Manager pressure dynamics compound all of this. If forecast misses lead to more coaching scrutiny, undercommitting and overdelivering becomes the rational strategy. The rep who calls $300K and closes $300K looks fine. The rep who calls $500K and closes $420K is in a 1:1 explaining themselves. Over time, reps learn what the system rewards.

Misaligned stage definitions give reps the mechanism to act on all of this. When a "proposal stage" can mean anything from "sent a deck" to "negotiating final terms," a rep can park a deal mid-funnel for weeks without detection. There's no audit trail, no buyer action required, no flag raised. The deal sits, invisible, until the rep is ready to move it.

Every rep who sandbagged made a rational calculation based on the system they're in. Worth asking why the system made this the smart move.

How to detect sandbagging before it breaks your forecast

Most pipeline reviews focus on deal status. The data that actually reveals sandbagging is deal velocity.

Here are the red flags one should watch out for: 

1. EOQ deal concentration: Pull the last 8 quarters of weekly close dates by rep. Chart what percentage of each rep's monthly revenue lands in the final week of the month. In a healthy org, that number ranges from 20% to 25%. When it consistently hits 35% or higher for a specific rep, and the deals landing in week 4 are the same ones that were "mid-stage" in weeks 1 and 2, you're looking at sandbagging patterns.

2. Deal velocity anomalies by rep: Track average days-in-stage per rep compared to the team median. Sandbagging shows up as artificially long mid-quarter stage durations, followed by sudden compression at period-end. A deal that sat in "negotiation" for 6 weeks and then closed in 3 days at the end of the quarter didn't suddenly accelerate. The rep moved it when they were ready.

3. Forecast accuracy variance by rep: Some reps consistently forecast within 5% of actuals. Others miss by 20% or more while hitting or exceeding quota. The rep who underforecasts and overdelivers every quarter isn't a conservative planner. They're managing their numbers. Pull forecast accuracy by rep for the last 4 quarters. Wide variance in the underforecast direction is a signal.

4. Stage churn patterns. Deals that move backward and forward between stages indicate fake progression. Healthy deals move forward through a pipeline because buyer commitment advances. A deal that bounces between "proposal" and "discovery" multiple times is being driven by the rep's timing, not buyer behavior.

5. Low activity-to-deal-size correlation. A rep closing a $150K deal with 4 logged activities in the CRM across a 90-day cycle should raise a question. Either they're under-logging (which is a data problem) or the deal was further along than the pipeline reflected for most of that cycle.

The data for all five checks is almost always already in your CRM. It just hasn't been pulled this way.

The leadership playbook: 3 steps to stop sandbagging

Behavioral coaching on top of a broken incentive structure produces nothing except a rep who gets better at hiding deals. Fix the system first.

1. Fix the system, not the behavior

Start with the comp plan. If you have a cap at 150% of quota, reps have a mathematically rational reason to hold deals above that threshold. Removing the cap or raising it significantly is the single highest-leverage change you can make. Rolling quotas, where quota is calculated on a trailing basis rather than hard quarterly resets, remove the incentive to bank deals across period boundaries. Extending accelerators past 100% attainment keeps the close incentive alive throughout the quarter.

Redefine your stages around buyer actions, not internal opinion. "Proposal stage" means nothing if it doesn't require a specific buyer commitment. A stage definition like "mutual action plan agreed and shared with buyer" is something a rep can't fake indefinitely. Either the buyer agreed to it, or they didn't. Buyer-action-gated stages remove the mechanism reps use to park deals mid-funnel.

Set quotas using bottom-up forecasting instead of last year's number plus a growth multiplier. Quotas that reps believe are achievable don't generate the same sandbagging behavior as targets that feel arbitrary. When reps trust the number, they have less reason to protect themselves from it.

Schedule a comp plan review with finance and HR in the next 30 days. Come in with one specific change that removes the incentive to hold deals across period boundaries.

2. Build pipeline transparency without interrogation

Weekly pipeline check-ins should be built around one question: "What changed since last week?" That framing normalizes deal stalls and slips instead of punishing them. A rep who says "the champion went dark" is giving you real information. A rep who says "still looks like this quarter" in response to "is this closing?" is giving you nothing.

Forecast banding reduces the precision pressure that drives undercommitting. When leadership commits to a range ("we're projecting $4.2M to $4.8M") rather than a single number, reps don't need to sandbag their forecasts defensively to avoid missing a point estimate. The target becomes a range within which they can operate honestly.

Avoma changes this dynamic. It automatically captures deal signals from every sales call (what objections came up, whether a decision-maker was on the call, and what next steps the buyer committed to) and syncs that data directly to the CRM without relying on the rep to log it. Leaders can cross-reference what was said in calls against what's showing in the pipeline. Sandbagging becomes harder to sustain when there's a real-time record of where every deal actually stands.

Run one pipeline review this week using "what changed" as the opening question. See how the information quality compares to a standard close-date review.

3. Measure and reinforce forecast accuracy as a leadership competency

Most orgs track quota attainment and ignore forecast accuracy by rep.

A rep who forecasts within 5% of actuals for three consecutive quarters demonstrates a skill that has direct value to the business. It means leadership can plan headcount, budget, and resource allocation with real confidence. That skill deserves recognition, not just the rep who happened to close the biggest deal.

Track forecast accuracy per rep over rolling quarters. Publish the data internally. Recognize the top forecasters explicitly. For the outliers who consistently underforecast by 15-20% while overachieving, the conversation is data-driven: "Your forecasts have missed by 18% for two quarters. Walk me through how you're thinking about your pipeline." That's a coaching conversation, not an accusation. And it's one the data supports.

Avoma's Forecast module helps here, too. Reps submit forecasts directly on the platform, and weighted-amount metrics calculate totals based on deal-stage probability rather than total pipeline value. The Commit, Open Deals, and Pipeline Coverage widgets all reflect probability-adjusted numbers, and the Forecast Submission Deals table includes a Weighted Amount column so leaders can see the likely-to-close value for every individual deal. That gives you a realistic baseline to measure rep forecast accuracy against, and not just what they called, but what the deal data actually supported.

Pull forecast accuracy by rep for the last 4 quarters. Identify the top 3 forecasters. Recognize one of them publicly this week. Coach one of the bottom 3 individually.

Quick self-audit: Is sandbagging a problem in your org?

Check every item that applies to your org.

• ‍4 or more checked: High sandbagging risk. Move to system fixes immediately. Start with the comp plan.‍
• 2-3 checked: Moderate risk. Begin the leadership playbook. Prioritize stage redefinition and weekly pipeline check-in format.‍
• 0-1 checked: Low risk. Audit your comp plan and stage definitions anyway. Prevention is cheaper than detection.

Conclusion

Sandbagging survives in orgs that treat it as a character problem. It disappears in orgs that treat it as a system problem.

Fix the comp plan. Redefine stages around buyer actions. Measure forecast accuracy as a performance metric. 

Clean pipeline data is the output, and it's the foundation for financial planning, headcount decisions, and board conversations that don't require significant caveats.

Avoma connects both sides of this. Call data captured automatically from every meeting tells you what's actually happening in deals. The Forecast module tells you whether reps are submitting numbers that reflect that reality. Together, they give you the ground truth your forecast has been missing.

See how Avoma helps sales leaders build forecasts they can trust. Explore Avoma with a free trial, or schedule a demo to see how it helps teams build more accurate and reliable forecasts.