Does your business actually need a CRM?

A business asking for a CRM may first need a reliable way to track conversations. Those are not always the same problem, and buying the wrong category of tool is an expensive way to find that out.

A CRM is a system for managing relationships over time: who you are speaking to, what stage the conversation has reached, what was agreed, and what happens next. If your sales process is short, informal and handled by one or two people who already know every customer by name, a simple shared record may meet the immediate need.

Four things people call a CRM

Being precise about the category makes the decision much easier.

A contact list

Names, numbers, emails, maybe a note. Useful, cheap, and often enough. A shared address book or a well kept table does this job.

A CRM

Contacts plus pipeline. Stages, owners, follow-up dates, a history of interactions. Built for businesses where the gap between first contact and paid work is long enough that things fall through it.

A job or operations system

This tracks work rather than relationships: jobs, sites, engineers, materials, scheduling, completion, invoicing. Many businesses that say they want a CRM actually want this. A sales pipeline is the small part of their day; delivery is the large part.

A bespoke system

Purpose built software that models how one organisation works, usually because the process is unusual enough that no product matches it without heavy compromise.

If your biggest problem happens after someone becomes a customer, a CRM is probably not the answer.

Signs a CRM is justified

• More than one person handles enquiries and they cannot see each other's work.
• Enquiries go quiet and nobody notices for weeks.
• You cannot answer, without asking someone, how many live opportunities exist.
• The sales cycle involves several contacts over weeks or months.
• Knowledge about a customer lives in one person's inbox and leaves when they do.
• You need handover between sales and delivery to be reliable rather than remembered.

Signs it is not

• Enquiries convert the same day or not at all.
• One person handles all customer contact and is not overloaded.
• You would be entering data purely so that the system has data in it.
• The real problem is scheduling, stock, quoting or job progress, not follow-up.
• Nobody has agreed what the stages of your process actually are.

That last point matters more than the software choice. A CRM records a process. If the process is undefined, the tool will record confusion faithfully.

When off the shelf is the better answer

For a fairly conventional pipeline of enquiry, quote, follow-up, won or lost, established products are hard to beat. They are mature, supported, updated without you, and cost a predictable amount per user. Buying one is usually the sensible first move, when the product fits the process and its costs and terms are acceptable.

Use a product when your process resembles the process the product assumes, when you can live with its vocabulary, and when the data you need to hold fits its fields without inventive workarounds.

When a custom internal tool makes more sense

Custom becomes reasonable when the shape of your work is genuinely specific and a product only fits after a chain of compromises. Common signals include operational data that has no natural home in the product, several disconnected tools holding pieces of the same record, or a workflow where people export to a spreadsheet to do the real work.

A custom internal tool is scoped to one organisation. That is its advantage and its cost: it fits precisely, and somebody has to maintain it. It is not a replacement for every commercial CRM and should not be sold as one.

Questions to answer before you buy or build

1. What decision or handoff is currently going wrong, and how often?
2. What are the actual stages of our process, written down in plain words?
3. Who will enter the data, and what do they get back for doing it?
4. What single question do we want to answer instantly that we cannot answer today?
5. What happens to this data if we stop paying the supplier?
6. Can we trial a product for a month against real work before committing?

If you cannot answer the second and third questions, wait. Defining the process takes time, but it can clarify whether a purchase is needed at all.

A reasonable sequence

Write the process down. Try a well supported product against it for a month with real enquiries. Note precisely where it fights you. If the friction is cosmetic, stay. If the friction is structural and repeated, that is when a scoped internal tool starts to earn its cost.

Doing nothing is also a legitimate outcome. A business that is not losing work to poor follow-up does not need a follow-up system.

Explore custom CRM and internal tools, or compare the wider options in buy, build or integrate.