Nobody updates the CRM. Fix the system, not the people.

When nobody updates the CRM, the cause is rarely laziness. It is an exchange-rate problem: the system charges salespeople minutes of typing and pays them back nothing they can use. Fix the exchange — automatic capture, fewer fields, automation that returns value to the person doing the feeding — and adoption follows without a single motivational speech.

Why does CRM entry actually stop?

Because every manual entry is a small tax with no visible refund. A salesperson who has just finished a call can either phone the next prospect or spend four minutes filling in fields that, as far as they can see, exist so a manager can inspect them later. They choose the next call, and they are arguably right to.

The pattern is predictable. Adoption is high in week one, patchy by month two, and by month six the CRM describes a version of the pipeline that stopped being true some time ago. At that point the reporting layer collapses too — the numbers an MD should be reading live, the ones described in The MD Dashboard Blueprint, are being computed from fiction. Commonly the response is a stern email about data discipline. It works for roughly a fortnight, because it changes the pressure without changing the exchange rate.

What does the CRM cost the person updating it?

Audit it honestly. Count the fields a rep must complete to log one call, create one deal, or move one stage. In many small firms the answer is ten or more, several of them mandatory dropdowns nobody upstream ever reads. Multiply by the number of touches in a working day and you get a real cost — typically 30–45 minutes of unpaid administration, paid daily, for a reward of zero.

Contrast what the system gives back: usually nothing. No reminders that save a deal, no prepared context before a meeting, no follow-up done on the rep's behalf. A system that only extracts will always be starved. This is a design question, and it should shape which CRM you choose in the first place — the tool your team will feed beats the tool with the longer feature list.

How do you rebuild adoption?

The mechanism runs in four moves, in this order:

1. Automate capture first. When an email is sent or received, then it logs itself against the contact. When a meeting sits in the calendar, then it appears on the deal without anyone typing. When a form is submitted, then the record creates itself. Every automated capture is a field a human never skips.
2. Delete fields. When a field has not been used in a report or an automation in the last quarter, then remove it. Most 5–50-staff firms need a dozen fields, not forty. Fewer boxes means less friction and, usefully, less room to lie.
3. Tie stages to events, not opinions. When stage changes require evidence — a booked meeting, a sent proposal — then updating becomes a by-product of selling rather than a separate chore. Designing those stages properly is its own discipline, covered in pipeline stages that mean something.
4. Pay the rep back. When a deal sits idle for seven days, then the system nudges the owner with the context needed to act. When a lead arrives, then the CRM routes it and drafts the first touch. The moment the CRM starts doing work for salespeople, they start keeping it accurate — because now bad data costs them.

Run the four moves and adoption typically recovers within a quarter, because the underlying trade has changed: the rep now gets more out than they put in.

What does the MD change on their side?

Stop using the CRM as a surveillance device in meetings. When Monday's pipeline review consists of interrogating reps about why fields are empty, the CRM becomes the prosecution's evidence, and people quietly manage what it says rather than what is true. Use it instead as the shared instrument the meeting is run from — deals discussed from the screen, decisions recorded into it during the conversation.

And close the loop the data feeds. An accurate CRM is what makes systematic follow-up possible at all — the sequences and reactivation passes described in The 90-Day Follow-Up Framework can only run against records that reflect reality. When reps see stale records producing embarrassing automated follow-ups, hygiene stops being abstract.

When is the tool actually the problem?

Occasionally. If logging an email genuinely requires switching applications, or the mobile interface cannot update a deal in under a minute, the tool is adding friction no process can remove, and replacing it is rational. But swapping tools without changing the exchange rate simply moves the graveyard. A firm that migrates its habits migrates its problem; the fix is the system around the CRM, and it costs less than the third licence you are about to buy.

---

Next step: the Growth System Audit — £450, seven days, credited against any build — maps where your growth system leaks, including whether your CRM is being fed or merely billed, and what to build first.