Question
Sandbagging shows as a commit consistently below what the pipeline supports, followed by deals closing that were never committed. Happy ears is the mirror image. Both are patterns across quarters rather than a judgment about one deal.
Any single deal can be called wrong for good reasons. A pattern of calling low and landing high across three quarters is not caution.
Track committed against closed per rep over time. The shape shows up quickly.
Commit well below what the pipeline supports, then deals closing that never appeared in commit.
It is usually rational: a rep punished for a miss and rewarded for an overachievement is being taught to do this.
The opposite: commit consistently above outcome, with the same deals rolling forward quarter after quarter.
More damaging, because the number leadership plans on is wrong in the direction that hurts.
If missing commit is punished more than beating it is rewarded, sandbagging is the correct strategy and no conversation will change it.
An independent read helps: a score built from buyer behavior rather than rep opinion gives you something to compare the commit against.
Questions
Track committed against closed per rep across several quarters. A consistent pattern of calling low and landing high is sandbagging; one cautious quarter is not.
Usually because missing commit is punished more heavily than beating it is rewarded. That is an incentive problem rather than a character one.
It arrives in Slack
Every morning, each rep gets one message naming the deals on their own book that moved overnight, biggest mover first, with the reason beside each number and the deals that have gone quiet underneath.
$99 a month, cancel any time.. Everyone on the team. No per seat charge. Connect a CRM and it runs. No implementation fee. 14 day trial. No card.
Related reading
Behind is a symptom with four different causes. Which one it is determines the conversation, and guessing wrong wastes a quarter.
Most forecasts multiply deal value by a stage probability nobody has checked. Here is the gap between that number and the actual win rate.
One is arithmetic, the other is a promise. Teams that conflate them get surprised twice.
Feature lists do not get approved. Frame it against a number already being missed, with arithmetic a CFO will check.
Reviewed September 20, 2026 against the product as it behaves today.