Your Recruiter Pipeline Has 340 Applicants and Hired 2 This Quarter

It is Thursday, 9:12 AM. Your Head of People opens Greenhouse on her first coffee. The dashboard reads 340 open applicants across 8 open reqs. The board of that same tab: 2 offers accepted this quarter, 41 candidates ghosted at the take-home stage, 88 applications sitting in "new" older than 21 days. The recruiter contract with the outside agency renews next Friday at $18K a month plus 22% of first-year comp on any placed hire. The CFO wants the renewal math by Monday.

She opens the exec channel and writes "recruiting recap coming Monday, running the numbers now." The Monday recap ships time-to-hire, defined three different ways across three tabs of the sheet. The board opens the deck, scrolls to slide 3, and asks whether the agency contract belongs on the Q4 line item.

The founders in this seat keep signing the next agency retainer and wondering why the same 340 applicants keep converting to the same 2 hires. Recruiting is not a req page and it is not a sourcer. Recruiting is a seven-stage queue that starts with a target profile and ends with a signed offer, and nobody on the org chart owns it end to end. The queue has a shape, and an agent stack owns it.

The 340 applicants, by the numbers

Sort the ATS. 62 applicants applied to the wrong role. 88 have no work authorization for the region on the req. 47 hit the auto-screen out on the tenure filter and nobody moved them to rejected. 34 are internal referrals that never got a first-touch email. Strip the noise and the real active pool is 109 candidates worth screening this week.

Of those 109, the in-house recruiter phone-screened 22 in the last two weeks. Moved 8 to the hiring manager. The hiring manager has open interview slots on Tuesday and Thursday and a stalled Slack thread on 3 of the 8. The other 87 sit in "new" or "reviewed" older than 14 days. Six weeks later the same 214-day AE ramp starts on the two hires that did close, because nobody staffed the onboarding queue either.

The sourcer who fills the top of the funnel does not own the screener rubric. The in-house recruiter who owns the phone screen does not own the hiring manager scheduling. The People Ops coordinator who owns Greenhouse hygiene does not own the take-home review. Four owners across two teams, one queue, zero handoffs on cadence. The recap ships whatever number is left after the finger-pointing.

Stage one: the sourcing pass that never became a queue

The Series B version of this function starts with a weekly sourcing brief per open req: 40 targeted profiles pulled from LinkedIn Recruiter and Gem, scored against the req rubric, matched against the referral network in the ATS, and dropped into the recruiter inbox by Monday 8 AM with pre-drafted outreach for the top 15. The recruiter reviews and hits send by 10 AM. Forty personalized touches leave the door every Monday per open req, on a cadence that never slips because a customer escalation landed.

The version most Series B teams run: the sourcer pulls 214 profiles over two weeks, sends a generic InMail to 88 of them, gets a 4% reply rate, and hands the recruiter the 3 warm leads on a Slack DM Friday afternoon. The recruiter is heads-down on interviews and does not respond until Tuesday. Two of the three are gone. The pipeline reads full on the dashboard and empty on the calendar.

The stage-one function is queue-work on a fixed cadence. The agent reads the open reqs and the rubric, pulls candidate lists from LinkedIn Recruiter, Gem, and the internal referral graph, scores against the rubric, joins against the ATS to dedupe against anyone touched in the last 12 months, and ships the ranked list of 40 targets per req to the recruiter inbox with drafted outreach in the recruiter's voice. Twelve hours of sourcer time per req a week collapses to a nightly agent run and a 30-minute recruiter review. The top of funnel fills on a cadence instead of a fire drill.

Stage two: the screening bottleneck

The 109 active applicants who deserve a phone screen this week wait on one recruiter who has 34 hours of interview coverage on her Google Calendar. The math does not work. Every candidate who waits more than 96 hours from application to first outreach drops the accept rate on any subsequent offer by a documented 12 to 22 percent. The pipeline that reads 340 on the dashboard is functionally 22 by Friday because the other 318 have gone quiet or accepted somewhere else.

