RPO is the wrong model for almost all scale-ups
The short answer
The economics of Recruitment Process Outsourcing break below 500 hires per year. Here is what to consider instead for your Series A-D tech company.
This week
Every leadership team wants a scalable hiring function. The mistake is assuming this means adopting enterprise-grade infrastructure. Many talent leaders, under pressure to build for the future, look to Recruitment Process Outsourcing, or RPO, as the answer. But the model was never designed for the speed, specialism, or volatility of a technology scale-up. This week, we look at the data on why RPO breaks for businesses hiring fewer than 500 people a year, and what the right alternative looks like.
The benchmark
The cost-per-hire for an embedded talent partner is up to 59% lower than for comparable RPO or agency models. This applies specifically to technology scale-ups hiring between 5 and 150 specialist roles per year. The saving comes from the commercial model. With an embedded subscription, you pay a flat monthly fee for a senior headhunting pod that works inside your business. You are paying for dedicated, expert capacity. RPO, by contrast, was designed for the Fortune 500. Its pricing has to cover significant overheads: vast delivery teams, management layers, and heavy implementation costs. For a scale-up, this means paying for infrastructure you do not use. The economics only begin to work at a volume of 500 or more hires per year, where those fixed costs can be spread across many repeatable roles. Below that threshold, the per-hire cost remains stubbornly high. Source: Saiyō, Embedded TA vs RPO: https://saiyo.io/insights/when-embedded-talent-acquisition-beats-rpo-for-technology-scale-ups
What we're seeing
The primary mismatch we see is not just cost, but capability. RPO delivery teams are typically junior-heavy and optimised for high-volume, pipeline-driven roles like customer support or entry-level sales. This model fails when faced with the roles that define a scale-up's trajectory: senior engineers, specialist GTM leaders, and niche product managers. These are not roles you fill from inbound applications. They require proactive headhunting, deep market knowledge, and the credibility to engage passive candidates. The teams we see succeeding here use senior headhunters, not junior sourcers. Furthermore, the operating model of RPO creates friction. An 8 to 12 week implementation is too slow for a business that needs to land a VP of Sales this quarter. A 2 to 3 year contract is too rigid for a hiring plan that can be rewritten by a single board meeting. The entire structure is built for a stability that technology scale-ups simply do not have. Source: Saiyō, RPO vs RaaS: https://saiyo.io/insights/rpo-vs-raas-which-hiring-model-fits-a-technology-scale-up
Why it matters now
In the current funding climate, capital efficiency is a board-level conversation. Committing to a multi-year, high-cost hiring model designed for a different kind of company is an unforced error. It introduces significant fixed costs and operational rigidity at a time when flexibility is a competitive advantage. Your hiring plan is not a static document. It is a response to market conditions, product velocity, and competitive threats. Your hiring infrastructure must be able to adapt with it. Tying the organisation to a long-term RPO contract removes your ability to scale hiring capacity up or down as needs change. Choosing a more flexible, embedded model is not just a cost-saving exercise. It is a strategic decision to align your talent acquisition function with the financial and operational realities of scaling a technology business today.
The play this week
Run a quick diagnostic on your current or proposed hiring model. Answer three questions with your finance and leadership teams. First, what is your genuine hiring forecast for the next 12 months, and is it firmly above or below the 500-hire threshold where RPO becomes viable? Second, what is the mix of roles? Are they predominantly senior, specialist positions that require proactive headhunting, or repeatable, high-volume roles suited to a pipeline model? Third, what are the switching costs and contract terms? Can you scale your hiring capacity up or down in-quarter without financial penalty or renegotiating a master services agreement? The answers will give you a clear, data-led view on whether your current model is a strategic enabler or a structural risk.
From Saiyō
The hidden cost of a mis-hire is usually 3–5× what your finance team has on the spreadsheet. Run the calculator in 2 minutes. See your real cost-per-hire: https://saiyo.io/pricing
The Saiyō Briefing
Liked this? Get the next one in your inbox.
One short email every Thursday with hiring benchmarks, patterns and frameworks for technology leaders. Unsubscribe anytime.