Headhunting vs recruitment agency: the difference that matters

They may sound similar, but they solve different problems. What truly separates direct search from CV delivery - and when each model makes sense.

They Sound the Same, They Cost Differently: Why the Difference Is Worth Knowing

What really separates true direct search from CV delivery, and when you actually need each one.

---

You get two quotes for the same role and both say exactly the same thing: "we'll find you candidates." One costs a fraction of the other. You pick the cheaper one, because on paper they promise the same result (which is fair enough, so why overpay?).

Here's the catch. You bought two completely different services that sound identical, and you took one where you needed the other. In the worst case you paid for headhunting and received the kind of recruitment you could have run in-house.

Same Result, Different Work

At the end of both processes you get the same thing: candidate profiles. And even here a warning is due, because sometimes all you get are inbound applications. That's precisely why the two are so easy to mix up and to judge on price alone.

But what happens before that result belongs to two different worlds. And it's that invisible part that decides whether you end up with a stack of paper and a vague sense that "a lot is happening," or a genuinely strong specialist in the right seat.

What "CV Delivery" Really Is

Let's be clear from the start: there's nothing wrong with it. It's simply a different service, one you can use when you genuinely need it.

A CV provider works *reactively*. They search databases, respond to applications, review the people who applied on their own or are easy to find, and pass you the ones who look right on paper and happen to be available. In this model, what counts most is volume, speed, and a low price.

And that's enough in specific situations. If the role is common, people apply for it, and the talent market is deep, then reacting to a flow of candidates is sensible and cheap. Your own internal capacity matters here too. This way of working pays off when you can process a stack of applications and put in the time to screen them and meet candidates.

Paying more for anything on top of that makes no sense.

You can sum up the whole mechanism in one sentence: a CV provider waits for the people who come to them, and (often, though not always) picks the best of that group.

What Direct Search Really Is

Direct search works the other way round. You don't wait for the people looking for a job. You go to the ones who aren't looking, but who stand a strong chance of having every competency you need.

This is the heart of it, the thing that changes everything: the best people, especially in niches, don't apply. There's no magic to it. Usually they're simply heads-down on their current work, or they just don't browse job boards. They won't answer your offer because they'll never see it. You have to identify them, pull them into the process, and assess them, ideally in a methodical, quality-driven way.

In practice it looks like this. You map the market, working out how many people even hold a given competency (often not thousands, but hundreds or dozens). You reach those people directly. You activate them, which means getting to a real conversation and confirmed interest rather than stopping at a generic message. Then you assess.

From a market of 150 to 500 people you run 10 to 20 conversations and present 3 to 6 genuinely matched candidates.

Direct search finds the right person in the places you can't reach on your own, and persuades them to talk to you in the first place.

How to Tell Which Service You're Getting

Because both will go by the same name. Here are the signals that separate them:

How many CVs versus how many conversations. A CV provider hands you a lot of profiles, fast. Direct search gives you few, but behind each one sits a conversation that actually took place. If you get thirty CVs in three days, you already know which service you bought.

"We have them in our database" versus "we mapped the market." A database is the past: people who landed in it at some point. A map is the present: who is genuinely available and reachable today. That's the difference between an archive and live market intelligence. A database is tempting, but it rarely brings the result you're hoping for.

Reactivation versus outreach. If they bring you people your own team has already messaged before, that usually isn't headhunting. It's a refresh of your own dead contacts. Real direct search brings you people who were never on your radar, and often the most interesting profiles are the non-obvious ones.

Interested candidate versus merely available. A CV in your inbox is not the same as a person who wants to talk to you about this specific role. Delivering a document is easy and adds nothing to the process. Getting someone to real, confirmed interest is work worth paying for.

Before comparing the invoices, review how headhunter fees are calculated and what a guarantee covers.

Why They Cost Differently, and Why Cheap Is Often the Most Expensive

The price reflects the work hidden behind it. Dozens of hours spent mapping the market and reaching passive candidates cost a different amount from searching a database and replying to applications. At EER, several specialists work on a single search, which clears most of the bottlenecks in a typical recruitment process. So this is not one service sold at two prices. These are two separate services.

But the real cost never sits on the invoice. It sits in time, and in the hidden costs around it.

We've seen a company try to hire its first leader in a new market on its own. The result was five months of "recruitment" and more than two hundred applications. In the end a single offer went out and was turned down. Back to square one, plans slipped by a full quarter. The saving on the recruitment model turned into a loss worth many times that saving.

Today's market only sharpens the effect. In Polish IT, job openings are growing several times faster than candidates. Filling a senior, niche role can take 8 to 14 weeks. In that environment, tipping a *larger volume* of CVs into the sieve doesn't work, because the right people simply aren't in that volume. You end up with more paper, the same results, and a rising cost just to process the data.

A role left open for a quarter costs far more than the price gap between two quotes. For positions where a new hire needs months to reach full speed, every week lost is real money off the table.

For a practical diagnostic framework, see what to change when an FPGA or ASIC role remains open for 90 days.

When You Need Which Model

Not every role calls for direct search, and there's no point overpaying for it when a simpler, cheaper option will do.

CV delivery is enough when the role is common, people apply for it, the market is deep, and the position isn't business-critical. In that case, relying on inbound candidates is fast, cheap, and sensible. This holds especially when you don't have the internal resources to post the ad and screen the people who send in their CVs.

Direct search is essential when the role is rare, senior, critical, confidential, the first hire in a new market, or when you've already tried and two hundred CVs led nowhere. In those cases the right people simply aren't in the application pool.

The simplest test: if the right people can be found through a job ad, you don't need direct search. If the risk that an ad won't be enough is too high, or the role is too important to compromise on, go with headhunting built on real direct search.

To Close

Both services sound the same because they end with the same word: "candidates." The whole difference is whether someone waited for the right person to come forward, or went out and found them where they couldn't be seen.

It's worth knowing which one you're buying. Because sometimes you pay for one when you need the other, and you only find that out a quarter of wasted time later.