Skip to main content
All posts

Agency Operations

Sourcing in Recruitment: How Agencies Find Candidates Who Never Apply

Sourcing is the proactive half of recruitment: finding and engaging candidates before they ever apply. Here is how it differs from recruiting, where agencies actually find people, and how to turn ad hoc searching into a repeatable engine.

Written by: Saply Team

Sourcing in Recruitment: How Agencies Find Candidates Who Never Apply

Sourcing in recruitment is the proactive process of finding and engaging potential candidates before they apply, including people who are not actively job hunting. Where recruiting manages the applicants who come to you, sourcing goes out and finds the ones who never would have. It is the top of the funnel: the work of turning an empty shortlist into a pool of qualified, contactable people.

For a staffing agency, sourcing is not a nice-to-have. When a client hands you a niche requirement with a short deadline, the candidate who fits is almost never sitting in your inbox. They are employed, content, and invisible to a job ad. Sourcing is how you reach them anyway.

Sourcing vs recruiting: the difference

The two words get used interchangeably, and that costs agencies real clarity. Sourcing and recruiting are different jobs, often done by different people, measured by different numbers.

SourcingRecruiting
DirectionOutbound: you find themInbound: they come to you
Candidate poolPassive and activeMostly active applicants
Core activityIdentify, research, make first contactScreen, interview, assess, close
Main outputA qualified, engaged candidate listA hire
Measured byResponse rate, pipeline built, qualified leadsTime to fill, offer acceptance, quality of hire

In a small agency one recruiter does both in a single afternoon. In a larger one, dedicated sourcers feed vetted candidates to recruiters who run the rest of the full cycle. Either way, the skills are distinct: sourcing rewards research and outreach, recruiting rewards assessment and persuasion.

The sourcing process, stage by stage

Good sourcing is not “search LinkedIn until someone replies”. It is a repeatable sequence, and each stage has a job to do before the next one starts.

1. Identify Build a search from the role and find matches 2. Engage Personal first contact that earns a reply 3. Qualify Confirm fit, interest, and availability 4. Hand off Into the recruiting pipeline

Identify. Start from the requirement, not the search bar. Translate the role into the two or three attributes that actually predict fit (a specific stack, a sector, a certification, a location radius) and build a Boolean or structured search around them. Over-specify and you get nobody; under-specify and you drown.

Engage. The first message decides everything. A passive candidate owes you nothing, so generic outreach gets ignored. Reference something specific to them and be honest about why you are reaching out.

Qualify. Interest is not fit. Before a sourced name reaches a recruiter, confirm the essentials: right skills, open to a move, and realistic on money and location. Skipping this is how pipelines fill with noise.

Hand off. A sourced candidate is only useful once they enter a structured candidate pipeline where a recruiter can track and progress them. Names in a spreadsheet are not a pipeline.

Where recruiters actually source candidates

There is no single best channel. Strong sourcers run several in parallel and lean on whichever fits the role.

ChannelBest forThe catch
Professional networks (LinkedIn)White-collar and technical rolesCrowded inboxes; response rates keep falling
Your own database / ATSRoles you have hired for beforeOnly as good as your data hygiene
Referrals from placed candidatesTrusted, pre-vetted introductionsDoes not scale on its own
Niche communities (GitHub, Behance, forums)Specialist and creative talentSlow; needs genuine domain fluency
Job boards and aggregatorsActive candidates in volumeMisses the passive majority entirely

The channel most agencies underuse is the one they already own. A recruiting database full of past applicants is a warm sourcing pool that costs nothing to search, yet most desks start every new role on LinkedIn as if their history did not exist. The candidate you placed two years ago, or the strong runner-up you rejected, is often a faster fill than a cold outreach campaign.

Active vs passive candidates, and why the split matters

The single most important idea in sourcing is that most of the workforce is not looking for a job at any given moment, yet a large share of those people would move for the right offer. Sourcing exists to reach that second group, the passive candidates, because your competitors’ job ads never will.

Active Applying now. Reachable by ads. Passive Employed and not applying, but open to the right move. Only sourcing reaches them. Illustrative split of the working population at any given moment. Exact ratios vary by market and role.

