Series · Before You Buy
How to know whether the problem really is your CRM
Four questions to tell a tool problem apart from a process, leadership or data-entry problem, before you sign the next licence.
Almost every conversation about CRM starts the same way: “we have one, but nobody uses it”. The immediate conclusion is usually that the tool is no good. Sometimes that is true. Often it is not.
Changing CRM is a costly, visible decision: licences, migration, training, months of management attention. If the real problem is somewhere else, the company pays for the change and keeps the problem. Before moving the tool, it is worth separating four causes that look identical from the top.
Is there a sales process, or is there a CRM?
A CRM does not create a process: it reflects one. If it is not defined what a qualified opportunity is, when it moves stage and what evidence is needed to move it, the system becomes a filing cabinet where each salesperson stores whatever they interpret.
The signal is clear: if two salespeople describe the process differently, the problem is not in the software.
Does recording serve the person doing the recording?
Data entry holds up when it gives something back to the salesperson: less work, better follow-up, more closed deals. When it exists only to feed a management report, it turns into administrative burden and gets abandoned in the first busy week.
A process does not exist to add bureaucracy; it exists so that an important result does not depend on remembering how to do it every time.
Does management lead with the CRM or in spite of it?
If the weekly pipeline review happens on a parallel spreadsheet, the team quickly learns which is the real source of truth.
Adoption is a consequence of leadership: it holds up when the conversation about results happens on the same information people are asked to capture.
Is the CRM connected to operations?
When closing a sale forces someone to re-enter the same data in administration and in operations, the CRM is experienced as an extra step rather than a starting point.
Here there is a legitimate technical problem, but it is one of integration, not of software brand.
| What you observe | Process problem | Tool problem |
|---|---|---|
| Two salespeople describe the process differently | Yes | No |
| Recording gives nothing back to the person recording | Yes | No |
| Management reviews the pipeline in a parallel spreadsheet | Yes | No |
| The process is defined and the system cannot represent it | No | Yes |
| Integration is technically impossible | No | Yes |
| The vendor stopped supporting the product | No | Yes |
When it really is the tool
There are cases where the change is justified: the process is defined and the system cannot represent it; maintenance cost grows with no relation to usage; integration is technically impossible; the vendor stopped supporting the product.
The difference is that in those cases the decision is made with judgment, not out of frustration.