I walked into a company not long ago that was convinced they had a $2.4 million pipeline.
The owner showed me the dashboard with genuine confidence. Numbers on a screen. Color-coded stages. A forecast that projected a strong quarter. The kind of report that makes a leadership meeting feel productive.
We spent about forty minutes together before I asked one question.
“When did someone last touch the oldest deal on that list?”
He didn’t know. So we looked it up together. The oldest active opportunity had not had a single logged activity in eleven months. It was still sitting in Stage 3 — Proposal Sent — with an expected close date that had passed in the previous fiscal year.
There were fourteen more just like it.
The real pipeline was closer to $600,000. And even that number required a few generous assumptions.
The Platform Did Not Lie. The Setup Did.
Here is the thing about CRM data that most people miss: the software is not the problem. Salesforce, HubSpot, Zoho — none of them invent bad data. They record exactly what they are given and report it back faithfully.
The problem is almost always what they were taught to record. And by whom.
Most CRMs at this size get set up one of three ways. A tech-savvy employee figures it out over a weekend. A vendor or implementation partner configures the default template with minor tweaks. Or a previous consultant builds something that made sense to them but was never explained to the team that had to live in it.
In every case the result is the same: a system configured for a generic process that has very little to do with how that specific organization actually closes business.
The stages mean different things to different people. The fields nobody explained get left blank. The pipeline fills up with deals that are technically open and practically dead. And the founder makes decisions based on a number that has not reflected reality in months.
The Three Ways CRMs Mislead You
The pipeline number is a fiction.
Not intentionally. Not maliciously. But when nobody has defined what counts as an active opportunity versus a stalled one — when there is no process for closing out dead deals — the pipeline becomes a graveyard that looks like a garden.
A $2M pipeline with no hygiene process is not a $2M pipeline. It is a collection of things someone once thought might become revenue. Those are very different things.
The activity data tells you who uses the CRM, not who is doing the work.
Some people log everything. Some people log nothing. The result is a dataset that reflects habits not performance. A sales rep with zero logged activity might be your best closer — they just write everything in a notebook. A rep with fifty logged calls this month might be busy and unproductive.
You cannot manage what you cannot measure. But you also cannot measure what was never designed to be measured.
The stages mean something different to everyone on your team.
This is the quietest and most damaging of the three. When Stage 3 means “I sent a proposal” to one person and “I had a good call” to another — you cannot forecast. You cannot compare. You cannot coach. You are looking at the same label on completely different realities.
Forecasting from inconsistent stage definitions is not forecasting. It is optimism wearing a spreadsheet.
What We Actually Do About It
When RVG comes into an organization to look at the CRM the first thing we do is not reconfigure anything. The first thing we do is understand how the organization actually closes business — not how the CRM assumes it does.
That gap between the two is where almost every problem lives.
From there the work follows a consistent sequence.
We audit what is actually in the system versus what should be. This conversation alone is usually enough for a founder to understand why their pipeline number has never matched their actual revenue.
We define what each stage actually means — not in general, but for this organization specifically. Entry criteria. Exit criteria. What has to be true to move something forward. Same definition for every person who touches the pipeline. Written down. Trained on. Visible in the CRM itself.
We clean the data ruthlessly. A smaller honest pipeline is worth infinitely more than a large dishonest one. Founders resist this step more than any other because it feels like shrinking the business. It is not. It is finally seeing the business clearly.
We reconnect the tool to the actual process — not the other way around. The CRM should reflect how your organization sells and serves. Not force your team to adapt to how a default template was built.
Finally we build one report the founder actually opens on Monday morning. Not twenty dashboards. One view. Five numbers that tell the truth about where the business actually is and where it is actually going.
The Question Worth Asking
If your pipeline number has never quite matched your actual results — if forecasting feels like guesswork dressed up as data — if your team treats the CRM as a compliance exercise rather than a tool they trust — the platform is probably not the problem.
The question is whether the system was built for your business or for someone’s idea of what your business might look like.
Those are almost never the same thing.