CRM diagnosis

Why is my CRM not working?

More training, cleaner data and better configuration can fix genuine CRM problems. If the same complaints keep returning, the useful question is whether the system is wrong or whether the business logic behind it is still unclear.

First separate the problem

Four different things can look like "the CRM isn't working".

The system is technically wrong.Configuration, integrations, permissions, duplicates or usability prevent it from doing a clearly defined job.
The workflow does not fit the work.People duplicate effort, update the CRM after the fact or make the important decision somewhere else.
The definitions are inconsistent.Teams use the same field names but mean different things by lead, opportunity, won, active or at risk.
The CRM covers only part of the customer flow.Sales is visible, while delivery, cost-to-serve, retention or commercial uncertainty sit elsewhere.
The test

If the business can define the job clearly and the CRM still cannot do it, fix the CRM.

If the business cannot yet agree what the system should recognise, when it should be recorded, who owns it or what happens next, configuration alone cannot settle that disagreement.

Adoption

Low usage does not identify the cause.

People may need training. They may also be avoiding a system that creates duplicate administration or does not help them perform the work.

I would look at what happens immediately before and after a CRM update: what decision has just been made, whether the information already exists elsewhere and whether anyone downstream actually uses it.

Data

Clean records can still represent an unclear process.

A data-cleanup project is useful when the records themselves are technically wrong.

It is less durable when the same ambiguity continues to create new records: different stage definitions, updates made from memory, inconsistent ownership or multiple systems holding different versions of the same customer.

Boundaries

The CRM does not have to contain everything. The business does need to connect what matters.

Delivery, finance and support may correctly live in different systems.

The design question is whether the business can still trace the customer across them: what was sold, what was promised, what was delivered, what it cost and what happened next.

The resulting Management View does not have to live in one application. It has to make the important commercial changes and their consequences traceable across the applications that already hold them.

Before another CRM project

What I would establish first.

What should the CRM know?

The customer states, events, risks and commitments that materially affect commercial decisions.

When should it know it?

The point in the work where the information becomes true, rather than when someone later remembers to update the record.

Who uses it next?

The person or function whose decision depends on that information and what they need to do with it.

Start here

Find out whether the problem is the CRM before rebuilding the CRM.

I research the business before the first call, then use the conversation to identify whether the useful next step sits in the system, the process behind it or somewhere else in the revenue flow.

If the core problem is that management cannot connect the current systems, see the Revenue Visibility Review.

If you are already using a named platform and want to know how this work fits around it, see the CRM and systems pages.