The complaint is always the same: "we bought the CRM, nobody uses it." The diagnosis is usually that sales lacks discipline. That diagnosis is almost always wrong.
Count the fields
Open your opportunity creation form and count the required fields. We regularly find fifteen or more, several of which nobody reads, at least one added years ago for a report that no longer exists.
A rep closing a call now faces four minutes of data entry. Ten calls a day is forty minutes of admin producing no value they can see. They will do it badly, late, or not at all — and that is a completely rational response.
The test
For every required field, ask one question: what decision does this field change?
If the answer is "it appears in a report," ask who reads that report and what they do differently based on it. Fields that survive this are genuinely needed. In our experience roughly half don't survive.
Stages that describe your process, not theirs
The second failure is pipeline stages named after internal activity — "proposal sent," "following up," "negotiating." These describe what your team did, not what the buyer did, and they're subjective. Two reps will stage the same deal differently, which is why the forecast is never believable.
Stages should be defined by observable buyer actions:
- Discovery held — a call happened, needs are documented
- Requirements confirmed — the buyer has stated what they need in writing
- Proposal reviewed — the buyer has been through it with you
- Verbal agreement — the buyer has said yes, pending paperwork
Each is objectively true or not. That's what makes a forecast defensible.
Automate the rest
Most of what your CRM asks reps to type could be captured automatically: call logging from the phone system, email activity from the inbox integration, meeting notes from a transcription tool, follow-up tasks generated by stage change.
When the CRM starts saving reps time instead of taxing it, adoption stops being something you have to enforce.
The sequence that works
- Cut required fields to those that change a decision.
- Redefine stages around observable buyer actions.
- Automate every capture that can be automated.
- Retrain on the simplified system.
- Only then hold people accountable to using it.
Doing step five first — which is what usually happens — produces compliance theatre and bad data.