What is Recruitment Process Outsourcing (RPO) and why does your business need it?
Hiring shouldn't feel like guesswork, but for a lot of businesses it does: slow, expensive and hit-and-miss, with every hiring manager running their own version of the process. Recruitment Process Outsourcing exists to fix that. This is what it is, how it differs from using an agency, and how to tell whether you need it.
What is Recruitment Process Outsourcing?
RPO is when a business hands part or all of its recruitment to an external specialist who runs it as if they were your in-house team. That's the difference from outsourcing a task: an RPO provider takes on the function, from employer brand and sourcing through interviews, compliance and onboarding, and is measured on the results. They work inside your systems and under your brand, so candidates experience your company, not a supplier. The aim is hiring that's faster, more consistent and better quality than you could run yourself at the same cost, with the data to prove it.
The hiring problems RPO is built to solve
Most businesses that come to us have one or more of the same four. Skills shortages in the roles that matter most, where the same candidates are being approached by everyone. Recruitment cost that's grown by accident, usually through agency fees nobody has added up. Compliance that gets harder every year, from right-to-work checks to the off-payroll rules, and is done by whoever remembers. And time-to-hire that keeps roles open for weeks while the team covers the gap. None of those is solved by working harder at the current process; they're solved by having a process.
What RPO gives you
Lower hiring cost, because a managed process replaces fees on every placement and the technology and market knowledge come with the provider. Faster hiring, through engaged talent pools and a process designed rather than inherited. Better candidates, from structured screening by people who do this all day. Scale, whether you're hiring five roles or five hundred, without adding permanent headcount. And compliance built into the process and evidenced, rather than promised. If you want to see how the cost compares with agencies for your volume, is RPO cheaper than using agencies has the honest answer.
RPO vs recruitment agencies: what's the difference?
Both fill roles. Beyond that they're different animals: an agency is engaged for a role and paid when it's filled; an RPO provider runs the function and is paid for the service.
| Criteria | Recruitment agency | RPO provider |
|---|---|---|
| Approach | Transactional: engaged role by role | Strategic partnership across your hiring |
| Scope | Sourcing and screening | Full recruitment lifecycle, from brief to onboarding |
| Integration | Works outside your process | Works inside your team, systems and brand |
| Customisation | Standard service, same for every client | Built around your process, goals and growth stage |
| Pricing | Percentage of salary per placement | Management fee, fixed or per hire, agreed in advance |
| Best for | One-off, urgent or hard-to-find specialist roles | Ongoing, high-volume or multi-role hiring |
Agencies are the right answer for a one-off senior or specialist hire where you need someone who knows exactly where the candidates are. RPO is the right answer when the problem is the volume, the process or the cost of hiring as a whole. Plenty of businesses use both, and a good RPO provider will tell you when a specialist search is the better route for a particular role. Once you have a provider, how to review your RPO partner covers the measures to hold them to.
Do you need RPO?
Three tests. If you hire fewer than about ten people a year, probably not; a good process and a specialist agency for the hard roles will serve you better, and the options for smaller businesses are worth a look. If your hiring is predictable and ongoing across several roles, end-to-end RPO usually pays for itself. If it comes in bursts with an end date, a new site or a launch, Project RPO gives you the same model for a defined piece of work. And if you can't tell which you are, the fact that nobody in the business can say how many hires are planned for the next six months is itself the answer. For the fuller decision, in-house against RPO on six criteria with five questions to settle it, read RPO vs in-house recruitment: which is right for your business?
Why Vermelo
Plenty of providers promise results. Recruitment isn't one shape, so your provider shouldn't be either. What you get from us:
UK market knowledge, with particular depth in insurance, regulated industries, technology and legal, because that's where we've done most of our work
A talent strategy built around your goals, growth stage and what your own team can already do, not a template with your logo on it
A model that flexes up and down, so a hiring surge or a project doesn't mean overcommitting
A named team who know your brand, your roles and your culture, and stay consistent from first brief to first day
In-house compliance specialists who understand your obligations, from IR35 to pre-employment checks, and build the evidence into the process
Our clients see an average time-to-hire/time-to-offer of 16 days
If you're comparing providers, how to find a reputable RPO provider sets out the questions to ask, including the ones we'd rather you asked us.
Start hiring smarter
If hiring is slower, more expensive or more chaotic than it should be, get in touch.
RPO, answered
Four, broadly. End-to-end RPO takes on the whole recruitment function for the long term. Project RPO covers a defined piece of hiring with a start and an end: a new site, a product launch, a hundred customer-service hires by March. Selective or hybrid RPO takes specific stages or business units (sourcing for engineering, say, or everything below manager level) while you keep the rest. And on-demand or embedded recruiters sit underneath all of them as the lightest version: capacity that joins your team when you need it. The right one depends on how much of your hiring is predictable, and for how long.
Usually one of three ways, or a blend. A management fee: a fixed monthly charge for the team and service, which suits steady volume. A cost per hire: a set amount for each completed hire, which suits variable volume and keeps the provider's interest aligned with yours. Or a hybrid: a lower fixed fee plus a per-hire element. Some contracts add a transition or set-up fee and some price project work as a single sum. Whatever the model, insist on seeing the total for your expected volume, because a low headline rate on the wrong model costs more than a higher rate on the right one.
Scope, so both sides know which roles, business units and stages are in and which are out. Service levels and the KPIs behind them: time-to-hire, offer acceptance, quality of hire, candidate experience, with what happens if they are missed. The pricing model and what is excluded from it. Who owns the data, the candidate pipeline and the process improvements when the contract ends, and how the transition back to you, or to another provider, works. Notice periods and the ability to flex the team up and down. And the compliance responsibilities on each side, from right-to-work checks to data protection. A contract that is vague on exit is a contract you will regret in year two.