Most teams that move off a spreadsheet and into an ATS keep using it like a spreadsheet. A board with columns, a candidate per card, cards moved to the right until someone gets hired and everyone else gets archived. It works. Positions get filled. The problem is not what the tool does for you during a search. The problem is everything you are losing while you use it that way.
Every search should make the next one easier.
- Every candidate you interviewed.
- Every screening.
- Every evaluation.
- Every conversation.
- Every reason someone moved forward, or didn't.
- Every person who was excellent, just not for that role.
- Every candidate who wasn't available eight months ago and might be today.
All of that should become a company asset. If you have been hiring for five years, you should have five years of accumulated advantage.
Five years of hiring, five years of advantage
Recruiting has the same shape as compound interest. A single search produces a small amount of reusable knowledge: a dozen people you would happily call again, a few notes on why the market rejected your salary band, one evaluation that tells you what "senior" actually meant for that team. On its own, it looks like nothing. Kept and added to the next search, and the one after that, it stops looking like nothing.
Two things in that chart are worth noticing. The first is the gap: by search ten, one team opens a role with sixty-something qualified people it already knows, already evaluated, with notes on each one. The other opens it with three names and a job post. The second is the shape of the gray line. It never goes up. Ten searches of work and the starting point is the same as on day one.
That is what happens when every new position starts with publishing again, waiting for applicants and reading CVs from scratch. The advantage you should have built simply disappears.
The problem with Excel is not Excel
It is easy to blame the spreadsheet, and the spreadsheet does deserve some of it. No search worth the name, no history per person, no link between the CV, the interview and the decision. But teams that moved to a proper ATS and kept the same habits have the same problem with a nicer interface.
The real issue is that your hiring process generates information every single day, and you are letting most of that knowledge leak. It leaks in specific places:
- The rejection with no reason. "Archived" tells the next recruiter nothing. "Strong backend, wanted fully remote, revisit if we open remote roles" tells them everything.
- The interview that lives in someone's head. The best signal in the whole process is the conversation, and it is usually the part that never gets written down.
- The silver medalist. The person who came second for a role is, by definition, a pre-qualified candidate for the next similar one. Most systems file them next to people who failed the first screen.
- The "not now". Someone who just started a job, was relocating, or had another offer. Timing was the only problem, and nobody wrote down when to try again.
- The search that starts with a job post. If the first step of a new position is publishing it instead of searching what you already have, the base is not being used even when it exists.
None of these are software failures. They are moments where the process produced something valuable and nothing captured it.
The loop
A good ATS should not just be the place where you manage candidates. It should be a talent base that becomes more valuable with every search. That only happens if the process is a loop, not a line:
What the tools are doing about it
The industry has noticed. Rediscovering talent you already have is now a headline feature across the market, and it is worth looking at how different products approach it:
- Ashby launched AI Talent Rediscovery, which evaluates the people already in your database against the criteria of a new role, refreshes stale profiles, and uses signals like stage progression and scorecard ratings to rank them. Its CRM groups contacts into talent pools that can move straight into an active pipeline.
- Greenhouse has Talent Rediscovery and talent filtering over past candidates and prospects, filterable by scorecard, milestone reached and rejection reason, alongside a CRM for sourced prospects.
- Manatal reads the job description and scores the candidates already in your pool against it with semantic matching, so past applicants show up for new roles without a manual search.
- Spott is an AI-native ATS and CRM for recruitment agencies, built around a recruiting database meant to stay useful over time, with conversation memory and interview transcript processing feeding it.
- Selenios, where I am CTO, so read this one with that in mind. Our bet is on the input side of the loop: screenings, interviews and evaluations turn into structured notes attached to the candidate, so the base gets denser with every conversation instead of only with every CV.
Notice what every one of these features depends on. Rediscovery ranks people using the scorecards, the rejection reasons, the notes and the stage history that your team recorded. A matching model is only as good as what it can read. Point the best rediscovery engine on the market at a database full of archived cards with no reasons and no notes, and it will rediscover CVs. That is all it has.
Habits that make the base compound
The tool is necessary and it is not sufficient. These are the habits that decide whether your ATS becomes a talent base or a filing cabinet:
- Search before you post. The first step of every new role is a query over the people you already know. Publishing comes second.
- Every rejection carries a reason. A short, structured one. "Skills", "seniority", "salary", "location", "timing", plus a sentence. It takes ten seconds and it is the most reusable data you will produce.
- Tag the silver medalists. Anyone who reached the final stages is a lead for the next similar role. Make them findable as such.
- Put a date on "not now". If the problem was timing, write down when timing might change, and let the system remind you.
- Capture the conversation. Interview notes and evaluations belong on the candidate's profile, not in a doc, a chat thread or someone's memory. If it was worth an hour of an interviewer's time, it is worth keeping.
- Measure it. Track how many hires and finalists come from people who were already in your base. If that number is not growing year over year, the base is not compounding.
A base, or a history
An ATS used as a board gives you a tidy record of what happened. An ATS used as a talent base gives you a head start on what happens next. The difference is not the software you bought. It is whether each search leaves something behind that the next one can use.
If, after years of hiring, your next search still starts from zero, you did not build a talent base. You built a history.