A fast-growing enterprise with an aggressive sales culture, a recently implemented CRM, and a leadership team that loved dashboards. The problem: the dashboards were beautiful fiction.
The $300M ghost
It was the third week of Q2 when a new VP of Sales asked me a seemingly innocent question: "Can you help me understand why our win rate has dropped 15 points in six months?"
I pulled the standard report. Everything looked normal. Pipeline volume was up. Average deal size was stable. The stage progression model showed opportunities moving predictably from Discovery to Closed Won.
But the win rate was down, and the VP had a gut feeling something was off.
I started digging into the underlying records. Not the aggregate metrics. The raw opportunity data. And I found something strange.
Over 400 opportunities, representing more than $300M in pipeline, had been created in the CRM with a close date exactly 90 days from creation. To the day. Not 89. Not 91. Exactly 90.
That is not how real sales cycles work. That is how a default value works.
The incentive architecture
What I found was a textbook example of metrics driving behavior. The compensation plan included a quarterly accelerator: reps at 100% of quota earned standard commission, reps at 120% earned a multiplier.
The pipeline dashboard the CRO reviewed weekly showed pipeline coverage ratio: how much pipeline each rep had relative to quota.
Reps learned quickly that the system measured pipeline quantity, not pipeline quality. So they gamed the input. Opportunities with optimistic close dates and inflated values, moved through stages on schedule. The dashboard stayed green. The forecast stayed "on track." The deals were nowhere near ready to close.
This had been going on for over a year. The CRM was not a record of customer conversations. It was a record of what reps needed the system to say to keep their managers happy.
Rebuilding the signal
The technical fix was conceptually simple and organizationally hard: replace self-reported pipeline with signal-based pipeline.
- Email and calendar integration verified that reps were actually talking to the people they claimed to be talking to.
- Product usage signals validated that prospects were actually engaging with the platform.
- An automated scoring model weighted opportunities on behavioral evidence, not stage names.
- A rep-level forecast confidence score became part of the management conversation.
The harder part was changing the questions leadership asked. Not "how much pipeline do you have?" but "what is the confidence level of your pipeline, and what signals support it?"
The confrontation
The first time the signal-based dashboard was presented in a sales leadership meeting, a top-performing rep saw his pipeline cut by 60%. He stood up and walked out.
His manager defended him: "He always hits his number. The system must be wrong."
I sat in that meeting and said nothing. The data was the data. The rep did always hit his number. He just hit it through a completely different mechanism than the CRM claimed: a small set of deep relationships he worked entirely outside the system. The CRM was fiction. His performance was real. They were simply not connected.
That rep eventually became one of the strongest advocates for the new system, because once it measured reality, it gave him credit for work he was already doing. His manager could see the real pattern. The company could learn from it.
What I learned
The most dangerous dashboards are the ones that look right. The ones that confirm what leadership already believes. The ones that stay green long after reality has turned red.
If your data system can be gamed, it will be gamed. Not because your people are dishonest, but because your incentive structure rewards the wrong inputs.
The job of a data leader is not to build better reports. It is to build systems that make gaming more expensive than honesty: metrics that are hard to fake, signals that are hard to manufacture, and consequences that flow directly from evidence.
The pipeline was never real. The question was whether anyone wanted to know.
The condensed version of this story, with the build details, is in the case study Pipeline integrity.