Back to Knowledge Center

It is a frequently cited statistic: various industry studies suggest that a significant share of CRM implementations never reach their strategic goals. After working closely with CRM processes in complex organisations, we see the same pattern recurring.

The figure varies between surveys and should be read as a pattern rather than a precise measurement: a substantial share of CRM implementations never reach the strategic goals used to justify them. The causes we keep seeing are organisational, not technical. The need arises when an organisation outgrows sharing information informally, but the process meant to replace that is rarely defined as clearly as the system is configured. Sales organisations are often set up to celebrate individual performance while CRM is designed for the team, and that tension does not resolve itself. And discipline fades when nobody owns the follow-up after go-live. The consequence is that changing system is rarely the answer on its own. If the process and the ownership are not in place, the same problems follow you into the new platform.

The Growth Trap and Organisational Complexity

The need for a CRM system typically arises when an organisation grows. In the early stages, everything works naturally: people overhear each other in the office and share information informally. But when the organisation reaches a certain size, especially in B2B with long sales cycles and broad buying groups, systematisation becomes essential. Without a shared system for achieving internal consensus around the customer journey, further growth is left to chance.

CRM Is a Team Sport, Not a Solo Event

This is perhaps the biggest obstacle: many sales organisations are set up to celebrate the individuals who create success, while the CRM system is designed for the team. For a salesperson who feels they have full control in their own head, CRM logging often feels like an administrative burden. But in modern B2B sales, solo runs barely exist anymore: How do you work effectively with a pipeline where the buying group in larger organisations can span many stakeholders with different priorities? How can marketing hit the right targets if they are shooting blind? What about customer service that should know about ongoing sales processes? CRM fails when salespeople want to play tennis while the organisation is trying to play football.

"The 70 % figure is real, but the failure pattern is rarely ‘wrong software’. It is almost always ‘right software, wrong adoption’. Process and discipline decide whether the platform delivers. Tooling decisions matter less than most projects assume."

Cartagena, from D365 implementations since 2003

The Discipline Death

Right after a completed project, motivation is high, but all too often the system gradually falls apart as discipline wanes. This happens because no one follows up, or because ownership of specific processes in the system is lacking. When discipline fails, data quality dies. And when data quality dies, value dies.

Don't Change Cars When the Tank Is Empty

We constantly see companies wanting to take the drastic step of switching CRM systems because they are dissatisfied with their current solution. Often it is like buying a new car because the old one is dirty and out of fuel. Before you consider a system change: Get control of customer data: establish clear routines for how a lead is born, how customers are created, nurtured and closed in the system. Define process ownership: who owns the data in the different phases? Build the foundation: if you do not have routines for ongoing data cleansing, a new system will suffer exactly the same fate as the old one.

For the practical adoption work, see Change Management for CRM. For how strategy decides what CRM should actually optimise for, see How to Build a CRM Strategy That Actually Drives Revenue. For the step from adoption to decision support, see From Gut Feeling to Facts.

Frequently asked questions about CRM projects and adoption

What is the most common reason CRM projects fail?

Low adoption: sellers do not use the system day-to-day. That is rarely caused by the technology itself. More often, the root cause is that change management was not budgeted, sponsor engagement was missing, or the processes around CRM were never redesigned alongside the rollout.

How long does it take before a CRM project is considered successful?

A good benchmark is 12 months: by then daily use should be established (60 til 80 % of users), data quality should be stable, and at least three leadership decisions should have been made on CRM data without anyone instinctively pulling their check from a spreadsheet instead.

What is the difference between a successful and a failed CRM project?

One marker separates them: in the successful project, a business sponsor owns the outcome, not IT. The rest follows. When the sponsor is the business owner, the project becomes about changing the way people work. When the sponsor is IT, the project becomes about delivering a system.

Should we choose platform first or process first?

Process first. If you do not know what you want your sales process to look like, the platform choice becomes arbitrary. Once the process is agreed, you can assess which platform best supports it, and the question becomes technical, not strategic.

Can a CRM project be saved if it has already failed?

Yes, more often than people expect. It rarely requires switching platforms. What helps is restarting a mini-version of the project with the right sponsor, a limited scope (3 til 5 key flows) and a structured 90-day adoption plan. After three months, you can assess whether the course is corrected.

Most CRM projects fail on adoption, not technology. What does adoption look like in your organisation today?

We help map why daily use is below target, and what to change first. The technology is rarely the answer, but the diagnosis tells you where it actually starts.

Book a CRM assessment

Related reading

Sources

Sources retrieved and checked 30 August 2026.