The Problem Every Recruiter Knows
If you’ve been recruiting for any length of time, you have a folder. It might be on your laptop, a shared drive, or buried in your email. It’s full of CVs from candidates you talked to six months ago, a year ago, two years ago. Some were brilliant fits for roles that didn’t quite work out. Some were earlier than the right opportunity. Some you simply ran out of time to place.
And the next time a client briefs you on a role, that folder might as well not exist. You can’t search it. You can’t filter by skill. You can’t remember which CV mentioned Kubernetes or which one had a finance background. So you do what every recruiter does — you go back to LinkedIn, you put out fresh feelers, and forty-five real candidates sitting on your hard drive go unconsidered.
That was the situation a specialist recruiter found themselves in earlier this year. They came to EmpireVault with a folder of around 45 CVs and a simple question: “Can I make this searchable?”
This is the story of how they did it — and the workflow any recruiter can copy.
Step 1: Loading Candidates Into the CRM
EmpireVault’s CRM has three contact types: Client, Consumer, and a recruitment-specific type called Candidate. The candidate type unlocks the AI indexing pipeline — when you mark a contact as a candidate and attach a CV, EmpireVault parses the document and extracts a structured set of keywords from it.
Adding 45 contacts one at a time would have been painful. EmpireVault’s contact form has an inline file uploader on the create screen, so each candidate took about thirty seconds: name, email, attach the PDF, save. The recruiter worked through the folder in a single afternoon.
Behind the scenes, two background jobs ran for each upload:
- Text extraction — the PDF (or DOCX) is parsed and the text is encrypted and stored against the attachment record.
- Keyword extraction — that text is sent to AI, which returns a structured list of skills, technologies, industries, and roles mentioned in the document.
By the next morning, all 45 CVs had been indexed. Each candidate’s contact record now had a tidy list of keywords tagged against it — Ruby, React, fintech, SaaS, team-lead, agile, and so on. The folder of dead PDFs had become a queryable database.
Step 2: Searching the Pool When a Client Briefs a Role
The first real test came when a client sent through a role brief. They needed a backend engineer with experience in a specific stack and prior exposure to a particular industry vertical. In a traditional CV folder, that’s a half-day reading exercise. In EmpireVault, it’s a search.
The recruiter went to the contacts list, filtered to contact_type = candidate, and added two keyword filters matching the client’s must-haves. The list shrank from 45 to a handful of strong matches in seconds.
The keyword search uses an OR within the keyword list and ANDs that with existing filters. So keywords = ruby, rails returns anyone whose CV mentions either — and you can stack additional filters on top: contact tags, custom fields, location, even a free-text search across name and notes. For one client brief, the recruiter combined three keyword filters with a custom-field filter and produced a tight short-list in under a minute.
Crucially, the AI doesn’t make things up. The keywords come directly from the CV text — no hallucination, no inferred skills. If a candidate’s CV doesn’t mention Postgres, they won’t show up under a Postgres search, even if you happen to know they’ve used it. This is a feature, not a bug. It keeps the short-list grounded in what’s actually documented.
Step 3: From Search Result to Targeted Email Campaign
Finding the right candidates is half the job. The other half is finding out which of them are actually interested — and that’s where the workflow gets interesting.
Once the recruiter had their short-list of, say, twelve potential matches, they did three things:
- Bulk-tagged the matched candidates with a role-specific tag — for example,
role-2026-q2-backend-fintech. This creates a saveable, reusable segment that any future filter can target. - Composed a campaign email describing the role at a high level (without naming the client) and asking whether the candidate would be open to learning more.
- Sent the campaign to the tagged segment. Open and click tracking is built in. Each candidate’s response, click, or non-engagement is recorded against their contact record automatically.
Within 48 hours, the recruiter had a clear picture: who opened the email, who clicked the role description, and who replied directly. The replies — typically a quick “yes, tell me more” or “not right now, thanks” — flow back into the unified inbox where they’re auto-linked to the matching contact. The recruiter didn’t have to manually thread anything.
What used to be “send forty individual emails and chase responses in a spreadsheet” became “send one campaign, watch the inbox, follow up on the warm replies.” For a forty-five candidate pool that would once have been a week’s work, the whole cycle — search, shortlist, outreach, response triage — took two days.
Step 4: The Compounding Effect
Here’s the part that doesn’t show up in the first month: every conversation makes the next search better.
When a candidate replies to a campaign with “I just took a new role, but ask me again in six months,” that note goes on their record. When a client interview produces feedback (“strong technically, communication needs work”), that goes on the record too. New CVs get added and indexed. Candidates already in the database get re-tagged as roles change.
The recruiter’s database, which started as 450 or so stale PDFs, is becoming a structured, ever-improving repository of who’s looking, who’s settled, who’s been interviewed before, and who’s worth a fresh approach. Every search runs against richer data than the last one.
This is the difference between a CV folder and a CRM. The folder is static. The CRM compounds.
How Any Recruiter Can Replicate This
If you’re sitting on a folder of CVs and want the same workflow, here’s the order of operations:
- Sign up for EmpireVault — the candidate-attachment-search feature is on every plan, no add-on required.
- Create candidate contacts with the inline upload form. One contact, one CV, thirty seconds.
- Wait an hour for indexing to complete on a batch of around 50 documents. (Larger batches take proportionally longer; AI keyword extraction is rate-limited per tenant.)
- Search the contacts list with keyword filters when a brief comes in.
- Tag matching candidates with a role-specific tag.
- Send a campaign from the matched segment with a short description of the role.
- Triage replies from the unified inbox.
That’s the whole loop. There’s nothing else to configure, no AI prompts to tune, no integrations to set up. The same database that holds your candidates also holds your clients, the conversations between them, the campaigns you’ve sent, and the responses you’ve received — all in one place.
A Note on What’s Indexed
EmpireVault indexes PDF, DOCX, and plain text CVs. Older binary .doc files are accepted but flagged as unsupported (no clean Ruby parser exists for that format without heavyweight dependencies). If you have a folder full of .doc files, batch-converting them to .docx with Word or LibreOffice before upload is well worth the ten minutes.
All extracted text is encrypted at rest. Keywords are stored as a structured list against each attachment, not as free-text in your contact’s notes. Changing a contact’s type away from “candidate” purges the keyword index — so if you offboard someone or repurpose a contact, no stale data hangs around.
Try It on Your Own Pool
If this matches the shape of your problem — a backlog of CVs, client briefs that come in fast, and not enough hours to read through everything by hand — start a free trial and load your own candidates. The first batch of fifty will index overnight. The first search you run after that will probably surface a name you’d forgotten you had.
EmpireVault is $49 per seat per month, with a 21-day free trial and no credit card required. The candidate-attachment-search feature is included on every plan, alongside the full CRM, email campaigns, unified inbox, and the rest of the suite.