When Does a Small Business Actually Need a CRM?

“You need a CRM” is one of the most common pieces of advice a growing small business hears, usually from whoever has just started using one themselves.

It's not bad advice exactly. It just tends to arrive before the actual question has been asked: does this business, right now, actually need one?

Sometimes the honest answer is yes and has been for a while.

Sometimes the honest answer is not yet. A well-kept spreadsheet may still be doing its job perfectly well.

The point is to understand which situation you're looking at rather than assume the answer is automatically “buy a CRM.”

What a CRM actually does

Strip away the sales language and a CRM is a shared, structured place to keep track of who your contacts are, what's been said to them and what needs to happen next.

That's it.

It doesn't generate leads. It won't fix a service problem or run itself the day you sign up.

What it can do is reduce dependence on any one person's memory, inbox or spreadsheet tab for information the wider business needs.

A spreadsheet can do a version of this too, sometimes for quite a long time.

The question isn't whether a spreadsheet is inferior software. It's whether the way you're currently tracking customers is creating risk or friction that a shared system would genuinely remove.

Signs a spreadsheet is still doing its job

A spreadsheet is often perfectly adequate and there's no prize for replacing it early.

It may still be doing its job well when:

• One or two people handle most customer contact and they know their own area well enough to keep it straight.
• Deals or enquiries move through a small number of predictable stages and nothing regularly falls through the gaps.
• Nobody is repeatedly asking, “Wait, did we already reply to this person?”
• The spreadsheet still gets updated promptly rather than several days after the conversation actually happened.

Signs the tracking has started costing you

The signs that a business has genuinely outgrown manual tracking tend to be less about size and more about how many people touch a customer and how often.

It's worth paying attention when:

• A lead goes cold because nobody followed up and ownership of that follow-up was never clear.
• More than one person needs the full picture on a customer but at least one of them is working from a partial one.
• Two people contact the same person, or nobody contacts them at all, because responsibility isn't clear.
• Finding out where a particular deal or enquiry stands means searching through an inbox rather than checking one shared place.
• The spreadsheet itself has started needing its own manual system: separate tabs, colour-coding and private notes layered on top just to keep it usable.

None of these things is a crisis on its own.

When they start happening regularly, though, the tracking system may be quietly costing the business money and attention.

That's a much more useful signal than any arbitrary headcount or revenue threshold.

What the evidence actually shows

It's worth looking at how AI and CRM adoption connect in practice because the two are increasingly sold together.

DSIT's UK Business Data Survey 2026 found that among businesses already using AI, only 21% said their AI tools were integrated into existing business systems, such as being embedded within a CRM rather than sitting apart from it.

The data suggests that even among businesses already using AI, integration into existing business systems is still far from universal.

CRM implementations can fall short even when the software itself is capable.

The reasons often sit outside the platform: unclear processes, limited adoption, poor configuration or insufficient time for testing and training.

The pattern isn't necessarily about the software being bad. Problems often begin when a business buys a CRM before agreeing how the team will actually use it.

The system can then sit half-configured, unloved and eventually ignored.

A case in point, at a much larger scale

The clearest illustration of this principle isn't a small-business story, but the underlying lesson doesn't depend entirely on scale.

In 1999, Hershey went live with a combined $112 million ERP, CRM and supply-chain system. A rollout originally planned over a much longer period was compressed so the system would be ready before a Y2K deadline.

The system went live in July, just as Halloween ordering season was beginning to build.

According to CIO, Hershey had inventory available but struggled to process and ship orders. The company reportedly missed around $100 million in Halloween and Christmas orders that year.

The systems themselves weren't simply defective. The business hadn't had enough time to test them properly, train staff or adapt its own processes before one of the busiest periods of the year.

Almost nobody reading this runs a business at Hershey's scale.

The useful part of the example is the mechanism: technology being installed to meet a deadline that had little to do with whether the business or its people were actually ready for it.

Where this fits into a connected business

This is the same argument we made in AI Enquiry Assistants: Where They Fit and Where They Don't.

The tool isn't the starting point. Understanding how the business actually works is.

A CRM bought before that understanding exists can become exactly what we've described elsewhere as business disconnection: one more system that doesn't quite match how work actually gets done.

It can end up sitting alongside the spreadsheets and inboxes it was supposed to replace rather than genuinely connecting them.

The signs worth checking before buying a CRM are close cousins of the three quiet signs of business disconnection: repeated questions, answers that take longer to find than they should and one person quietly holding more of the business in their head than anyone realises.

If those sound familiar, a CRM may be worth a serious look.

If they don't, the honest answer may simply be not yet.

What this looks like in practice

In one Davina Connect implementation for Bridging Loans Broker, the CRM and its pipeline stages were built around how the business already qualified and booked enquiries rather than forcing the business to work around the software.

Staff could still move a contact through the pipeline manually. The surrounding automation stayed in step with that action instead of continuing from outdated information.

The CRM had a role, but it worked as part of the wider customer journey rather than as a separate system.

Questions worth asking before buying one

• What specific, repeated need is this CRM meant to address rather than simply “we should probably have one”?
• Who on the team actually needs the full picture on a customer and what are they missing right now?
• Has the team agreed how the CRM will be used day to day before the contract is signed?
• Is there enough time to configure, test and train properly or is the system being squeezed in around an unrelated deadline?
• Will the CRM connect with the systems already in use or become one more separate place for information?