Learn › Recruiting unit economics
The recruiter capacity ceiling — how many qualified meetings one recruiter can actually run
Recruiter capacity gets discussed in adjectives — busy, slammed, at capacity, fully loaded. Adjectives don’t manage. The actual ceiling on qualified candidate meetings per recruiter per week is a function of three time budgets — sourcing, meeting itself, and post-meeting work — that don’t compress equally. This guide derives the ceiling from production data, names where AI sourcing genuinely changes the math, and where it doesn’t.
A typical Japan agency recruiter without AI sourcing tops out around 8–10 qualified candidate meetings per week. The ceiling is set by three time budgets that have to all fit in a 40-hour week: sourcing-to-produce-the-meeting (typically 60–70% of the week pre-AI, 15–25% with AI), the meeting itself plus prep and write-up (1.5 hours per qualified meeting), and downstream candidate-and-client management on placements in flight. AI sourcing raises the ceiling to 14–18 meetings per week by collapsing the sourcing time-budget. It does not raise the ceiling to 30 — the meeting and post-meeting time-budgets don’t compress without quality loss.
The three time budgets
Take a recruiter’s working week as a fixed budget — call it 40 hours, knowing actual hours run higher and not all are productive. Inside that budget, three categories of work compete: candidate-discovery (sourcing), meeting work (prep, the meeting itself, the post-meeting write-up), and downstream pipeline management (candidates already in flight, scheduling, debrief, offer support). Anything else — admin, all-hands, training, internal politics — eats from the same budget without producing meetings.
Each budget has a fixed-cost floor and a variable-cost component. The fixed floor is what the recruiter has to do regardless of meeting volume — pipeline check-ins, weekly admin, recurring meetings. The variable component scales with meeting volume — every meeting requires its own prep, the meeting itself, and write-up. The capacity ceiling is the meeting volume at which variable plus fixed equals the available budget.
Budget 1 — sourcing
Pre-AI, sourcing time per qualified meeting averages 2.5 hours across our historical agency dataset. That includes Boolean searches, profile-by-profile review, scout-mail drafting, and the back-and-forth before a meeting is on the calendar. A recruiter producing 8 qualified meetings per week is running 20 hours of sourcing, or 50% of the working week; one producing 10 meetings is at 25 hours, 62%. Push the number higher and other budgets get crowded out, then meetings get dropped or quality drops.
AI sourcing changes this number sharply. In our 2026 cohort, AI-sourced qualified meetings cost 25–40 minutes of sourcing-time on average — the recruiter is reviewing the platform’s ranked output, picking who to message, and approving or lightly editing the platform-drafted scout. The same 8 meetings now consume 4–5 hours of sourcing-time instead of 20. Twelve meetings consume 6–8 hours. The sourcing budget stops being the binding constraint.
Budget 2 — the meeting itself
This budget has a hard floor that doesn’t compress. A qualified candidate meeting consumes 1.5 hours on average: 20 minutes prep (review the candidate profile, refresh on the role, line up the qualification questions), 45 minutes meeting time (Japanese candidate meetings run longer than US-equivalents because the relationship-building component is non-optional), and 25 minutes write-up (notes for the file, candidate-fit assessment for the client, debrief preparation). Some recruiters compress prep below 20 minutes; the meeting suffers. Some compress write-up below 25; the placement suffers when the candidate moves to client interview without a proper fit memo.
AI cannot meaningfully compress this budget. Some platforms attempt it — auto-generated meeting summaries, scoring-based prep notes — but the work product is the recruiter’s relationship-building and judgment, and those don’t outsource. A recruiter running 12 qualified meetings per week is consuming 18 hours on this budget alone. A recruiter running 18 meetings is at 27 hours, two-thirds of the working week.
Budget 3 — downstream pipeline management
Every qualified meeting that progresses produces downstream work: client debrief, second-round prep, candidate scheduling and feedback, offer support, candidate-side closing conversations. Across our cohort, this budget averages 3 hours per placement-track candidate over the placement cycle. A recruiter running a healthy book at 1:39 placement-to-meeting ratio has roughly 1 placement-track candidate per 39 meetings, but the pipeline of in-flight candidates is much higher — typically 8–15 candidates in various stages of post-first-meeting progression at any given time.
This budget is hard to predict because it depends on which candidates progress. A senior recruiter with a strong book sees 25–35% of qualified meetings convert to second-round client interviews; a junior with the same meeting count sees 15–20%. The downstream budget for the senior is 2× the junior’s at the same meeting volume. AI doesn’t change this because the work is candidate-side relationship management plus client-side coordination — the recruiter is irreplaceable here.
Putting it together — the math
Take a 40-hour week, allow 6 hours for fixed-cost work that produces no meetings (admin, weekly all-hands, training, internal coordination). That leaves 34 hours for meeting-producing work split across the three budgets.
= 5.0 hr/meeting → 34 hr ÷ 5.0 = ~7 meetings/week (range 6–10)
Post-AI, sourcing time drops to ~0.55 hr per meeting on average. Meeting and pipeline budgets are unchanged. The ceiling lifts.
= 3.05 hr/meeting → 34 hr ÷ 3.05 = ~11 meetings/week (range 9–14)
The ceiling lift is meaningful — 50–60% more meetings per recruiter per week — but it isn’t unlimited. A recruiter cannot run 25 meetings per week without breaking the meeting and pipeline budgets, and breaking those budgets is the recipe for placement-rate collapse.
Why the simple version of this math is dangerous
The math above is averaged across role types and recruiter seniorities. Real recruiters don’t run at the average. Senior recruiters with strong client relationships hit higher meeting-to-placement conversion ratios but spend more time on downstream pipeline management. Junior recruiters need more sourcing-time per meeting because they’re less efficient at scout-mail drafting and follow-up. A team-level capacity model that ignores this variance produces planning numbers that don’t survive contact with the team.
The right way to use the model is per-recruiter rather than per-team. Audit each recruiter’s actual time-budget allocation across two weeks — 30-minute granularity, calendar-based, not self-report. Compute their actual meeting capacity at current allocation. Then model what happens when AI sourcing collapses their sourcing budget and re-allocates the recovered hours to meeting and pipeline. The recovered hours are usually 15–25 per recruiter per week — enough to add 4–6 meetings per week per recruiter without breaking other budgets.
What this means for hiring decisions
If your existing recruiting team is at the 8–10 meetings per recruiter per week ceiling and unfilled reqs persist, you have three levers: hire more recruiters, contract for RPO, or compress the sourcing budget with AI sourcing. The third lever is cheapest per added meeting — the math above shows ~50–60% capacity gain on the existing headcount at AI sourcing’s typical cost per meeting. Hire-more-recruiters is most expensive per added meeting once you account for the months of ramp-up before a new recruiter hits average productivity. RPO sits between, useful for spike capacity.
Most teams that have done this audit find a single conclusion: they were budgeting for new heads when the math says they needed to budget for sourcing tools. The fixed cost of an additional recruiter is high; the variable cost of AI sourcing scales with usage. At the team’s current meeting volume, AI sourcing usually pays back in the first quarter.
Frequently asked
Why is the meeting time-budget 1.5 hours and not 1?
Because the meeting itself is only the middle part. A qualified meeting requires prep (you cannot run a candidate meeting cold and expect placement-quality output), the meeting itself runs 30–60 minutes in Japan mid-career segments depending on seniority, and the post-meeting write-up is what turns the meeting into a usable artifact for the client conversation. Compressing any of the three under 20 minutes consistently degrades placement rate. The 1.5 hours is the average across our cohort; teams running shorter prep see worse downstream conversion.
What about senior recruiters who claim they can do 20 meetings a week?
They’re either counting differently (initial screens that didn’t reach client introduction, candidate calls with low qualification, internal pipeline reviews framed as meetings) or they’re running on a recruiter-coordinator model where the senior recruiter does the meetings while a coordinator handles sourcing and pipeline admin. The latter model genuinely raises a senior’s meeting count because two people are doing the work that the model assumes one is doing. It also doubles the team-level cost; the per-meeting unit economics rarely beat AI sourcing on a single recruiter.
Doesn't AI sourcing also reduce post-meeting write-up time?
Marginally. The platform may pre-fill the candidate context the recruiter would otherwise have to gather for the file, saving 5–10 minutes per write-up. It does not write the candidate-fit assessment, the client-pitch language, or the recruiter’s qualitative read on the candidate’s interview-day signal. The bulk of the write-up budget — the part that determines whether the candidate progresses to client introduction — is irreducibly the recruiter’s. We use 25 minutes as the post-AI write-up baseline, down from 30 pre-AI; the gain is real but small.
How does this model apply to in-house TA recruiters?
The structure transfers. The downstream pipeline budget is usually larger (in-house TA invests more time in the offer-acceptance and onboarding-bridge stages than agency recruiters do), and the variable per-meeting time budget is usually smaller (the in-house recruiter knows the company’s hiring criteria intimately, so prep and write-up compress). Net, an in-house TA recruiter’s pre-AI ceiling sits in a similar 7–10 meetings per week range, with AI sourcing producing a similar 50–60% lift to roughly 11–14.
What's the right way to measure my team's current ceiling?
Two-week 30-minute calendar audit per recruiter, no self-report. Tag each block as sourcing / meeting (incl. prep + write-up) / pipeline / fixed-cost. Average across the team. Then count qualified meetings produced over the same two weeks. The ratio gives you team-level meeting-time-cost. Apply the math in this guide. Methodology details in our calendar audit briefing.
Sources
Time-budget figures (2.5 hours per meeting pre-AI, 0.55 hours per meeting post-AI, 1.5 hours per qualified meeting, 3 hours per placement-track candidate) are averages across ESAI Agency K.K.’s historical agency dataset and the 2026 production cohort. The 1:39.625 placement-to-meeting ratio is documented in the meeting unit-economics cornerstone. The calendar-audit methodology and team-level percentages are documented in the calendar audit briefing. Methodology, sample sizes, and statistical methods on our methodology page.
Find your team's actual ceiling
If your team is hitting 8–10 meetings per recruiter per week and reqs are still backing up, the math says AI sourcing is the cheapest next lever. Ten free credits validate it on your own reqs.