Does Your Business Need a New CRM or a Clearer Process?

📅 20/10/2026⏱ 8 min readBusiness Insights

At some point, someone says it out loud. “This CRM isn’t working. Should we switch?”

It is a fair question. Follow-ups are slipping, and the data cannot be trusted. As a result, the team has quietly gone back to spreadsheets. Meanwhile, a different system looks cleaner, and the demo made everything seem simple.

However, a new CRM or a clearer process is not always an either-or choice. Sometimes the system is the limit. More often, though, the system is simply showing you how the work really runs.

So this article helps you tell the difference before you spend the money.

Why the CRM usually gets the blame

A CRM is where the work becomes visible. For example, every missed follow-up, duplicate contact and empty field shows up there. As a result, it is easy to read the mess as the CRM's fault.

But a CRM only records what people put into it. If two people use the same field differently, the CRM will hold both. Likewise, if nobody agreed what a stage means, the stages will drift.

Switching also feels like progress, because there is a decision, a date and a fresh start. However, if the underlying process has not changed, the old habits move across with the data.

In other words, the business can end up paying twice. First it pays for the new system, and then it pays again for the same disconnection.

Signs the process is the real limit

These patterns suggest the process needs attention first. Indeed, any of them can sit comfortably inside a perfectly capable CRM.

People mean different things by the same stage or field.
Nobody has agreed who owns the next step after an enquiry arrives.
Team members keep their own spreadsheets or notes alongside the CRM.
Follow-up depends on someone remembering, rather than on a clear trigger.
Reports look wrong because data is entered in different ways.
Information still has to be copied between the CRM and the inbox, forms or calendar.

None of these is a software fault. Instead, they are gaps between people, information, systems and processes. A new CRM would inherit every one of them.

Signs the CRM itself may be the limit

Sometimes the system genuinely does not fit. The test, then, is whether you can name the limit specifically, and write it down.

It cannot connect to something you have defined as essential, such as your enquiry form or phone system.
It cannot support a process you have already mapped and agreed.
Permissions or reporting cannot be set up the way the business needs, even after the settings have been checked.
The cost or licence structure no longer fits the way the team works.
You cannot export your data in a usable form.

Notice the common thread. In each case, the need is specific and already understood. Therefore, a vague feeling that the CRM is clunky is not enough. Neither is a demo that looks tidier.

New CRM or clearer process: the one-page test

Here is the most useful question we know. Could someone in your team draw, on a single page, how an enquiry moves from first contact to done?

If you cannot, start there

If the page is hard to draw, a new CRM will not draw it for you. People will still disagree about the stages. Instead, the new system will hold the disagreement in a smarter-looking screen.

If you can, compare the page with the CRM

If the page is clear, the comparison becomes easy. Does the CRM support each step? Where it does not, is the gap in the settings, or in the product? Only the second is a reason to switch.

What a clearer process actually means

'Clearer' can sound vague. In practice, it comes down to a few plain things that anyone in the team can see.

Each stage has a name and a meaning that everyone shares.
Each step has one named owner.
Information lives in one agreed place, and is entered once.
There is a simple rule for what happens next, and when.
There is a defined route for a person to step in when judgement is needed.

None of this needs new software. However, it gives any software, old or new, something solid to work with. It also makes the choice between systems far easier, because you know what you are asking each one to do.

What to do before you pay to switch

First, work through a short checklist. It can save money and upheaval.

Write down what the business needs the CRM to do, in plain words.
Map the current process on one page, and mark where it breaks.
Agree what each stage means, and who owns each step.
Check what the current CRM already offers, and what has never been set up.
Clean the data you would want to keep, before it moves anywhere.
Decide how the team will use the system day to day.

Next, take care with the customer data itself. Customer records are personal data, so UK GDPR still applies when you move them. For this reason, the ICO publishes guidance for organisations on what that involves.

See the ICO's UK GDPR guidance and resources for the starting point.

If you do switch, keep the process first

Sometimes the honest answer is that the CRM has reached its limit. In that case, a move can be the right decision.

Even then, the order matters. First, move the agreed process, not the old mess. Then pick a quieter period rather than your busiest weeks. Next, test one flow of enquiries before the whole business moves. Finally, keep a clear route for a person to step in.

In one Davina Connect implementation, for Bridging Loans Broker, the CRM followed how the business already qualified and booked enquiries. The pipeline stages followed the work, rather than the other way round. Staff could still move a contact through the pipeline by hand. In that case, the surrounding automation stayed in step with the manual action. The team therefore did not have to change how they worked.

Understand first. Technology second.

Frequently asked questions

How do I know if my CRM is the issue?

Start by naming the limit specifically. If it is a clear need the system cannot meet, the CRM may be the issue. However, if it is a vague frustration, look at the process first.

Will a new CRM fix our follow-up?

Not on its own. A CRM can prompt follow-up, but someone still has to own it. So first agree the trigger and the owner, and then set the system to support them.

Is it worth fixing the process before switching?

Usually, yes. A clearer process makes either decision easier. For instance, it shows what you need from a CRM, and it moves with you if you do switch.

Can I use the CRM I already have?

Often you can. First, check what the current system already offers, and which settings have never been used. Then compare it with the process you have mapped.

When is a new CRM the right choice?

When the limit is specific, written down and cannot be met by the settings. For example, an essential connection may be missing. In that case, switching can be sensible.

Understand first, then decide

A new CRM or a clearer process is rarely a question the software can answer for you. Instead, it starts with how the work actually moves through the business.

The Davina Connect Business Review looks at people, information, systems and processes together. As a result, the recommendation might be a better process, a changed setting or, sometimes, a new system. It never starts with a tool.