Why 7 in 10 CRM Implementations Fail to Deliver ROI — And How to Be in the 30%

I've been selling and delivering CRM projects since before Salesforce became a household name. And in that time, one statistic has remained stubbornly consistent: the majority of CRM implementations — most analysts put it at around 70% — don't deliver the return on investment that was promised when the project was signed off.

That's a damning number. And if you're about to invest in a CRM programme, or you're sitting with one that isn't performing as hoped, it's worth understanding why this keeps happening — and what the businesses in the 30% do differently.

The mistake that starts before go-live

The single most common failure I see is treating CRM as an IT project. The purchase decision sits with the technology team, the implementation is managed by IT, and the business teams are handed a system at the end and told to use it.

It almost never works. Not because the technology is wrong. Not because the configuration is poor. But because the people who need to use the system every day had no hand in designing it, don't understand why it works the way it does, and — quite rationally — revert to whatever they were doing before.

The 30% get this right from day one. Executive sponsorship isn't a line item on a project plan — it's genuine, visible, ongoing commitment from the leadership team that this is how the business will operate going forward. That message has to come from the top, and it has to be credible.

Process first, platform second

Here's something I tell every prospective client: if your sales process is broken, a CRM will make it faster to be broken. Technology amplifies what's already there. It doesn't fix underlying process problems.

The businesses that get the best results from CRM spend time before implementation defining — really defining — how they want to manage their customer relationships. What does a good lead look like? What are the stages in your sales cycle, and what has to be true to move between them? What does your customer service team need to see in order to resolve an issue first time?

These are process questions. Answer them first. Then choose the platform that fits the process — not the other way around.

User adoption is the only metric that matters at go-live

In the first 90 days after a CRM goes live, I don't particularly care about pipeline accuracy or forecast quality. Those things matter enormously later. But right now, the only thing I want to see is that people are actually using the system.

That means training that goes beyond "here's how to log a contact." It means understanding what's in it for the individual user — because until your sales team can see that the CRM helps them close deals rather than just report on them, you're fighting human nature. And it means leadership actively using the system, not just asking for reports from it.

Adoption problems are almost always visible early. If you're not actively tracking and addressing them in the first three months, they calcify into habits that are very hard to break.

The ongoing investment mindset

The businesses in the 30% don't think of their CRM as a project with a start date and an end date. They think of it as a platform they're continuously improving.

That means regular reviews of how the system is being used. It means taking advantage of the two or three major platform releases that Salesforce, Microsoft and Oracle each deliver every year. It means listening to users about what's working and what isn't, and making changes. And it means having someone — internally or through a partner — who is genuinely accountable for getting value from the investment.

If you want to be in the 30%, here are the questions I'd ask of any CRM programme, at any stage:

• Does the executive sponsor use the CRM personally, or just receive reports from it?
• Were the business users involved in the design, or just the IT team?
• Can you articulate what good looks like in your sales or service process — before touching the technology?
• Do you have a plan for adoption that goes beyond training videos?
• What happens to the CRM after go-live? Who owns continuous improvement?

None of these are technology questions. That's the point.