SmartHire vs. RPO: A Sourcing Layer vs. Outsourcing the Entire Recruiting Function

Recruitment Process Outsourcing (RPO) hands all or part of your hiring process to an external provider. A sourcing layer takes a different approach: it adds candidate flow to the team and tools you already have. Both aim at the same problem, too few qualified candidates and too much recruiting effort, but they solve it in different ways, with different costs, risks and levels of control. This is an honest comparison of when each makes sense, and how to decide between them.

What RPO is

In an RPO arrangement, a provider takes over some or all recruiting activities for an agreed period. That can include sourcing, screening, scheduling, offers and reporting. The provider may embed staff in your organisation, use its own systems and manage the whole process against agreed targets.

• Scope: end to end, or a defined part of the process
• Model: typically a monthly fee, a per-hire fee or a combination
• Team: provider staff working on your behalf, sometimes embedded in your team
• Goal: to reduce your internal recruiting workload and improve delivery

What a sourcing layer is

A sourcing layer generates and pre-screens candidates upstream of your applicant tracking system. It reaches people who are not applying, gets them interested, qualifies them against your criteria and delivers those who fit into your existing pipeline. Your recruiters continue to run interviews, decisions and offers.

• Scope: the top of the funnel, from reaching candidates to delivering qualified ones
• Model: campaign and platform based, focused on candidate flow
• Team: your own recruiters stay in control of the process
• Goal: more qualified candidates, with less sorting

Side-by-side comparison

• Control: RPO gives up some control to the provider. A sourcing layer leaves control with your team
• Scope: RPO can cover the whole process. A sourcing layer covers the top of the funnel
• Speed to start: RPO usually needs a longer set-up and transition. A sourcing layer can start delivering candidates within days
• Integration: RPO often changes how your team works. A sourcing layer feeds your existing ATS
• Ownership: with RPO, process and know-how may sit with the provider. With a sourcing layer, data and candidates build up with you
• Flexibility: RPO contracts are often longer. A sourcing layer can scale up or down with campaigns
• Cost structure: RPO costs cover people and process. A sourcing layer costs cover campaigns, pages and filtering

When RPO makes sense

• You want to remove most of the recruiting workload from your organisation
• You are starting in a new market and have no local recruiting capability
• Your hiring is highly variable and you want capacity on demand
• You do not have an in-house team, and do not want to build one
• You need a provider accountable for the full process against targets

When a sourcing layer makes sense

• You have a recruiting team and an ATS that work well
• Your main problem is too few qualified candidates, not the process after them
• You hire similar roles regularly and want to build a pipeline you own
• You want to reach passive candidates who do not apply on their own
• You want to keep control of the candidate experience and your employer brand
• You want to scale without adding recruiters

Cost: what to compare

Do not compare headline prices alone. RPO and sourcing layers have different cost structures, so compare on cost per hire and total cost of ownership.

• Fees: monthly, per hire or campaign-based, and what they include
• Internal time: how much of your team's time each model still requires
• Set-up and transition cost
• Contract length and exit terms
• Effect on time to hire and quality of hire
• What you own at the end: data, pipeline and process

Risks to consider

• RPO: dependence on the provider, a possible drop in service quality after transition, and difficulty bringing recruiting back in-house
• RPO: your employer brand is represented by someone else
• Sourcing layer: it only helps if your team can follow up quickly on the candidates it delivers
• Sourcing layer: results depend on the quality of ads, landing pages and qualification
• Both: unclear targets and measurement lead to disappointment

Can you use both?

Yes. Some organisations use RPO for parts of the process, such as scheduling or administration, and add a sourcing layer to strengthen candidate flow. Others use a sourcing layer as the first step, and only consider RPO if the process itself proves to be the bottleneck.

How to decide

• Where is your real bottleneck: too few candidates, or too little capacity to process them?
• Do you want to keep control of the process, or hand it over?
• How fast do you need results?
• How much of your recruiting is repeatable and could be systematised?
• What would you want to own in three years: a pipeline, or a contract?

Questions to ask any provider

• How will you measure success, and which numbers will I see?
• Who does the work, and who is my day-to-day contact?
• How does this integrate with my ATS and existing workflows?
• What happens to the data and candidates if we stop?
• What are the contract length and exit terms?
• Can you show results for roles like mine?

A short checklist before you sign anything

Whichever route you consider, agree the basics in writing before you commit. Vague agreements are the most common source of disappointment with both RPO providers and sourcing tools.

• Define the numbers that count as success, such as cost per hire, time to fill and qualified candidates per week
• Confirm who owns candidate data, ads and landing pages if you stop
• Agree reporting: what you will see, how often and in what format
• Check how the service integrates with your ATS and your existing approvals
• Clarify the notice period, minimum term and any exit costs
• Start with a defined pilot on one role, and compare against your current channels

How SmartHire fits

SmartHire is a sourcing layer, not an RPO. We run campaigns on Meta, Instagram, TikTok and Snapchat, build tailored landing pages, filter candidates with AI against your requirements and deliver only matches into the ATS or pipeline you already use. Your team stays in control of interviews and decisions. The first filtered candidates typically arrive within 3–5 days.

What is the difference between RPO and a sourcing layer?

RPO hands all or part of your recruiting process to an external provider. A sourcing layer adds candidate flow to the team and tools you already have, and leaves control with you.

Is a sourcing layer cheaper than RPO?

It depends on scope. They have different cost structures, so compare cost per hire and total cost of ownership rather than headline fees. A sourcing layer usually needs less transition and leaves you with a pipeline you own.

Do I need to change my ATS to use a sourcing layer?

No. A sourcing layer is designed to feed your existing ATS through an API or standard integration, so your workflows stay the same.

When is RPO the better choice?

When you want to remove most of the recruiting workload, are entering a new market without local capability, or need on-demand capacity and a provider accountable for the whole process.

Can I start with a sourcing layer and add RPO later?

Yes. Many organisations start by fixing candidate flow, and only consider RPO if the process after that turns out to be the bottleneck.