Why Most Talent Pipelines Go Cold

Ask a talent team whether they have a pipeline for a given kind of role and they'll almost always say yes. Ask whether they could get five of those people into a process this week and the answer tends to change.

What most companies call a pipeline is a CRM with thousands of names in it. These are people who talked to a recruiter somewhere between six months and three years ago and never got past the screening stage. Since then many of them have taken other jobs, changed industries, or stopped answering messages from companies that never followed up. Teams spend real money on sourcing tools, CRM platforms and outreach campaigns to fill that database, and then have no meaningful contact with the people in it until a role opens. By then they're effectively cold again, and that turns the pipeline into a list with a better name.

So what would a real pipeline be? I think it's a set of relationships, and a relationship only exists if both sides have put something into it. The candidate has learned something real about the company, and the recruiter has learned something real about the candidate: what they want, when they might move, what would make them move. Without that, a name in a CRM is worth about as much as a name you could find tomorrow.

Relationships also decay, and that's where the usual approach goes wrong. A sourcer finds passive candidates, some of them respond, and then the conversation gets parked until a matching req appears. Weeks go by, then months. Meanwhile the candidate's life moves on. They get promoted, or stop looking, or join a company that did stay in touch. The CRM entry still looks healthy. The relationship behind it has expired.

I don't know exactly how long a warm conversation stays warm, but I'd guess a few months at most, and most companies' pipeline outreach runs on a cycle of six months or a year. That gap is why "we have a pipeline for this role" so rarely turns into "we have qualified people we can move this week."

The obvious diagnosis is that recruiters should prioritize pipeline work better. I don't think that's it. The problem is capacity. Keeping a pipeline warm means regular, specific contact with a lot of people, and re-qualifying them as roles change. A recruiter who is also handling live reqs can't run a relationship program with a couple of hundred candidates on the side. Whenever a live req is on fire, the pipeline work is what gets dropped, and that is the right call each time it's made.

The arithmetic makes this plain. Say a recruiter can have ten substantive conversations a day, and a meaningful bench needs around thirty active conversations per role type. With a handful of role types, the numbers stop working before you've counted sourcing, scheduling, admin, or the actual open roles. So pipeline stays a strategy on a slide, and every time a req opens the team is back to searching from scratch.

Larger companies with dedicated sourcing teams run into the same wall at a different place. They do have volume. What they can't do is qualify it fast enough to use. When a req opens there might be three hundred people "in pipeline," and someone has to work out which of them are still relevant, still available and still interested. That can easily take another week of triage before the real search starts.

In both cases the limit is the same thing: the number of real conversations a recruiting team can have. A recruiter can only hold so many of those in a day, and when a live req needs them, the bench waits. That's the limit we built Asendia to remove. Software that phones people doesn't run out of day, so everyone in the pipeline can be talked to when they should be, instead of when a recruiter finds a quiet week. When a candidate comes into your sourcing flow, whether they applied to a job post or responded to an outbound campaign, Asendia calls them within hours and has a spoken qualification conversation that adapts as it goes, covering their situation, timing, motivations and fit for the role. The candidate learns something about the company, and the recruiter gets a structured qualification summary, so both sides have put something in. It can also check back in on a schedule before a relationship goes cold, refreshing the qualification when a role's requirements shift and flagging when someone's availability or interest has changed.

For agencies, this means that when a client role opens, the relevant candidates on the bench have already been screened against it. Recruiters spend their time on judgment calls instead of triage. Screened candidates show up in the ATS with qualification notes and excerpts from the conversation attached. We've looked at what this does to agency economics more broadly in our post on how AI is changing the recruiting agency business.

I suspect many organizations have quietly agreed to believe in a pipeline that doesn't really exist. The CRM keeps growing and the quarterly report shows pipeline growth. Then a senior role opens in a function where everyone was sure there was a bench, and the same emergency search begins as always. Better tools and bigger sourcing budgets haven't changed that. A real pipeline needs contact at a frequency and depth that human recruiting capacity has never been able to sustain, and that limit no longer has to be fixed.

If you want to know where you stand, pick the role type you're most confident you have a bench for, and try to get five people from it on the phone this week.

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