What is Recruitment Process Outsourcing (RPO)?

RPO stands for Recruitment Process Outsourcing. It means handing some or all of your hiring process to an outside company that acts as your recruiting team. They source, screen, schedule, and sometimes close candidates on your behalf, usually under a monthly retainer or per-hire fee.

That's the textbook answer. Here's the real one.

RPO is what companies buy when their internal hiring breaks down and nobody wants to fix the actual problem. It's a $9.7 billion industry built on the gap between "we need to hire people" and "we don't have the infrastructure to hire people well." Sometimes that gap is real. Sometimes it's just that nobody invested in the internal team. The difference matters, because one of those situations justifies outsourcing and the other one just delays the reckoning.

I spend a lot of time in recruiting communities. The sentiment around RPO right now is brutal. The RPO model is, to use the technical term, totally f***ed in the current market. Nobody's signing contracts at $15-20K per head per month when internal teams can post on LinkedIn and get 200 applicants in a week. The value proposition that made RPO compelling in 2018 has eroded, and the industry hasn't figured out what replaces it.

But RPO isn't dead. It's just being honest about what it is for the first time.

How RPO actually works

An RPO provider embeds into your hiring process. Depending on the contract, they might handle everything from writing job descriptions to extending offers, or they might just own one piece, like sourcing or screening.

The typical setup looks like this. You sign a contract (usually 12-24 months). The RPO assigns recruiters to your account. Those recruiters use your ATS, your employer brand, your interview process. Externally, candidates think they're talking to your company. Internally, the recruiting team reports to the RPO, not to you.

There are three common models:

• ‍Full RPO. The provider runs your entire recruiting function. You don't have internal recruiters. This is common at companies that are scaling fast and don't want to build a TA team from scratch. It's also common at companies that had a TA team, laid them off, and now need to hire again.‍
• Project RPO. You bring in an RPO for a specific hiring push. Opening a new office. Launching a new division. Hiring 50 people in 90 days. The engagement has a clear start and end date.‍
• Selective RPO. The provider handles specific roles or functions. Maybe they own all your engineering hiring while your internal team handles everything else. Or they run executive search while you handle volume roles.

The pricing varies wildly. Some RPOs charge a monthly management fee plus a per-hire fee. Some charge a flat monthly retainer. Some charge a percentage of salary like a staffing agency but call it RPO because the word sounds more strategic. Most of it is staffing agencies in a trench coat pretending to be consultants. That's uncharitable, but it captures something real about the confusion in the market.

