2026-01-20
How to Track Sourcing Metrics: KPIs Every Recruiter Should Measure
How to Track Sourcing Metrics: KPIs Every Recruiter Should Measure
If you're sourcing developers without measuring your results, you're flying blind. Sourcing metrics aren't just vanity numbers—they're the foundation of a data-driven recruiting function that scales.
Most technical recruiters track activity (calls, emails, messages sent) but ignore outcomes (quality of candidates, time-to-hire, cost-per-placement). That's backward. This guide covers the KPIs that actually matter, how to measure them, and how to use the data to improve your sourcing ROI.
Why Sourcing Metrics Matter for Technical Recruiting
Technical recruiting has changed dramatically. You're no longer competing just with other recruiters—you're competing with employer branding, job boards, LinkedIn, and direct outreach from companies. Without data, you can't know what's working.
Sourcing metrics reveal:
- Which channels deliver quality candidates (direct outreach vs. LinkedIn vs. GitHub vs. job boards)
- How long it takes to fill roles by technology and seniority level
- Which messaging approaches convert technical candidates into applicants
- How much each hire actually costs when you factor in sourcing time
- Where bottlenecks exist in your pipeline
For recruiting agencies and in-house talent teams, this is the difference between profitable, scalable hiring and spinning wheels on low-quality outreach.
Core Sourcing KPIs You Must Track
1. Cost Per Qualified Lead (CPQL)
Cost Per Qualified Lead is your sourcing spending divided by the number of qualified candidates you source.
Formula:
Total Sourcing Cost / Number of Qualified Leads = CPQL
What counts as "qualified"? A candidate who meets your minimum technical requirements and actively engages with your outreach (responds, opens email, clicks your link).
Why it matters: This metric forces you to define quality upfront. A $5 CPQL sourcing JavaScript developers via GitHub is exceptional. A $200 CPQL via random LinkedIn scraping is wasteful.
Industry benchmark: For technical sourcing, a reasonable CPQL ranges from $10-50 depending on: - Tech stack rarity (Go developers cost more to source than JavaScript developers) - Seniority level (senior engineers = higher CPQL) - Geography (US tech hubs cost more than remote/international sourcing)
How to track: Use your ATS to log sourcing spend per channel, then tag leads with "qualified" status when they meet minimum criteria.
2. Sourcing Pipeline Conversion Rate
Pipeline Conversion Rate measures how many sourced candidates move through each stage of your hiring funnel.
Track this at multiple levels:
| Stage | Definition | Typical Conversion |
|---|---|---|
| Outreach → Reply | % of sourced candidates who respond | 15-25% |
| Reply → Qualified Call | % of replies that turn into screened conversations | 40-60% |
| Qualified Call → Interview | % of calls that advance to technical interview | 60-80% |
| Interview → Offer | % of interview processes that close | 20-40% |
Why it matters: This tells you exactly where your funnel leaks. If 80% of sourced developers ignore your outreach, that's a messaging problem. If 90% respond but 0% get past the first call, you have a screener problem.
How to track: Use your ATS to segment candidates by stage, then calculate the ratio month-over-month. Track by sourcing channel to see which channels produce candidates most likely to advance.
3. Time to Hire (from Sourcing to Offer)
Time to Hire measures how long your sourcing process takes, from initial outreach to offer acceptance.
Break this into stages:
- Source-to-Response Time: How long between outreach and first candidate reply (median: 2-7 days)
- Source-to-Screen Time: How long between outreach and first qualified conversation (median: 5-14 days)
- Source-to-Interview Time: How long between outreach and technical interview (median: 10-21 days)
- Source-to-Offer Time: Total time from outreach to written offer (median: 30-60 days)
Why it matters: In competitive markets, speed is a recruiting weapon. If your source-to-offer time is 90 days while competitors are 45 days, you'll lose candidates.
How to track: Log timestamps in your ATS for each interaction. Use reporting to calculate median (not average—one slow hire skews the data) time between stages.
Pro tip: Track this separately by tech stack. Sourcing a senior Rust developer will take longer than sourcing a mid-level JavaScript developer—that's normal. But within each category, trends matter.
4. Cost Per Hire (from Sourcing)
Cost Per Hire is the total cost of the hiring process divided by the number of hires. For sourcing-specific tracking, focus on sourcing cost per hire.
Formula:
(Recruiting Tools + Sourcing Time + Outreach Platforms + Recruitment Marketing) / Number of Hires Closed = CPH
Example: You spend $5,000/month on recruiting software, $3,000 on sourcer salary (allocated), $2,000 on LinkedIn, and close 2 senior engineers. Cost per hire = $5,000/2 = $5,000.
Why it matters: This is the metric executives care about. If you're paying $500/hire vs. $5,000/hire, you need to know why—and whether it's sustainable.
Industry benchmark: For technical recruiting: - Junior developers: $800-2,000 per hire - Mid-level developers: $2,000-5,000 per hire - Senior developers: $3,000-10,000 per hire - Specialized roles (Rust, Kubernetes, AI/ML): $5,000-15,000+ per hire
How to track: Create a monthly spreadsheet with all sourcing costs. Divide by confirmed hires (wait until 90 days to confirm they stay). Compare quarters and years.
5. Source of Hire Effectiveness
Source of Hire tracks which channels deliver candidates who: 1. Actually get hired 2. Stay longer 3. Perform better
Track every candidate back to original source: direct outreach, LinkedIn, GitHub, job board, employee referral, recruiter network, etc.
| Source | Avg Time to Hire | % Conversion to Hire | CPH | 90-Day Retention |
|---|---|---|---|---|
| Direct GitHub Outreach | 25 days | 8% | $1,200 | 95% |
| LinkedIn Recruiter | 35 days | 6% | $2,800 | 88% |
| Employee Referral | 18 days | 15% | $800 | 98% |
| Job Board | 40 days | 4% | $4,500 | 80% |
| Agency | 50 days | 5% | $6,200 | 85% |
Why it matters: This tells you where to invest. If GitHub sourcing costs 60% less and converts 40% faster, that's where your effort should go.
How to track: Tag every candidate with their original source in your ATS. Run quarterly reports to see which sources deliver quality hires at acceptable cost.
6. Sourcing Response Rate by Channel
Response Rate is the percentage of sourced candidates who reply to your initial outreach, by channel.
Typical response rates for technical outreach:
- Cold GitHub messages: 8-15%
- Cold LinkedIn messages (non-recruiter): 12-20%
- LinkedIn Recruiter InMail: 25-35%
- Email to verified email (from GitHub/portfolio): 15-25%
- Referral warm intro: 40-60%
Why it matters: Low response rates mean messaging problems, targeting problems, or channel problems. High response rates mean you're reaching the right people with compelling hooks.
How to track: Log outreach in your ATS and tag responses. Calculate response rate weekly by channel and messaging approach. Test different subject lines and hooks.
Example: If your GitHub message response rate is 5% but LinkedIn is 18%, you're wasting time on GitHub—or your GitHub hooks are weak. Test different approaches.
7. Candidate Quality Score (Non-Starter to Strong Fit)
Create a Candidate Quality Rating that separates signal from noise.
| Rating | Criteria |
|---|---|
| Strong Fit | Meets technical reqs, available in 2 weeks, wants the role |
| Good Fit | Meets reqs, available in 4 weeks, somewhat interested |
| Possible Fit | Meets 80% of reqs, longer timeline, needs convincing |
| No Fit | Missing key technical skills or not available for 3+ months |
Track the percentage of candidates you source who fall into each category.
- Strong sourcing produces 20-30% Strong Fit candidates
- Weak sourcing produces 5-10% Strong Fit candidates
Why it matters: This prevents you from counting "candidate conversations" as a success metric. A 100 conversations with 5 strong candidates is worse than 20 conversations with 10 strong candidates.
How to track: Grade candidates at first screening. Calculate percentage in each bucket. Compare by sourcer, channel, and time period.
Leading Indicators vs. Lagging Indicators
Leading indicators predict future success. Lagging indicators measure past success.
Focus on both, but emphasize leading indicators because you can actually influence them:
| Leading Indicator | Lagging Indicator |
|---|---|
| Outreach volume (by channel) | Hires closed |
| Response rate | Retention rate |
| Qualified lead volume | Time to hire |
| Pipeline conversion rate | Cost per hire |
| Candidate quality score | Revenue impact per hire |
Why this matters: You can't change last month's hires. But you can adjust this week's outreach volume, channels, and messaging. Track leading indicators daily, lagging indicators monthly.
Setting Up Your Sourcing Metrics Dashboard
You don't need fancy tools to start. A Google Sheet with these columns works:
- Date sourced
- Candidate name
- Tech stack
- Source (GitHub, LinkedIn, email, etc.)
- Response (yes/no)
- Date first replied
- Qualified (yes/no)
- Date first screen call
- Outcome (hired, rejected, withdrew, pending)
- Time to hire (in days)
Once you have 100+ data points, you'll see patterns. Then automate with your ATS.
For teams using modern ATS platforms (Lever, Greenhouse, JazzHR): - Use built-in pipeline reporting - Create custom fields for "sourcing channel" and "quality score" - Set up automated dashboards - Export monthly for deeper analysis
For agencies: Track metrics per client and per recruiter. You'll discover which team members source higher-quality candidates.
Benchmarking Your Metrics Against Industry Standards
Here's realistic benchmarking data based on technical recruiting:
| Metric | Below Average | Average | Excellent |
|---|---|---|---|
| CPQL | $150+ | $50-75 | $10-30 |
| Response Rate | <10% | 15-20% | 25%+ |
| Sourcing Conversion | <3% | 5-8% | 10%+ |
| Time to Hire | 90+ days | 45-60 days | 30-40 days |
| CPH | $5,000+ | $2,000-3,000 | $800-1,500 |
Don't obsess over being "excellent" at everything. Different roles, geographies, and skill levels have different benchmarks. Focus on:
- Understanding your baseline
- Setting realistic targets (10-20% improvement per quarter)
- Improving leading indicators first (response rate before cost-per-hire)
How to Improve Your Sourcing Metrics
Improve Response Rate
- Test different hooks. A/B test subject lines and opening messages. What works for Python developers won't work for Go developers.
- Verify email accuracy. Wrong email address = 0% response rate. Use tools like RocketReach or Hunter to validate emails from GitHub.
- Time outreach strategically. Send messages Tuesday-Thursday, 9am-11am in target timezone. Avoid Mondays and Fridays.
- Personalize beyond name. Reference specific GitHub projects, contributions, or blog posts. "I saw you built X—we're doing similar work" beats generic flattery.
Improve Conversion Rate
- Screen faster. If it takes you 10 days to schedule a call after a reply, you lose momentum. Aim for 24-48 hours.
- Improve your pitch. What's compelling about your role? Not the company—the problem, team, and tech stack. Technical people respond to interesting problems.
- Use technical filters. Pre-screen for experience level, tools, and specific skills before calling. Don't waste time on calls with unqualified candidates.
Reduce Time to Hire
- Build pipeline during slow periods. Don't wait until you have an open req to source. Build a bench of interested candidates month-round.
- Use structured screening. A 15-minute phone screen should eliminate 60-70% of candidates, advancing only strong fits.
- Parallel processes. Interview multiple candidates simultaneously. Serial interviewing kills speed.
Reduce Cost Per Hire
- Source higher-volume channels. Job boards and LinkedIn ads cost less per candidate but convert lower. GitHub sourcing costs more per candidate but converts higher. Mix both.
- Improve quality upfront. Sourcing 50 mediocre candidates costs more than sourcing 10 strong ones, even if the per-candidate cost is lower.
- Automate what you can. Use Zumo or similar tools to analyze GitHub activity for technical fit before you even message someone.
Tools That Help Track Sourcing Metrics
- ATS with reporting: Lever, Greenhouse, Workable, Bullhorn
- Sourcing intelligence: Zumo (analyzes GitHub to find proven developers), GitHub, LinkedIn
- Email tracking: Mailchimp, Outreach, Apollo
- Analytics dashboards: Tableau, Looker, Google Data Studio
- Spreadsheets: Google Sheets with VLOOKUP and pivot tables (surprisingly effective for <50 hires/month)
Common Mistakes When Tracking Sourcing Metrics
1. Confusing activity with results. "We sent 500 outreach messages" is activity. "We sourced 50 qualified candidates who convert at 8%" is a result. Track results.
2. Measuring the wrong stage. Don't obsess over who you source. Measure who gets hired and stays. If 90% of your sourced candidates are unqualified, sourcing more won't help.
3. Ignoring quality over volume. If you source 100 candidates and hire 1, that's a 1% conversion rate. If you source 10 and hire 1, that's also 1%—but you spent 90% less time. Quality matters more than volume.
4. Not comparing across channels. You think GitHub sourcing isn't working because you've only sourced 5 candidates. Meanwhile, you've sourced 100 via LinkedIn and hired 0. Compare like-for-like.
5. Setting unrealistic targets. You can't go from 40-day time to hire to 20 days overnight. Set quarterly targets (10% improvement) and compound them.
FAQ
What's a good sourcing conversion rate?
A realistic sourcing-to-hire conversion rate is 5-8% for technical recruiting. This means 100 sourced candidates = 5-8 hires. This accounts for candidates who don't respond, aren't as strong as expected, reject offers, or need longer notice periods. Anything above 10% is excellent; below 3% indicates a targeting or messaging problem.
How often should I review sourcing metrics?
Review leading indicators weekly (outreach volume, response rate, qualified leads). Review lagging indicators monthly (hires, time to hire, cost per hire). Review quarterly benchmarking to spot trends and adjust strategy. Don't obsess daily—data needs time to stabilize.
Should I measure sourcing ROI differently for contractors vs. full-time employees?
Yes. Contractor sourcing typically converts faster (contractors evaluate roles in days, not weeks) and costs less per hire. Full-time hiring takes longer but generates more revenue per employee. Track metrics separately to avoid comparing apples to oranges. A 30-day time to hire for contractors is normal; for senior FTE, 60+ days is normal.
What's the difference between Cost Per Lead and Cost Per Hire?
Cost Per Lead (or CPQL) = recruiting spend ÷ number of sourced candidates. Cost Per Hire = recruiting spend ÷ number of candidates who actually accepted offers. CPL is faster to calculate but less meaningful. CPH is the true cost but includes variables outside sourcing (interview quality, offer package, competing offers).
How do I know if I should hire a recruiter vs. a sourcier?
If your sourcing cost per hire is above $3,000 or time to hire exceeds 90 days, hiring a dedicated sourcer usually pays for itself. A good sourcer focused purely on pipeline might reduce time to hire by 40% and cost per hire by 35%. Compare: sourcer salary ($50k-80k) vs. 10 hires × $1,000 CPH savings = $10,000+ annual savings.
Related Reading
- Technical Recruiting Metrics: What to Report to Clients
- How to Track and Attribute Recruiting Revenue by Source
- How to Use Data to Improve Your Recruiting Process
Start Tracking, Start Improving
You can't improve what you don't measure. Most technical recruiting teams are flying blind—tracking activity instead of outcomes.
This month: Implement three sourcing metrics: response rate by channel, source of hire, and time to hire. Use a spreadsheet if necessary. Within 30 days, you'll have enough data to spot your biggest opportunity.
Next month: Build a simple dashboard and share it with your team. Make sourcing metrics visible.
This quarter: Set realistic targets and run experiments. Test new channels, messaging, or screening approaches. Measure results.
Want to improve your sourcing metrics immediately? Zumo analyzes GitHub activity to identify proven developers who match your requirements before you spend time on outreach. See how much faster your sourcing pipeline becomes when you're reaching the right candidates.
For more recruiting strategies and sourcing techniques, check out our sourcing guides.