That is also why sourcing pays off most on the roles job ads fail at. Advertise a common role in a loose labour market and applicants arrive on their own. Advertise a scarce skill and the silence is the whole problem. European labour markets have stayed genuinely tight in the segments agencies live in, and temporary and contract work remains a large slice of employment, roughly one in nine employees across the EU sit on temporary contracts, per Eurostat. Scarce supply is exactly the condition sourcing is built for.

How agencies build a repeatable sourcing engine

Ad hoc sourcing produces streaky results: a great week, then a dry month. Turning it into an engine means treating it as a process you can measure and improve.

  • Write a real search brief. Before touching a channel, agree the must-haves, the nice-to-haves, and the hard exclusions with whoever owns the role. Most wasted sourcing traces back to a fuzzy brief.
  • Template the outreach, personalise the opening. Keep a proven message structure, then change the first two lines for every person. The structure saves time; the opening earns the reply.
  • Log everyone, not just the yeses. A strong candidate who is not ready today is next quarter’s fast fill. Capture them so they compound into a talent pool instead of evaporating.
  • Track a handful of numbers. Messages sent, response rate, qualified candidates produced, and how many reach submission. Without these you cannot tell a channel problem from a message problem.

Sourcing and GDPR: the European rulebook

For agencies in Europe this is not optional detail. The moment you copy a passive candidate’s details from a public profile into your database, you are processing personal data, and the GDPR applies whether or not that person ever applied. In practice this means you need a lawful basis to hold sourced data, a retention limit rather than a forever list, and a way to tell candidates you hold their information when required.

The honest caveat: sourcing from public profiles is legal and normal, but “it was on LinkedIn” is not a lawful basis on its own. Agencies that treat sourced data with the same discipline as applicant data, clear retention rules, EU-based storage, and an answer ready for any DPO who asks, avoid the compliance headaches that catch out competitors who scrape first and think later.

Where sourcing ends and the rest of the workflow begins

Sourcing gets you a name and a CV. Everything that turns that into a placement happens downstream, and that is where the time usually leaks. A sourced candidate’s CV still has to be read, reformatted to your client’s template, scored against the role, and pushed into your ATS.

This is the seam where automation earns its keep. Sourcing itself stays human, because judgement about who to approach and how does not automate well yet. But once a CV lands, tools take over: parsing pulls it into structured data, candidate matching scores it against the open vacancy so you know instantly whether the person you just sourced is worth pursuing, and formatting turns their raw CV into a client-ready submission in your own template. In Saply that post-sourcing chain runs from a single upload. The honest limit worth stating plainly: Saply does not do the sourcing, it does not find the person for you, it handles the CV work that starts the moment you have one, so your sourcers spend their hours reaching people instead of reformatting documents.

Frequently asked questions

What is the difference between sourcing and recruiting?

Sourcing is the proactive front end: finding and making first contact with potential candidates, including passive ones who have not applied. Recruiting is everything after a candidate is in play: screening, interviewing, assessing, and closing. In small agencies one person does both; in larger ones, sourcers feed qualified candidates to recruiters.

What does a sourcer do all day?

A sourcer translates open roles into searches, finds matching candidates across channels, and sends personalised outreach to start a conversation. They research people, write first messages, and qualify interest before passing warm candidates to a recruiter. The job is measured by pipeline built and response rate, not by hires directly.

What are the best sourcing channels for a staffing agency?

The most reliable is your own database of past candidates, because it is warm and free to search. Beyond that, professional networks like LinkedIn suit technical and white-collar roles, referrals give pre-vetted introductions, and niche communities work for specialist talent. Strong agencies run several channels at once rather than betting on one.

Is sourcing candidates from LinkedIn GDPR compliant?

It can be, but the public availability of a profile is not by itself a lawful basis for storing that data. Under the GDPR you need a valid lawful basis, a retention policy, and a way to inform candidates you hold their details. Treat sourced data with the same rules as applicant data and keep processing inside the EU where your clients expect it.

How do you measure whether sourcing is working?

Track four numbers: outreach volume, response rate, qualified candidates produced, and how many reach client submission. Response rate tells you whether your messaging works; qualified-candidate count tells you whether your targeting works. Together they separate a channel problem from a message problem, which is the difference no vanity metric shows.