How to build a recruiting desk

A recruiting desk is one recruiter (or a small team) owning the full cycle for their own book of clients: finding the business, taking the job order, sourcing and screening, presenting candidates, and closing the placement. Building one is mostly a capacity problem — the same hours have to cover business development and delivery, which compete for the same time, and a desk that is not deliberately structured tends to default entirely to whichever one feels more urgent that week, usually delivery, at the expense of the business development that keeps the desk fed six months later.

This is a different question from getting a new recruiter productive. See how to onboard a new recruiter for the 90-day ramp. This page is the operating model once someone is running their own desk: how the hours split, how many requisitions it can carry, and the systems that make it repeatable rather than reactive.

A desk means owning revenue end to end

The distinction that matters: a desk recruiter's income depends directly on their own pipeline of clients and candidates, not on requisitions handed to them. That changes the job. Someone on a pure delivery role can focus entirely on filling what lands on their desk. A 360 recruiter has to generate what lands on their own desk in the first place, which means protecting time for activities that do not produce an immediate placement — calls to prospective clients, following up on stale relationships — even when an active search is pulling for every hour.

The three jobs inside one desk

A desk that only ever does delivery fills current roles well and runs dry every few months when the last batch of clients stops generating new work. A desk that spends too much time on BD and not enough on delivery has job orders it cannot fill fast enough to keep clients. The fix is not balance in the abstract — it is a protected, specific time allocation, covered below.

How many requisitions a desk can actually run

There is no reliable published number for this, because it depends on role difficulty, whether searches are exclusive or contingency, and how much of the week goes to BD versus delivery. Work it out from your own numbers instead:

Track your own version of this calculation quarterly. The number moves with role mix — a run of hard-to-fill specialized roles lowers it, a run of similar, previously-filled roles raises it — and a fixed "I run 10 reqs" rule ignores that variation.

A weekly time-block template

Weekly desk plan — [Recruiter], week of [date]

BD block (protected, same time every week):     [X hours]
  - New client outreach: ____
  - Follow-up on warm leads: ____
  - Check-ins with existing clients (not tied to an open req): ____

Delivery block:                                  [X hours]
  - Active requisitions this week: ____ (list, with next action each)
  - Sourcing time allocated per req: ____
  - Submittals due this week: ____

Pipeline block:                                  [X hours]
  - Candidates to re-engage from past searches: ____
  - Roles to build ahead of an expected opening: ____

Admin / ATS hygiene:                             [X hours]

Total planned hours: ____
Reqs carried this week: ____   New job orders targeted: ____

The BD block is the one most desks let slip first under a delivery deadline. Protecting it means treating it like a client meeting you cannot move, not a task you get to if the week allows.

Building BD alongside delivery, not after it

New desks often try to build a full client roster before taking on delivery work, and stall, because a cold pitch with no placement track record to point to is a hard sell. Reverse it where possible: take on delivery work (even split-fee or overflow work from a more established recruiter) to build a specific, provable track record — average time-to-fill, quality of candidates presented, client satisfaction — then use that record in BD conversations. "I filled three roles like this in the last quarter, averaging 24 days" is a far stronger opening than a cold pitch with nothing behind it. For what to say once a prospect is on the phone, see how to negotiate recruitment fees for the terms conversation that follows a won pitch.

Specializing: niche, vertical, or generalist

A specialized desk (one industry, one function, or one role type) builds referrals and repeat business faster than a generalist desk, because expertise compounds — the second search in a niche is faster than the first, and clients notice. The tradeoff is exposure to a single market's cycles; a niche that slows down takes the whole desk with it. A generalist desk trades that compounding speed for broader resilience across market conditions. Neither is categorically better — the choice should match the market you actually have access to and how much runway you have to build depth in one area before it needs to pay off.

Systems that make a desk repeatable

• Templates for every recurring document: intake summary, submittal, client update, offer call script. Writing each from scratch every time is the single biggest hidden time cost on a desk.
• A consistent note structure in the ATS, so a candidate or client record is useful to you (or a colleague covering for you) months later without reconstruction. A desk that records screens with something like Interview Signal gets a client-ready submittal summary within a minute of hanging up, which matters most on the weeks BD and delivery are both pulling hardest.
• A tracked pipeline of past candidates, tagged by skill and role type, so a new job order does not always start from a blank search.
• A standing weekly review of the desk plan against what actually happened, ten minutes, to catch drift — BD time quietly disappearing for a month, or one client consuming a disproportionate share of delivery hours.

Measuring whether the desk is actually working

A desk plan that never gets checked against results drifts quietly. Review these monthly rather than only when something feels wrong — by the time a desk "feels" off, the underlying numbers have usually been off for a while.

Recruiting agency metrics has the full formulas and worked examples for each of these. The point here is narrower: review them against the time-block plan specifically, so a slipping number can be traced back to which block of the week actually slipped, rather than triggering a vague sense that "things feel busier but nothing's closing."

When a desk needs to split

A single recruiter's desk has a ceiling, and growth past it usually means adding help rather than working more hours. Common signs it is time: BD time has been zero for more than a month running despite the plan calling for it, submittal quality is visibly dropping under volume, or a researcher doing only sourcing would free enough delivery time to justify the cost. Adding a researcher or a junior recruiter to take over part of the sourcing load is usually the first step, before splitting into a full team structure; see how to onboard a new recruiter once that decision is made.

Splitting too early carries its own cost: a researcher without enough sourcing volume to stay busy is an expense the desk cannot yet support, and a second recruiter added before BD is generating enough job orders for two people competes with the original recruiter for the same pipeline instead of adding capacity. Confirm the bottleneck with the monthly metrics above before adding headcount, rather than reacting to a single unusually heavy month.