//
An explanation for recruitment agencies of what database enrichment actually involves, how it differs from data cleansing, and when it pays off versus when it's an expensive exercise that goes nowhere.
In short
Database enrichment is the process of supplementing and updating your existing candidate database with current, missing or new information. For recruitment agencies that means in practice: pulling current job title, updating employer, validating contact data, adding skills, refreshing availability. The source is usually LinkedIn, supplemented with public data and direct outreach.
Short answer: enrichment is not a substitute for data cleansing. Clean first, then enrich. Enrichment only pays off once your database is structurally sound. Agencies that sequence this correctly extract 20 to 40 percent more placements from their existing candidate pool.
TL;DR
An outdated database is not an administrative problem, it's a commercial one. Recruiters working from a database with three-year-old job titles, employers and contact details consistently call the wrong people at the wrong moment.
In this article: the difference between cleansing, enrichment and monitoring, when each type of work makes sense, what enrichment actually delivers, and how to set it up without breaking your system.
What is database enrichment, exactly?
Database enrichment is adding to or updating information on profiles you already have. It differs from three related terms that often get mixed up:
Data cleansing is clean-up. Merging duplicates, correcting wrong fields, removing invalid emails. This works on the structure of your data.
Data enrichment is supplementation. A 2022 profile with "Manager at ABC" gets updated to "Director at XYZ" plus the new LinkedIn URL plus the new office.
Data monitoring is surveillance. Continuously flagging when candidates change jobs, get promoted, or become available, so you can reach out at the right moment.
In a well-running recruitment agency, these three work together, but in this order: cleansing first, then enrichment, then monitoring. Setting up monitoring on a messy database produces lots of alerts about the wrong people.
How fast do candidate profiles go stale?
Labor market mobility data shows that in the Netherlands, the average employee changes employers every 3 to 5 years. In specific segments it moves faster: tech professionals switch every 2 to 3 years on average, in healthcare and finance more often between roles within the same organization.
Concretely: in a database of 10,000 candidates built over 4 years, an estimated 40 to 60 percent of job titles and employers are outdated. Between 15 and 25 percent of email addresses no longer work because they were corporate addresses tied to a previous employer. Phone numbers usually still work.
For a staffing or contracting agency this isn't a small thing. An outdated profile isn't a profile anymore, it's noise. And noise costs time: recruiters search on skills and job titles that aren't relevant, call people who have already been working for a direct client of the agency for two years, or email addresses that bounce.
When do you actually need enrichment?
Not always. An agency that only places candidates from fresh leads (candidates who applied in the last 6 months) benefits less from enrichment. The payoff sits with agencies that regularly draw on their existing database.
Four situations where enrichment demonstrably delivers:
You work a lot with returning candidates. Agencies in IT, finance and engineering place candidates multiple times over their careers. A current job title is the difference between a relevant pitch and an awkward opener.
You do warm sourcing on career moves. When a candidate has just switched roles or just been promoted, that's a natural reason to reach out. But you have to know about it at the moment it happens.
You're preparing a sector-specific campaign. Before you email 500 people about a new role, you want to know if those people still work in the same sector. Enriching upfront is cheaper than emailing, bouncing and burning your reputation.
You've done an ATS migration or database merger. Acquisitions or system migrations often leave entire cohorts of profiles untouched for years. A one-time bulk enrichment addresses backlog.
How does enrichment work technically?
Three main routes, often combined:
LinkedIn sync. Software compares the profile in your ATS against the same person's public LinkedIn profile, flags differences and updates fields. The most scalable method. Good tools let you choose per field whether to overwrite, supplement or protect (think notes you've added yourself).
External data supplementation. Filling in from public sources: business registries for company data, public registers for diplomas, vertical platforms for certifications. Works mainly for B2B context.
Direct outreach. Automated emails or forms asking the candidate themselves for current info. Low response (typically 5-15 percent), but 100 percent reliable and GDPR-friendly because the candidate consents themselves.
In practice, most agencies work with option 1 as the baseline, option 3 as a supplement for specific groups.
What it actually delivers
Three measurable effects when enrichment is done properly:
More placements from existing database. Agencies that enrich structurally report 20 to 40 percent more activation of dormant candidates. Not all of those activations lead to a placement, but the funnel gets wider.
Lower acquisition cost per candidate. Every new candidate via marketing, job boards or paid sourcing costs between 50 and 300 euros. An activated candidate from your own database costs the rate of an enrichment action, typically less than one euro per profile.
Faster response to vacancies. If your database is current, you can generate a shortlist within a day instead of searching for a week. Agencies that are sharp on this win more assignments from agencies with a slow shortlist.
GDPR and enrichment
A sensitive topic, because enrichment means processing personal data without the candidate requesting anything from you at that moment. Three principles to follow:
Legal basis. Enrichment falls under "legitimate interest" (article 6(1)(f) GDPR), provided you can substantiate it and include it in your privacy notice. For existing candidates with explicit consent this isn't an issue.
Data minimization. Enrich only fields you need for your service. The fact that you can find someone's home address through public sources doesn't mean you should store it.
Retention periods. Enriching doesn't automatically extend a candidate profile's retention period. Standard is 4 weeks after an application process, or 2 years with explicit consent. An enriched profile whose retention period has expired still needs to be deleted or anonymized.
Comparison: manual versus automated
Manual | Automated | |
|---|---|---|
Time per profile | 5-10 minutes | Seconds |
Scalability | A few hundred per month max | Thousands per day |
Cost per profile | 3-7 euros (recruiter time) | 0.10-0.80 euros |
Continuity | Stops when recruiter does other work | 24/7 |
Error risk | Variable per person | Consistent, testable upfront |
Suited for | Hot prospects, top 50 candidates | Whole database, bulk actions |
Most agencies pick a hybrid approach: automated for the entire database as baseline, manual deep-dive on candidates actively in scope for a vacancy.
FAQ
Is enrichment the same as scraping?
No. Scraping is mass-extracting data from a website without permission or API. Enrichment connects to sources through authorized routes (LinkedIn integrations with OAuth, public registry APIs, form input from the candidate themselves). Good enrichment tools don't work via scraping, because that violates LinkedIn's terms of service and sits in legally grey territory.
How often should you enrich a database?
For the average recruitment database: bulk enrichment once or twice a year, plus continuous monitoring on live updates. Agencies actively working from their existing network often move to monthly cycles for commercially relevant segments.
Should you throw out an outdated database and start over?
Almost never. A database represents years of recruiter conversations, placement history and relationship context. Enriching costs less than rebuilding, and you don't lose historical data. Only in cases of mass GDPR violations or fundamentally corrupted data is starting from scratch defensible.
What's the difference between Spadework Up-to-databaser and a data broker like Cognism or Lusha?
Data brokers sell you new contact details of people who aren't yet in your database. Up-to-databaser updates profiles you already have. Different target group, different pricing structure, different GDPR position. Agencies often use both, but for different purposes.
Is enriching GDPR-safe if I use an external tool?
Yes, provided the tool operates as a processor under a data processing agreement, processes data inside the EU, and only updates fields you originally collected lawfully. Ask every vendor for their DPA and sub-processor list before signing.
Sources
CBS labor mobility Netherlands 2024-2025, average duration of employee-employer relationships
Dutch Data Protection Authority, recruitment and selection guidelines 2024
LinkedIn Talent Solutions, terms of service and API policy
ABU & NBBU, Dutch staffing sector guidelines on candidate data
Spadework client data May 2026: activation rates of dormant candidates, average enrichment time, cost structure
Minggo, RecruiterXL, Trinity Sales: NL market overview of database enrichment and tooling
Want to know how clean and current your own database actually is? Spadework offers a free database analysis where we map out what percentage of your profiles is outdated, how many candidates you can activate, and what it would deliver.



