Where Your Sourcing Budget Goes After Candidates Apply

There's an odd blind spot in the way most recruiting teams judge their sourcing. They measure almost everything up to the moment someone applies, and very little after it.

The numbers they do watch are sensible ones: cost per click, application completion rate, source of hire. They tell you whether a job board or a campaign is bringing people in, and for plenty of teams they look fine. Applications are coming in. The career page gets traffic. These are the figures that go on the dashboard and justify next year's budget.

What almost nobody measures is how many of those applicants were ever contacted, and how long it took.

That second question matters more than it seems, because of what an active candidate does while they wait. They keep applying. Some of the other companies they applied to will move faster than you. So if your first call comes four days after the application, a real share of the people you paid to attract are already in someone else's process by the time you reach them, and some are further along there than they'll ever get with you.

The sourcing report says the campaign worked, and in a sense it did. The people showed up. But there's no line on any report for the ones who showed up and then left because nobody called, and I think that's where a lot of sourcing money actually goes.

It helps to put numbers on it. Suppose a mid-market company has 40 roles open and spends $168,000 a year on job boards and sourcing tools, which is a reasonable amount for that volume. Suppose 30% of the people who finish an application don't hear back in time, and some fraction of those were qualified. The company works out cost per hire the usual way, by dividing sourcing spend by hires. That number is now wrong, and nobody will notice.

The error is in how the lost candidates get counted. The qualified people who applied, waited, and took an offer elsewhere don't appear as losses. If they appear at all, it's as "sourced but not qualified." Their true category is something like "sourced and lost because we were slow," and that isn't a field anyone fills in.

Some of these are exactly the people you'd most want. They saw your employer brand, read the job description, and spent twenty minutes on your application. Of all the places they could have applied, they picked you. After three days of silence they went ahead with whoever called back. You paid once to attract them and then lost them to a backlog, and the sourcing report shows neither the payment nor the loss.

Why is first contact so slow? For the obvious reason. It has always needed a recruiter to pick up the phone during business hours, and a recruiter only has so many hours. Someone managing 15 open roles can realistically start conversations with perhaps 20 to 30 new applicants a week. A good sourcing campaign can produce that many in an afternoon.

It follows that the better your sourcing gets, the worse this problem gets. Every extra dollar that works brings in more applicants than the screening side can reach in time. Past a certain point you're paying to lengthen a queue.

If the loss comes from slow first contact, then faster first contact should recover it without touching the sourcing budget. The same ads would bring in the same people. The difference is that more of them would get a real conversation while they were still interested. I'd expect cost per hire to fall for the dull reason that more of the money you already spend would turn into hires.

That's the gap we built Asendia around. If the limit is how many hours recruiters have for first calls, the thing to change is who makes the first call. Asendia phones applicants itself, soon after they apply, including in the evening when no recruiter is working. Someone who finishes your application after dinner in the middle of the week gets a call that same evening instead of four days later. It's a spoken conversation that adapts to what they say and follows your criteria for that role, and a structured summary lands in your ATS before your team starts work the next morning.

Because it doesn't run out of hours, a weekend campaign that brings in 300 applications doesn't leave a backlog on Monday morning. It leaves 300 summaries, with excerpts from each conversation and a ranked shortlist, waiting in the pipeline. Your recruiters start the week deciding whom to advance rather than whom to call first, and the sourcing money you spent on the weekend actually turns into conversations. There's a separate post on how this is splitting the agency model in two.

If you want to know whether this applies to you, look at last month's applicants and measure the time from application to first contact. If nobody has measured that before, you've learned something already.

Conversations about sourcing budgets tend to be about channels, allocation, and cost per application. Those are the right things to work on if your problem is attracting candidates. I suspect that for most teams it isn't. They attract plenty of people and lose them in the few days after they apply. For a team like that, spending more on sourcing mostly buys a longer queue. The cheaper fix is to make sure that when someone applies, they hear from you before they've finished interviewing somewhere else.

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