Understanding the Choice: RPO vs In-House Recruitment
When a company's hiring needs exceed what a handful of managers can handle informally, a decision point arrives: build an internal recruitment function, or outsource it. This decision has significant long-term implications for cost, quality, speed and institutional knowledge — and it is often made poorly, based on immediate pressure rather than strategic thinking.
Recruitment Process Outsourcing (RPO) is an arrangement where an external provider takes responsibility for some or all of the company's recruiting activities. The provider supplies recruiters, technology and processes — typically with a per-hire fee structure, though models vary. The appeal is immediate capability without fixed overhead.
An in-house approach means hiring your own recruitment team, investing in technology (typically an ATS), building your own processes, and accumulating institutional knowledge about what works in your specific context. The investment is higher upfront, but the compounding value over time is significant.
The reality that most discussions of this choice miss is that it is not binary. The most sophisticated talent acquisition strategies are hybrid: a core internal function with its own ATS, supported by selective RPO or agency partnerships for specific role types, geographies or volume peaks. Understanding when to use each element is the actual skill.
The Hidden Cost of Pure RPO
RPO providers typically own the candidate relationship, the candidate data, and often the recruitment CRM in which that data sits. When you transition away from an RPO provider — as most companies eventually do as they scale — you may lose access to years of candidate pipeline data, sourcing intelligence and institutional knowledge. Always ensure your contract specifies data portability and ownership before signing.
What RPO Actually Delivers
To evaluate RPO honestly, you need to understand what it genuinely provides and what it does not — because RPO providers, like all vendors, market their strengths and are quiet about their limitations.
Immediate capacity. The primary genuine advantage of RPO is speed-to-capacity. If you need to hire 50 people in the next six months and have no internal recruitment function, an RPO provider can begin operating within weeks. Building an equivalent internal function — hiring, onboarding and ramping recruiters, selecting and implementing an ATS, establishing processes — takes significantly longer.
Variable cost structure. RPO converts fixed recruitment costs (recruiter salaries, technology subscriptions) into variable costs (per-hire fees). For companies with highly uneven hiring volumes, or for companies uncertain about their growth trajectory, this can be financially attractive. You pay more per hire when you hire, and nothing when you don't.
Specialist market knowledge. A good RPO provider specialising in your sector will have built sourcing networks, candidate relationships and market intelligence that an internal team starting from scratch would take years to develop. This is a genuine advantage for specialised roles in competitive markets.
Process maturity. Established RPO providers bring documented, tested recruitment processes. For a company that has never built a structured recruitment process, this can reduce the time and error cost of figuring things out from scratch.
What RPO does not deliver: deep institutional knowledge of your company's culture and true differentiators, genuine candidate advocacy (RPO recruiters represent multiple clients simultaneously), data ownership and portability, or control over the candidate experience.
What an In-House ATS Actually Delivers
An in-house ATS-centred recruitment function, built and operated correctly, delivers different advantages — and its value compounds over time in ways that RPO does not.
Candidate data ownership. Every application, every candidate profile, every communication, every source attribution, and every hiring decision is your data, stored in your system, accessible to you permanently. Over time, this builds a talent pool of previous applicants who can be re-engaged for future roles, a database of employer branding touchpoints, and historical data that informs future sourcing decisions.
Process control and optimisation. When you own the process, you can measure it precisely, identify bottlenecks, and make targeted improvements. An ATS gives you real-time visibility into conversion rates, time-in-stage, source quality and hiring manager performance. This data drives continuous improvement in ways that are not possible when the process is managed externally.
Consistent candidate experience. Your career page, your application form, your automated communications, your interview process and your offer experience all reflect your brand and your values. Candidates who apply in-house are experiencing your company directly — not a recruiter's perception of it.
Cost efficiency at scale. Below approximately 20-30 hires per year, RPO can be cost-competitive with in-house recruitment. Above that threshold, the economics typically shift strongly in favour of internal capability. A recruiter who costs €60-80k per year can manage 50-80 hires annually — a cost-per-hire of €800-1,600 — compared to RPO or agency fees that typically run 15-25% of first-year salary for professional roles.
Treegarden as Your In-House Foundation
Treegarden is designed as the core infrastructure for in-house recruitment teams: Kanban pipeline management, AI Match Score, bulk CV upload (up to 50 files), automated interview scheduling, eJobs and BestJobs integrations, career page builder, and full GDPR compliance. Everything your team needs to run professional recruitment internally without enterprise-level pricing.
The Decision Framework: By Company Stage
The right balance between RPO and in-house recruitment changes as a company grows. Here is a framework for thinking about it at different stages.
Early stage (fewer than 20 employees, fewer than 10 hires per year). At this stage, formal recruitment infrastructure is rarely necessary. Founders and managers recruit directly, often through networks. An ATS at this stage is useful for organisation and compliance, but it does not need to be sophisticated. RPO is generally not cost-effective for individual roles at this volume — agency recruiters on a contingency basis are usually more flexible.
Growth stage (20-100 employees, 10-30 hires per year). This is the inflection point where many companies first consider RPO, because hiring pressure exceeds the capacity of manager-led recruitment but does not yet justify a dedicated internal team. RPO or a part-time embedded recruiter are both reasonable options, but this is also the moment to invest in an ATS — because the candidate data and process intelligence you build now will be enormously valuable in two years. Do not let an RPO provider lock your data in their system.
Scale-up stage (100-500 employees, 30-100 hires per year). At this stage, an internal recruitment function almost always makes economic and strategic sense. The cost-per-hire economics clearly favour internal capability, and the institutional knowledge accumulated by an internal team — about which roles are hardest to fill, which sourcing channels produce the best quality, which hiring managers are effective interviewers — is enormously valuable and impossible to build with external providers. RPO can still play a role for specific role types or geographies where internal capability is absent.
Enterprise stage (500+ employees, 100+ hires per year). At this scale, the recruitment function is a significant operation in its own right. Internal capability is the foundation, supplemented by selective agency and RPO partnerships for the highest-complexity or highest-volume situations. The ATS is a critical business system that integrates with HRIS, payroll and workforce planning tools.
The Hybrid Model in Practice
The most common effective model for mid-size companies is: internal recruiter(s) managing the ATS and handling standard roles, with RPO or agency partnerships for executive search, specialised technical roles, and sudden volume spikes. The key discipline is ensuring that all candidate data — including RPO-sourced candidates — is captured in your internal ATS, not siloed in the provider's system.
Data Ownership: The Critical Consideration
The question of data ownership deserves more prominence than it typically receives in RPO vs in-house discussions. It is, arguably, the most strategically significant factor in the long term.
Every year of recruitment generates valuable data: which sourcing channels produce the highest-quality candidates for which role types, which interview questions best predict performance, which job descriptions attract the right applicants, which candidate profiles fail probation and which succeed. This data, accumulated over years and analysed correctly, is a significant competitive advantage in talent acquisition.
Under an RPO model, this data typically belongs to the provider or is managed in their system. Even if you have contractual access, extracting and using it requires coordination with the provider and is often incomplete. When you eventually transition to an in-house model, you start from zero.
Under an in-house ATS model, all of this data is yours from day one. Your talent pool grows continuously. Your sourcing intelligence accumulates. Your quality-of-hire analytics inform future hiring decisions. This compounding advantage is invisible in a year-one cost comparison but becomes substantial over a three-to-five year horizon.
Making the Transition from RPO to In-House
Many companies eventually reach a point where they want to transition from RPO to in-house recruitment. This transition is often more complex than anticipated — and the complexity is almost always centred on data migration and process documentation.
Before transitioning, negotiate data export rights with your RPO provider. You are entitled to all candidate data that relates to your job posts and applications — but your ability to actually extract and use it depends on the provider's cooperation and the format they provide it in. Insist on structured data export (CSV or JSON) rather than PDF reports.
Implement your ATS before you end the RPO relationship, not after. Running a parallel period — where the ATS is live and capturing new candidates while the RPO provider manages existing pipelines — allows your team to build proficiency in the new system before it becomes mission-critical.
Document every process from the RPO engagement that you want to preserve: the screening criteria for each role type, the interview frameworks, the offer letter templates, the rejection communications. This institutional knowledge, accumulated by the provider, often walks out the door when the contract ends.
Treegarden for RPO-to-In-House Transitions
Treegarden's bulk CV upload (up to 50 files at once) and candidate import tools make it straightforward to migrate historical candidate data from an RPO provider into your own system. Combined with the career page builder and job board integrations, new applications start flowing into your ATS from day one of the transition.
Frequently Asked Questions
What is Recruitment Process Outsourcing (RPO)?
RPO is an arrangement where an external provider takes over responsibility for some or all of a company's recruitment functions. This can range from a single role type (project RPO) to the company's entire talent acquisition operation (end-to-end RPO). The RPO provider typically uses their own technology, processes and recruiters, though some operate within the client's existing ATS.
Can you use RPO and an in-house ATS simultaneously?
Yes, and this is increasingly common. A company might use an RPO provider for high-volume or specialist roles while managing other hiring in-house through their ATS. The critical requirement is that both channels feed into the same ATS so candidate data, source tracking and pipeline visibility are consolidated. Allowing an RPO provider to operate in a separate system creates data silos and reporting gaps.
How do you compare the cost of RPO vs an in-house ATS?
The cost comparison requires calculating total cost-per-hire for each model, including all direct and indirect costs. For RPO: provider fees (typically per-hire or percentage of salary), plus internal coordination time. For in-house: ATS subscription, recruiter salaries and benefits, job board costs, LinkedIn Recruiter licences, and overhead. The in-house model generally becomes more cost-effective above approximately 20-30 hires per year, depending on role seniority and market complexity.