RPO Pricing Models and When Each One Works
RPO pricing determines whether volume changes help you or hurt you, and most providers discover which after signing.
Recruitment process outsourcing is priced in three broad ways, and the choice determines what happens to your margin when the client's hiring volume changes. Since volume always changes, the pricing model is effectively a bet on which direction. Providers that pick without modelling the downside discover the problem in the quarter when hiring pauses and the cost base does not.
Last reviewed August 2026. Structural framework. Verify current market practice before quoting.
Key takeaways
- Per-hire pricing transfers volume risk to you. Which is fine when volume rises and severe when it stops.
- FTE pricing is predictable and caps your upside. You are selling capacity rather than outcomes.
- Managed service pricing suits mature, stable programmes. And requires scope discipline that most contracts lack.
- Scope creep is the failure mode in all three. Because RPO scope is genuinely hard to define in advance.
Per hire
The client pays a fixed fee per placement. Simple, familiar, and it transfers volume risk entirely to the provider.
Works when hiring volume is predictable and reasonably high, and when roles are similar enough that an average fee is meaningful.
Breaks when volume drops, because your team is sized for the plan and the revenue is not. It also breaks when the role mix shifts towards harder requirements at the same fee, which happens gradually and is rarely renegotiated.
The protection is a minimum volume commitment or a fee that varies by role band. Both are negotiable and rarely requested.
Per FTE or dedicated resource
The client pays for recruiter capacity, typically monthly per dedicated person.
Works when volume is uncertain, when the scope includes work beyond placements such as employer branding or process design, or when the client wants control over how the resource is deployed.
Breaks when the client treats a dedicated recruiter as unlimited capacity, or when your efficiency improves and you cannot capture the benefit because you are paid for time rather than outcomes.
That last point matters more as delivery automates. A provider producing roughly ten submission-ready profiles in hours rather than days is worth more and is paid the same, per AI in RPO delivery.
Managed service and outcome pricing
A fee for delivering a defined recruiting outcome, sometimes with service level commitments attached and sometimes with penalties.
Works when the programme is mature, the scope is genuinely definable, and both sides have enough history to know what normal looks like.
Breaks when scope is vague, which it usually is at the start of a relationship. An outcome contract with an undefined scope transfers unlimited risk to the provider.
This is the model most providers want and the one that requires the most disciplined contracting to survive.
Scope creep, the failure mode in all three
RPO scope is genuinely hard to define because recruiting work expands into adjacent activity naturally.
It starts with sourcing and screening. Then scheduling. Then offer management. Then onboarding coordination. Then a report the client wants weekly. Each addition is small, none is refused, and eighteen months later the team is doing substantially more than was priced.
Two protections. A written scope listing what is included and, more usefully, what is not. And a change mechanism that is used rather than avoided, since providers who never invoke it teach the client that scope is elastic.
How automation changes the model choice
If throughput improves, the pricing model determines who captures the benefit.
Per hire: you capture it. Delivering the same volume with fewer recruiters improves margin directly, which makes this the model that rewards efficiency investment.
Per FTE: the client captures it. You are paid for time regardless of what that time produces, so efficiency gains accrue to them.
Managed service: you capture it, provided scope holds.
A provider investing seriously in delivery automation should prefer per-hire or managed pricing, and should be conscious that FTE pricing quietly transfers the return on that investment to the client.
What to model before quoting
The downside volume case. What happens to your margin if hiring drops by half, which it will at some point.
Role mix drift. What happens if the average requirement gets harder while the fee stays flat.
Ramp cost. Standing up a programme costs before it earns, and that belongs in the pricing rather than in hope.
Scope elasticity. What the team will realistically be asked for beyond the written scope, and whether the fee absorbs it.
Frequently asked questions
What are the main RPO pricing models?
Per hire, where the client pays a fixed fee per placement; per FTE or dedicated resource, where they pay monthly for recruiter capacity; and managed service or outcome pricing, where a fee covers a defined recruiting outcome.
Which RPO pricing model transfers the most risk to the provider?
Per hire, since the team is sized for a hiring plan and the revenue depends entirely on placements actually happening. It works well when volume rises and severely when it stops.
When does per FTE pricing make sense?
When volume is uncertain, when scope includes work beyond placements such as process design or employer branding, or when the client wants control over how the dedicated resource is deployed.
Why does managed service pricing fail?
Usually because scope is vague at the start of a relationship, and an outcome contract with an undefined scope transfers unlimited risk to the provider. It suits mature programmes where both sides know what normal looks like.
How does automation affect RPO pricing choice?
It determines who captures the efficiency benefit. Per-hire and managed models let the provider capture it; FTE pricing transfers it to the client, since you are paid for time regardless of what that time produces.
What should an RPO provider model before quoting?
The downside volume case if hiring halves, role mix drift towards harder requirements at a flat fee, the ramp cost of standing up the programme, and how much scope elasticity the fee needs to absorb.
The scenario to run before signing
Model your margin at half the committed hiring volume. Every RPO contract eventually meets a quarter where the client pauses, and the pricing model decides whether that is uncomfortable or existential.
If the answer is unacceptable, negotiate a minimum volume commitment now rather than a rescue conversation later.
See delivery cost per role
Bring an RPO account and we will show you the cost per role delivered with sourcing and screening automated.
Book a demoFounder of Sortinghat, an AI-native ATS and CRM for staffing, search and RPO firms. Writes about recruiter capacity, sourcing economics and what actually changes when AI reaches a delivery desk. More about the author
Related reading