TL;DR
The fields aren't empty because your reps don't care. They're empty because you're asking someone mid-deal, mid-quarter, mid-pipeline to stop selling and start typing.
The CRM is a faithful record of what people had time to write down, which is a fraction of what they actually know. The gap between what's in the system and what the team has learned is where deals go cold, handovers fall apart, and forecasts drift from reality. This isn't a discipline problem. It's a design problem.
A Day in the Life
It's 2pm on a Tuesday. Sarah has already run four calls. The second one went long because the prospect opened up about their restructuring and revealed that procurement, not the VP she'd been selling to, would sign off on anything over $50k. That changes everything about how she positions the deal. She needs to update the opportunity record, adjust her strategy notes, add the procurement contact, and revise the next steps.
But the third call starts in two minutes. She makes a mental note: update the CRM later.
The third call is a demo that runs hot. The prospect pushes back on pricing but loves the product. They mention a competitor by name and ask how the implementation timeline compares. They want a proposal by Friday. Sarah needs to capture all of this: the pricing objection, the competitive mention, the timeline pressure, the proposal deadline.
But she's already dialling into the fourth call.
By 5pm she's had six conversations, each one generating context that matters. The procurement detail. The pricing objection. The competitor name. The personal detail about the prospect relocating to Austin that would make the follow-up feel human instead of generic. She opens the CRM and stares at six records that need updating. Her daughter's school play starts in 90 minutes. Her quota review is tomorrow morning.
She types "good convo, follow up Friday" into the notes field of one record. She updates the deal stage on another. The other four get nothing. The procurement detail, the one that actually changes the deal strategy, stays in her head. By Thursday, it's half-remembered. By next week, it's gone.
Sarah isn't a bad rep. She's the best rep on the team. She hit 118% of target last quarter. She just doesn't have time to be a database administrator on top of everything else. And neither does anyone else.
The Real Reason CRM Fields Are Empty
Every conversation about CRM data quality starts in the same place: reps aren't updating their records. And the response is always the same: more training, mandatory fields, manager check-ins, adoption scorecards.
But the diagnosis is wrong. The fields aren't empty because reps lack discipline. They're empty because the system creates a direct conflict between selling and documenting. Every minute spent logging is a minute not spent on the next call, the next follow-up, the next deal. And reps are measured, compensated, and promoted based on revenue, not record completeness.
The numbers confirm what anyone on a sales floor already knows. 68% of sellers say CRM data entry is their most time-consuming task (Salesroom). Reps spend only 28% of their working week actually selling (Salesforce). The rest goes to admin, meetings, and preparation, with CRM data entry eating the largest share. According to one study, 79% of opportunity data that reps collect never makes it into the CRM at all.
This isn't a training gap. It's a structural conflict. You're asking the most expensive people in the building to do the lowest-value work at the worst possible moment: immediately after a call, when the next opportunity is already waiting.
What's in Your CRM vs What Your Team Actually Knows
Open any CRM record for an active deal. You'll see a deal stage, some activity timestamps, maybe a few lines in the notes field. That's the administrative footprint of the relationship.
Now ask the rep who owns that deal what they actually know. They'll tell you the prospect's real concern isn't pricing, it's implementation risk because their last vendor botched the rollout. They'll tell you the VP they've been meeting with is supportive but the CFO is the one who will kill the deal if the ROI case isn't airtight. They'll tell you the prospect mentioned a competitor twice, not as a threat but because they're genuinely evaluating both options and the decision comes down to onboarding speed. They'll tell you the prospect's team is being reorganised and the timeline might slip by a quarter.
None of this is in the CRM. Not because the rep doesn't think it matters. Because there's no field for "the CFO is the real blocker," no dropdown for "they're also talking to a competitor about onboarding speed," no text box that naturally captures the nuance of a 30-minute conversation. The CRM was designed to track deals, not to hold the context that actually determines whether those deals close.
The gap between what's in the system and what the team knows is where the real cost lives. It's the context that would make a follow-up specific instead of generic. The insight that would help a manager coach the deal effectively. The detail that would make a handover seamless instead of starting from scratch. All of it stays trapped in the rep's head, invisible to the rest of the organisation, and at risk of disappearing every time they get busy, go on leave, or move on.
The Trust Problem Nobody Talks About
Here's the stat that should concern every sales leader: only 2% of sales teams feel more than 90% confident in the accuracy of their CRM data (Salesroom). 75% of teams have less than 80% confidence. And 37% of reps admit to fabricating data because the burden of manual entry conflicts with the pressure to hit quota.
Think about what this means for every report, forecast, and decision that depends on CRM data.
The pipeline review that leadership runs every Monday is built on records that were entered in a rush, padded to clear mandatory fields, and haven't been updated since the last time someone was forced to. The forecast that the board sees is an aggregation of best guesses from reps who filled in the "probability" dropdown because the system wouldn't let them save without it. The segmentation that marketing uses to target campaigns is based on industry fields that were selected once during lead creation and never revisited.
The CRM was supposed to be the single source of truth. Instead, it's become the single source of whatever people had time and motivation to enter. When leaders pull a report, they're not seeing reality. They're seeing the administrative residue of a thousand rushed moments between calls.
The reps know this. That's why the best ones keep their own spreadsheets, their own notes apps, their own mental models of their pipeline. They trust their own memory more than the system. Which means the most valuable context in the business lives in the least accessible, least durable, least shareable format possible: individual heads.
What Poor CRM Hygene Actually Costs
The cost of incomplete CRM data extends far beyond messy records.
44% of businesses lose more than 10% of their annual revenue due to inaccurate CRM data. For a company doing $10M in annual revenue, that's over a million dollars in deals lost, fumbled, or mismanaged because the system didn't reflect reality.
But the number that makes it personal is the time cost. The Logging Tax Calculator breaks this down for any team size. For a team of 10 reps running 6 calls a day and spending 12 minutes per call on post-call documentation, the annual salary cost alone is over $170,000. Factor in the revenue those reps would have generated if they'd been selling instead of typing, and the total cost approaches $900,000 per year.
That's before you count the downstream damage. The forecast that was wrong because deal stages weren't updated. The account that churned because the CS handover was missing half the context from the sales process. The new hire who took six months to ramp because the accounts they inherited had records that told 20% of the story. The marketing campaign that targeted the wrong segment because the CRM fields it relied on were filled in to clear a validation rule, not to reflect reality.
Each of these is a direct consequence of the same structural problem: the system depends entirely on humans finding time to do data entry, and humans never have enough time.
Why Every Fix So Far Has Failed
If you've tried to solve CRM data quality, you've probably tried at least one of these:
Mandatory fields. The most common response. If reps can't save a record without filling in the field, the field will get filled. In theory, this works. In practice, reps fill in the minimum to clear the validation and move on. "TBD" in the next steps field. "Other" in the competitor dropdown. A one-line note that captures none of the context from a 30-minute conversation. The data becomes technically complete and practically useless. The reporting looks cleaner. The insight doesn't improve.
Training and adoption programs. Someone builds a deck about "why CRM matters." Reps attend the session, nod, and go back to the same behaviour within a week. Not because they don't understand the value. Because the structural conflict between selling and documenting hasn't changed. Understanding why CRM data matters doesn't create the time to enter it.
Gamification. Leaderboards for data completeness, prizes for the rep with the most updated records. This works for a sprint. Maybe two weeks. Then the novelty fades and the team reverts to the default: do the minimum, focus on quota.
Data cleanup projects. Rev ops spends a quarter scrubbing records, enriching contacts, deduplicating accounts. The CRM looks pristine for about a month. Then the same decay starts again because the underlying capture mechanism hasn't changed. B2B contact data decays at roughly 22.5% per year. A cleanup without a change in how data enters the system is a temporary fix with a permanent cost.
Every one of these approaches assumes the problem is behavioural. That if you push harder, train better, or incentivise differently, reps will update their records. But the problem isn't behaviour. It's architecture. You're asking humans to be the bridge between where knowledge is created and where it needs to live, and that bridge is manual, tedious, and in direct competition with the work that actually pays.
What If the CRM Filled Itself?
The CRM data quality problem disappears when you stop asking reps to be data entry clerks.
Not when you make data entry faster. Not when you add AI to summarise a call. Not when you reduce the number of required fields. When you remove the rep from the capture process entirely.
This is what Soda was built for. It runs quietly in the background while people work, capturing the context from calls, conversations, browsing, and screen activity, and routing it to where it needs to go. The CRM gets updated with what was discussed, what was committed to, what matters, without anyone typing a word. The deal notes reflect the actual conversation, not a rushed summary written 45 minutes later. The context from every interaction is captured as it happens, not reconstructed from memory at the end of the day.
The result isn't just cleaner data. It's the end of the conflict. Reps sell. The CRM reflects reality. Leadership sees the real pipeline, not a filtered version of it. Handovers contain the full picture. Follow-ups reference what was actually said. And the knowledge that used to walk out the door when someone left the team stays in the system, building organisational memory that compounds over time.
Your CRM was never going to be a record of everything your team knows. It was always going to be a record of what they had time to write down. The question is whether you keep asking them to find that time, or whether you find a way to capture the knowledge without asking at all.