Small Business12 October 2026 · 5 min read

CRM for a small business: when the spreadsheet stops working

A desk with a notebook of names and a telephone

A spreadsheet is a perfectly good CRM, right up until the afternoon somebody rings about a quote and nobody can find it. That afternoon is the signal, not the number of rows.

Most small businesses are sold a CRM long before they need one, then set it up in a weekend, then stop using it by March because it asks for more than it gives back. It is worth being clear about what actually changes.

The four signs the spreadsheet has stopped working

Two people answer the same enquiry differently. Not because anybody is careless, but because what was said last time lives in somebody’s inbox.
Follow-ups depend on remembering. If the second chase happens only when somebody thinks of it, you are losing work you have already paid to win.
Nobody can say what is in the pipeline. Not a feeling, a number: what is out, what it is worth, how old it is, what is next on each one.
The history is in three places. Email, phone, and whatever was written on a job sheet. Nobody reconstructs that under pressure.

What a CRM is actually for

One record per customer, with everything that has happened on it, and a next action with a date on every live opportunity. That is it. Every other feature is optional, and most of them are the reason people abandon the thing.

The test of a good setup is whether somebody can pick up a customer they have never spoken to and sound informed in ten seconds. If they can, it is working. If they have to go hunting, the software has not solved the problem, it has moved it.

Why most CRM projects fail

It asks for data nobody has time to enter. If the system only works when every field is filled, it will not work.
It does not match how you actually sell. Generic pipelines have stages that mean nothing in your trade, so people invent their own and the reporting becomes fiction.
It is somewhere else. If enquiries arrive on the website, the phone and Instagram, and the CRM is a tab nobody has open, it goes stale within weeks.

That last one is why we build the enquiry form, the inbox and the pipeline as one thing rather than three. A lead that arrives on the site should already be in the pipeline with a next action, before anybody has typed anything. That is the CRM and pipeline side of what we do, and it usually sits on top of the same system as the automation that chases the quote.

What to do before buying anything

Write down the last ten enquiries and what happened to each. Most businesses find two or three that simply stopped, with no decision either way. Those are the ones a CRM is worth paying for, and that number is also the honest way to judge whether a system earned its cost at the end of the year.

Then start smaller than you think. One record per customer, one owner, one next action. Add nothing else until that is a habit. If a packaged tool does that for you, buy it; if your sales process has rules a generic pipeline cannot express, that is when a built system makes sense, and we will say which we think it is before quoting.

Questions

Before you ask.

When does a small business actually need a CRM?

When two people answer the same enquiry differently, when follow-ups depend on somebody remembering, when nobody can say what is in the pipeline and what it is worth, or when a customer’s history is spread across email, phone and job sheets.

Is a spreadsheet good enough?

Often, yes, and for a long time. The signal to move is not the number of rows, it is the first afternoon somebody rings about a quote and nobody can find what was said.

Why do most CRM rollouts fail?

They ask for data nobody has time to enter, the stages do not match how the business actually sells, or the CRM is a separate tab nobody has open while enquiries arrive somewhere else.

Should the website feed the CRM?

Yes. An enquiry from the site should arrive as a record with an owner and a next action, before anybody types anything. If the website and the pipeline are separate systems, one of them goes stale.

Packaged CRM or a built one?

Buy packaged if a standard pipeline matches how you sell. Build when your process has rules a generic pipeline cannot express, or when the CRM needs to sit on the same system as your orders, bookings or jobs.