Sales Enablement Aside—Sandbagging: How to Detect and Fix Deal Padding in Your B2B Forecast
By Rick Elmore ·
Every RevOps leader has seen it: a rep sitting on a signed deal until next quarter, or quietly logging a closed opportunity as "still in negotiation" so it lands after the current number is already safe. That's sales sandbagging, and it quietly corrupts your forecast, your capacity planning, and your ability to trust the pipeline you're staring at every Monday.
Sandbagging isn't laziness. It's rational behavior in response to how you've built comp and quota. The good news: it leaves fingerprints all over your CRM. Here's how to spot it and how to fix the underlying incentives that create it.
1. Understand why reps sandbag in the first place
Before you build detection rules, get the motive right. Reps sandbag because the system rewards it. When quotas reset hard each quarter and accelerators kick in only after 100% attainment, a rep who's already hit the number this quarter has zero incentive to pull in a deal that would be worth far more on next quarter's board.
- Quota safety: Bank deals for a slower future period to smooth out attainment.
- Accelerator timing: Push deals into a quarter where they'll cross into higher commission tiers.
- Sandbag the forecast, not the deal: Under-report confidence so a slip never counts against them.
- Manager pressure: Reps hide upside to avoid getting quota raised next year.
If you treat sandbagging as a character flaw, you'll chase individuals forever. Treat it as an incentive design problem and you can fix it structurally.
2. Watch the gap between activity and stage
The clearest tell is a deal whose activity says "hot" while its stage says "early." When a rep has logged three exec meetings, a security review, and a pricing conversation, but the opportunity is still parked in Stage 2, something is off. Real deals don't generate procurement activity while sitting in discovery.
Build a simple flag in your reporting: opportunities where recent activity volume (meetings, emails to multiple stakeholders, proposal opens) is in the top quartile but stage is in the bottom half. Those are your prime sandbag candidates. Review them by name in pipeline meetings.
3. Track time-in-stage against the deal's own history
Sandbagging often shows up as a deal that suddenly freezes. A rep moves an opportunity briskly through discovery and demo, then it sits in "proposal" for six weeks with no logged reason. Compare each deal's time-in-stage to your team's median for that stage and that deal size. Outliers that stall late in the cycle, after buying signals have already fired, deserve a hard look.
- Deals that stall in the last two stages, not the first two, are the suspicious ones.
- A stall with continued activity is sandbagging; a stall with no activity is usually a real slip.
- Watch for deals that "wake up" precisely on the first day of a new quarter.
4. Look for close-date clustering at quarter boundaries
Pull every open deal and plot its close date. If you see a suspicious pile-up in the first two or three weeks after quarter-end, that's not a coincidence, it's reps parking deals just over the line. Healthy pipelines have close dates distributed across the period based on real buying timelines, not clustered right after the pressure lifts.
Even more telling: deals whose close date has been pushed exactly one quarter, more than once, without any change in stage or activity. That pattern is a rep managing their number, not managing a customer.
5. Compare forecast category to actual behavior
Reps who sandbag the forecast keep deals in "pipeline" or "best case" long after the evidence says "commit." Audit your commit-versus-actual by rep over a few quarters. A rep who consistently closes far above their committed number isn't a hero, they're hiding pipeline. That over-delivery feels great until you realize you can't plan hiring, capacity, or cash against a forecast that's deliberately soft.
The metric to watch is forecast conversion by category. If a rep's "best case" bucket converts at 80% while the team average is 40%, they're mislabeling near-certain deals to stay safe.
6. Separate real slippage from deliberate padding
Not every stalled deal is sandbagging, and if you accuse a rep of gaming when the deal genuinely died, you'll lose trust fast. Use a consistent test: does the delay correlate with buyer behavior or with the calendar?
- Real slip: Buyer activity drops, champion goes quiet, competing priority emerges. Evidence in the account.
- Sandbag: Buyer activity stays warm, but the deal moves only when it benefits the rep's number.
The distinction lives in the activity data, which is exactly why clean CRM hygiene and automated activity capture matter so much. If you're relying on reps to manually log everything, you have no ground truth to reason from.
7. Instrument your CRM so signals surface automatically
Manual detection doesn't scale. The teams that actually eliminate sandbagging build the signals into the system so managers see flags without hunting for them. This is core RevOps work, and it's where a well-configured revenue engine earns its keep.
- Auto-capture email and calendar activity so stage-versus-activity gaps are visible without rep input.
- Set stage-progression rules that require evidence (a logged demo, an uploaded proposal) before a deal can advance or stay parked.
- Build alerts for close-date pushes, especially repeat pushes on the same deal.
- Create a weekly "hidden pipeline" report that lists high-activity, low-stage deals by rep.
We build this instrumentation as part of the RevOps layer for our clients. If you want the full picture of how that fits alongside lead gen and sales automation, our pricing and packages break it down.
8. Fix the comp plan that rewards banking deals
Detection tells you who's sandbagging. The comp plan tells you why. If your plan resets attainment to zero each quarter with steep accelerators, you've built a machine that pays reps to hold deals. Consider structural changes that reduce the incentive:
- Annualized accelerators: Let attainment and tiers roll up over the year so pulling a deal forward never costs the rep money.
- Reward booked date, not just closed date: Pay on when revenue is actually recognized to reduce timing games.
- Flatten the cliff: Smooth the jump between quota tiers so there's less benefit to gaming which quarter a deal lands in.
When the financial reason to sandbag disappears, most of the behavior does too. You'll never regulate your way out of a comp plan that pays people to hide deals.
9. Make honest forecasting the path of least resistance
Reps sandbag the forecast to protect themselves from being wrong. Remove the punishment for an honest miss and you remove half the motive. If a rep commits a deal in good faith and it slips for a real reason, that shouldn't count against them the way a lowball would. Coach on forecast accuracy, not just forecast optimism.
Pair that with visibility. When reps know the system automatically surfaces high-activity deals stuck in early stages, sandbagging stops being worth the effort. The behavior thrives in the dark. Good instrumentation turns the lights on.
10. Run a quarterly sandbag review, not a witch hunt
Institutionalize the practice. Once a quarter, pull the four signals together — activity-versus-stage gaps, time-in-stage outliers, close-date clustering, and forecast-category conversion — and review them as a team, not as an interrogation. Frame it as pipeline hygiene. The goal is an accurate number everyone can plan against, not catching people.
Over two or three cycles, reps learn that the pipeline is watched, comp doesn't reward hiding, and honest forecasting is safe. That combination is what actually kills sandbagging for good.
Frequently asked questions
Is sales sandbagging always intentional?
Not always. Some reps sandbag deliberately to bank deals or protect their number, but plenty do it out of habit or caution, keeping deals in a conservative stage because they've been burned by slips before. That's why you look at patterns across a rep's whole pipeline rather than judging a single deal. Consistent behavior points to intent; a one-off usually doesn't.
How can RevOps detect sandbagging without accusing reps unfairly?
Anchor every conversation in data the rep can see too. When you flag a deal because it has top-quartile activity but is stuck in Stage 2, you're pointing at evidence, not motives. Use consistent, transparent rules applied to everyone, and frame reviews as improving forecast accuracy. Reps rarely argue with their own activity log.
Will fixing the comp plan eliminate sandbagging completely?
It removes the biggest driver, but not every one. Comp changes like annualized accelerators and paying on booked date kill the financial incentive to hold deals. You still need instrumentation to catch habitual under-reporting and a culture where honest forecasts aren't punished. Structure plus visibility plus coaching is what gets you there.
If your forecast keeps beating itself and you can't tell whether that's talent or hidden pipeline, we'll help you find out. Book a Revenue Systems Audit and we'll pressure-test your pipeline signals, stage rules, and comp incentives together.