What a CRM Actually Does

Why a spreadsheet works — until it suddenly does not

Most businesses start tracking leads in a spreadsheet, and for a while, that is completely fine. With a handful of enquiries a week, one person can hold the whole picture in their head: who reached out, what was promised, who still needs a call back. The spreadsheet is really just a backup for memory that is already doing most of the work.

The trouble starts when volume or headcount grows past what memory can reliably hold. A spreadsheet does not remind anyone that a lead has gone quiet for eleven days. It does not know that the person who spoke to a prospect last week is now on leave, and that nobody else can see what was actually discussed. It does not stop two people on the same team from calling the same lead on the same afternoon, unaware of each other. These are not spreadsheet bugs — a spreadsheet was never built to do any of this. It is a table, not a system.

The common failure story looks the same across most small businesses: a promising enquiry comes in, gets a first reply, and then sits untouched in a row nobody revisits. Nobody decided to drop it. It just never had anything actively pushing it back into view. Multiply that by every lead that arrives while the business owner or sales rep is busy with something else, and a spreadsheet quietly becomes a graveyard of good leads that were never technically lost — just never followed up.

What a CRM actually centralizes

A Customer Relationship Management tool solves a narrower problem than its name suggests. It is not about managing "relationships" in the abstract — it is about centralizing three concrete things that a spreadsheet cannot hold on its own.

Contact history. Every call, email, WhatsApp message, meeting note and quote sent to a person or company lives on one timeline, attached to that record. Anyone who opens the lead — including someone who has never spoken to them before — can read the full story in under a minute instead of asking the prospect to repeat themselves.

Deal stage. Where an opportunity currently sits — new, in conversation, waiting on a decision, closed — is visible at a glance, to anyone who needs to know, without asking the person handling it. This is the difference between a manager who can answer "what is likely to close this month?" instantly and one who has to go ask three people and wait for replies.

Tasks. What needs to happen next, and by when, is attached directly to the record rather than floating in someone's head or a personal to-do list. When the person responsible for a lead is unavailable, the task is still visible and still gets picked up.

A CRM is a system, not a database

It is worth being precise about this distinction early, because it explains most CRM rollouts that quietly fail. A database is a place things get dumped and occasionally looked up. A system is something that actively drives what happens next — it tells someone to follow up today, flags a deal that has stalled, and shows a manager where attention is actually needed.

A CRM only delivers the second kind of value if the whole team treats it as the single source of truth, updated in real time, rather than an optional extra kept alongside the "real" tracking that still happens in someone's private notebook or memory. Chapter 5 covers this failure mode directly, because it is the single most common reason a CRM purchase does not pay off.

Who actually needs one, and when

This is less about company size than about whether coordination and memory have become the actual bottleneck. A solo consultant fielding a few enquiries a month, all handled personally from first contact to close, can often get by without one — for a while. The moment more than one person needs to see the same pipeline, or the pace of enquiries outpaces what any single person can hold in their head, the maths changes. At that point, the cost of a missed follow-up or a duplicated outreach starts to outweigh the effort of setting up and maintaining a proper system.

• You cannot remember which leads you have already followed up with this week.
• Two people on the team have separately contacted the same lead without knowing it.
• A lead has gone quiet and nobody notices until someone happens to ask "did we ever hear back from them?"
• Every new hire needs a personal walkthrough of "how we track this stuff" because it lives in someone's head, not a system.
• Contact history for a lead was lost because the person who spoke to them left the business.
• Reporting on "how many deals are we likely to close this month" means manually counting rows in a spreadsheet.