I want to show you a number.
23%.
That's the percentage of CRM data in enterprise sales organizations that is accurate and complete, according to Salesforce's own State of Sales research. One in four fields. In the system your entire revenue operation runs on.
If your CFO walked in and said, "Hey, I want to run the business on financials that are 23% accurate," you'd call a board meeting. But when it's CRM data, we all kind of shrug and schedule another pipeline review.
That's the 23% problem. And it's not a rep problem. It's a design problem.
The Number That Actually Should Scare You
The 23% stat is bad. But there's a worse one sitting right behind it.
79% of opportunity data never enters the CRM at all. Not late. Not incomplete. Just gone. The rep talked to the prospect, learned something, maybe learned something important, and none of it made it into the system.
Think about what lives in that 79%. The prospect who mentioned their budget is frozen until Q3. The one who said the real decision-maker is someone you haven't met yet. The one who brought up your competitor by name and said they're already in a trial.
That intelligence exists. It just exists only in the rep's head. Which means it's one busy week, one new territory, one personnel change away from disappearing entirely.
And yet, every week, revenue leaders sit in forecast calls and try to make high-stakes decisions based on this data. What's going to close this quarter? Where are the risks? What does the pipeline actually look like?
The honest answer is: nobody knows. Not really. The CRM isn't showing you what's happening. It's showing you a reconstruction of what happened, built from memory, usually days after the fact, usually in a hurry.
Why the Data Is Missing
This is the part that took me a long time to understand.
Field reps aren't lazy. They're not ignoring the CRM out of spite. Most of them genuinely want to keep things updated.
The problem is the workflow.
Think about what we actually ask a field rep to do. They drive to a customer site. They run a meeting. They walk out to the parking lot. And then we expect them to open a laptop, log into a CRM, and fill in 15 to 20 fields from memory, in detail, with nuance, accurately, while they're still processing the meeting and thinking about the next one.
That's not a workflow. That's a wish.
The window where a rep's recall is perfect is about three to five minutes. The walk from the conference room to the car. After that, the details start compressing. By the end of the day, after three more meetings, two hours of driving, and a stack of unread emails, the notes they enter are a summary of a summary. By Friday, when most batch updates happen, it's closer to creative writing.
This is why 38% of a sales rep's week goes to non-selling activity. Not because reps are inefficient, but because the systems we've built require enormous administrative overhead from the people least positioned to provide it.
What Broken CRM Data Actually Costs
Let's translate this into something concrete.
The wasted time is real. Reps lose a couple of hours a week to CRM entry, and across a team that adds up. But the bigger cost is not the hours. It is every decision you make on data that is 23% accurate.
When forecasts are built on incomplete information, they drift. Revenue leaders miss their number, not because the deals aren't there, but because the signal is too weak to navigate accurately. More than half of revenue leaders missed their sales forecast twice in a single year. Twice. That's not bad luck. That's a data infrastructure problem.
The pipeline isn't lying to you. It's just missing most of the truth.
The Fix Is Simpler Than You Think
The solution to the 23% problem isn't a better CRM. It isn't more training on data hygiene. It isn't a new pipeline review cadence.
It's capturing the data where it actually lives, in the rep's head, right after the meeting, using the tool reps already carry and trust.
Their phone.
A rep calls in after a meeting. They talk through what happened. June asks follow-up questions based on your methodology, the same questions a great manager would ask. That conversation becomes structured CRM data. Budget, timeline, objections, next steps, stakeholder map, written to the CRM automatically, while the details are still fresh.
No app. No laptop. No Friday batch fiction. Just a few-minute call from the parking lot, and the data is done.
That's the whole idea behind CallJune. Not to make reps more disciplined. To make accurate data entry the path of least resistance, so it actually happens, right when it should.
The Forecast Isn't Broken. The Input Is.
If your pipeline reviews feel like theater, if your forecast calls are really just educated guesses, if your best reps are spending too much of their week on admin instead of selling, the 23% problem is already costing you more than you think.
The good news is it's fixable. And the fix doesn't require a new CRM, a six-month implementation, or a company-wide behavior change.
It just requires meeting your reps where they already are.
Want to see how it works? Call the demo line at calljune.ai. Talk through a mock meeting. See what comes back as structured data. Takes about three minutes, which is exactly how long your reps have before the details start to fade.
Shawn Johnson is the founder of CallJune. He spent 25 years in B2B sales as a rep and manager before building a voice-AI tool to fix the CRM data problem he watched undermine every methodology his teams ever used.