A hiring system manages people applying for a job that exists. A CRM manages relationships with people before it does. Most teams have the first and improvise the second, which is why every search starts from nothing.
The difference
CRM stands for customer relationship management. In hiring it means keeping in touch with people you might want later.
| Hiring system | Recruitment CRM | |
|---|---|---|
| Organised around | Open jobs | People and groups |
| A record starts when | Someone applies | You become interested in them |
| Time frame | Weeks | Months to years |
| Success means | Jobs filled | Having people ready when a job opens |
| Fails by | Slow stages | Becoming a newsletter nobody reads |
Many hiring systems now include CRM features. Whether you need a separate product depends far less on the software than on whether anyone is actually going to keep in touch with people.
Who goes in a group
Group people by type of job, not by campaign. Someone belongs in one if you would plausibly want them in the next twelve months:
- People who nearly got hired before — the most valuable group, as Module 5 argued.
- Strong applicants for jobs that closed or were cancelled.
- People you approached who were interested but not right now. Timing is the most common reason for a no.
- Referrals with nowhere to go yet.
- Former employees, which most companies ignore completely.
Every entry needs a reason and a date attached. A group of names with no context is a list, and lists do not get used because nobody can remember who is in them.
Keeping in touch without becoming spam
The failure is a monthly company newsletter sent to people who never asked for one. It produces unsubscribes, and worse, it teaches a valuable audience to ignore your name.
What works is less often and more relevant:
- Quarterly at most, unless there is something genuinely specific.
- Tied to something real — a team growing, a product launch, a job that suits them.
- Personal where the group is small. Twenty near-misses deserve individual messages, not a broadcast.
- With a clear way to opt out, honoured immediately.
The permission side is not optional. You need a reason to hold and contact these people, and in most places you needed to tell them when you collected their details. Module 11 covers it. The practical version: that "may we keep you in mind for future jobs?" question at rejection is doing real work.
Measure people, not emails
Email statistics make this look successful while telling you nothing.
| Measure | Question it answers |
|---|---|
| Group size by type of job | Do we have people ready for the jobs we will open? |
| People contacted per hire, group vs cold | Is the group actually cheaper? |
| Time to first interview, group vs cold | Is it faster? |
| Share of hires from the group | The headline number, and the one to grow |
| Opt-outs per send | Whether you are burning the audience |
Start small
One group, for the type of job you hire most often, filled with the near-misses from last year. That is a morning's work and it will produce candidates on your next search. Company-wide talent communities usually die because they started too big to maintain.