Recruitment process outsourcing, and the pricing model that decides what you get

Recruitment process outsourcing means handing some or all of your recruiting to a provider who runs it as your process, usually under your employer brand. It is a real and sometimes excellent answer to a scale problem. It is also the category where the pricing model, more than the provider, decides what actually arrives, and where the transition costs at both ends are routinely underestimated. This page covers the three shapes RPO comes in, what each pricing model rewards, and what to settle before an implementation starts.

The three shapes RPO comes in

These get sold under one acronym and they are not the same purchase. The governance, the commitment and the exit risk differ at every level.

Enterprise or full-cycle RPO

The provider runs the whole function across most of your hiring, on a multi-year contract, with its own team, technology and reporting. This is an outsourcing decision rather than a hiring one, and it should be priced and governed like one.

Project RPO

A defined surge for a defined period. A new site, a funded expansion, a season. You are buying a temporary team you do not have to hire and then release.

On-demand or recruiter-on-demand

Sourcers and recruiters by the month, embedded in your team and managed by you. The lightest shape, and the one closest to staff augmentation.

RPO next to a talent acquisition function

Both take recruiting work off your team. What differs is what you are counting when you pay for it.

Dimension	Recruitment process outsourcing	A talent acquisition function
What you buy	Recruiting capacity operating as your process, most often measured in recruiter headcount or in hires delivered.	The hiring process run end to end for the roles you have open, with the screening as the substance of it.
Cost structure	Recruiter FTEs by the month, or a management fee plus an amount per hire, or a straight cost per hire. Each rewards something different.	Flat, and not indexed to heads, to hires or to package.
Incentive alignment	FTE pricing pays for hours, so effort is the product and the outcome is governed by an SLA. Cost-per-hire pricing pays for joins, which quietly reintroduces the volume incentive many buyers chose RPO to escape.	Nothing in the fee moves with the offer, the count or the hours, so the only thing left to compete on is whether the shortlist is right.
Capacity	The real strength of the model. Ramping six recruiters for nine months is precisely what it was built to do.	Sized to your open roles rather than to a headcount plan, and it absorbs the reading rather than adding to your seat count.
Continuity	Strong during the contract and fragile at its edges. Calibration lives in embedded people you do not employ, and it leaves when the contract does.	Calibration is retained in the engagement, so what you rejected and why keeps improving the next shortlist.
What it structurally cannot do	Work below its own scale. Implementation, brand training and system integration are fixed costs that assume years and volume, and beneath that they dominate the value.	Take over an employer-brand operation across hundreds of hires a year in several countries. At that scale an enterprise RPO is the right structure.

RPO is bought against a hiring forecast, and the forecast is the part that most often turns out to be wrong. Pressure-test whether your hiring capacity matches the plan before sizing a contract around it.

When RPO is the right structure

At the scale it was designed for, nothing else does this job as well.

Large, repeatable volume across similar roles, where a consistent process and a consistent candidate experience are worth more than bespoke judgement on each seat.
A defined surge with a known end, where hiring a team you would later have to release is the worse option for everyone including the recruiters.
A hiring operation that has to look and feel like yours to candidates, at a scale where your employer brand is doing much of the recruiting work.
Multi-country hiring where local employment practice, language and compliance are the actual difficulty rather than the sourcing.

What to settle before the implementation starts

Each of these is cheap to fix in the contract and expensive to discover in month seven.

Decide whether you are buying hours or outcomes: FTE pricing buys recruiter hours. If the hires are wrong, the invoice is unchanged and the only lever left is an SLA. Cost-per-hire pricing buys joins, which puts the volume incentive back into a model many buyers picked specifically to escape it. Neither is dishonest. Both require you to know which one you signed.
The SLA becomes the product: Whatever you measure is what an embedded team optimises, and time-to-submit is the most commonly chosen and most easily satisfied metric in the category. If submissions are the target, submissions are what you receive, and the reading moves back onto your hiring managers.
The team that pitched is not the team that arrives: Ask to meet the named recruiters who will hold your roles, ask what else they will be holding, and ask what happens when one of them is reassigned. Continuity of people is the entire mechanism by which an embedded model learns your bar.
Exit is a project, not a notice period: When the contract ends, the calibration, the pipeline relationships and often the tooling leave with the provider. Agree at the start what comes back to you and in what format, including candidate history and rejection reasons, because that is the asset the contract spent years building.
Below a certain scale the fixed costs win: Implementation, employer-brand training and system integration are paid regardless of how many hires follow them. Without enough volume or enough contract length, you are carrying an outsourcing overhead to solve a hiring problem.

