We rolled out a new CRM six months ago and made it mandatory for the sales team. I was hoping for at least 80% adoption by now, but our tracking shows only about 40% of deals and activities are logged.
I’m in customer support, so I don’t manage the team directly. What actually works to get adoption up? Our use case is pretty standard SaaS sales. Did we pick the wrong tool, or is this about process?
Ouch, that's a familiar frustration. The "mandatory but only 40% logged" pattern almost always means the CRM is seen as extra reporting work, not a tool that makes their lives easier.
Have you checked what part of their workflow *isn't* in the tool? Often the gap is in the small, quick actions - like updating a deal stage after a call. If they're using another system (even just email and spreadsheets) for the actual work, the CRM becomes data entry. Can you integrate it directly with their calendar and email? Auto-log meetings and email threads? The goal is to make logging a byproduct of selling.
Also, since you're in support, you have a unique angle. Are support cases linked to the CRM deals? If sales can see that having accurate CRM data helps you resolve customer issues faster, that's a direct value prop to them. Maybe show them a quick example where missing CRM data hurt a renewal chance? Sometimes they need to see the downstream pain.
Clean code, happy life
That 40% figure is telling you exactly where the friction is. It's almost never the tool - it's that the process doesn't fit into their natural workflow.
Since you're in support, you have a unique lever. Can you tie commission payouts or deal approvals to CRM data completeness? I've seen teams where finance won't process a commission unless the deal record is fully updated. It sounds harsh, but it aligns the incentive directly. Alternatively, show them how clean CRM data helps you spot renewal risks earlier, which protects their commission.
Sometimes the issue is just one cumbersome field. Have you sat with a few reps to watch them enter data? The blocker could be as simple as a required field that's hard to get info for, so they avoid the whole record.
Data is sacred.
Totally feel your pain on that 40% figure. Been through a similar rollout on the project management side.
You mentioned you're in support - that's actually a huge advantage! Can you build a feedback loop where you use the CRM data to proactively flag customer health scores or renewal risks for the sales team? When they see accurate data directly helps them protect their commissions, adoption becomes self-serving. We saw a big jump when we started auto-generating account health reports from logged activities.
It's almost always process, not the tool. The 40% is the low-hanging fruit where data entry is easy. The gap is in the messy middle of deals. Maybe run a "CRM amnesty" week - no penalties, just help them clean up old deals together. Sometimes the backlog feels too big to start.
Always testing.
I like the "CRM amnesty week" idea. That can really remove the psychological barrier of a huge, messy backlog. It frames the tool as a helpful resource rather than a punitive reporting system.
One caveat from similar rollouts I've seen: the feedback loop you mentioned is powerful, but it only works if the data is reliable from the start. If you're generating health scores from incomplete or stale data, sales will immediately discredit the reports. You might need to start with a manual, high-touch version of that loop first. For example, personally flagging a few at-risk accounts you spotted via CRM activity gaps for a specific rep, then showing them the connection.
The key is making the value undeniable to them, not just to management.
The amnesty week is a good psychological reset, but it's a temporary fix if the daily workflow is still broken. You clean up the backlog, then they're right back facing the same fields and clicks that caused the backlog in the first place.
The point about unreliable data killing the feedback loop is crucial. I've seen teams try to implement health scores and the reps just laughed because the data was garbage. Starting manual is smart, but it's also a trap. If you, in support, are the one manually connecting dots, you've just added to your own workload and the CRM is still an external reporting tool for sales. The value has to come from their own use.
The real test is what happens after amnesty week. If you don't fix the one or two biggest process hiccups they complain about during that week, you'll be back at 40% in a month.
Your CRM is lying to you.
The "low-hanging fruit" point is spot on. That 40% is the easy stuff that takes zero thought. The issue is always the 60% that's messy, where the tool doesn't fit the real-life conversation.
Your feedback loop idea only works if the data feeding it is complete. You can't generate reliable health scores from 40% of the activities. It creates a vicious cycle: they don't log, so the reports are wrong, so they trust the reports less, so they don't log. Starting with manual reports just burns out the support person.
The amnesty week can work as a cultural reset, but only if you pair it with fixing the single biggest friction point you discover during that week. Otherwise you're just building a fresh backlog.
That 40% adoption is such a classic signal. I agree with everyone that it's almost certainly process, not the tool. Since you're in support, you have a unique opportunity to build a bridge.
You could create a simple, manual win for them. Next time you're on a support call and see a deal in the CRM is missing key info, like the champion or next renewal date, just send a quick, friendly Slack to the rep. Say something like, "Hey, just helping out with X for Customer Y, noticed the renewal date wasn't logged - once you pop it in, I can set up a reminder for you." It frames the CRM as a shared workspace that helps you help *them*, not a separate reporting bucket.
That small, positive interaction can do more than a dozen mandates. It shows the immediate value to their own workflow, protecting their commission and saving them from chasing you for info later.
Proactive health reports sound great on a slide. In reality, they're the fastest way to destroy credibility when the source data is 60% missing. You can't generate reliable signals from a black hole.
The amnesty week is a decent reset button, but it's just procedural debt forgiveness. If you don't fix the actual workflow pain point you uncover during that week, you're just prepping the field for a fresh crop of backlog by month's end.
The real trap is thinking support can build the feedback loop alone. If the value isn't immediate and obvious to the rep during their own workflow, it's just another report to ignore.
Beware of free tiers