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

Vaishali Badgujar

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 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 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 "proposal stage" in the CRM is sandbagging. Both know exactly what they're doing.

📌 Key takeaway: Sandbagging isn't a forecasting error. It's a deliberate choice to misrepresent where a deal stands, made because the system rewards that choice more than honesty does.

Sandbagging vs. conservative forecasting

The two get lumped together unfairly. One reflects real uncertainty. The other manages what leadership sees.

Comparison of conservative forecasting and sandbagging in sales
Criteria	Conservative forecasting	Sandbagging
Rep's statement	"I'd call this 60/40. The champion hasn't confirmed budget yet."	"Maybe a Q3 thing," when the buyer asked for an invoice last week.
What it reflects	An honest read of deal risk	A deliberate delay or misreport
CRM stage	Matches what the buyer has agreed to	Lags behind what the buyer has agreed to
Motive	Accuracy	Comp timing, quota protection

Sandbagging shows up more in SaaS and enterprise sales than in other segments. The reasons are structural. Deal sizes are large enough that the timing of one signature can shift a rep's quarterly comp. Sales cycles are long enough that a rep can claim a deal "just wasn't ready" without raising a flag. And quota mechanics give reps several period boundaries to work each year.

Here's how it plays out in practice, based on an anonymized pattern seen across enterprise teams: a rep has a $200K ARR deal ready to sign in week 3 of Q2. Their Q2 quota is already covered. If the deal closes in Q2, leadership reads it as a sign that Q3's target should go up. So the rep delays the contract by 10 days. The deal lands in Q3, seeds the new quarter strong, and the rep avoids a quota hike. Leadership forecasted a Q2 shortfall, then watched an artificial Q3 spike. Forecast credibility takes the hit either way.

Once you can name the difference between a cautious forecast and a managed one, the next question is why reps make that choice in the first place.

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 reads it as proof the target was set too low, and next quarter's number goes up. Reps who've watched this happen 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 closed that period adds zero incremental comp. The math is simple: hold the deal, let it count next quarter when the accelerator resets, and start the new period ahead.‍
Quarterly resets create the same incentive from another angle. A rep who closes in week 2 of Q1 starts Q2 at zero, possibly with a higher target. A rep who holds that deal until week 1 of Q2 starts the new quarter with a win already on the board. Most reps take the option that doesn't leave them starting from zero.‍
Manager pressure compounds all of it. If a forecast miss triggers extra coaching scrutiny, undercommitting and overdelivering becomes the safer strategy. The rep who calls $300K and closes $300K looks fine. The rep who calls $500K and closes $420K spends a 1:1 explaining themselves. Reps learn what the system rewards.‍
Misaligned stage definitions give reps the mechanism to act on all of it. When "proposal stage" can mean anything from "sent a deck" to "negotiating final terms," a rep can park a deal mid-funnel for weeks with no audit trail, no required buyer action, and no flag raised.

⚠️ Common mistake: Treating sandbagging as a rep integrity issue and responding with more oversight. Every rep who sandbagged made a rational calculation based on the system they're in. More monitoring doesn't fix a system that still rewards the behavior.

The causes point to the system. The next step is proving it's happening in your pipeline, not just suspecting it.

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:

Common signals that may indicate sales forecast sandbagging
Signal	What to check	Red flag
EOQ deal concentration	% of each rep's monthly revenue closing in the final week	35%+ for a specific rep, especially on deals that were "mid-stage" in weeks 1–2
Deal velocity anomalies	Average days-in-stage per rep vs. team median	Long mid-quarter stalls followed by sudden close-out compression
Forecast accuracy variance	Forecast-to-actual gap by rep, last 4 quarters	Consistent underforecasting of 15–20%+ while hitting or beating quota
Stage churn	Deals moving backward and forward between stages	Repeated bouncing between stages with no buyer-driven cause
Activity-to-deal-size correlation	Logged activity volume vs. deal size and cycle length	Large deals closing off a thin activity trail

A deal that sat in "negotiation" for six weeks and then closed in three days at quarter-end didn't suddenly accelerate. The rep moved it when they were ready to.

