CRM hygiene without a mandate
Nobody updates the CRM because they are asked to. Four structural changes that make the data accurate as a side effect of work reps already do.
Every quarter, someone sends the email. The CRM is the single source of truth. Please keep it up to date. Compliance will be reviewed.
Compliance improves for eleven days.
The reason is not laziness. It is that updating a CRM is work that benefits someone other than the person doing it, at a moment when they are busy, and the cost of not doing it is deferred and diffuse. No amount of asking changes that arithmetic. Structure does.
1. Capture at the point of work, not after it
If a rep has to leave the tool they are working in to record what just happened, the record will be late, thin, or absent.
The fix is unglamorous integration work: calls logged automatically with outcome, duration and timestamp; email threads synced against the contact; meetings created from the calendar. The test is whether a rep can complete an entire day of selling without opening the CRM and still have it be accurate at 6pm.
This is not a nice-to-have. It is the whole game. Every other item on this list is a rounding error next to it.
2. Make required fields earn their place
Every required field is a tax, and the revenue it raises is spent on a report someone requested once.
Audit them. For each one, find the report or automation that consumes it. If nothing does, delete the field. If something does, ask whether that thing is still used.
What survives is usually three or four fields per object. Reps will fill those in, because a short list reads as a real requirement and a long one reads as bureaucracy to be defeated with dropdown defaults.
A required field that everyone sets to the first option is worse than no field. It is inaccurate data with the authority of a required field.
3. Let stale data expire
Contact data decays at roughly 25–30% a year — people change jobs, companies rebrand, phone systems change. A CRM with no decay model becomes progressively more confident about progressively worse information.
Two mechanisms:
- Age the record. A contact not verified in twelve months is flagged, not silently trusted. Re-verify on a schedule rather than on discovery-by-bounce.
- Bounce the truth back. A hard bounce is authoritative evidence that a record is wrong. It should mark the record automatically, not wait for someone to notice a pattern.
4. Define stages by evidence, not by feeling
"Qualified" means whatever the rep who set it thought it meant. Pipeline built on that is a forecast built on vocabulary.
Each stage needs an observable exit criterion — something a third party could verify from the record alone:
| Stage | Exit criterion |
|---|---|
| Prospecting | A contact at the account has replied |
| Discovery | Budget owner identified by name and confirmed in writing |
| Evaluation | Success criteria documented and agreed by the buyer |
| Negotiation | Pricing sent, procurement contact known |
| Closed won | Signed |
The immediate effect of adopting this is that the pipeline shrinks, sometimes by a third. That is not a loss. That is the forecast becoming true.
What this is really about
None of these changes are about data for its own sake. They are about whether the number a sales leader takes into a board meeting is a measurement or an assertion.
The board can tell the difference. Usually about one quarter after it stops mattering.