A founder on Reddit recently described a frustration every operations leader will recognise. He built his company a custom CRM. Eight months in, the whole team uses it every day as an organiser for their work. And almost nobody touches the features that actually accelerate things: the automatic email linking, the file storage automation, the follow-up reminders. Projects sit there with no follow-up scheduled, even though the system raises an alarm when that happens.
He has told them. He has shown them. It has not worked.
His question was how to get his colleagues on board. The answers he received reframed the problem completely, and the reframe is the useful part: his team is not failing his CRM. His rollout is asking the CRM to do something CRMs never do on their own.
At a Glance
- Daily use is the win: Eight months in, the team opens the CRM every day. Most internal tools never get that far, and the daily habit is the hard part of adoption.
- People adopt workflows, not features: Feature tours and training sessions do not move adoption. Inserting the system into work that is already happening does.
- Gates beat reminders: A follow-up date required before a project can move forward gets entered. An alarm everyone can ignore does not.
1. Level One Is the Win
The first correction the thread offered was about the scoreboard. The builder was measuring adoption by feature coverage: how much of what he built is being used. By that measure, his rollout is stuck at level one.
Measured by habit, it is a success. Eight months after launch, the system is the team’s daily organiser. That is the outcome most CRM projects, bought or built, never reach. The graveyard is full of systems with more features and no users.
Both things are true at once. The unused features are real money left on the table: follow-ups not set, emails not linked, files not filed. But that is the second problem, and it is not solved by fixing the first one harder. The daily habit is the foundation. The question is what gets built on it, and the answer is not more features. It is workflow.
2. Nobody Adopts Features. They Adopt Workflows.
For the people on a sales or delivery team, the CRM is roughly the seventh or eighth most important tool in their day. Their actual work, the calls, the quotes, the problems in front of a customer, mostly happens somewhere else. A feature only gets adopted when it removes friction from that work, in the moment the work happens.
That is why telling and showing fails. A feature tour teaches people what the system can do. It does not change what their Tuesday looks like.
What changes a Tuesday is insertion. Send the email from inside the CRM, so linking it to the project is automatic rather than a second step. Let the system produce the list of open projects on its own, instead of asking someone to build it. Run the five-minute morning stand-up with the CRM as the agenda, each person looking at their own follow-up list. And when someone keeps a private spreadsheet because it answers one question quickly, replace the spreadsheet with a CRM view that answers the same question. If they use the view, they have adopted the feature behind it without ever attending a training session on it.
3. Reminders Get Ignored. Gates Get Used.
The builder’s sharpest symptom was follow-ups. Users do not set them often enough, and many projects have none at all, even though the system alarms when a project has no follow-up. The thread’s verdict on alarms was blunt: a notification that can be dismissed will be dismissed, because entering the data feels optional.
The fix is to stop asking and start gating. Ask for the follow-up date at the moment the project is saved, in the flow of the work, not later in a reminder. Better, make the follow-up date a condition: a project cannot move to its next status without one. The field stops being data entry and becomes the price of progress, which is a price people pay without resentment because it is obviously connected to the work.
The same logic handles the other unused features. Anything that can run in the background should run in the background by default. Automatic email linking and file storage automation do not need adoption campaigns. They need to be switched on, so the organisation happens whether or not anyone learned a new step.
The Feature Tour
Show the team everything the system can do, and hope usage follows. Training is measured by who attended. Three months later, the team is back at level one and the builder is scheduling another tour.
The Workflow Fix
Take one workflow the team already runs, rebuild it inside the CRM, and remove the old way of doing it. Adoption is measured by whether Tuesday got easier. Then take the next workflow.
4. The One Training Argument Worth Keeping
The thread disagreed about training, and the disagreement is instructive. One camp argued for the full programme: manuals, documentation, training on every feature, pointing to a company that skipped it and got angry users and low adoption. The other camp said stop training altogether and fix friction instead.
The workable middle is narrow and specific. Introduce one feature at a time, attached to one person’s most annoying daily task, with a short demonstration of that feature doing that task. When one colleague visibly saves half an hour a day, the rest of the team asks for it. That request is worth more than any rollout plan.
Two supporting habits came up repeatedly. Ask your heaviest users what annoys them: unused features are often one extra click or one confusing name away from used, and fixing that beats another presentation. And give each team a champion, one person who uses the system properly in public, so the standard is visible in the work rather than in a policy.
The Bottom Line
A CRM your team opens every day but uses at level one is not a failed system. It is a successful habit waiting for its workflows. Stop measuring adoption by feature coverage. Insert the system into the work where the work already happens, gate the fields that matter instead of reminding people about them, automate everything that can run quietly in the background, and let one person’s saved half hour sell the next feature for you.
Level one is not the problem. Staying there because the answer was another feature tour is.
Using the CRM Is Not the Same as Using It Well
If your team’s CRM is a daily organiser and nothing more, the gap is workflow design, not effort. Book a call and we will look at how your team actually works, where the system helps, and which workflow to fix first.
