We don't want more candidates. We want fewer.

"We don't want more candidates, we want fewer."

That's a senior TA leader at a large enterprise, said flat, on a call last week. It came up in six separate conversations that same week. Not from teams who are struggling to attract people. From teams drowning in them.

Here's the desk it comes from. One recruiter, sometimes two, sitting on more open roles than they can properly work. Under a single req there are 400 applications. Maybe six are worth opening. The rest have to be read, or at least skimmed, before anyone can be sure they're not the six.

400 applicants isn't a win. For a two-person team it's 400 things to clear, and maybe six that matter.

Why does more volume make a lean team slower, not faster?

Because someone still has to look at all of it. Volume only helps if you've got the people to process it. Most lean teams don't.

A TA manager at an enterprise retailer said it clearly: "We don't want loads of non-relevant applications because we're a lean team." The team's already going through a lot directly. Every irrelevant application is time taken from a real conversation.

If a recruiter spends 90 seconds ruling out each of 350 no-hopers, that's nearly nine hours gone on a single role, before they've spoken to anyone. Multiply that by a full desk of open reqs and the week disappears into sifting.

So the goal for a small team isn't a bigger top of funnel. It's fewer people arriving, and the ones who arrive being right.

What does "fewer but relevant" actually look like in practice?

Qualified candidates landing in your ATS, not a pile of applications for you to grade.

A qualified candidate is one checked against the specific criteria you set for the role: the must-have skills, the experience level, the location, whatever "good" means for that req. Not keyword-matched to a job title. Measured against what you said good looks like.

Archer's job here is deliberately narrow. You define what a strong candidate for the role is. Archer reaches out to the market and qualifies people against that definition. The ones who clear it land in the ATS you already use. You spend your time on the conversation, not the cull.

The division of labour matters here. Recruiters own quality. You decide what counts as a fit, and you can be as strict as you want. Archer does the reach and the qualifying. It doesn't get to lower the bar to hit a number.

Doesn't an AI sourcing tool just add to the flood?

Plenty of tools promise more candidates faster, which for a lean team is the opposite of help.

Archer is built the other way round. It works to a definition of quality, not a volume target. If ten people match what you asked for, you get ten qualified candidates. You don't get a padded list to make the output look busy.

For a team of one or two, that's the difference between a shortlist you can act on today and a queue you'll never get to the bottom of.

Where does this help lean teams most?

Roles you're flooded on. The high-volume, low-relevance ones where the good candidates are real but buried, and the team can't dig fast enough.

Archer reaches into the market for those roles and brings back people who meet your criteria, straight into the ATS. No new system to learn. No separate inbox to check. The recruiter picks up qualified candidates where they already work.

That's the whole point of it for a small team. Less to clear. More conversations that go somewhere.

If your week is mostly ruling people out, that's the problem worth fixing first.