Why sales reps don’t update the CRM: it isn’t laziness
Short answer
Sales reps don’t update the CRM because it works for their manager, not for them: logging takes time away from selling, bad news in a record invites questions, and the real conversation happens in a messenger anyway. Fines produce tidy, invented records. What works: fewer fields, facts taken from the conversation itself, penalties for hidden problems rather than reported ones, and a record that is useful to the rep.
Your rep isn’t lazy. Your rep can count, and better than you’d like.
The manager reminds everyone to update the CRM. Then reminds them in the group chat. Then introduces a penalty. By month’s end every record is filled in, every deal is “in progress”, and the money is the same.
The usual conclusion is that reps are lazy. It’s a convenient one: nothing needs to change except the people. But people change and the empty records stay. So it isn’t the people.
Five real reasons
The system doesn’t work for the rep
Look at who actually needs the CRM in your team. Reports go to the manager. The pipeline goes to the owner. The forecast goes to finance. The rep gets one more window to feed. People rarely feed what doesn’t feed them.
Logging costs time, and you pay for sales
Every minute in a record is a minute away from a client. Commission is paid on revenue, not on tidiness. The rep does exactly what your incentive plan teaches. Being offended by that is odd.
The real work happens elsewhere
The client writes in a messenger. Haggles there, promises there, disappears there. For any of it to reach the CRM, someone has to retell the conversation by hand. Double work for a worse copy. How that kills a rollout is covered in why CRM implementations fail.
Honesty gets punished
Write “client lost” and you get asked why. Write “thinking it over” and you get a quiet week. Reps choose the quiet week. You taught them that yourself, and for free.
The record was designed in a meeting
Fields were added for years. Every department asked for its own, nobody removed anything. Half are read by no one and all are mandatory. So the rep types whatever makes the save button work.
Why penalties fail
A penalty solves one problem: the field stops being empty. An empty field is at least honest. One filled in under threat looks like data and isn’t.
- Stages move to match the report date. The deal is “in negotiation” because someone will ask on Friday.
- Records are written in the evening, in a batch. From memory, from one template.
- Bad news gets postponed. The client left on Monday; the record says “thinking” until month’s end.
You used to know the data was missing. Now you’re sure it’s there. The second is more expensive.
What to change
- Remove the extra fields. Ask of each one: what decision did it drive last month? No answer, no field. Stage, next step with a date and amount are usually enough.
- Take facts from the work itself. When the rep wrote, when the client replied, what was promised, when it was paid: all of that already happened in the chat and at the till. A person shouldn’t have to retell the system what it could see for itself.
- Make logging pay off for the rep. A client reminder, instant history, commission calculated without arguing with accounting. When the record saves them time, the reminders stop.
- Separate bad news from hidden problems. “The client left, here’s why” is a normal working conversation. “The client left a month ago and the record says all is well” is a different one. Punish the first and you’ll get the second.
- Define stages by client action. Not “negotiation” but “client received the contract and replied”. A stage confirmed by a fact is harder to move on a Friday.
- Use the CRM yourself, in front of everyone. If the data isn’t used anywhere, the rep knows. The rep knows a lot of things.
How to run a review that doesn’t depend on retelling is in the piece on the pipeline review when the CRM is wrong. What to measure per person is in chat KPIs for managers.
Check yourself
- Can you name a decision you made this week from CRM data?
- Does the rep open a record for themselves, or only for you?
- What happens to the person who reports bad news first?
- How many fields did nobody read last month?
- Where is the client conversation happening right now, and can the system see it?
If most of these are awkward to answer, your reps aren’t the problem. They just count well.
You can’t force people to write down a truth they’ll be questioned about.
// Take it with you
You can’t force people to write down a truth they’ll be questioned about.
Drop it in the team chat. Let them think you came up with it.
New articles, once a week, in Telegram.Subscribe →
Questions and answers
Why don't sales reps update the CRM?
Because it doesn’t pay them to. Logging takes time they could spend with a client, the benefit goes to the manager, and honest bad news in a record leads to an unpleasant conversation. Laziness rarely has anything to do with it.
How do I get my sales team to use the CRM?
You can force it, but you’ll get records made for the report. It works better to cut fields to a minimum, take facts from the chats and calls themselves, and tie logging to something useful: reminders, client history, commission calculation.
Should I penalize reps for not updating the CRM?
A penalty cures the empty field, not the truth inside it. Reps will fill it in faster and more optimistically. If anything deserves a penalty, it’s the hidden problem, not the reported one.
How many fields should a deal record have?
As many as are used in decisions. If nobody has looked at a field for a week, remove it. Stage, next step, the date of that step and the amount usually stay.