📊 Data point: in a healthy pipeline, EOQ close concentration typically runs 20–25%. Anything sustained above 35% for one rep, on deals that look mid-stage weeks earlier, is worth a direct conversation.

Detection tells you where the problem lives. Fixing it means changing what the system rewards.

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.

How to execute this: schedule a comp plan review with finance and HR in the next 30 days. Bring one specific change that removes the incentive to hold deals across a period boundary, and put a decision date on the calendar.

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.

💡 Pro tip: Avoma captures deal signals from every sales call automatically, including objections raised, whether a decision-maker joined, and what the buyer committed to next. That data syncs to the CRM without depending on the rep to log it, so leaders can check what was said on a call against what the pipeline shows. Sandbagging gets harder to sustain when a real-time record of every deal already exists.

How to execute this: run one pipeline review this week using "what changed" as the opening question, and compare the quality of what you hear against 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.

✅ Best practice: track forecast accuracy per rep across rolling quarters, publish the data internally, and recognize the most accurate forecasters explicitly, not just the reps who closed the biggest single deal.

For the outliers who consistently underforecast by 15–20% while overachieving, the conversation is data-driven, not accusatory: "Your forecasts have missed by 18% for two quarters. Walk me through how you're reading your pipeline."

Avoma's Forecast module supports this directly. Reps submit forecasts on the platform, and weighted-amount metrics calculate totals from deal-stage probability rather than raw pipeline value. The Commit, Open Deals, and Pipeline Coverage widgets reflect those probability-adjusted numbers, and the Forecast Submission Deals table includes a Weighted Amount column showing the likely-to-close value for every deal. That gives you a real baseline to measure rep accuracy against: not just what a rep called, but what the deal data supported.

How to execute this: pull forecast accuracy by rep for the last four quarters, identify your top three forecasters, recognize one publicly this week, and coach one of the bottom three individually.

The framework fixes the system. The self-audit below tells you how urgently you need to run it.

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

Check every item that applies to your org.

☑ Forecasts miss targets by 10% or more more than twice per year

☑ 30% or more of monthly closures happen in the final week of the month

☑ Rep forecast accuracy varies widely across the team (some within 5%, others off by 20%+)

☑ At least one rep has hit your comp cap more than once in the past year

☑ Stage definitions reference time ranges rather than specific buyer actions

☑ Pipeline reviews focus on expected close dates rather than deal velocity or stage duration

‍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.

Frequently Asked Questions

What's the difference between sandbagging and conservative forecasting?

Conservative forecasting is when a rep reports uncertainty they genuinely feel about a deal's outcome. Sandbagging is when a rep withholds information they have. A rep who says "I think this deal is about 60/40 because we haven't confirmed budget" is forecasting conservatively. A rep who has verbal agreement but keeps the deal in an early stage to delay the close date is sandbagging. The difference is whether the rep is sharing their honest read or managing what leadership sees.

Why do sales reps sandbag deals?

Reps sandbag because the comp plan or quota structure creates a rational incentive to do so. The most common drivers are comp caps (no incremental comp above 150% quota means holding deals until next period), quota compression (hitting quota early signals the target was too low, raising it next year), quarterly resets that punish closing early, and manager pressure dynamics where undercommitting and overdelivering is safer than missing a called number. Sandbagging is almost always a system design problem, not a character flaw.

How do you detect sandbagging in a sales pipeline?

The most reliable method is analyzing deal velocity data rather than deal status. Pull weekly close date distributions by rep and look for EOQ concentration (35%+ of monthly revenue landing in the final week). Track average days-in-stage by rep and compare to team medians. Look for stage churn patterns where deals regress and then suddenly jump to closed. Cross-reference forecast accuracy by rep, specifically reps who consistently underforecast while overachieving quota.

Does fixing sandbagging require punishing reps?

Rarely. Most sandbagging is a rational response to a system that incentivizes it. The fix is to remove those incentives: adjust comp caps, redefine stages around buyer actions, and build pipeline reviews that reward transparency rather than punish misses. When behavioral intervention is needed, the conversation should be grounded in specific data (velocity patterns, forecast variance) and framed as a coaching discussion rather than an accusation. Repeated, deliberate pipeline misrepresentation after system fixes are in place is a different matter.