Every profile in your database, as it is today.
Spadework fills in what's missing, corrects what's outdated, and keeps every profile current from there. In your own system, in the structure you already use.
Your records did not change, everyone in them did.
Thousands of contacts, and not one of them tells you when something changes.
Of your 20,000 contacts, 3,340 changed employer this year. 1,900 moved to a different sector too, so your filters miss them entirely. You find out when someone else has already called.
DNB analysis of CBS microdata, 2011 to 2025
16.7 per cent of employees change employer each year, and 57 per cent of those also change sector. That is a national average across all employees. In flex and secondment the rate runs higher, so treat your number as the floor.
Complete first, then current.
Complete
Spadework reads what you already have: the CVs, the documents, the notes, the fields that were filled in once. Empty fields get filled. Contradictions get flagged. What was scattered across four attachments ends up in the fields your recruiters actually search on.
Current
After that it does not stop. When something about a person changes, their profile changes with it. A new employer, a new role, a new certification. The record catches up on its own, and the recruiter who owns that relationship hears about it.
Everything happens inside your own database. Nothing is copied out, nothing is pooled with other customers, nothing is shared.
Four steps, and you approve each one.
See what you actually have
Spadework reads your whole database and shows you the state of it: how many profiles are incomplete, which fields are empty most often, and where the biggest gaps sit.
Set the rules
You choose which fields may be enriched, what happens when new data disagrees with old data, and which parts are in scope. Then you run it as a simulation.
Run it in bulk
Filter by sector, by recruiter, by date of last contact. Set a limit. You see the impact before you start, not after.
Keep it current
From then on, changes come in as they happen. Where they land is your choice: on the record, as a task, or in an inbox.
Your database becomes a goldmine.
You find the people you already had
A search that returned 4 names now returns 30. For the rest, the field you searched on was simply empty.
You get there before your competitor
When someone changes jobs or roles, you get a heads-up right away. That is the moment to call, not three months later.
You stop updating records
No more evenings on the phone asking what someone does these days. It is already there.
Nothing gets written that you have not approved.
Start runs
Does a run fire the moment new data is there, or does it wait until you start it? You set that per agent, and you can change it whenever you want.
Apply changes
Does a run write the enrichment straight away, or does it put the result up for approval first? Also per agent.
An agent only takes the next step once you switch it on.
Spadework doesn't replace your ATS, it adds to it.
The enriched profile lands in your own system, in your own fields. Your recruiters never have to log in here.
Frequently asked questions.
Waar de nieuwe data vandaan komt, of het je eigen invoer overschrijft, en of de AVG dit toelaat.
The updates come from public sources: the profiles where people keep track of their own work and career. Spadework matches that to the record already in your database, nothing comes in from outside your own network.
Your database stays yours. Nothing is shared with or pulled from another agency.
Yes, and that is usually the starting point. Most databases Spadework sees for the first time are a mix of duplicate records, outdated job titles and empty fields.
The first run shows exactly how much of that there is, per field and per record. You do not need to tidy up before you can start, the tidying up is the work itself.
Then you see that before anything is written. Simulate on a selection of your database first, review what a run would change, and only then run it on the rest.
No field gets overwritten without you first setting the rules for what a run is allowed to touch.
Not automatically. You decide per field whether a run may fill it in, correct it, or leave it alone. A field your recruiter typed in by hand can stay out of reach.
And an empty field is not an error to overwrite, it gets filled. A wrong field gets corrected. Everything else stays as it is.
Yes. The enrichment lands in the fields you already use, in the structure you already have. No new field gets added that you have to learn separately.
If a field is set up differently than usual, we align that together before the first run.
No. Spadework connects to the systems staffing agencies already run on. If you work with a different one, we look at it with you and get the integration built.
Without an ATS you upload your contacts and receive your opportunities by email.
Yes. You choose the selection yourself: a sector, a team, part of your database. Many agencies start there and only expand once the first run holds up.
The whole database at once is also possible, but never required.
It stays current. After the first run, Spadework keeps your database updated, so a profile cannot quietly go three years stale again before anyone notices.
How often that happens, and for which fields, is something you set yourself.
Yes. Spadework works within your own database, on people who are there with consent, and it is built and hosted in the EU. Nobody outside your own network enters the system.
Nothing is pooled either. One agency's data never ends up with another.
Yes, because the agents run on this data. A signal is only as reliable as the record underneath it: an outdated job title or an empty field makes a good opportunity unfindable.
Enrichments is not an extra step next to the agents, it is the foundation they stand on.
Not answered here? We reply faster than you would expect, usually within 24 hours.
Get in touch