← All posts

Why salespeople do not update the CRM, and what to do instead

· Bob Ottley

Every sales director has tried the Friday deadline, the dashboard on the wall and naming the people who are behind. Each works for about three weeks. The problem is not the people. It is the design.

1,100hours a year, example: a team of eight updating by hand
3.5 daysaverage age of a record updated once a week
1word to update the CRM: YES

It is a design problem

I have run sales teams and sat in more pipeline reviews than I can count. Not once could I say with confidence which half of the forecast was real. The reps were not lazy. We were asking them to finish a meeting, open a different application, find the right record and type what just happened into a form. Every field in that form answered the manager's question, not theirs.

So it got done last, in a rush, the night before the pipeline review. And what got typed then was the shape of a deal, not the deal.

The numbers behind it

Take a team of eight sales people, each with eight customer conversations a week, and say a proper update takes 20 minutes after each one. That is around 2.7 hours per person per week, about 21 hours across the team, and over 1,100 hours a year. At a loaded cost of £35 an hour, that is close to £39,000 a year of selling time spent typing.

Example figures. Change the inputs to your own team; most come out in the same range.

And the result is still late. If a record is updated once a week, on Friday, the information in it is on average three and a half days old, and a week old by Thursday. A forecast built on it is a forecast of last week.

Change the direction

As long as the rep has to go to the CRM, no policy fixes it. So we built TellMyCRM the other way round: what happened reaches the CRM instead.

  • Say it once. A voice note or a message on WhatsApp, Teams or Slack after the meeting. "Budget signed off, they want to start in November, move it to proposal."
  • Read what already happened. The emails and Teams meetings are read for what changed, so the record moves even when nobody remembers to say so.
  • Nothing is guessed into the CRM. Every change is read back to the rep, and written only when they reply YES. A CRM that fills itself with guesses is the same problem, only faster.

The rep has to get more back than it takes

This is the part most CRM projects miss. If the system only takes from the salesperson, it will be ignored, however often the director reminds them. So the rep gets something back every day: the brief before a meeting, the follow-up email already drafted, and a nudge when a customer has gone quiet for too long.

What the director gets

A forecast where every figure adds up from deals you can open, and every fact links to the email or meeting it came from. "The customer is keen" is not evidence. "They confirmed budget in Tuesday's meeting" is.

The same idea works outside sales

Any system people are meant to keep up to date fails the same way: job sheets, timesheets, stock counts, site visits. If keeping the record is a chore that helps somebody else, it will be late and thin. Move the work to where people already are, ask them to confirm rather than type, and give them something back for it.

Have a job like this? Tell us in a few lines what gets copied, checked or chased by hand. We will come back with questions, not slides.

Book a call

Next: The problems that fall between your systems