CRM stands for customer relationship management, and CRM software is the system a business uses to keep track of the people it sells to. That’s the short version. The longer one matters more, because “CRM” gets used for everything from a contact list to a huge platform with its own consultants, and it’s hard to choose when you’re not sure what you’re choosing.
So here’s a plain explanation of what CRM software does, what’s in a typical system, what a sales team really uses and how to pick one. We build a CRM ourselves, so keep that in mind as you read. We’ve tried to describe the category fairly.
What it’s for
At its simplest, a CRM is a shared memory for your sales team. Every lead and customer has a record. The record holds who they are, how they found you, what’s been said, what’s been promised and what happens next. Anyone on the team can open it and know where things stand.
Without one, that knowledge lives in inboxes, notebooks, spreadsheets and people’s heads. It works while one or two people are selling. It stops working when more people need the same information, when a follow-up gets missed, or when somebody’s away and nobody else knows what they were doing. If that’s the stage you’re at, seven signs your sales team has outgrown its spreadsheet is worth reading.
What’s in a typical system
Different products package things differently, but most include the same building blocks.
Contact and lead records. The core. Names, companies, phone numbers, emails, where the lead came from and who owns it, plus your own fields for whatever matters to your business. In Henkan CRM this is the lead profile, one page holding the contacts, deals, notes, tasks and full history.
Activity history. A dated log of calls, emails, notes and changes, so nobody has to ask “what happened last time?”
Tasks and reminders. A way to say “ring this person on Thursday” and have the system remind the right person on the day. This is the feature that most directly stops leads going cold. See tasks and callbacks.
A pipeline. A view of your deals by stage, with values, so you can see what’s in progress and where things stall. See the sales pipeline, and how to set up a sales pipeline your team will follow.
Ways to get leads in. Web forms, imports and connections to other tools, so leads arrive without being retyped. See capture.
Email, calls and messaging. Sending emails from the record, logging calls and keeping replies with the lead.
Quotes and proposals. In some systems, building and sending a proposal from the lead and collecting a signature. See proposals and e-signature.
Reports and dashboards. Where leads come from, how long deals take, how each person is doing and what you can expect to win.
Permissions. Who can see and change what.
Where the differences are
Two systems can tick the same boxes and feel completely different to use. The things that actually separate them are:
How much it asks of you. A heavy system wants lots of fields filled in and lots of set-up. A lighter one gets out of the way. For a small or medium-sized team the lighter one usually wins, because it actually gets used.
How well it fits your process. Can you use your own stages, fields and deal types, or do you bend your process to the system’s?
Who can run it. If only one technical person can change anything, you’ve swapped one dependency for another.
What’s included and what’s extra. Features sold separately can change what you really pay. We cover that in how CRM pricing works.
What happens to your data. Where it’s held, who can see it and whether you can get it out again.
Do you need one?
Not necessarily, and not yet, for everyone. One person with a short list of leads can manage with a good spreadsheet. A CRM earns its place when follow-ups are slipping, when history matters, when more than one person works the same leads, or when you want to see numbers without asking someone to build them. Our honest comparison, spreadsheet vs CRM, goes through both sides.
How to choose
Keep it practical.
Start by writing down what’s actually going wrong in your sales process. Missed callbacks, no history, proposals chased by hand. That’s your requirements list, and it matters far more than any feature table.
Then describe how you sell: where leads come from, your stages, what you sell and who does what. Take that to every demo, and ask to see your own process in the system.
Check that your whole team could use it, which means your least technical rep, not your most enthusiastic one. Ask about set-up, data import, pricing, contract terms, where data’s held and how you get it back. Get answers in writing.
How to choose a CRM for a team of 3 to 15 goes through this step by step, and what makes a good CRM for a small business looks at it from the other direction: what to look for and what to ignore.
CRM, lead management and other terms
You’ll see several names for similar things: CRM system, customer management software, client relationship management, contact management. They overlap a lot. One distinction is worth knowing. Lead management software focuses on the early part, capturing and following up enquiries. A full CRM covers that and the rest of the relationship. We explain the difference in lead management software: what it does and who needs it.
Getting started well
Whichever system you pick, how you introduce it matters as much as the choice. Move your data across carefully (moving from Excel to a CRM shows how), pick a switch-over day, and make sure the manager runs meetings from the system so everyone follows. Getting your whole team to use the CRM covers the first weeks. And for small teams in particular, CRM for small business sets out what you need and what you can skip.
Where Henkan CRM fits
We built Henkan CRM for small and medium-sized sales teams that follow up leads and send proposals. You set your own deal types, stages and fields, and reps, managers and owners each see what they need, which you can browse on the for who pages. There’s no self-serve sign-up. After a demo we set it up with you, and our team imports your data from a spreadsheet or another CRM. If you want to see how we compare with other systems, Henkan CRM vs other CRMs sets out the questions we think matter.
What it looks like in a normal week
It helps to picture it. On Monday a rep opens their task list and sees six callbacks due, two overdue ones in red. They work through them, and after each call they log the outcome and set the next date. A web enquiry that came in over the weekend already has an owner and a source. On Wednesday a manager opens the pipeline, sees two deals have sat at the same stage for a fortnight and asks about them. On Friday a proposal goes out from a lead’s page, and the system shows when the client opens it.
None of that is clever. It’s the routine of selling, with the remembering done by software rather than by people. That’s really all a CRM is for, and it’s why the best ones feel almost dull to use.
Cloud, on-site and other jargon
Most CRMs today are cloud-based, which means you use them in a browser and the supplier looks after the servers, updates and backups. That’s what small and medium-sized teams generally want. You’ll also hear about integrations (connections to other tools), APIs and webhooks (ways for systems to pass information to each other) and automation (rules that do routine work for you). Ask what each one actually does in the product you’re looking at. If a supplier can’t explain it plainly, that tells you something.
If you’d like to see CRM software working on a sales process like yours, book a demo.




