Guide
A plain-English explainer on recruitment process outsourcing: what it means, how it works, the different models, and how to tell whether it beats using an agency or hiring in-house.
8 min readLast updated
RPO stands for recruitment process outsourcing. It is an arrangement where a business hands all or part of its hiring to an external partner, who runs recruitment as an extension of the internal team — owning sourcing, screening, scheduling, offers and reporting — usually for a fixed fee rather than a fee per placement. The difference from a recruitment agency is ownership. An agency is engaged role by role and is measured on placements. An RPO partner is engaged to run the hiring function — sourcing, screening, scheduling, offers, reporting and process design — and is measured on how well that function performs.
RPO also stands for recovery point objective in IT and disaster recovery, which is a completely unrelated concept. This guide is about RPO in a hiring context.
Think of RPO as renting a talent function rather than buying individual hires. Instead of briefing an agency each time a vacancy opens and paying a percentage of salary when someone starts, you bring in a partner who owns the machinery of hiring on your behalf, usually for a fixed monthly fee tied to the scope you agree. In practice that means the RPO partner works inside your systems and under your employer brand. They use your applicant tracking system, your email domain and your interview process. Candidates experience your company hiring them, not a third party marketing them a job. What sits inside scope varies by engagement, but the common core is intake and role definition, sourcing and outreach, screening, interview coordination, candidate communication, offer management, and reporting on how the funnel is performing. What usually sits outside scope is anything that has to be yours: the hiring decision, the employment relationship, compensation policy, and the final say on whether someone is right for your team.
RPO works in five stages: diagnose, embed, run, report and hand back. Most engagements follow that shape whatever the provider calls it.
RPO is an umbrella term. Four models sit underneath it, and the differences matter more than the label.
The partner owns the entire hiring function across every role and every department, usually on a long-term contract. This suits large organisations with continuous, high-volume hiring and an appetite to outsource the whole discipline.
A defined burst of hiring with a start and an end: opening an office, standing up a new function, or delivering against a funding round. The partner covers the spike, then steps back rather than becoming a permanent fixture.
A recruiter works inside your team as though they were your own, under your brand and in your tooling, focused on your hiring plan rather than a portfolio of clients. This is what most growing companies actually mean when they ask about RPO.
What is embedded recruitment?Interview design, scorecards, tooling and hiring-manager capability can technically all sit inside an RPO scope. Most providers, ourselves included, keep the embedded team on delivery and run advisory as separate work, so process change gets proper focus instead of competing with live roles.
Talent advisoryThe three routes solve different problems. The honest comparison is about what you are buying and what you are left with, not which one is 'best'.
| Comparison point | RPO / embedded | Recruitment agency | In-house team |
|---|---|---|---|
| What you engage | A hiring function that runs your process for you | A supplier who introduces candidates for specific roles | Permanent employees who own recruitment internally |
| How it's charged | Typically a fixed fee tied to agreed scope | Typically success-only, paid on placement | Salary, benefits, tooling and management overhead |
| Measured on | Function performance: quality, funnel health, experience | Placements made | Function performance, plus everything else the team owns |
| Candidate experience | Your brand, your process, one consistent point of contact | The agency's brand sits between you and the candidate | Your brand, your process |
| What's left behind | Documented process, data and tooling you keep | The hire; the process stays where it was | Everything, as long as the people stay |
| Best when | You have a rolling hiring plan but not enough volume for a permanent team | You have occasional or one-off roles, or need niche market reach | Hiring is continuous, predictable and core to how you operate |
What you engage
RPO / embedded
A hiring function that runs your process for you
Recruitment agency
A supplier who introduces candidates for specific roles
In-house team
Permanent employees who own recruitment internally
How it's charged
RPO / embedded
Typically a fixed fee tied to agreed scope
Recruitment agency
Typically success-only, paid on placement
In-house team
Salary, benefits, tooling and management overhead
Measured on
RPO / embedded
Function performance: quality, funnel health, experience
Recruitment agency
Placements made
In-house team
Function performance, plus everything else the team owns
Candidate experience
RPO / embedded
Your brand, your process, one consistent point of contact
Recruitment agency
The agency's brand sits between you and the candidate
In-house team
Your brand, your process
What's left behind
RPO / embedded
Documented process, data and tooling you keep
Recruitment agency
The hire; the process stays where it was
In-house team
Everything, as long as the people stay
Best when
RPO / embedded
You have a rolling hiring plan but not enough volume for a permanent team
Recruitment agency
You have occasional or one-off roles, or need niche market reach
In-house team
Hiring is continuous, predictable and core to how you operate
If you're hiring occasionally rather than continuously, the agency model is usually the cheaper and more sensible route. Read about contingent recruitment
The jargon buyers run into when comparing providers.
FAQs
RPO stands for recruitment process outsourcing. In an IT or disaster-recovery context the same acronym means recovery point objective, which is unrelated — if you arrived here looking for that, this isn't the page.
It's an arrangement where an external partner runs all or part of your hiring function as an extension of your internal team, rather than being briefed role by role like an agency. The partner typically owns sourcing, screening, interview coordination, offer management and reporting, and works under your employer brand.
The partner starts by diagnosing your hiring plan, process and tooling, then embeds into your systems — your ATS, your calendars, your chat tool, your branding. From there they run the pipeline end to end and report on funnel health, with the process documentation and data staying with you at the end of the engagement.
An agency is engaged transactionally to fill a specific role and is measured on making that placement. An RPO partner is engaged to run the hiring function and is measured on how the function performs overall — quality of hire, funnel conversion, candidate experience and whether hiring managers are being properly supported.
Embedded recruitment is where an experienced recruiter works inside your business for an agreed period — using your ATS, your calendars and your employer brand — and runs hiring as part of your team rather than pitching candidates from outside. It is charged for the time and scope agreed, not per placement, and the process and data stay with you afterwards. At Velo North this sits inside our Fractional model.
Embedded recruitment is a model of RPO rather than a separate thing. It describes the version where a recruiter works inside your team under your brand, as opposed to a large outsourced service centre operating at arm's length. Most growing companies asking about RPO are describing embedded recruitment.
Consistency, ownership and what's left behind. You get a process that runs the same way every time, candidates who deal with your brand rather than an intermediary, visibility of how your funnel is actually performing, and documentation and tooling you keep afterwards — rather than a hire and no improvement to how you hire.
RPO is usually priced as a fixed fee tied to the scope agreed — the number of roles, the level of involvement and the duration — rather than as a percentage of each salary. That makes cost predictable and separates the fee from the individual hire. We scope it in a conversation before quoting anything.
Usually at the point where there's too much hiring to handle ad hoc but not enough to justify a permanent talent acquisition headcount. If founders or managers are absorbing recruitment alongside their real jobs, or agency fees are mounting across several roles without the process getting better, that's the trigger.
Project RPO is a defined burst of hiring with a clear start and end — standing up a new function, opening a location, or delivering against a funding round. It gives you the capacity of an RPO engagement for the spike without committing to an open-ended contract.
RPO generally covers permanent hiring and the process around it. MSP — managed service provider — generally covers the contingent workforce: contractors and temporary staff, along with supplier management, compliance and billing. They solve different problems and are often run by different providers.
Yes, and that's a common path. Companies often start with success-only agency support for individual roles, then move to an RPO or embedded model once hiring becomes continuous enough that paying per placement stops making sense.
Tell us what you're hiring for over the next few months and we'll tell you honestly which model fits — including when the answer is an agency, or nothing at all.