Recruitment agencies · CRM
Keep clients, open roles and candidates in one record your whole desk reads.
A CRM for a recruitment agency holds two relationships at once: the client who pays the fee and the candidate who fills the role. GullySales sets up the pipeline stages, the fields and the habits so a recruiter's notes stay with the agency when the recruiter moves on.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What CRM means
A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.
Last updated 14 Nov 2026. Rules for this trade differ by state and professional body, and they change. We describe restrictions in general terms, so check the current position with your own council or adviser before you publish anything.
For recruitment agencies
Where it usually goes wrong, and what we would do.
“The spreadsheet of CVs has no memory of the conversation”
A recruiter finds a name in a folder but not what was promised, what salary was discussed or why the candidate declined last time. Without that note the next call repeats the same questions and the candidate feels like a stranger again.
“Client and candidate need separate pipelines”
A role moves from brief to shortlist to interview to offer to joining. A candidate moves from sourced to screened to submitted to placed. Forcing both into one list hides which role is stuck and which candidate has gone quiet.
“When a recruiter leaves, the relationships leave too”
The HR manager knows one recruiter's mobile number, not the agency. If the notes live in that recruiter's phone and inbox, the account walks out with them. A shared record is the agency's only claim on its own clients.
“Free-text fields make a skill search useless”
A search for a candidate with a particular tool, notice period or city only works if those details sit in fields, not in a paragraph. The way a CRM is set up decides whether the database answers a search or just stores CVs.
What we do
What we deliver for recruitment agencies.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
Two-sided pipeline design
Separate stages for client roles and for candidates, linked so a role shows every candidate submitted against it.
Result: You see which role or candidate is stuck at a glance.
Field design for searchable candidates
Fields for skill, current employer, notice period, expected pay, city and consent status, filled by choice lists where possible.
Result: A skill search returns real matches, not a folder to scan.
Import and clean-up of the existing database
Your current sheets and CV folders merged, duplicates flagged and candidates marked as verified, unverified or unreachable.
Result: The database separates people you can call from names you cannot.
Client account records
Contacts, roles briefed, shortlists sent, fees invoiced and the reason for any lost role, held against each client company.
Result: Any recruiter can pick up an account with its history.
Recruiter habits and ownership rules
A short written routine for logging a call, a submission and a feedback note, plus who owns a candidate when two recruiters have spoken.
Result: Notes get written because the routine is clear and short.
How the result is measured
- Enquiries logged in the CRM
- Data completeness
- Reports generated from CRM data
Recorded as a baseline before work starts, so every later report has an honest comparison.
Fields worth keeping
What a recruitment desk records so a search can be found again.
- Skill and tool tags
- Filled by the recruiter after screening, from a fixed list, so a search for a specific skill returns people who actually have it and not a text match.
- Notice period and current pay
- Asked on first contact and updated at offer stage. Lets you drop candidates who cannot meet a client's joining date before a shortlist is built.
- Last verified date
- Set whenever a recruiter confirms the person is still looking. Stops the desk shortlisting candidates whose details went stale long ago.
- Client contact role
- Whether the person is HR, hiring manager or founder, entered by the account owner. Decides what kind of update goes to that contact.
- Mandate source
- Entered when a brief arrives: referral, past client, outreach or inbound. Shows which channel brought paying searches and which only brought CVs.
- Reason for drop or rejection
- Picked from a short list by the recruiter at the point of loss. Over time it shows whether searches fail on pay, notice period or fit.
Who it is for
This is written for these recruitment agencies.
- IT and technology staffing agencies
- Blue-collar and industrial workforce agencies
- Executive search and leadership hiring firms
- Contract and temporary staffing agencies
- Sector-specialist recruitment firms
- Bulk and volume hiring agencies
- Boutique niche-skill recruitment firms
Before you decide
When this may not be the right fit.
- Your recruiters keep candidate notes in their own phones and will not move them, so a shared system would hold the same gaps as the sheet.
- You place too few people for the CRM to repay the effort of data entry, and a well-kept sheet would serve until volume grows.
- Nobody is willing to own data quality, so tags would be filled differently by each recruiter and the search would stay unreliable.
Before you decide
Agree the work. Know how to judge it.
CRM for recruitment agencies: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
List the records your team uses and show how an enquiry becomes an order today. Bring examples of duplicate entries, missing owners, and reports that require manual correction.
Make the scope clear
Agree the stages, required fields, access roles, and integrations before configuring the system. Separate software subscriptions from setup, data work, and training.
Check the work in use
Ask the people who will use the CRM to complete a real handover and find the next action without help. Check that the management report can be traced back to individual records.
Know when to change course
If the process is unclear, buying a more complex CRM adds more places for confusion. Start with the minimum fields and rules the team can use consistently.
These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.
Before we start
What to have ready before the work starts.
The records, access and decisions this work needs from recruitment agencies. Anything missing is noted in the written scope, with who will supply it.
- The current spreadsheets and CV folders
- Give us every file where candidate or client details live, even half-finished ones. We map them before moving anything. Files we do not see cannot be imported, and the record starts incomplete.
- A list of pipeline stages in your words
- Write the stages as consultants say them, for both sides. A page of notes will do. If the stages are not agreed, we propose some, and the tool may feel foreign to the people who must use it. Include the point at which a candidate counts as submitted, because two consultants can use the same word for different moments.
- A sample of candidates with consent noted
- Tell us how candidates came to you and whether they agreed to be held on file. Even a rough source column helps. Where nothing is known, we plan a confirmation step before they are mailed.
- A person who decides on the tool
- Name who chooses the CRM, who approves its cost and who enforces its use. If these are three people who disagree, the project stalls. With one decision-maker, a stalled question about cost or training is settled at once, and the import can go ahead on the date agreed.
How it works
How the CRM work runs
The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.
- 1
Look at the CV folders and the spreadsheets
We open the spreadsheet of CVs, the shared drive and the portal exports with a consultant, and note where each candidate's story lives. You tell us which records are trusted. We end with a plain inventory of what you hold, in how many places and in what state. We also note which fields hold a skill written three different ways, such as Java, JAVA and core java, since those are the first to be merged.
- 2
Draw the client and candidate pipelines apart
A candidate moves from registered to submitted, interviewed, offered and joined; a client moves from enquiry to brief, search, shortlist and fee. We draw both on paper with the consultants. You rename stages to match how your people talk, so the tool follows the work.
- 3
Design fields that a skill search can use
Free text makes a search for a skill useless. With a consultant we choose fields for function, skill, notice period, expected pay band, city and source, using lists where we can. You decide which fields are compulsory. Too long a list of compulsory fields will be skipped.
- 4
Clean and import the existing database
We remove duplicates, fix obvious errors and import the records into the tool you choose. A consultant checks twenty candidates and five clients against memory. You decide what is deleted. Records with no sign of consent are tagged for a confirmation message.
- 5
Agree ownership rules and read the first use
We write a short page on who owns which records, what happens when a recruiter leaves and who updates after each call. After a period of use, we compare the record with the figures noted before the tool: submissions, mandates and time lost searching. You tell us what consultants skip.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales management. A target, a review routine and someone who owns the number.
Step 1
Sales audit
Find where deals are being lost and what to fix first.
Start here if you cannot say where orders are lost.
Step 2
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3 · you are here
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
Which CRM should a recruitment agency use?
Can the CRM connect to Naukri or LinkedIn?
How do we keep candidate data lawful in the CRM?
Who should own the fields in a recruitment CRM?
Which tool suits an agency with six consultants?
Who owns the fields in a recruitment record?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
From the blog
Further reading for recruitment agencies.
6 min read · 6 Oct 2026How companies choose an outside service firmCompanies pick an outside service firm by asking people they trust. See who is asked, what they check and where a service firm drops off the list.
7 min read · 21 Sept 2026How to advertise to HR headsAn HR head's year runs on fixed dates. Advertise against renewal and appraisal cycles, and sell to the payroll executive who is blamed when salary is late.
7 min read · 4 Sept 2026How to get recruitment clients for a staffing or placement agencyWin recruitment clients by choosing a niche, reaching hiring managers with candidates in hand, filling the first role fast and growing the account.
More for recruitment agencies
Related work to consider.
Closest to this: leads and follow-up
Also for recruitment agencies
Or start from the overview: sales and marketing for recruitment agencies.
Your next practical step
Tell us what you are trying to grow, and we will read it before we call.
Eight short steps, mostly taps. Skip anything you would rather answer on the call.