Most employers default to per-role recruitment: define a vacancy, engage a recruiter, pay a fee when the role is filled. That model works well for occasional, unpredictable hiring needs. It becomes expensive and inefficient when hiring is sustained, repeatable, or high-volume.
Recruitment process outsourcing, or RPO, is the alternative. Instead of paying per placement, the employer engages a recruitment partner on a retainer to provide dedicated sourcing and delivery capacity against an agreed scope of roles. Per-hire rates are lower. The process is more consistent. And the relationship between the employer and recruiter is structured for a long-term outcome rather than a transactional one.
When per-role recruitment stops working
Per-role recruitment is the right model when hiring is occasional and the roles are diverse. It is the wrong model when:
- You are hiring three or more roles of a similar type in a given year. At that volume, a per-role contingent fee is a significant cost that a retainer arrangement could reduce materially.
- Your hiring needs are ongoing rather than event-driven. A business that expects to hire ten to twenty people over the next twelve months benefits more from a dedicated partner with accumulated knowledge of the brief than from running ten individual searches.
- Your roles are similar enough that a recurring process pays dividends. A recruiter who has sourced and screened for the same role type multiple times builds pattern recognition that an occasional recruiter cannot match.
- Your time-to-fill is a problem. Per-role recruitment starts from scratch each time. An RPO arrangement with a partner who has active pipelines for your common role types fills roles faster.
How RPO works in the India market
RPO in India is a well-established model. Large multinationals with Indian operations have used it for years to manage volume hiring for technology, finance, operations, and business process functions. The model translates well to smaller international employers who want India-based delivery capacity without the overhead of managing a recruitment team directly.
The structure varies. At its simplest, an RPO retainer buys a defined number of hours or a defined delivery scope per month. The partner maintains active pipelines for the employer's common role types, sources proactively, and delivers shortlists against incoming briefs on a compressed timeline.
For international employers, the version that works best is typically a structured retained arrangement: a monthly fee that covers a defined number of roles per month, with a reduced per-hire fee against the contingent equivalent. The recruiter has predictable revenue. The employer has predictable cost and faster delivery.
The cost case
The economics of RPO vs per-role contingent recruitment are straightforward.
A contingent placement at 15 percent of a 30L INR (approximately AUD 56K) annual package costs approximately 4.5L INR per hire. Across ten hires in a year, that is 45L INR in recruitment fees.
An RPO retainer structured at a monthly fee plus a reduced per-hire rate for the same ten hires might cost 30 to 35L INR in total, with faster time-to-fill and a consistent process across all ten roles.
The saving is real. So is the service improvement, because the recruiter under an RPO model is optimised for your specific needs, not for closing individual placements across a diverse client portfolio.
What the brief looks like for an RPO engagement
Unlike a per-role brief that describes a single vacancy, an RPO brief describes the employer's hiring programme. It covers:
The role types the employer hires repeatedly. Not every role needs to be in scope. The value is in standardising the delivery for the roles that are most common.
The volume and cadence of expected hiring. A rough forecast is sufficient: we expect to hire two to three finance managers and four to five technology professionals over the next twelve months.
The current process and its pain points. Time-to-fill, quality of shortlists, consistency of process, cost per hire. The RPO partner designs around these pain points specifically.
The integration with the employer's ATS or hiring workflow. A good RPO partner works inside your process, not parallel to it.
When RPO is not the right model
- Hiring is genuinely unpredictable and infrequent. If you hire one or two people a year, a retainer is not cost-efficient relative to per-role contingent.
- The roles are senior and diverse. RPO works for mid-level roles with recurring profiles. C-suite and leadership mandates are better suited to retained executive search.
- The employer does not have the management bandwidth to engage properly with a retained partner. RPO requires a working relationship, not just a transaction.
What to look for in an India RPO partner
Active pipelines vs reactive sourcing
A good RPO partner maintains live candidate pipelines for your common role types, not just a database they search when a brief arrives. Ask how they maintain pipeline between active briefs.
Quality control at the shortlist level
The volume nature of RPO creates a risk of shortcut screening. A partner that maintains written summaries and human review regardless of volume is rare and valuable.
Transparency on process and metrics
Time-to-shortlist, offer acceptance rate, 90-day retention rate. A credible RPO partner tracks these and shares them.
Flexibility on scope
The best RPO arrangements allow the scope to flex with the employer's actual hiring needs, rather than locking both sides into a rigid commitment that does not reflect how hiring actually works.
Getting started
The right starting point for an RPO conversation is a review of the past twelve months of hiring: how many roles, of what type, at what cost, and with what outcome. That review usually reveals whether an RPO model would have been more efficient, and what the scope of a future arrangement should look like.
We are happy to have that conversation as part of the intake process. If RPO is not the right model for your situation, we will say so.