Recruitment process outsourcing is when a company hands over ownership of some or all of its hiring process, sourcing, screening, sometimes the offer stage, to an outside provider that runs it inside the provider's own systems. This breaks down the three ways that's sold, what each is priced on, and the arithmetic for deciding whether to buy the process or build one you keep.
What recruitment process outsourcing actually is
Recruitment process outsourcing is not the same thing as a staffing agency filling one open role. An agency works a single requisition and charges a fee when you hire their candidate. Recruitment process outsourcing, usually shortened to RPO, is a standing arrangement rather than a one-off placement: the vendor owns a set scope of hiring on an ongoing basis, whether that's one role or every role in a region, and runs the applicant tracking system that hiring happens in.
There are three shapes this takes. End to end RPO covers most or all of a company's hiring on an ongoing basis. Project based RPO covers a defined chunk of hiring with a start and end date. On demand RPO is a recruiter or two embedded in your team for a set stretch of time, working your requisitions but on the vendor's clock. Outsourced recruiting always means one of these three, and the pricing mechanism is different for each.
The three models, and what each one is priced on
End to end RPO is typically priced as a percentage of the placed candidate's first year salary, charged per hire as they land. This is the model that scales with your hiring volume and your salary bands, so it costs more in absolute terms the more senior or the more numerous the roles.
Project based RPO is usually priced differently: a flat monthly fee per recruiter assigned to the account, for the length of the project. If a vendor puts two recruiters on your six month expansion, you're paying for two recruiter-months each month, not a percentage of what those recruiters place.
On demand RPO uses the same flat monthly fee per recruiter mechanism as project based work, just without a fixed end date built into the contract. You can usually scale the number of recruiters up or down month to month, which is the main lever you have to control rpo cost once you're inside a contract. What you don't get in any of the three models is a fee schedule you can compare apples to apples across vendors, because the base (percentage of salary versus flat monthly rate) is different depending on which model you're buying.
When outsourcing the hiring process is the right call
There are three situations where outsourcing recruiting is the correct call, not a compromise.
A hiring spike with a known end date. A warehouse opening that needs sixty people in ten weeks doesn't justify hiring and training an internal recruiting team you'll have nothing for in month three. Building in-house loses here because the fixed cost of standing up a function outlives the need for it.
An office opening in a country where you have no existing network. You don't know which job boards convert, what the going comp bands are, or which messages get a reply in that market. A vendor with existing local reach skips months of trial and error. Building in-house loses here because the learning curve alone can eat the entire hiring window.
A company with no recruiting function that needs one working next month. If nobody internally has run a sourcing sequence before, on demand RPO gets requisitions filled while you decide whether to build the function permanently. Building in-house loses here because you'd be learning the job and doing the job at the same time, with live roles waiting.
Outside these three, rpo vs in house recruiting starts to tilt the other way, which is the part vendors don't lead with.
What you're buying, and what stays with the vendor
Here's the mechanism worth understanding before you sign: the hires happen inside the vendor's applicant tracking system, using the vendor's sourcing sequences, the vendor's outreach message templates, and the vendor's candidate database built up over years of sourcing across other clients. That's what actually does the work. You get filled roles and a status report. What you don't get is the system any of it ran on, so when the contract ends, the machinery goes with the vendor and only the hires stay with you.
Compare that to what a single source of truth for the data you already have looks like when it's built inside your own CRM: every candidate touch, every message variant, every outcome sits in a system your team can query next quarter. With RPO, that same information exists, it's just sitting in a system you don't have a login for once the contract ends.
The cost that never shows up on the invoice
Run this forward two years and a hundred hires. The roles are filled. The invoices are paid, priced either as a percentage per hire or a flat monthly fee per recruiter, whichever model you signed. Then the contract ends, or you decide to bring recruiting in-house, and here's what you're left with: no pipeline of candidates who were close but not hired, no message template that you know gets a 20% reply rate versus one that gets 3%, no candidate database, no sequence you can hand to a new recruiter on day one.
That's the real rpo cost, and it doesn't show up on any invoice because it's not a cost you pay, it's a cost you don't avoid. The learning that happens over a hundred hires, which channels work, which messages land, which candidates are worth a second look next time, was outsourced along with the process. The day the contract stops, all of it stops producing, because none of it was ever yours.
Building the process you keep
The in-house alternative is slower to start and looks more expensive in month one, because you're paying for a recruiter's time and for tools before a single hire lands. But every sequence, every template, and every candidate record gets built inside your own ATS and CRM, tools you already run. Hire thirty and you haven't just filled thirty roles, you've built a database of hundreds of screened candidates, a set of message templates ranked by actual reply rate, and a sourcing playbook a second recruiter can pick up without starting from zero. This is what own systems you can walk away from and nothing stops working means in practice: the assets sit in tools you control, not a vendor's account.
The real downside, and it is a real one, is speed and ownership. Standing up an in-house function from nothing typically takes longer to produce a first hire than plugging into a vendor who already has candidates warmed up. And someone on your team has to own it, meaning a recruiter or an operations lead whose job includes maintaining the ATS, the templates, and the sourcing cadence, not just filling requisitions. If nobody is willing to own that, in-house recruiting quietly decays into an unmaintained spreadsheet within two quarters.
The breakeven arithmetic
Here is a worked example, not a benchmark, so swap in your own numbers before you act on it. Assume an average hire salary of $70,000 and an end to end RPO fee of 20% of first year salary, which works out to $14,000 per hire. Assume an in-house function costs $100,000 a year fully loaded, one recruiter at roughly $90,000 plus ATS and sourcing tools at roughly $10,000, and that one recruiter can comfortably handle up to 25 hires a year.
Divide $100,000 by $14,000 and the breakeven lands at just over seven hires a year. Below seven hires a year, RPO's per-hire fee costs less than carrying a full-time function. Above seven, the fixed cost of in-house recruiting is already covered, and every additional hire that year is close to free by comparison, while each RPO hire keeps costing the same $14,000 whether it's hire one or hire twenty. The volume where building wins isn't exotic, it's a company hiring roughly one person a month.
A short test before you sign anything
Three questions settle most of these decisions before you've read a single proposal.
- Does the need have an end date? If yes, project based or on demand outsourced recruiting is the right tool. If no, keep reading.
- Is the role or market repeatable, meaning will you hire this kind of role again in this market? If no, build nothing, outsource it. If yes, every hire you outsource is a rebuild you'll pay for again next year.
- Do you want to own the candidate data, the sequences, and the message templates when this is done? If you don't care, RPO is simpler. If you do, RPO was never going to hand it to you, so build in-house.
A hiring spike with an end date and no repeat need is a clean case for outsourcing. Ongoing, repeatable hiring where you want the pipeline to compound is a clean case for building it yourself. Most real situations sit somewhere in between, which is exactly why the three questions matter more than any vendor's pitch deck.
Common questions
Is recruitment process outsourcing cheaper than hiring in-house?
For one or two roles or a short spike, usually yes. Past a certain hire volume the ongoing fee outweighs the cost of building and running the function yourself.
What's the difference between RPO and a staffing agency?
A staffing agency fills a single requisition for a fee per hire. RPO takes over sourcing, screening, and often the offer process for a defined scope or time period.
How is RPO usually priced?
End to end programs are typically priced as a percentage of the placed candidate's first year salary, while project based and on demand engagements are usually a flat monthly fee per recruiter.
Can you move from RPO to in-house recruiting later?
Yes, but you're rebuilding the pipeline, messaging, and candidate data from zero unless the contract specifically hands that over.
The build versus rent decision in this article isn't unique to recruiting. The same tradeoff shows up in quoting, lead follow-up, and weekly reporting: tools that either produce a process your team owns or an output you keep paying to rent. If you're weighing that same question for your sales or marketing operations, start with a Revenue Roadmap and get a fixed price on the version that stays yours.
