If you run a sales team, you have had this conversation. You ask for the CRM to be updated. It gets updated for three weeks. It goes back to how it was.
What gets written about this always lands in the same place: training, clearer process, a better designed CRM, more discipline. Reasonable advice, and twenty years of not solving it. Worth asking why.
Logging gives nothing back to the person logging
A rep lives on closing. The CRM asks them for fifteen minutes a day to produce something they already know, which mostly serves so that somebody else can build a report.
This is not bad faith. It is a bad trade. When somebody logs carefully, what they get back is that their manager can see the pipeline. When they do not, nothing happens until Friday's meeting, and by Friday it gets filled in from memory at the last minute, which is worse than not filling it in.
Any plan that starts with "we need to get the team to log things" is fighting that.
What you actually lose
Not tidiness. Decisions.
- The forecast. It comes from close dates and stages the team types in. It is worth exactly what that typing is worth.
- "No activity for X days." It means "nobody logged anything for X days", not "nobody has spoken to them for X days". It is the metric most used to prioritise and the one that ages worst.
- The clients that do not exist. Companies you have been talking to for weeks with no record anywhere. Those appear on no list, because appearing would require somebody to have created them.
That last one is hardest to see, because a CRM cannot show it to you. It records what has been typed into it, so by construction it cannot see what has not been.
Why CRM automation only half helps
The obvious answer is capturing activity automatically, and CRMs offer it. It is worth knowing how far it goes.
In HubSpot, for instance: incoming email from a contact that already exists is logged; outgoing needs every rep to install a browser extension, so from a phone it is not logged; and from somebody who is not a contact nothing is logged. We measured it on a real portal and out of the box the leak was one hundred per cent.
Rolling out the extension fixes part of it and you should do it. But it leaves out the phone and, above all, it leaves out whoever is not in the CRM.
The way out is not getting them to log
It is no longer depending on them logging.
The activity already exists. It is in the team's email and calendar, with its date and its participants, and it happened whether or not somebody copied it into the CRM. What is missing is not writing it down again: it is comparing what happened against what the CRM believes happened, and keeping the difference.
That changes Friday's conversation. It stops being "why have you not updated this?" and becomes "this deal says it is in negotiation and the client has not answered in six weeks, what do we do?".
The first question puts somebody on the defensive. The second one is useful.
What you can do this week
- Measure the gap before deciding anything. Take three clients, count the emails in your inbox with them and the ones on their record. The difference is the size of the problem.
- Roll out the automatic capture your CRM already ships. It is free and it fixes desktop email.
- Then decide what you do about what is left, which is the phone and the people who are not on the record.
CERUNA does the third one: it reads your team's email and calendar headers, crosses them against the CRM, and names what never arrived. Start with a Revenue Blind Spot Audit: €750, report in 72 hours, refunded if it does not find three things you did not know.
And one thing worth saying: if after measuring it turns out your team does log things, congratulations, you do not have this problem. Knowing that is worth something too.