Why a Talent Pool Stops Being a Pipeline

Consider the day a role you've been waiting on finally gets approved. The talent acquisition team does the sensible thing and goes to the database. There's a list from a hiring campaign for a similar role about eighteen months ago, with names, emails, and LinkedIn profiles. It looks like a head start.

Usually it isn't much of one, because the people on that list have moved on without telling you. Some of them took jobs they would happily have left for this one, but they took them six months ago, after you went quiet. Some got promoted, and this role would now be a step down. Others relocated, changed what they expect to be paid, went into management, or left the field. None of that made it into the database, because nobody's job was to put it there.

How fast does this happen? One commonly cited estimate says about half of the contact and employment details in a candidate database go out of date within a year. Even if the real figure is lower, think about what two years does to a list. Most of the entries describe someone who no longer exists in the form you wrote down.

The idea behind talent pools was sound. Build a bench of good candidates before you need them, so that when headcount comes through you're ahead of everyone else. What went wrong is that building the pool became a process and keeping it current never did. Plenty of companies now have candidate databases thousands of entries deep, and most of those entries produce almost nothing.

The standard advice is to keep the pool warm: quarterly newsletters, job posts to your network, nurture sequences. Most recruiting teams do some version of this, and none of it tells you what you actually need to know when a role opens, which is who on the list is qualified for this particular job, able to move, and interested right now. A newsletter tells you who opens newsletters. To learn whether someone's situation has changed, or whether their pay expectations have shifted, or whether they'd even take a call about the role, you have to talk to them.

And talking to a few hundred people about one opening is precisely the thing a recruiting team can't do without making it someone's entire job for two weeks. So here is what tends to happen instead. The team pulls the list and sends a generic email. A small fraction reply. They talk to a couple of dozen people, call that using the pipeline, and then spend the next month sourcing from outside as if the list didn't exist. By then it effectively doesn't.

You could treat all this as wasted outreach, but I think the larger cost is the false confidence. Suppose a company believes it has a 2,000-person engineering talent pool. It will make different decisions from a company that knows it's starting from zero. It will put off proactive sourcing, pay less attention to its referral program, and skip building the agency relationships it would build if it knew the bench was empty. The number shows up in dashboards and in capacity presentations, and people plan around it.

Then a quarter comes when fifteen engineering roles need filling and the pool turns up four people who are both qualified and available. At that point the gap between what everyone assumed and what was true isn't only a problem for recruiting. Hires land late, and the delay spreads into product timelines and into how much the teams waiting on those hires can get done.

If you follow this through, better CRM software or stricter tagging won't fix it. The information you're missing lives in people's heads, and the only way to get it out is to ask them. The obstacle all along was that nobody had time to make three hundred calls.

Software helps here for a fairly unglamorous reason: it doesn't mind dialing. A recruiter can get through only so many calls in a day, and a program that phones people doesn't have that ceiling, so nobody on the list has to wait their turn. When a role opens, Asendia can go through an existing candidate list and call every person on it within a day, having the conversation a recruiter would have. What are you looking for now? Where are you in your career? Does the timing work? The people who are qualified and interested go back into the ATS with updated details and notes from the conversation, sitting in the same pipeline as new applicants.

It's also worth being able to tell, before a role opens, whether your pool is real. I went through how to separate database size from actual pipeline depth in the post on what recruitment KPIs to track in a post-AI world.

A simple test, if you want one: take the list you'd pull for your most common role and ask how many of the people on it you could reach this week and know, afterwards, whether they'd take the job. That number, not the size of the database, is your talent pool.

Ready to transform your hiring strategy? Schedule a Demo with our founders today!