What a CRM is (and why your business probably needs one already)

Almost every small business already has a CRM. The problem is it's scattered across a notebook, a spreadsheet that got copied three times, each rep's WhatsApp chats and the memory of whoever has been answering the phone for ten years. It works until someone goes on holiday, changes jobs, or simply forgets to call back a customer who was about to buy.

What a CRM is, plainly

CRM stands for customer relationship management. In practice it's a single place holding everything your business knows about each customer and each prospect: who they are, how to reach them, what you sold them, what they asked for, what was promised, when to follow up. It isn't invoicing and it isn't an ERP: the ERP knows what you sold them; the CRM knows why they bought and what's missing for them to buy again.

Put another way: the ERP stores closed deals, the CRM stores the ones still open. And that's where the money nobody accounts for gets lost, because a sale that never happened shows up in no report.

What a CRM looks like inside

“Organizing the customer relationship” sounds like consultancy talk until you see it on screen. These four views are the ones used every day: a customer record, a pipeline, a portfolio you can filter, and the rep's day on their phone. Names and numbers are made up — none of these is a real customer's screen — but each one is built on a CRM running in production today.

That record is the difference between a business that knows its customers and a person who knows its customers. While the knowledge lives in someone's head, the company is renting it; once it lives in the record, the company owns it.

Five signs you already need one

• When a rep leaves, their book of business leaves too: nobody else knows who they were talking to or where things stood.
• Someone asks “has this customer bought from us before?” and answering means checking the billing system, the inbox and a chat thread.
• Follow-up depends on someone remembering. Every “I'll call you next week” quietly falls through.
• You can't say with data how many active prospects you have, in which area, or how long they've gone without contact.
• The same customer is entered two or three times, with the name spelled differently each time.

Before the CRM comes the list: who you're going to sell to

There's an earlier step almost nobody has solved. To sell in an area you first need to know who's in that area, and that list usually doesn't exist: it's built by hand, goes stale, and lives in the head of whoever walked the route.

For a distributor selling door to door, that list was built from the map: we drew the polygon over the city, the system swept it cell by cell, and 747 businesses in the category were surveyed with address, phone and opening hours, deduplicated so the same location wouldn't appear twice. Only with that list loaded does the CRM make sense, because an empty CRM sells nothing.

What the organization gains in the first weeks

Almost none of what follows needs a year-long rollout or a predictive model. It depends on something far more boring: the data existing, living in one place, and being filterable.

Why most CRMs end up abandoned

Almost always for the same reason: the data never gets entered. And it doesn't get entered because the tool was designed for someone sitting at a computer with time to spare. A rep standing on the sidewalk between two visits isn't going to fill in a fifteen-field form: they're going to write in the notebook. By month's end the CRM is empty and the wrong conclusion is that “the system doesn't work”.

The fix isn't demanding more discipline, it's lowering the cost of logging. In that same CRM, the rep dictates or writes the daily report in plain prose — who they visited, what was asked for, when to come back — and a language model interprets it and proposes the updates already structured. The person confirms or corrects. That's the difference between it getting logged and not.

The other thing that decides whether it gets used is how much work it saves on day one: the app opening straight onto today's route, ordered by priority and proximity; a price list that's searchable on the phone instead of a PDF; each profile — rep, supervisor, back office — seeing only what's theirs.

A CRM also shows you what you'd rather not see

Tidying up the customer relationship almost always uncovers deeper data problems. In one back office with 10,055 customers synced from their ERP, measuring showed only 31% had a tax ID on file. That stops being a suspicion and becomes a concrete list of things to fix — and it explains why invoicing, collections and any campaign fail later on.

Off-the-shelf or custom?

If your sales process is fairly standard — few channels, a small team, a simple cycle — an off-the-shelf CRM is enough and it's the cheapest way to start. Custom is worth considering when the way you sell doesn't fit the packaged form: selling on the street, different prices per customer, a prospect list you have to build, internal approvals, or an integration with the management system you already run. When a vendor tells you “that can't be done”, it usually means it doesn't fit their product, not that it's impossible.

Where to start

• Write down on one page what you need to know about a customer in order to sell better. That's your CRM's data model, not the feature list on a brochure.
• Unify the customer list first: one customer, one record, no duplicates. Without that, any tool will lie to you.
• Pick a single process to start with — prospect follow-up, say — and measure after four weeks how many contacts didn't fall through. Then add the rest.

If you'd like, tell me how your team sells today and I'll tell you whether an off-the-shelf CRM is enough or whether it's worth building one around your operation. The first call is a no-strings diagnosis.