Why a half-used CRM is worse than no CRM at all (and how to fix adoption)
April 7, 2026
Share
I've worked with start-ups at various stages and what I usually hear is ‘We have a CRM but…’
→ Half the team logs activity, half doesn’t
→ Deals sit in the same stage for months with no notes
→ There are three contact records for the same person
→ Someone is still running the real pipeline in a spreadsheet
Sounds familiar? You’re not alone.
Each of those is small on its own. Together they mean your reporting describes a version of the business that doesn't exist. Or worse, reporting doesn't exist because every knows the data is not reliable. Deals stay in the same stage for months, while conversations are progressing in calls and emails.
Most of them fail because of how they're rolled out.
The numbers are famously hard to pin down. Writing in Harvard Business Review, Scott Edinger cited a CIO analysis of a dozen analyst reports that put CRM project failure anywhere between 18% and 69%, averaging around one third. Forrester surveyed 133 organisations using leading CRM platforms and found that where the problems were people-related, slow user adoption was the single biggest threat, ahead of weak change management and training.
The spread in those figures tells you something on its own. If the failure rate depended mainly on the platform, it would be far more consistent. But it's not, because it really depends on how the new CRM is implemented and how close the CRM is tailored to be to the users' true needs.
Usually the implementation.
The tool can also be not suitable to your team's needs, but any CRM alone won't solve this. You'd be moving the same habits into a nicer interface and paying more for the privilege.
Three things, in the below order:
1. A proper audit.
You can't judge a CRM until you can see what's actually in it. That means the duplicate records, the fields nobody fills in, the stages deals never really pass through, the automation built for a sales motion you abandoned two years ago. Most teams have never looked at their CRM this way, which is why the same problems keep coming back after every clean-up.
2. A reorganisation of your CRM to reflect how you actually use it
Not how the CRM's default template thinks you should. Your pipeline stages should match how deals genuinely progress, your required fields should be the ones your team needs to make a decision, and everything else should be removed. Adoption follows when the system stops feeling like admin and starts saving people time.
3. Custom training for your team for the tool you're already paying for.
Role-specific, based on your process, and not the vendor's generic walkthrough. A salesperson and a founder need to know different things about the same CRM, and neither of them learns it from a recorded webinar about features.
Train people on a system that doesn't match their work and they'll go back to the spreadsheet within a month.
Sometimes the honest answer is that you're on the wrong CRM.
Maybe it was chosen for a company you've since outgrown. Maybe it was picked because someone had used it before. If that's the case, migrating now will save you money and time down the line because every month adds records, integrations and habits that have to move with you.
Either way, the starting point is the same: look at what's really in your CRM, not what you assume is in there.
Does this sound like your team? We can help. With 14 years of experience auditing and migrating CRMs, and as an Attio Expert Partner, we untangle your data into an organised database and turn it into the single source of truth your team needs to operate efficiently – complete with AI-driven automations and integrations to save everyone time.
Check out our CRM audit and migration services and testimonials –>
Most CRM implementations fail because of how they are rolled out, not because of the software. Analyst estimates vary widely: writing in Harvard Business Review, Scott Edinger cited a CIO analysis of a dozen analyst reports that put CRM project failure anywhere between 18% and 69%, averaging around one third. Forrester's survey of 133 organisations using leading CRM platforms found that where problems were people-related, slow user adoption was the single biggest threat, ahead of weak change management and training. In practice this means the tool works and the team does not use it consistently, so the data stops reflecting reality.
Yes, because a half-used CRM hides the problem instead of exposing it. With no CRM, everyone knows the pipeline lives in someone's head or a spreadsheet, and they plan accordingly. With a CRM that only part of the team updates, forecasts get built on partial data, deals look active when nobody has touched them for months, and duplicate records quietly split one relationship across three histories. The dashboard gives you confidence that has not been earned.
Start with an audit either way, because you cannot judge the platform until you can see what is actually in it. In many cases the CRM is fine and the configuration is the problem: stages that do not match how deals really progress, required fields nobody fills in, automation built for a sales motion you have since abandoned. But if the CRM was chosen for a company you have outgrown, or you are paying for a tier you use a fraction of, migrating sooner usually costs less than migrating later, because every month adds records, integrations and habits that have to move with you.
Adoption improves when the CRM reflects how the team already works, rather than asking the team to work around the CRM. That takes three things, in order: an audit of what is actually in the system, a rebuild of pipelines, fields and stages to match your real sales process, and role-specific training on the tool you are already paying for. Generic vendor training rarely moves adoption because it teaches the software rather than your process.
