Why Sales Reps Don't Update the CRM. It Isn't Laziness.
Sales reps don't update the CRM because it is extra work, done at the worst moment, for somebody else. It isn't laziness. Why the usual fixes fail, and what works instead.
Sales reps don't update the CRM because it is extra work, done at the worst moment, for somebody else. The update is due straight after a call, just as the next one starts. The fields are shaped for management reporting rather than for the rep's next conversation. And the rep pays for it in time today, while the value goes to the forecast later.
"We're working for the platform," a VP of Sales told us in August.
That makes an empty CRM a design problem, not a discipline problem. It also explains why the usual fixes, from mandates to required fields to another round of training, don't last. Each of them adds effort to a task that fails because of effort.
How much time do sales reps spend on CRM data entry?
About 13% of the working week, or roughly 5.2 hours of a 40-hour week. Salesforce's 2026 State of Sales report finds sales reps spend just 22% of the workweek meeting with customers. The other 78% goes to prospecting (18%), creating quotes (17%), planning (16%), manual data entry (13%), training (11%) and other (3%). The survey covered 4,050 sales professionals in 22 countries.
Five hours a week is the visible cost, and it is not the expensive one. The expensive part is what never makes it into the CRM: the objection raised in the second half of the call, the budget that moved to next quarter, the stakeholder who joined late and asked the sharpest question. Even when the call is recorded, those details sit in a transcript nobody rereads, not in the record the forecast, the manager and the next rep work from.
Why don't sales reps update the CRM?
Because the task is badly designed for the person doing it.
The record is for someone else
CRM fields are built around what management reports on, not what the rep needs before the next call. Stage, close date and amount matter to a manager looking at forty deals at once. The rep needs to remember that the CFO is sceptical and that the pilot has to start before the budget freeze. The CRM asks firmly for the first and has no obvious place for the second, so the rep does the work and the benefit lands with somebody else.
The update is due at the worst possible moment
The best time to record a meeting is straight after it, which is exactly when a rep is heading into the next one. So the update slides to the evening or to Friday, and by then recording has turned into recall. Memory fades fastest in the first few hours after we learn something, as psychologists have known since the 1880s. Longer sales cycles add to it: 57% of sales professionals in the Salesforce survey say customers take longer to decide than they used to.
"If you're in such a mode of doing so many meetings a day and having to update everything, having to document everything, then obviously you miss on some things," a sales lead at one of our customers told us.
It is translation, not typing
The slow part of updating a CRM is converting a conversation into fields, not typing it. A 40-minute call with three people, a detour about a competitor and a half-commitment has to become a stage, a next step, a close date and a handful of custom properties. That conversion is judgement work, which is why faster interfaces and mobile apps haven't closed the gap.
It is one more place to update
Updating the CRM means copying information out of every tool that doesn't write to it. Sales teams run an average of eight tools, and 42% of reps say they are overwhelmed by how many (Salesforce). The problem is not the number of tools but the number of places a rep has to look and update. Gartner warned in November 2025 that beyond a certain point, more AI does not mean more productivity.
Nothing comes back
People use systems that help them, and most CRMs give the rep little back for the effort. How useful people find a system predicts whether they use it more strongly than how easy it is (Davis, 1989), and a study of 240 salespeople found perceived usefulness was the strongest driver of CRM acceptance (Avlonitis and Panagopoulos, 2005). Meanwhile 46% of reps say they rarely get feedback on their sales conversations (Salesforce). A record nobody coaches from is a record nobody has a reason to fill in.
"I've got Salesforce. But I honestly have no idea why it's supposed to be useful for me... I don't know what it gives me," the founder of a logistics company told us.
What does an out-of-date CRM cost the business?
An out-of-date CRM moves the cost of every skipped update from the rep to whoever relies on the record next.
Most teams already distrust what is there. In Validity's 2025 survey of 602 CRM users and administrators in the US, UK and Australia, 76% said less than half of their organisation's CRM data is accurate and complete.
The forecast. A forecast is a sum of stages and close dates. When those are stale or guessed, so is the number at the top, however careful the model built on it.
Planning and coaching. Reps already spend 16% of the week on planning, much of it rebuilding context the CRM should have held. Managers hit the same wall: the most common obstacle sales teams report in developing their reps is lack of access to data and insights, cited by 40% (Salesforce).
The handover. When a rep leaves or passes an account on, whatever never reached the CRM leaves with them.
"Let's say a person quits, another one starts. Are they going to be reliably, every time, able to pick up a thread with a client, understand what's going on? Probably not," a VP of Sales at a Nordic fintech told us.
AI built on top. Manual errors are the most common data issue among sales teams using AI agents, and 46% of sales professionals using agents say data quality issues hurt their sales (Salesforce). An agent reading an empty record is just guessing with more confidence.
The few minutes a rep saves by skipping an update turn into a forecast nobody fully trusts, a handover that starts from zero and an AI project running on guesses.
Why don't mandates, required fields and leaderboards fix it?
"Anything that requires an extra step is an extra burden," a sales leader at a Nordic enterprise software company told us. That sentence explains why the standard fixes fail.
Our answer, and the argument of this piece:
If the problem is extra work, any fix that adds work makes it worse.
Mandates. "If it isn't in the CRM, it didn't happen" raises compliance for a few weeks, then produces the minimum entry that survives inspection. Pushed harder, it produces fiction: in Validity's survey, 37% said staff regularly fabricate CRM data to tell leaders what they want to hear. It is Goodhart's law inside a sales team, in the anthropologist Marilyn Strathern's phrasing: when a measure becomes a target, it ceases to be a good measure.
Required fields. A field that blocks the save button gets filled with whatever unblocks it. The record looks complete and is less true than before, and nobody can tell which values were guessed.
Leaderboards and activity counts. They reward logging activity, not recording what the customer said. Ten logged calls with no notes score better than one call written up properly.
More training. In a study of 454 salespeople at two firms, Speier and Venkatesh found reps felt positive about a new sales system straight after training and had widely rejected it six months later, while absenteeism and voluntary turnover rose. Training changes what people intend to do. It doesn't change what the task costs them every afternoon.
To be fair to discipline: a clean-up sprint before a board meeting or a CRM migration does fix the data, once. It does not change what happens next Tuesday.
How do you get sales reps to update the CRM?
Stop making it their job. The CRM should update itself from the calls, meetings and emails that already happen, and reps should approve changes rather than type them. If adding steps is what fails, removing the step is the fix.
- Capture from the sources that already exist. Most of what a CRM needs has already been said or written somewhere: in a recorded call or meeting, an email thread, a calendar invite. Pull it from there and resolve it into the right record and fields, so nobody retypes what the customer already said.
- Use voice for the gaps. Some things never reach a recording: the in-person meeting, the conversation in the corridor, the rep's own read on the deal. A 30-second spoken recap straight afterwards covers them while the details are fresh. Voice is one input, not the strategy.
- Review instead of entry. When the system proposes the update, a person only has to check it: the stage change, the next step, the new contact. Approving a correct update takes seconds. Writing it from memory is the job that wasn't getting done. The manager's role moves from chasing updates to spot-checking them.
- Give the record back to the rep. Turn what was captured into something the rep actually uses, such as a brief before the next meeting with that account. That is the usefulness the research above points to, and it is what keeps the loop running.
It is also the test the fintech VP of Sales quoted above set for any new tool: it has to work "in a way that it decreases the amount of work a rep needs to put in."
What removing data entry won't fix
It is a capped prize. Remove manual data entry entirely and that is 13% of the week; 65 points of the 78 are untouched. Prospecting, quotes, planning and training still need their own answers.
Saved time does not become selling time on its own. In a 2026 Gartner survey of 210 sales leaders, AI was saving sellers 4.8 hours a week, and 72% of organisations reported low reinvestment of that time into higher-value work. Someone has to decide in advance which customer conversations the hours become.
A vague process stays vague. If nobody agrees what a stage means, a perfectly updated CRM records vague stages faster.
For some teams, the hours are not the point. "Our deals take 6 to 18 months. Their problem on the admin side is nowhere, by a very small margin, caused by CRM updates," a sales leader at the same Nordic enterprise software company told us. For teams like theirs the case for a complete record is continuity and a forecast they can trust, not time saved.
Where Spiich fits
Spiich is an agentic sales platform for B2B sales teams, and it is built on the argument above. It takes CRM updates off reps by running those steps on top of the CRM a team already has. HubSpot, Attio, Pipedrive and Salesforce are all natively supported.
It captures context from meetings, calls and email, and from voice or typed notes. Meetings can be recorded by the Spiich Recorder desktop app with no bot in the call, or by a meeting bot if the rep prefers one.
It resolves that context into the right record and updates whatever the CRM holds, from deal stages, amounts and contacts to activities, tasks, notes and your own custom fields. Writes go straight to the CRM by default. In proposal mode, each change waits for a person to approve it.
Before each meeting, it digests everything known about the account, from CRM history and email threads to past conversations and fresh research on the company, into a brief written for that specific meeting. On the breakdown above, that covers data entry, much of planning and part of prospecting.
Hedda runs all of its CRM work through Spiich and reports 0 manual CRM updates in Attio since adopting it.
Spiich is not a CRM. The CRM stays the system of record, and Spiich is the system of intelligence and action on top of it. Follow-ups are drafted for the rep to send, so nothing reaches a customer without a person.
The CRM was never short of fields. It was short of a reason to fill them.
Frequently asked questions
Sources
- Salesforce, State of Sales, 7th edition (2026). Anonymous survey of 4,050 sales professionals in 22 countries, August to September 2025. Figures from pages 8, 15, 16, 21, 25 and 33.
- Validity, The State of CRM Data Management in 2025. 602 CRM users and administrators in the US, UK and Australia, published July 2025.
- Gartner, AI agents in sales predictions, November 2025.
- Gartner, survey of 210 sales leaders, published May 2026.
- Speier, C. and Venkatesh, V. (2002). The Hidden Minefields in the Adoption of Sales Force Automation Technologies. Journal of Marketing, 66(3).
- Davis, F. D. (1989). Perceived Usefulness, Perceived Ease of Use, and User Acceptance of Information Technology. MIS Quarterly, 13(3).
- Avlonitis, G. J. and Panagopoulos, N. G. (2005). Antecedents and consequences of CRM technology acceptance in the sales force. Industrial Marketing Management, 34(4).
- Murre, J. M. J. and Dros, J. (2015). Replication and Analysis of Ebbinghaus' Forgetting Curve. PLOS ONE, 10(7).
- Strathern, M. (1997). 'Improving ratings': audit in the British University system. European Review, 5(3).
- Spiich sales and customer conversations, January to September 2026. Quoted anonymously and lightly edited for filler words; cuts are marked.
Stop asking reps to update the CRM
See how Spiich keeps HubSpot, Attio, Pipedrive and Salesforce current from the calls, meetings and emails your team already has.
Book a demo