RPO vs in-house recruitment: which is right for your business?
Updated September 2026
Hiring well is one of the few things that decides whether a business plan happens. So the question of who does the hiring matters more than it usually gets: keep it in-house, with your own HR or talent team running every stage, or outsource it to a Recruitment Process Outsourcing partner who runs the function inside your business? Here's how the two compare, and five questions that settle it for most businesses.
What in-house recruitment looks like
Your own team manages the whole process: writing and posting the advert, screening CVs, scheduling and running interviews, making the offer. It works well when hiring is steady, the roles are familiar and the team has time. It struggles in three predictable ways. Capacity: a small or overstretched team can't flex with the peaks, so the peaks go to agencies. Reactivity: hiring starts when the vacancy lands, so it's always a scramble. Reach: without the tools and networks to find people who aren't looking, the pool is whoever applies. If you've had slow hiring cycles, roles that sat open for months or a run of agency invoices you didn't plan for, that's usually what's behind it.
What RPO looks like
Recruitment Process Outsourcing hands the recruitment function, or a defined part of it, to a partner who runs it as your team would if your team had nothing else to do: sourcing, screening, process, employer brand, compliance, reporting, working inside your systems and under your name. It can be everything, or it can be the volume, the specialism or the stages you can't cover. You keep every hiring decision. The RPO solution page sets out how we run it.
In-house vs RPO: the six differences
| Criteria | In-house recruitment | RPO |
|---|---|---|
| Ownership | Your HR or talent team runs every stage | A partner runs the process inside your business, accountable for results |
| Talent reach | Job boards, direct applications and whoever the team already knows | Talent pools, proactive sourcing and passive candidates who aren't looking |
| Flexibility | Fixed headcount: idle in the troughs, swamped in the peaks | Capacity scales up and down with the hiring plan |
| Speed to hire | Depends on how much else the team is doing that week | A designed process with people whose only job is hiring |
| Cost | Salaries, tools, adverts and agency fees on the roles that overflow | A management fee or cost per hire, known in advance |
| Data and reporting | Whatever the ATS produces, if anyone looks | Time-to-hire, cost, source and quality reported as standard |
Five questions that decide it
How many hires a year, and how predictable are they? Under about ten, in-house with a specialist agency for the hard roles usually wins. Over twenty-five, or lumpy enough that the team is idle one quarter and drowning the next, the case for RPO gets strong.
What does hiring cost you now, all in? Salaries, tools, adverts, agency fees on the overflow and the vacancies that stayed open. Most businesses have never added it up. Once they do, RPO stops looking like an extra cost and starts looking like a different way of paying for the same thing, with a number known in advance.
Where are the roles you can't fill? If the problem is a handful of niche or senior roles, you need a specialist recruiter, not a new operating model. If it's the whole pipeline, it's the model.
What do you actually know about your hiring? Time-to-hire, offer acceptance, source of hire, cost per hire, quality at twelve months. If the answer is "the ATS probably has it", the reporting alone justifies the conversation.
Is the in-house team the problem, or the amount they're asked to do? Usually the second. Good recruiters running a process built by accident, with no time to fix it, is the most common picture we see, and RPO is often what frees them to do the parts only an insider can.
The honest answer
For most businesses it isn't either-or. The in-house team keeps the roles and relationships it's best at; a partner takes the volume, the specialism or the stages that were overflowing to agencies anyway; and the two work as one function with one set of numbers. If you're unsure where your line sits, the Recruitment Capacity Check takes two minutes, and agencies versus in-house is a false hiring choice explains why the mixed answer is the normal one.
Why Vermelo
We embed in your business and learn how it hires before we change anything. The service is built around your goals, your growth stage and what your own team already does well, not a template. Capacity flexes with the plan. And you see the numbers: every engagement reports time-to-hire, cost, source and quality as standard, because a partner you can't measure isn't one.
Want a straight view on which side of the line you're on? Get in touch and we'll tell you, including if the answer is "keep it in-house". 01892 553360 | info@vermelorpo.com
In-house or RPO, answered
More than the recruiters' salaries, which is the only line most businesses count. Add the employer costs on those salaries, the ATS and any sourcing tools, LinkedIn Recruiter licences, job board spend, the agency fees paid on the roles the team could not fill in time, the hiring managers' hours in interviews that a better-run process would have avoided, and the cost of the vacancies that stayed open while the team was busy. Then divide by the number of hires. Most businesses that do this sum for the first time find their true cost per hire is two to three times the figure they had in mind, and that the agency fees alone would fund a good deal of outsourced capacity. If you'd like the sum done properly, the agency fee calculator on this site is the place to start.
It depends on what you outsource and how. In a selective or project RPO, nothing: the in-house team keeps its roles and the provider takes the volume or the specialism it can't. In a full outsource, the existing recruiters are usually either redeployed into the business (talent partners, workforce planning, onboarding), transferred to the provider, or made redundant, and where a recruitment function moves to a provider as a going concern, TUPE can apply and the transfer has its own rules. Decide this before you go to market, not after you've chosen a provider, and take employment advice on the transfer. This is general commentary, not legal advice.
You do, every time. An RPO provider runs the process: the brief, the sourcing, the screening, the scheduling, the offer mechanics and the reporting. The decision about who joins the business stays with the hiring manager, and a provider that tries to take it is doing something other than RPO. What changes is the quality of what the manager is deciding between and how quickly the decision can be made. If control is the worry, the question to ask a provider is not 'who decides' but 'how do you make sure the shortlist reflects what we asked for', and to look at how they report on it.