What is the difference between an ATS and a recruitment CRM?
An ATS tracks candidates through a role you are already working. A recruitment CRM tracks the relationships that produce roles in the first place: clients, contacts, prospects and the candidates you have not placed yet. Agencies need both, because winning the role and filling it are different jobs, and a system built only for one leaves the other in a spreadsheet.
The distinction comes from who each was built for. Applicant tracking systems grew up inside employers, where the role already exists and the job is to move applicants through it in an orderly way. Everything is organised around the vacancy: applications arrive, stages advance, someone is hired, the record closes.
Agencies do not work that way. Before there is a role there is a client relationship, a conversation with a hiring manager, a candidate you met two years ago who has just become available. That is CRM work, and an ATS has nowhere sensible to put it.
The practical result of using only an ATS is that the commercial half of the desk goes somewhere else. Business development lives in a spreadsheet, client conversations live in an inbox, and the candidates you did not place stop existing the day the role closes. Most agencies have felt this: the placement they missed was someone already in the database, but nothing surfaced them.
A system built for agencies keeps both on one record. The candidate you rejected for one role is the candidate you place on the next, and the client who went quiet is the client whose team just grew. Neither is visible if the two halves live in different tools.
What is an ATS in recruitment?
ATS stands for applicant tracking system. It is software for moving people through a vacancy: the role is opened, applications arrive from adverts and job boards, each applicant is screened, interviewed, offered or rejected, and the record closes when someone starts.
The core objects are the job and the application. A good ATS is strong on stages, parsing CVs, publishing adverts, scheduling interviews, collecting feedback and reporting on how long each stage takes. It answers the question "where is everyone on this role?" very well.
Most ATS products were designed for in-house talent teams. That shows in what they leave out. There is usually no concept of a client company that pays a fee, no sales pipeline for winning new roles, and no sense that a candidate is an ongoing relationship rather than an application to one job.
What is a recruitment CRM?
CRM stands for customer relationship management. In recruitment it means a system organised around people and companies rather than vacancies: candidates, client companies, the contacts inside them, prospects you have not worked with yet, and the history of every conversation with each.
A recruitment CRM is where business development lives. It holds the call you had with a hiring manager in January, the note that their team is growing, the candidate who told you they would move in the spring, and the reminder to call both of them. None of that is attached to a role, because the role does not exist yet.
It is worth separating a recruitment CRM from a general sales CRM. A sales CRM tracks deals with customers. A recruitment CRM has to track two markets at once, clients and candidates, and the fact that the same person can be a candidate this year and a hiring manager next year.
ATS vs CRM vs agency platform: side by side
The clearest way to see the difference is by what each system is organised around and what it can hold. The third column describes a platform built for agencies, where both halves share one database.
| Capability | ATS | Recruitment CRM | Agency platform (both) |
|---|---|---|---|
| Organised around | The vacancy | The relationship | Both, on the same records |
| Client companies and contacts | Minimal or none | Full records and history | Full records, linked to their roles |
| Winning new business | Not covered | Deals, prospects, follow-ups | Deals that become roles when won |
| Pipeline for a live role | Strong | Weak or absent | Strong |
| Candidate history across roles | Per application | Across the whole relationship | Across every role and client |
| Adverts and applications | Strong | Usually not covered | Covered |
| Submitting CVs to a client | Not designed for it | Sometimes | Tracked per client and role |
| Placements, fees and invoices | Not covered | Rarely | Covered in some platforms |
| Reports answer | How fast are we hiring? | Who should we call? | What will we bill, and from whom? |
Why do recruitment agencies need both?
Because an agency runs two sales processes at once. It sells to clients, to win the role, and it sells to candidates, to fill it. An ATS covers the second process once a role exists. A CRM covers the first, and everything in the gaps between roles.
The money is in the joins. The candidate who came second on one role is often the fastest placement on the next one, but only if something surfaces them. A client who went quiet after a placement is worth a call when their team grows, but only if someone can see that relationship next to the placement history. Two separate tools can each hold half of that picture without either being able to act on it.
When is an ATS on its own enough?
An ATS alone is the right tool when there is no client to sell to. That describes an in-house talent team hiring for its own employer, and it is why ATS products are designed that way.
For an agency, an ATS alone can work for a short period in narrow circumstances: a single consultant filling a handful of retained roles for clients they already know well, with business development happening in their head and their inbox. It stops working the moment a second consultant joins, because the knowledge that was in one person's head now needs to be shared.
Signs your agency has outgrown its setup
These tend to show up before anyone describes the problem as a software problem.
- Business development lives in a spreadsheet or a separate sales tool that nobody updates after a role is won.
- Two consultants have approached the same client contact in the same week without knowing it.
- A candidate was placed by a competitor who was already in your database, rejected from an earlier role.
- You cannot answer "which clients have we not spoken to in ninety days?" without someone building a report by hand.
- Client feedback on submitted CVs sits in email threads instead of on the candidate's record.
- The same candidate appears three or four times, each record holding a different part of their history.
- Placement fees and contract margin are worked out in a finance spreadsheet at month end rather than seen on the placement.
One platform or two connected tools?
Connecting a separate ATS and CRM with an integration is possible, and it is sometimes the sensible route when one system is deeply embedded. The weakness is that integrations sync fields, not meaning. A note, a rejection reason or a submission to a client often does not map cleanly from one data model to the other, so each tool ends up with a thinner version of the other's records.
A single platform avoids the sync problem because there is only one candidate record and one client record. The trade-off is that you depend on one vendor to do both halves well, so it is worth testing both halves properly during a trial rather than assuming the second one is as strong as the first.
What UK agencies should check before choosing
Feature lists all look alike, so the useful checks are the ones that expose how the system behaves on a normal week.
- Can a won business development deal turn into a live role without retyping the client, the contact and the terms?
- Does a candidate's full history follow them onto a new role, including past submissions and client feedback?
- How does it stop duplicates at every entry point: applications, imports, browser capture and manual entry?
- Does email and calendar sync attach conversations to the right client, contact and candidate automatically?
- How does it support UK GDPR: recording the lawful basis, telling candidates you hold their data, and handling deletion requests?
- If you run contractors, does the placement carry pay rate, charge rate and margin, or does finance live somewhere else?
- How long does it take to import your current data, and who does the field mapping?
Where Vayora fits
Vayora is built for UK agencies doing permanent and contract recruitment, with the CRM and ATS on one database: client companies, contacts and a deals pipeline sit alongside roles with configurable stages, submissions and a client portal. Past candidates are resurfaced for new roles, duplicates are detected and merged, and placements carry fees, rates and invoicing. It is not built for in-house hiring teams, and it does not cover temporary staffing or umbrella payroll.
Common questions
- What does ATS stand for in recruitment?
- ATS stands for applicant tracking system. It is software that manages candidates through a specific vacancy, from application or sourcing through screening, interviews, offer and start. It is organised around the job rather than the person, which suits in-house hiring teams well and leaves recruitment agencies needing something extra for client relationships and business development.
- Can a recruitment agency use a general sales CRM instead of a recruitment CRM?
- It can for business development, and some small agencies start that way. The limit is that a sales CRM has no idea what a candidate, a submission or a placement is, so the candidate side ends up in another tool or a spreadsheet. The agency then maintains two sets of records for the same people and the same clients.
- Does a one-person recruitment agency need a CRM?
- Usually yes, earlier than people expect. A solo recruiter can hold relationships in their head for a while, but the value of a recruitment desk is the network, and a network that only exists in one person's memory and inbox cannot be searched, handed over or sold. Starting with a proper record also avoids a painful migration later.
- How long can an agency keep candidate data in its CRM under UK GDPR?
- The law sets no fixed period. You must keep data only as long as you have a genuine reason, usually legitimate interests in placing the person, and tell candidates you hold their data, within a month where it came from another source. Separately, the Conduct of Employment Agencies and Employment Businesses Regulations 2003 require certain records to be kept for at least a year.
- Is it better to replace my ATS or add a CRM alongside it?
- Add a CRM if your current ATS is working well and the gap is only business development, and you can live with syncing two records for each person. Replace both with one platform if you keep hitting duplicate records, missing history or double-handling of the same client. The deciding test is whether one consultant can see the whole relationship on one screen.