Whatever the pricing model, the number to hold a provider to is not submissions. It is how many of the people you meet you would actually hire. Ours, with the sample and the conditions attached, is published rather than quoted in a proposal.

What a function does differently from an embedded team

The distinction that matters is where the calibration lives when people move on.

Nothing is priced in recruiter heads, so changing the amount of work does not mean renegotiating a headcount.
The success profile is calibrated with the people who will manage the role before sourcing starts, and it is the thing screened against, so the measure is fit rather than submission speed.
Candidates are screened on 40+ signals, called and verified, and scored against the role, so hiring managers review decisions rather than queues.
The calibration is retained in the engagement rather than in one embedded individual who can be reassigned, which is the failure mode embedded models are most exposed to.
One role is enough to start, so there is no volume commitment to underwrite before you know whether the work is any good.

Continuity1 is not an RPO. There is no embedded headcount, no multi-year commitment, no implementation project, and the engagement is not sized in recruiter FTEs. If you are hiring hundreds of people a year and need a branded hiring operation across several countries, an enterprise RPO is the right structure and this is the wrong page.

How Continuity1 runs this funnel

The screening above is the job. These are the numbers it produces when a function owns it end to end, set against the published benchmarks for the same market.

The calibration figure is the one an embedded model finds hardest to keep, because it lives in people who can be reassigned.

20 to 49%: Shortlist-to-interview rate over one engagement; The industry curve points the other way; interview load keeps rising.; Continuity1 tracked engagement
1 in 3: Shortlisted candidates you meet who become the hire; Aligned engagements run nearer 1 in 2, distant ones nearer 1 in 10. The market takes about 180 applicants to make one hire, and that sifting lands on your team rather than ours.; Continuity1 tracked engagements
~3: Interviews your team sits in, per hire; Ashby puts technical roles at 17.6 interviews per hire across the whole process, up 52% since 2021. The rest of that load sits with the function, not with you.; Ashby talent-trends report
95%: Offers that close inside your stated band; 20 of the last 21. A flat fee earns nothing from an inflated offer; a percentage of CTC earns more.; Continuity1 tracked engagements

Every brief becomes a success profile before sourcing starts, calibrated with the people who will manage the role. That calibration is the step most hiring skips, and it is why a shortlist either matches the job or matches the job advert.

You review a scored shortlist and make the calls. The filtering never lands on your calendar.

Share a role See the workings and the citations

Questions buyers ask

What is the difference between RPO and a recruitment agency?

An agency sells introductions for a role and is paid when somebody joins. An RPO takes over the process itself and is paid for capacity or for volume, usually working under your brand so candidates experience it as your company. The practical difference is where the process lives. With an agency it stays yours. With an RPO it moves, and so does the knowledge of how it runs.

At what hiring volume does RPO start to make sense?

When the fixed costs of implementation, brand training and integration are small next to the hiring they support, and when the volume is predictable enough to size a team against. Ask a provider to show implementation effort separately from run cost. If they will not separate the two, you cannot answer this question and neither can they.

What happens to our hiring when an RPO contract ends?

That depends entirely on what you agreed at the start. The pipeline relationships, the calibration and often the tooling belong to the provider. Write the exit into the contract on day one, specify the format your candidate history returns in, and plan for a transition period in which hiring slows rather than one in which it does not.

Can we run an RPO and keep our internal TA team?

Frequently, and the split is what decides whether it works. The internal team should keep the decisions, the hiring-manager relationships and the employer brand. Ambiguity about who owns the bar is the most common reason these arrangements sour, and it shows up first as duplicated work rather than as an argument.