RPO is recruitment process outsourcing: an employer transfers all or part of its recruitment process to an external provider that takes ownership of the process and responsibility for results. Here is the association's own definition, how RPO is priced, and how it differs from a search firm.
Recruitment Process Outsourcing (RPO) is, in the RPO Association's own words, "a form of business process outsourcing (BPO) where an employer transfers all or part of its recruitment processes to an external service provider." The defining feature is not candidate supply. It is ownership of the process: the provider designs and manages how hiring works, and answers for the results.
One quick note before moving on: in disaster recovery, RPO means something entirely different. AWS defines Recovery Point Objective as "the maximum acceptable amount of time since the last data recovery point," a measure of acceptable data loss. That is a systems concept, not a hiring one. This article is about the recruitment kind, and we will not mention the other one again.
The RPO Association draws this line itself, and it is worth quoting exactly because it is the clearest sentence anyone in the industry has written on the topic. RPO "differs greatly from providers such as staffing companies and contingent/retained search providers in that it assumes ownership of the design and management of the recruitment process and the responsibility for results."
A staffing company or a search firm is hired to fill a role. RPO is hired to run the hiring function, or a defined slice of it: requisition intake, sourcing strategy, screening workflow, interview coordination, offer management, reporting, sometimes the applicant tracking system itself. The provider does not just work inside your process. It owns the process design and is accountable for how it performs.
That distinction matters more than the fee structure. A search firm's scope ends at the fill. An RPO provider's scope is the machinery that produces fills, across however many roles and hiring managers the engagement covers, for as long as the contract runs.
The RPO Association publishes three pricing structures. It does not publish dollar figures for any of them, so no dollar range should be attributed to the association or to RPO as a category generally.
| Model | How the fee works | What it suits |
|---|---|---|
| Management Fee | The employer pays a monthly or hourly fee. The fee covers staff costs, technology, sourcing, account management, overhead, and other expenses. | Employers who want predictable, ongoing recruitment capacity regardless of hiring volume in a given month. |
| Pay for Performance | Each job requisition has an open fee, and each filled position has a close fee. | Employers who want cost to track activity: fees rise and fall with the number of roles opened and filled. |
| Hybrid True Up | Employers pay a minimum monthly management fee. The open and close fees are then compared to the minimum monthly fee, and the employer pays the higher of the two amounts. | Employers who want a cost floor during slow months without losing the activity-based ceiling during busy ones. |
These are structural descriptions, not price tags. If you want an actual sense of how these models are typically quoted in the market, that belongs in a separate conversation with an RPO provider, not in an association definition. A dedicated look at how RPO deals get priced in practice is at RPO pricing explained.
A retained or contingent search is scoped to one role. It starts when the role opens, ends when someone accepts an offer, and the relationship resets for the next hire. RPO is not scoped to a role. It is scoped to a process, running continuously across a portfolio of open positions and the hiring managers who own them.
That means RPO suits a company with sustained hiring volume across multiple functions, where the value is in standardizing intake, sourcing and reporting once and running it repeatedly. It does not suit a company with one hard role open right now. Buying process infrastructure for a single hire is buying more than the problem requires.
Read more on how the different fee structures line up against each other in recruiter fees and engagement models explained, and on the mechanics that separate a scoped search from an ongoing arrangement in what is an embedded recruiter.
We run an Embedded Partner model that is easy to confuse with RPO because both involve ongoing, multi-role capacity. The structural difference is worth being precise about.
Embedded Partner gives a client dedicated recruitment capacity for multiple active roles, working as an extension of the client's own team, for a monthly fee plus a reduced success fee. That capacity works inside the client's existing hiring process: their intake, their interview stages, their offer approvals. It does not redesign that process. It staffs it.
An RPO provider, by the RPO Association's own definition, assumes ownership of the process design and management itself, not just the labor running through it. That is the honest distinction: capacity working inside your process versus a provider owning the process.
Pricing for Embedded Partner, like our other two models, is available on request. Fees vary based on role seniority, search complexity and hiring volume, and we do not publish a dollar figure, a percentage, or any comparison of magnitude here. A closer comparison of the two models sits in embedded recruiter vs RPO, and the Hiring Scorecard is built to recommend Embedded Partner specifically when ongoing recruitment support is requested or four or more roles are open at once.
A company with one or two open roles a year is buying infrastructure it will not use. RPO's value comes from repetition: the same process, applied across many requisitions, over enough time that the setup cost pays for itself. Strip the volume away and you are left paying for a management layer around a single hire, which a scoped search handles more directly and at a scope that matches the actual problem.
If the honest answer to "how many roles are open right now" is one, a retained or contingent search, or a sourcing-focused engagement, is the better-fitting purchase. RPO earns its keep at volume, not at one.
RPO is process ownership, not candidate supply: an external provider designs and manages recruitment across a portfolio of roles and is accountable for the results, priced through a management fee, pay-for-performance, or hybrid true-up structure, none of which the RPO Association attaches dollar figures to. It fits companies with sustained hiring volume across multiple roles and hiring managers, not a company with one open seat. If that is your situation, a scoped search, described in what is retained search or what is contingency recruiting, is the more direct purchase.
A success fee is paid on a single placement, usually as part of a retained or contingent search scoped to one role. RPO pricing, as the RPO Association describes it, runs on a management fee, a pay-for-performance open and close fee structure, or a hybrid true-up between the two, applied across an ongoing portfolio of roles rather than one hire. Neither the association nor this article states dollar figures for these structures; they are described by mechanism only.
The RPO Association does not publish a specific role-count threshold, and neither do we for our own Embedded Partner model, though our Hiring Scorecard treats four or more concurrently open roles, or a request for ongoing support, as the signal worth acting on. Below that, the process-design overhead of RPO tends to outweigh what a single scoped search would cost to run.
Not necessarily. Some employers run RPO for high-volume, repeatable roles and still use a retained or contingent search firm for an executive or highly specialized hire that needs individual calibration rather than a standardized process. The two are structured for different problems: RPO owns a process across volume, search firms own one hire at a time.
How Recruitmint's Embedded Partner model is structured, what it includes, and the volume threshold at which the Hiring Scorecard recommends it over a single search.
Embedded recruiting and RPO both provide ongoing recruiting capacity, but differ in scope and how pricing is structured. Here is an honest comparison, using Recruitmint's Embedded Partner model and the RPO Association's own published pricing categories.
The market convention for retained executive search fees, what that means in dollar terms at different compensation levels, and how Recruitmint's Full Search model compares in structure.
Recruit