A 10x recruiter runs a hundred jobs
One job cannot go faster than its client. One person can run ten times as many of them. The only thing that ever stopped you was the admin, and that is the part a machine is good at.
Gowri wrote last week about the pipe: a job runs from a pool of people to a signed contract, the narrowest section is a hiring manager with two interview slots a week, and adding AI anywhere upstream of that just builds pressure. Several people read it as an argument that AI cannot help an agency grow. It is an argument about where the growth is, and the growth is outside the pipe.
A pipe has one tap and the client sets it. You do not get more out of a job by pushing harder at the front. You get more out of a desk by running more pipes at once, and the number of pipes a person can hold open has always been capped by something that has nothing to do with judgement. This post is about that cap, why it sat at ten for so long, and what it takes to move it to a hundred.
The growth is in how many pipes you hold open
Put the two pictures next to each other. The first is one job, the one from the last post, with its squeeze at the client interview. The second is the same job ten times over, each with its own client, its own diary and its own squeeze. Nothing about any single pipe has changed. What has changed is that there are ten of them, and ten taps running at two a week is a very different desk from one.
This is why the last post and this one do not contradict each other. The rate per pipe is the client's and you cannot buy it. The number of pipes is yours, and you can.
Where a consultant's week actually goes
Take an ordinary Tuesday on a desk with ten live roles. There is a candidate who needs three interview times from a client who has not replied. There are two interview confirmations to send, one reschedule, a candidate asking what the parking is like, another asking for the job spec again. Two CVs need reformatting into the agency template before they can go to a client. A reference has to be chased for a placement that starts Monday. A right-to-work document has expired. Four candidates from last week's shortlist want to know where they stand, and one of them has gone quiet and needs a nudge. Somewhere in that there are three phone calls that decide whether a person goes forward, and one meeting with a hiring manager about why the last two were not right.
Write the day down and sort it into two piles. The first pile is traffic: things that have to happen, in the right order, on time, and that do not need a recruiter's judgement to happen. The second pile is the calls and the meeting. On most desks I have looked at, the first pile is most of the day and the second pile is under two hours of it, and the two hours are the only part that produces a placement.
The important thing about the traffic pile is how it scales. Add an eleventh role and you do not add an eleventh call. You add another client to schedule around, another set of confirmations, another two CVs to format, another candidate who wants to know where they stand. The traffic grows in a straight line with the number of jobs. The judgement barely moves, because a job in the qualify stage needs three or four real conversations a week and a job sitting with a client needs none.
Why ten was the ceiling
Ten is roughly where the traffic pile fills the week on a desk that runs it by hand. Every agency owner has watched the same thing: a good consultant takes on a twelfth and a thirteenth role, the calls still get made because those are the bit they like, and what slips is the chasing. A client waits a day longer for interview times. A candidate does not hear back for a week and assumes the worst. The pipe from the last post starts leaking because the traffic outgrew the hours, and nobody stopped caring.
So the ceiling was never the consultant's ability to judge people. It was the consultant's ability to move messages, documents and diary invites around fast enough to keep ten clients and forty candidates from noticing they were one of ten. That is a logistics problem, and logistics is what machines are for.
What a desk of a hundred actually looks like
The number sounds absurd until you look at what state those hundred jobs are in on any given Monday. A job is only demanding while it is in the sourcing and qualify stages, when a recruiter is talking to people and deciding who goes forward. That lasts a week or two. After that it sits with the client: shortlist sent, interviews being booked, feedback awaited, offer being drafted. In that state it needs traffic every day and judgement almost never.
On a desk of a hundred open roles, twenty to thirty are in the stage that needs a human this week. The rest are waiting on someone else's diary, and what they need is for nothing to be dropped while they wait. Nobody is running a hundred qualify stages at once. They are running twenty five and keeping seventy five warm, and keeping seventy five warm by hand is the thing that was impossible.
A 10x recruiter is someone whose seventy five waiting jobs do not leak while their attention is on the twenty five that need it. The judgement stays human and stays roughly the size it always was. The traffic has to leave the desk.
What we built Recruitly to take off the desk
Everything below is a piece of traffic from that Tuesday, and what happens to it when the desk runs on Recruitly. None of it involves the software deciding whether a candidate is any good, and that is deliberate.
Scheduling. The calendar syncs with Google or Outlook, the meeting scheduler books interviews against real availability, and confirmations and reminders go out on their own. The client who has not replied with times gets chased by the system.
Chasing. Automation rules fire on the events that used to sit on a sticky note. A candidate moves stage and both the candidate and the client contact get told. A CV goes to a client and a follow-up sequence starts, so the chase for feedback happens on a schedule instead of when you remember. A candidate with no activity on their record for a while gets an email asking for an update, and a placement about to start puts a task on the owner's list a week before, with the same for the day it ends.
Candidate questions and updates. The candidate portal shows people where they stand, so "any news?" stops arriving in your inbox. Auto responses answer the questions that have answers. The conversation history sits on the record, across email, SMS and WhatsApp, so whoever picks it up next sees the whole thread.
CV admin. Bulk CV parse turns a folder of documents into records. The branded CV comes out of a template, the blind CV redacts what you tell it to, and submitting to a client is a single action from the pipeline with the cover note and the stage set. Nobody reformats a document by hand into the agency template on a Tuesday afternoon.
Notes and calls. Calls are transcribed and summarised, so the three conversations that mattered are on the record without anyone typing them up. The candidate brief and the scorecard get a first draft from the CV and the job spec, and the recruiter changes whatever is wrong, which is the right way round.
Compliance and paperwork. CV and document expiry run on triggers rather than on somebody remembering. Offer letters and terms go out for signature through DigiSign and you can see who has opened what. Email and phone enrichment finds the contact details a candidate forgot to include.
Two things are missing from that list on purpose. Recruitly does not ring a candidate and mark them qualified, and it does not auto-submit a CV to a client because a score said so. We looked hard at both, and both fail for the reason the last post spelled out: they turn an unknown into a confident colour and hand the finding out to the hiring manager, who responds by giving you fewer slots. The AI in Recruitly is on the branches, where speed is pure upside and nobody's judgement is being replaced. The scorecard drafts and the recruiter decides, and we are keeping it that way.
The week after
Here is the same consultant a few months in, with a desk that has grown from ten roles to somewhere between eighty and a hundred. Monday starts with a list of the twenty five jobs that need a human this week, because the other seventy five are being chased, confirmed and updated without anyone touching them. The calls that decide get made, three or four per active job, and they are the bulk of the day rather than the bit squeezed in between confirmations. The meeting with the hiring manager about why the last two were wrong still happens, because that meeting is where the trust lives and it always will be.
Two things follow that agency owners tend not to expect. The first is that the intake valve from the last post becomes the normal way to run the desk. When a recruiter is holding a hundred pipes, sourcing to what each client can decide this week is simply how you keep the desk sane, and the activity targets that pushed people to source three hundred for a role stop making sense to anyone. The second is that the client section, the one made of trust, gets wider on its own. A hiring manager whose interviews are booked the same day, whose feedback is chased politely and on time, and who never receives a CV the recruiter has not looked at, gives that agency more of their diary. That is the only way that section has ever been widened.
How to tell if a desk is ready for a hundred
You do not go from ten to a hundred by buying software and adding roles. You go by taking the traffic off first and then letting the desk grow into the hours that appear. Four checks before you try.
- Sort last week into the two piles, traffic and judgement. If the judgement pile is under a fifth of the week, the desk is carrying its own admin and there is room. If it is over half, the desk is already lean and the gain is smaller.
- Count the jobs by state. How many are in sourcing or qualify right now, and how many are waiting on a client. If most are waiting, the seventy five are already there and they are the ones leaking.
- Pick one branch and move it entirely. Scheduling is the usual first one, because it is the most visible to clients and the most annoying to consultants. Move the whole branch, because a branch that is half by hand is still a branch the recruiter has to watch.
- Add roles only as the traffic hours fall. The ceiling moves only when the admin leaves. A consultant given twenty roles and the same admin is a consultant with twenty leaking pipes.
The pipe still does not care where you widened it, and a desk is as many pipes as one person can hold open without any of them leaking. For twenty years the admin set that number, and we built Recruitly so the recruiter sets it instead.
Written for agency owners who read the last post and asked, reasonably, where the growth is supposed to come from.



