There. You know what CRM is. And that knowledge is almost completely useless for making a good decision about CRM for your business.
Why definitions fail
CRM definitions explain the category. On their own, they can leave you knowing what CRM is without knowing what it means for your business.
Definitions describe a category. They do not help you navigate within it. Knowing that CRM manages customer relationships does not tell you which CRM to choose, how to implement it, or what success looks like.
Apply it to your work
Choose the CRM question before the CRM product
What problem in the customer relationship needs to change?
- The work is clear
Test fit against the actual process, users and information.
- The work is still unclear
Define the problem and what success would look like before selecting a system.
The questions that actually matter
Instead of what is CRM, ask these questions.
What problem am I trying to solve?
Not improve customer relationships. That is too vague. What specific operational problem do you have? Leads are falling through the gaps. Sales pipeline visibility is poor. Customer data is scattered. Follow-ups are inconsistent.
The more specific the problem, the better your CRM decision will be.
What does my sales process actually look like?
Not the version on the wall chart. The real version. How do leads come in? What happens to them? Who is responsible for each stage? Where do things get stuck? Where do things fall through?
Your CRM needs to support this process, not replace it with a generic one.
Who needs to use it?
Every person who will interact with the CRM has different needs. Sales needs pipeline visibility. Marketing needs campaign tracking. Operations needs customer data. Leadership needs reports.
Optimising only for one group can make the system less useful for others. Understand the needs of the people who will use it before choosing.
What data do I have, and what state is it in?
Migrating bad data into a new CRM gives you bad data in a new system. Before choosing a CRM, audit your existing data. How complete is it? How consistent? How current?
This audit often reveals that the data problem is bigger than the software problem.
What am I willing to change?
A CRM works when people use it. People use it when it fits how they work. But a CRM also requires some changes in how people work: data entry, process adherence, reporting.
How much change is your organisation willing to accept? The answer to this question determines the complexity of CRM you can successfully adopt.
How will I know it is working?
Define success before you start. Choose targets relevant to your baseline and capacity. Illustrative targets might include visibility of every active opportunity, lead response within four working hours, or completeness above 90% for agreed essential fields. These are example targets, not measured outcomes or standards every business should adopt.
Measurable success criteria prevent the slow drift into CRM is not working but we are not sure why.
The decision framework
Here is a simple framework for CRM decisions:
- Define the specific problem
- Map the current process
- Identify who needs to use it
- Audit your data
- Determine your change appetite
- Set measurable success criteria
- Then, and only then, evaluate platforms
Starting at step seven can leave important operational questions unanswered.
The better question
The question is not what is CRM. The question is what do we need from CRM, given who we are, how we work, and what we are trying to achieve?
That question is harder to answer. It requires honest self-assessment. It requires understanding your operations. It requires knowing your people.
But it leads to better decisions. And better decisions lead to CRM that actually works.
From the Yopla source archive dated 2025-12-20. Refreshed for this edition.
All insights