CRM Is Not Software... It Never Was!

I have sat across the table from enough business owners and sales leaders to know what the conversation usually sounds like. They want a CRM. Specifically, they want HubSpot. They have seen a demo, a competitor is using it, or someone on the team recommended it. The question they come to me with is almost always the same: how do we set it up?

It is the wrong question. Not because HubSpot is the wrong answer, in many cases it is exactly the right answer. But the question reveals a fundamental misunderstanding of what CRM actually is, and that misunderstanding is usually the reason the implementation will struggle.

The problem is not the platform. The problem is that most organisations approach CRM as a software project when it is actually an operational strategy.

If Your CRM Is Already Not Working, Read This First

A significant number of the businesses I speak with are not approaching CRM for the first time. They already have a platform. It may even be HubSpot. But six months or two years in, something is off. The team is not logging activity consistently. The pipeline does not reflect reality. Leadership has stopped trusting the reports. Nobody can say with confidence where a deal actually is or why a customer went quiet.

If that sounds familiar, it is worth knowing that the problem is almost certainly not the platform. I have audited enough CRM portals to say with confidence that the gap between what a CRM could do and what it is actually doing for a business is almost never a software problem. It is a strategy and process problem that was present before the platform was installed and that the platform faithfully preserved.

The frustrating truth is that a CRM implementation can make a struggling operation feel more organised in the short term, contacts are in one place, pipelines are visible, someone built a dashboard, while the underlying operational gaps remain untouched. It takes a few months for the gap between the appearance of organisation and the reality of the operation to become visible. By then, the implementation is often blamed.

This article is about what should happen before the platform is touched, and what needs to change if the platform is already in place and underdelivering. The answer is the same in both cases: strategy and process before software.

When an organisation with unclear processes, inconsistent follow-up, and customer knowledge scattered across WhatsApp threads installs a CRM, what they get is a more expensive version of the same problem. The dysfunction is now digital.

I have seen it play out more times than I care to count. A business invests in a platform, spends weeks on configuration, and six months later the CRM is either not being used properly or has become a graveyard of outdated contacts and half-completed deals. Leadership concludes that CRM does not work for businesses like theirs. In reality, CRM failed because the foundation was never built.

What CRM Actually Is

|CRM stands for Customer Relationship Management. Note what is absent from that definition: software. A platform. A subscription. A database.

CRM is the structured management of customer relationships across the entire lifecycle in order to maximise long-term mutual value. It is strategic. It is cross-functional. It is lifecycle-oriented, customer-centric, and revenue-connected. It is how an organisation thinks about, designs, and operates its relationships with the people it serves.

Software, whether that is HubSpot, Salesforce, Zoho, or anything else — is the operational layer that supports the strategy. It is where the strategy runs. It is not the strategy itself.

This distinction matters enormously in practice. Organisations that understand CRM as a strategy design their customer journey before they configure a pipeline. They define lifecycle stages before they build automation. They clarify ownership and accountability before they set up workflows. Then they use the platform to make those decisions visible, consistent, and scalable.

Organisations that understand CRM as software do the opposite. They configure first and think later. They automate before they have standardised the process being automated. They add contacts before they have decided what to do with them.

The Sequence That Changes Your Perspective

There is a principle I return to in every client engagement, regardless of industry, geography, or team size. It is deceptively simple.

This is not a preference or a consulting philosophy. It is the correct sequence for building anything operational that involves human beings. Technology should support operational maturity, it should not attempt to create it.

What does this look like in practice? It means that before a single workflow is built, before the first pipeline stage is created, before a single contact is imported, the following questions need to have real answers.

• Who owns the customer relationship at each stage of the lifecycle?

• What does the handoff from sales to onboarding look like, and who is responsible for making sure it happens cleanly?

• How does the organisation define a qualified lead, and is that definition shared across every team member who interacts with prospects?

• What does a successful customer onboarding look like, and how do you know when it has been completed?

These are people and process questions. They have nothing to do with software. And yet most organisations cannot answer them clearly before they start their CRM implementation.

When the sequence is wrong — when technology is introduced before people and process are aligned — the platform absorbs and reflects whatever dysfunction already exists. Inconsistent follow-up becomes inconsistently logged activity.

Unclear ownership becomes unassigned contacts. Poor handoffs become broken workflows. The CRM does not fix these problems. It makes them visible in a way that is harder to ignore, which is useful, but only if the organisation is prepared to address what it finds.

Force and Friction: A Practical Lens

One of the frameworks I use in consulting work is something I call Force and Friction. It is a straightforward diagnostic lens that applies to any customer-facing operation.

Force is anything that moves a customer relationship forward.

• Trust

• Clarity

• Responsiveness

• Confidence

• Convenience

• Consistency

When an organisation scores well on these, customers move through the lifecycle smoothly, from awareness to enquiry to commitment to retention.

Friction is anything that slows down, damages, or blocks that movement.

• Delays

• Unclear processes

• Slow or Poor communication

• Inconsistent handoffs

• Onboarding confusion

• Operational silos

When friction is present, customers feel it, even if they cannot name exactly what is wrong. They feel the confusion when no one follows up. They feel the gap when they have to re-explain their situation to a new team member who was never briefed. They feel the uncertainty when they do not know what happens next.

The objective of CRM strategy is to design and operate a system that increases Force while reducing Friction across every stage of the customer lifecycle. That design work ideally should happen before the platform is touched. The platform is where the design is implemented.

When I audit a client's CRM, I am not primarily looking at what has been configured in the software. I am looking at whether the underlying operation has enough Force to sustain the customer relationships it is trying to manage. Most of the time, the friction is obvious before I have opened a single report.

The Five Maturity Levels

Not every organisation starts in the same place, and not every organisation needs to reach the same destination. What matters is understanding where you are, so you can make informed decisions about where to go next.

I evaluate CRM maturity across five levels. Most businesses engaging with CRM for the first time, or revisiting a failed implementation, are operating somewhere in the first two.

The goal of most initial engagements is not to reach Level 5. It is to move from Level 1 to Level 2 with the right foundations, or from Level 2 to Level 3 with clarity and intention. Each progression requires operational work before platform work.

What This Means for Your Business

If you are considering a CRM implementation, or wondering why a previous one did not deliver what you expected, the most useful question to ask is not which platform to use. It is this: do we have the operational clarity to support a CRM?

That means asking whether your team has a shared understanding of the customer journey. Whether you know who owns the relationship at each stage. Whether your follow-up is consistent enough to be automated without amplifying inconsistency. Whether your customer knowledge is documented anywhere, or whether it lives in a WhatsApp group and the memory of your most experienced team member.

If the honest answer to most of those questions is no, that is not a reason to delay. It is a reason to start with strategy before software. To define before you configure. To build the operational foundation that makes the platform worth deploying.

A CRM should make a good operation more visible and more scalable. It will not make a struggling operation suddenly work. That is a job for the strategy, the process design, and the people who need to operate it.

Where to Start

The most practical starting point for any organisation approaching CRM, for the first time or the second, is an honest readiness assessment. Not a software demo. Not a pricing comparison. An assessment of where your operation actually is, what gaps exist in your customer journey, and what needs to be resolved before a platform will help rather than hinder.

We built a self-serve CRM Readiness Assessment specifically for this purpose. It takes around ten minutes to complete, covers five core areas of your customer operation, and gives you an immediate maturity level with a breakdown by category. No contact details required to see your results.

If you are planning a CRM implementation in the next six months, or if you are trying to understand why your current CRM is not delivering what you expected, it is a useful place to start.