The stage-two function scores the 109 against the rubric, drafts a personalized outreach in the recruiter's voice referencing the specific line item on the resume that matched, sends the top 60 through the recruiter's approval queue by Tuesday morning, and books the accepted screens directly into the recruiter's calendar via the ATS integration. The recruiter walks into Wednesday with 22 booked screens instead of an inbox of 88 stalled threads. Same recruiter, same 34 hours, four times the working conversations. The copilot version of this stack covers why seat-level AI does not close this gap even at $38K a month.

The debrief step matters as much as the outreach. The agent reads the recorded phone screen from Gong or Metaview, extracts the answers against the rubric, drafts the scorecard, drops it in Greenhouse with a proposed advance-or-reject decision, and posts the top 6 candidates per req into the hiring manager Slack channel on Thursday. The hiring manager reads six curated candidates instead of scrolling through 34 partial scorecards on a Friday afternoon.

Stage three: the 21-day silent gap between screen and offer

The candidate who cleared the phone screen on Tuesday waits. The hiring manager cancels the Thursday panel because a customer escalation lands. The panel reschedules to the following week. The take-home lands the week after that. The reference call slips because the recruiter is running two other loops. Twenty-one silent days between phone screen and offer. The candidate accepts the competing offer that moved in 9 days. The req reopens.

The stage-three function reads every open loop by candidate and by stage, pings the hiring manager Slack DM the moment a panel slot slips 48 hours, drafts the reschedule email in the candidate's voice referencing the specific work sample already reviewed, chases the two references on the reference list on day one of the offer stage, and ships a daily status card into #recruiting-live listing every candidate past SLA at their current stage. The 21-day silent gap closes to 9 to 12 days across the loop, and the offer accept rate holds in the 62 to 74 percent band instead of the 34 to 41 percent band the current path ships.

The math against the next agency retainer

Run two paths against the $18K a month plus 22% placement fee. Path A repeats the current motion Q3, ships 4 to 6 hires on the year at a loaded agency cost of $340K to $520K, and books the same 340 applicants through the same 2 hires per quarter on the in-house side. The board asks whether the agency belongs on the Q4 line item. The Head of People opens the renewal Tuesday and does not know how to answer the CFO's follow-up email.

Path B ships a two-sprint fractional AI recruiting function at $84K to $132K in build across the first 60 days and $6K to $10K a month to run. The sourcing function goes live at the start of sprint one. The screening and scheduling function goes live at the start of sprint two. The stalled-loop function goes live inside 14 days on the existing pipeline. Same 8 open reqs, run through the three functions, moves the 340 applicants through 60 personalized screens a week, 22 booked interviews, 8 hiring manager panels, and 3 to 5 hires closed on the quarter instead of 2.

The observed conversion range on this pattern across the Series B talent-motion book: 4 to 6 sourced hires a year on the current path becomes 14 to 22 sourced hires on the same 8 open reqs, and the loaded talent spend line reads $180K to $260K against the same headcount plan instead of $340K to $520K. Same open reqs, different queue. The 14-day sprints that ship this function cost less than one placement fee on a Senior Engineer offer.

The four numbers a Head of People runs before the next agency check

The founders reading this signed an agency retainer in April for the summer hiring push. Before the next $18K wire goes out, run four numbers against the recruiting function, not the agency scope. Score the queue, not the sourcer.

Sourced touches per open req per week. Measure the median personalized outreach messages sent per open req in a week. A healthy function runs 30 to 50. A stuck function runs 4 to 12, and the pipeline reads full on the dashboard and empty on the calendar.

Application to first personalized touch. Measure the median hours between an application landing in the ATS and the first personalized message in the candidate's inbox. A healthy function runs under 48 hours. A stuck function runs 5 to 14 days, and the accept rate on the eventual offer drops 12 to 22 percent.

Days from phone screen to offer. Measure the median calendar days between a completed phone screen and a signed offer in the winning candidate's inbox. A healthy function runs 9 to 14 days. A stuck function runs 21 to 34 days, and the accept rate lands in the 34 to 41 percent band.

Loaded cost per closed hire. Divide agency retainer plus placement fees plus internal recruiter loaded cost by hires closed on the quarter. A healthy function runs $18K to $34K per hire on Series B non-executive roles. A stuck function runs $84K to $132K per hire. Any two numbers in the stuck zone means the queue is the problem, not the agency, and you can scope the recruiting function in a 30-minute call this week.