AI with Michal

Sourcing ROI

A set of metrics that connect sourcing channel spend (time, tools, fees) to qualified pipeline and eventual hires, so TA teams can direct effort and budget toward the sources that produce the most value at the lowest cost.

Michal Juhas · Last reviewed June 14, 2026

What is sourcing ROI?

Sourcing ROI connects every hour, tool subscription, and agency fee spent on finding candidates to the qualified pipeline and hired outcomes that spending produced. It answers the question a head of talent or CFO will eventually ask: "Which of our sourcing channels is actually worth the money?" Without this data, TA teams defend budgets with activity metrics (contacts sent, InMails used) that do not speak the same language as finance or operations.

Illustration: three sourcing channel tiles with cost chips flowing into a conversion funnel, with a per-channel ROI comparison bar chart showing the most efficient source highlighted

In practice

  • A sourcing lead runs a quarterly channel report that shows LinkedIn sourcing, employee referrals, and agency hires side by side: cost per channel, hires attributed, and average time-to-offer. Employee referrals cost 40 percent less per hire and close three weeks faster. She reallocates 15 percent of the agency fee budget to a referral incentive program.
  • After deploying an AI outreach tool for three months, a sourcer compares response rates before and after. The tool increased outreach volume by 2x but response rate dropped from 18 to 11 percent. Qualified pipeline rate stayed flat. The ROI case is weaker than the vendor claimed.
  • A TA manager builds a simple attribution rule in the ATS: the first-added source field gets credited for the hire. This single standard ends six months of arguments about which channel deserves credit for engineers who appeared in two pipelines simultaneously.

Quick read, then how hiring teams use it

This is for sourcers, TA leads, and recruiting operations professionals who own sourcing budgets or report on sourcing effectiveness. Skim the first section to get a shared vocabulary. Use the second when you are building a sourcing channel report or preparing a budget justification.

Plain-language summary

  • What it means for you: Knowing which sources produce quality hires at what cost lets you invest more in what works and stop paying for what does not.
  • How you would use it: Build a simple tracking table: source, hires, total cost, cost per hire, and average days to close. Review it before every budget conversation.
  • How to get started: Pull the last 12 months of hired candidates from your ATS. Group them by first-recorded source. Calculate total spend per source category. You now have a baseline.
  • When it is a good time: When a sourcing tool contract is up for renewal, when agency spend exceeds 30 percent of total TA spend, and before every annual planning cycle.

When you are running live reqs and tools

  • What it means for you: At scale, sourcing ROI is the signal that tells you whether to double down on AI tooling, shift budget from job boards to direct sourcing, or renegotiate agency terms.
  • When it is a good time: Monthly for channel monitoring, quarterly for budget reallocation, and immediately when a conversion metric drops more than 20 percent below your baseline.
  • How to use it: Connect your ATS source field to a reporting layer (a Looker dashboard, a BI tool, or a structured export to a spreadsheet). Build conversion funnels by source using sourcing funnel metrics. Flag any channel where qualified pipeline rate drops below 20 percent of contacts.
  • How to get started: Audit your ATS source field for the last 90 days. Clean up inconsistent values (LinkedIn, LinkedIn Recruiter, and LI are the same channel). Set a standard taxonomy and train every recruiter on it. Clean data is the prerequisite for accurate ROI.
  • What to watch for: Contact-count vanity metrics from AI tools that inflate the top of the funnel without improving qualified pipeline. Sourcing ROI is measured at the qualified response and hired stages, not at contacts sent.

Where we talk about this

On AI with Michal live sessions, sourcing ROI comes up in the sourcing automation track when we discuss how to evaluate tools and justify spend. If you want to build a channel attribution model in a session with peers, start at the workshops page and bring your current channel mix and cost data.

Around the web (opinions and rabbit holes)

Third-party creators move fast. Treat these as starting points, not endorsements, and double-check anything before wiring candidate data.

YouTube

Reddit

Quora

Related on this site

Frequently asked questions

What metrics make up sourcing ROI?
Core metrics: contacts made, response rate, qualified responses (positive reply with intent to proceed), phone screen pass rate, hiring manager interview rate, offer rate, and accepted offer rate by channel. Cost metrics layer on top: time spent sourcing per hire, tool subscription cost allocated per hire, and agency fee per hire for any externally sourced candidates. Track each metric by channel so you can see which source produces qualified pipeline efficiently versus which source inflates contact counts but never converts past phone screen. See sourcing funnel metrics for the funnel math and talent acquisition metrics for the broader KPI set.
How do you attribute a hire to a sourcing channel when multiple channels touched the candidate?
Most teams use first-touch or last-touch attribution because ATS fields support it: the field where the candidate was first added (LinkedIn, GitHub, referral, inbound application) or the most recent touchpoint before application. Neither is fully accurate. A better model for high-value searches logs every touchpoint in a candidate note field and uses the sourcer's judgment on what actually moved the candidate. For programmatic and inbound channels, last-touch is usually fine. For sourced candidates, first-touch attribution credits the sourcer who did the work. Align your attribution model before running ROI reports so everyone reads the same numbers. See candidate data enrichment for data provenance tracking.
What is a reasonable cost-per-sourced-hire benchmark?
Benchmarks vary widely by role, market, and sourcing model, so treat external numbers as context rather than targets. General ranges: cost per hire for inbound applications tends to run 10 to 30 percent of fully loaded cost for a sourced hire. Agency-sourced technical roles in competitive markets often exceed 20 percent of first-year salary. Internal sourcing teams operating with good tooling and process can reach 8 to 15 percent of salary at scale. More useful than an industry number is your own trend line: is cost per sourced hire rising or falling as you add tools or headcount? Track the trend quarterly and investigate the biggest swings.
How does AI change sourcing ROI calculations?
AI tools improve ROI by increasing sourcer capacity (more profiles reviewed per hour with AI scoring), improving response rates through better-personalized outreach (see AI outreach drafting), and reducing time on manual tasks. The cost side also changes: tool subscriptions, API costs for enrichment, and time spent calibrating prompts all count. The risk is that AI-inflated contact volume looks like improved productivity when response rate drops because the personalization is shallow. Measure response rate and qualified-pipeline rate, not just contacts sent. A tool that sends three times as many messages at half the response rate probably costs more than it saves.
How do you present sourcing ROI to a budget owner who does not know sourcing?
Lead with outcomes the business owner already cares about: time to hire, cost per hire, and quality-of-hire trends. Then show sourcing data as the driver: "We reduced cost per hire for engineering roles by 22 percent this quarter by shifting 60 percent of sourcing to direct outreach, reducing agency dependency." Avoid jargon (InMails, Boolean, sequential sourcing). Use a one-page table: channel, hires attributed, total cost, cost per hire, and average time-to-offer. If AI tools drove efficiency, show the before-and-after comparison with the tool listed. Finance thinks in unit economics; give them a denominator-per-hire number for every line item. See talent acquisition metrics for the full KPI context.
How often should you review sourcing ROI and adjust channel mix?
Review at a minimum quarterly, and immediately when a high-cost channel shows declining conversion. Talent markets shift faster than annual budget cycles, so a channel that worked well for engineering roles in one quarter may underperform the next as LinkedIn InMail response rates shift or a platform changes its algorithm. Build a lightweight monthly channel report that shows response rate and qualified pipeline rate by source, and bring the quarterly summary to the talent acquisition budget review. See talent acquisition budget for how sourcing ROI data feeds budget reforecasting. Become a member for peer benchmarks from practitioners running similar sourcing models.

← Back to AI glossary in practice