Should you use a CRM?

The question is normally asked as one about size — are we big enough for a CRM — and size is a poor predictor. What creates the need is the handoff. While one person receives every enquiry, works it and remembers it, their own record is adequate and often better than anything imposed. The moment an enquiry can arrive with one person and be worked by another, information starts being lost in the gap, and that happens at two people rather than at twenty.

The second trigger is retrospective. If you cannot say how many enquiries arrived last month, how many were answered, and what became of them, you have already lost the thread, and no amount of memory reconstructs it. That inability is worth treating as the signal itself, because it is precisely the data that decides marketing spend, capacity and whether anything is being lost.

What is genuinely needed at first is small enough that the tool is a secondary question. Arrival time, channel, source, first response time, and outcome including none — five fields, captured at arrival. A spreadsheet holds those and can be running this afternoon, which matters because the most common failure in this decision is a lengthy evaluation that ends with nothing in place for another quarter.

A dedicated system earns its place when the manual version starts failing in specific ways: entries not made because someone was busy, no reliable prompt for follow-up, no shared view when several people are involved, and no history visible when a customer calls back. Those are the functions worth paying for. A system bought before those failures appear is generally bought on features nobody yet needs, and configured by someone guessing at how the work will run.

The selection criteria that matter are unglamorous and rarely lead a demonstration. Can it capture enquiries automatically from your actual channels, or does everything require typing? Does it show a customer's history when they get in touch? Can you get your data out in a usable form? Will the people who must use it find it faster than not using it? The last question decides more outcomes than any feature comparison, and it is answerable only by having those people try it.

The trap worth naming is buying capability for a future state. Businesses select systems for the pipeline stages, automation and reporting they expect to need in three years, then require staff to operate that complexity today for no present benefit. The result is the familiar one: partial adoption, unreliable data, and a conclusion that the system was wrong when the configuration was.