The case for RPO (when it's honest)

RPO works in a few specific situations, and the people who've been on both sides of it are pretty clear about which ones.

• ‍You're entering a new market. If you're a US company opening an office in Berlin, you don't know German labor law, salary benchmarks, or where the talent hangs out. An RPO with local expertise fills a genuine knowledge gap. This is the use case that almost nobody argues with.‍
• You have a temporary volume spike. You just closed a funding round and need to triple headcount in six months. Building an internal TA team for a surge that will normalize in a year doesn't make sense. Project RPO exists for exactly this scenario.‍
• You need executive search. I talk to corporate recruiters who haven't paid an external fee since 2021, except for exec search. C-suite and VP-level searches require networks and discretion that most internal teams don't have. This is the one area where outside help consistently earns its fee.‍
• You genuinely don't want to build a recruiting function. Some companies, especially in industries where hiring is episodic rather than constant, decide that recruiting isn't a core competency they want to own. That's a legitimate strategic choice. RPO lets them have a recruiting function without building one.

In all four cases, the company is buying expertise or capacity it truly doesn't have. That's the honest version of RPO. You're paying someone to do something you can't do yourself, at least not right now.

The case against RPO (which is most of the time)

Here's where it gets uncomfortable for the RPO industry. Most companies that buy RPO aren't in any of those four situations. They're buying RPO because their internal process is slow, their recruiters are overwhelmed, and an RPO salesperson showed up at the right moment with a slide deck about "strategic talent partnerships."

• ‍Companies outsource because they won't invest internally. I've watched companies spend $200K a year on RPO fees while refusing to pay $85K for a good internal recruiter because it comes out of a different budget line. The math doesn't make sense, but the organizational politics do.‍
• RPO recruiters don't know your company. An RPO recruiter handling your account is also handling two or three other accounts. They learned your company from a briefing document, not from sitting in your all-hands meetings. They don't know that your engineering manager says "senior" but means "someone who can mentor juniors." They don't know that your sales team's culture is completely different from your product team's culture. They're working from a job description, not from context.‍
• The candidate experience suffers. When a candidate's first interaction with your company is through someone who doesn't actually work there, something is lost. The RPO recruiter can recite your values from the career page. They can't tell a candidate what it's actually like to work on your team on a Tuesday afternoon. Candidates sense the difference, especially strong candidates who are evaluating you as much as you're evaluating them.‍
• You lose visibility into your own pipeline. I've talked to plenty of recruiters who've done both sides. Six years in agency, then corporate. The consensus is the same: outsource when you have to, avoid it when you can do it yourself. The reason is control. When recruiting is in-house, you see every candidate, every rejection reason, every drop-off point. When it's outsourced, you see a shortlist and a monthly report. The learning that comes from running your own process disappears.‍
• Spray and pray is the default. Spray and pray messaging isn't a strategy. It's desperation. And it's the default mode for a lot of RPO outreach. Volume over quality. Templates over personalization. The RPO's incentive is to fill the role. Your incentive is to fill it with someone who'll stay. Those incentives diverge more often than either side admits.

The RPO industry's real problem

The RPO model was built for a world where sourcing was hard. Finding candidates required expertise, tools, and networks that most companies didn't have. An RPO brought LinkedIn Recruiter licenses, Boolean search skills, and a database of passive candidates.

That world is mostly gone. LinkedIn made sourcing accessible to anyone with a subscription. Indeed and job boards deliver hundreds of applicants per posting. The average corporate recruiter today has access to the same tools the RPOs use. The sourcing advantage has collapsed.

What hasn't changed is the applicant screening bottleneck. Getting candidates is easy. Evaluating them is still painfully slow. Phone screens take 20-30 minutes each. Calendar coordination adds days. A recruiter handling three open roles with 100 candidates each is spending their entire week on logistics, not judgment.

This is the gap RPOs are actually filling for most of their clients. Not sourcing expertise. Not strategic talent advisory. Screening bandwidth. Companies are paying $15-20K per month because their recruiter doesn't have time to screen 200 candidates, and nobody thought to fix the screening process itself.

That's an expensive solution to a workflow problem.

What to ask before signing an RPO contract

If you're considering RPO, these questions will tell you whether you actually need it:

• ‍Is your problem sourcing or screening? If candidates are already coming in from job boards and your bottleneck is getting through them, RPO isn't solving your problem. It's adding cost to a process that needs redesigning, not outsourcing.‍
• What would it cost to fix this internally? Add up the RPO contract. Compare it to hiring one more recruiter plus better tooling. In most cases, the internal investment is cheaper and builds lasting capability. The RPO contract ends and you're back where you started. The internal investment compounds.‍
• Can you clearly define what the RPO will own? Vague scope is where RPO engagements go sideways. "They'll handle recruiting" isn't a scope. "They'll own sourcing and first-round screening for engineering roles in our London office for 6 months" is a scope. If you can't define it precisely, you're not ready to outsource it.‍
• What happens when the contract ends? The best RPOs build capability you keep. The worst ones create dependency you can't escape. Ask what the transition plan looks like. If there isn't one, the RPO is designed to be permanent, which means you're not outsourcing a function. You're renting one.‍
• Are you outsourcing expertise or just hours? If you're hiring in a market you don't understand, RPO adds expertise. If you're hiring for the same roles you always hire for and you just need more hands, you don't need an RPO. You need a faster process.

The alternative most companies don't consider

There's a middle path between "do everything manually" and "outsource everything to an RPO." It's fixing the step that's actually broken.

For most teams, that step is screening. You've got 150 candidates for a customer success role. Your recruiter is spending three weeks on phone screens. The hiring manager is frustrated. The RPO pitch sounds tempting.

But what if screening didn't take three weeks?

One-way video interviews let candidates record responses on their own time. No scheduling. No phone tag. No 20-minute calls where you know in the first 90 seconds it's not a match. You write the screening questions once. Every candidate answers the same questions. You review when you have time.

With a platform like Truffle, which combines resume screening, one-way video interviews, and talent assessments, the screening step that was consuming your entire week compresses into a few hours. AI transcribes and analyzes every response against the criteria you defined, surfacing match scores and Candidate Shorts that show you the most revealing 30 seconds of each interview. You're not outsourcing your judgment. You're getting better evidence to use it faster.

The recruiter who was drowning in phone screens? She's now reviewing her top 15 candidates in 45 minutes instead of screening 60 by phone over three weeks. She still makes every decision. She still knows the candidates. She just isn't spending her week on calendar coordination and repetitive conversations.

That's $99 per month instead of $15,000. And you keep control of the candidate experience, the employer brand, and the institutional knowledge that comes from running your own process.

When to use RPO and when to fix your process instead

Use RPO when you're buying genuine expertise you don't have: a new geography, a niche function, executive search, or a time-bound surge that doesn't justify permanent headcount.

Fix your process when the problem is bandwidth, not capability. If you know how to recruit for these roles but you just can't get through the volume, the answer isn't more people doing the same slow thing. It's a faster way to do the thing.

The RPO industry will probably evolve toward the expertise end of this spectrum. The bandwidth-for-hire model is under too much pressure from better tools and more capable internal teams. The RPOs that survive will be the ones that genuinely know something their clients don't, not the ones that are just extra hands on a broken process.

For teams between 30 and 200 employees hiring for roles they understand well, the math almost never favors RPO. Invest in your internal team. Give them tools that compress hiring from weeks to hours. Let the RPOs focus on the engagements where they actually earn their fee.

The principle is simple. Outsource when you have to. Do it yourself when you can. The trick is making sure "when you can" covers a lot more ground than it used to.

Frequently asked questions about recruitment process outsourcing

What's the difference between full lifecycle RPO, project RPO, and on-demand RPO?

Full lifecycle RPO (sometimes called end-to-end RPO or enterprise RPO) means the provider runs your entire recruitment function permanently. They own everything from workforce planning and candidate sourcing to offer management and background checks. Project RPO is time-bound: you bring in a provider for a specific hiring surge, like opening a new office or scaling a department, and the engagement ends when the project does. On-demand RPO (also called modular RPO or contingent RPO) is the most flexible. You tap the provider for specific roles or tasks as hiring needs arise without a long-term contract. Hybrid RPO blends these models, typically combining a small permanent RPO team with on-demand capacity for spikes. The right model depends on whether your hiring volume is steady, seasonal, or unpredictable.

How is RPO different from a staffing agency or managed service provider?

A staffing agency finds candidates for a fee, usually 15-25% of first-year salary. They work outside your process. An RPO provider embeds inside your process, using your applicant tracking system, your employer branding, and your interview structure. The candidate doesn't know they're talking to an outsourced recruiter. A managed service provider (MSP) is a layer above both. MSPs manage your relationships with multiple staffing agencies and RPO providers, handling vendor selection, service level agreements, and consolidated billing. Think of it this way: a staffing agency fills roles, an RPO runs your recruitment function, and an MSP manages the vendors who do either. Business process outsourcing (BPO) is the broadest category and covers outsourcing any business function, not just hiring.

What does an RPO provider actually handle day to day?

A full-service offering typically covers: recruitment strategy and workforce planning, job descriptions and job postings, candidate sourcing (both active candidates and passive candidates), resume review, screening candidates through structured interviews or talent assessment, candidate communication throughout the process, salary negotiations, offer management, and background checks. Some RPO providers also handle recruitment marketing, employer branding, candidate relationship management, and data analytics on hiring performance. The scope depends on your contract. Most RPO partnerships are customized, so you can carve out the pieces your internal team wants to keep, like final interviews with hiring managers, and hand over the rest.

How do I choose the right RPO provider?

Start with the question from the article: are you outsourcing expertise or just hours? If you need industry expertise or global reach in a market you don't know, prioritize providers with deep specialization in your sector and geography. If you need high volume RPO capacity, prioritize providers with strong technology partners and proven operational scale. Either way, look at how they handle talent intelligence and market analysis. A good provider should give you hiring data and advanced analytics that help you make better decisions, not just a stack of resumes. Check their technology stack: do they use AI-powered tracking systems, or are they still running everything through spreadsheets? Ask about their candidate communication process. Ask to talk to clients who ended an engagement, not just current ones. And get specific about service level agreements: what are the time to fill targets, cost per hire benchmarks, and quality of hire metrics they'll commit to?

Does RPO actually reduce cost per hire and time to fill?

It can, but the math is more nuanced than RPO providers suggest. Cost per hire often drops because RPO replaces contingency agency fees (15-25% per hire) with a lower blended rate. But operational costs like the management overhead of running an RPO relationship, the time spent on alignment calls, and the knowledge transfer during onboarding are rarely included in the comparison. Time to fill typically improves early in an engagement because the RPO throws more recruiters at the problem. Whether it stays improved depends on whether the provider actually fixes your process or just adds headcount to a broken one. The real cost savings come when RPO helps you build internal capability: better talent pools, stronger employer brand, lower turnover rates, and improved quality of candidates reaching hiring managers. If the RPO just rents you recruiters and the numbers revert when they leave, you paid for a temporary fix.

Can RPO help with internal mobility and workforce planning?

Some RPO solutions include workforce planning and internal mobility as part of their scope, but most don't. Traditional RPO is focused on external hiring: filling open roles with outside candidates. Internal mobility, moving existing employees into new roles, is usually owned by HR or a dedicated talent team. That said, the better RPO providers will flag when an external search could be solved internally, especially if they have visibility into your workforce data and business objectives. If internal mobility and long-term workforce trends matter to your recruitment strategy, ask about it explicitly during provider selection. It's a differentiator between providers who think strategically about your talent pipeline and providers who just fill requisitions.