Retained Search vs RPO in India 2026: Which Model Actually Fits Your Hire

TL;DR

Retained executive search and RPO (Recruitment Process Outsourcing) get pitched to Indian founders as if they were the same conversation with a different price tag. They are not. Retained search is a calibrated process to close one critical leader; RPO is a managed funnel to close many roles at lower seniority. Retained costs 28% to 33% of a single CXO's annual cash compensation; RPO is priced per requisition, per hire, or as a monthly managed fee that ranges from ₹6 lakh to ₹35 lakh a month depending on volume. The right answer is almost never one or the other; it is both, sequenced. CXO and other top-of-pyramid hires go retained. Engineering, product, and senior IC volume hiring goes RPO. The most expensive mistake is using one model for the wrong role. For the structural context on which leadership roles justify retained, our CHRO India 2026 guide is the closest companion to this piece.

What each model actually delivers

1. Retained search is built around one role at a time. A senior partner, a small team, four to six finalists, structured intake, written assessments, off-list references, and replacement guarantees. The unit of work is the single mandate.
2. RPO is built around a hiring plan, not a role. An embedded team of sourcers, recruiters, coordinators, and sometimes assessors who plug into your ATS, run your funnel, and deliver hires against a quarterly headcount plan. The unit of work is the requisition.
3. Retained measures success in shortlist quality. Did you see the right four to six humans, and did the right one say yes? Funnel size is irrelevant if those finalists are wrong.
4. RPO measures success in throughput and unit economics. Cost per hire, time to fill, offer acceptance rate, and 90 day retention across the cohort. Individual mandates are de-emphasised; the system is the product.
5. Retained is paid for process, even when it does not close. RPO is paid for outcomes, milestones, or seat-time. That single fact changes everything else about how the engagement runs.

Salary in India 2026 (with bands) and what each model costs against them

These ranges show the role band, the average comp at hire, and the typical engagement cost under each model. Cash compensation only; equity ignored for the cost math.

Series A to B startup CXO, ₹50 lakh to ₹1.5 crore comp. Retained: ₹14 lakh to ₹45 lakh per search. RPO: not used at this level. Pairs well with the VP Finance India 2026 hiring guide when the leadership team is being built role by role.

Series B to C senior leader (VP, Director, Head), ₹70 lakh to ₹2 crore comp. Retained: ₹21 lakh to ₹60 lakh per search if the role is critical. RPO: typically not used unless multiple similar roles are open in parallel.

Series C to pre-IPO product, engineering, and design IC and middle management, ₹40 lakh to ₹1.4 crore comp. RPO: ₹6 lakh to ₹20 lakh a month for an embedded team of three to six. Retained: only for CXO or named exceptional ICs.

Listed mid-cap leadership team, ₹2 crore to ₹5 crore plus LTI per CXO. Retained: ₹60 lakh to ₹1.65 crore per CXO search, often with portfolio discounts on three plus searches per year. RPO: typically used for high volume IC and middle management hiring, ₹15 lakh to ₹35 lakh a month.

GCC India scale hiring, 50 to 400 hires per year. RPO: ₹15 lakh to ₹35 lakh a month or seat-based pricing of ₹2.5 lakh to ₹4 lakh per recruiter per month. Retained: reserved for the site head and small leadership bench. For role definitions inside the GCC context, see the VP Engineering vs CTO India 2026 guide.

Calibration points to sanity check any quote:

• If a vendor proposes RPO pricing for a CXO role, they are repackaging contingency recruiting in expensive wrapping.
• If a vendor proposes retained pricing for a 30 engineer hiring plan, they are about to make a fortune from one client and deliver mediocre throughput.
• If RPO pricing is purely per-hire with no monthly floor, the vendor will deprioritise hard-to-fill roles toward the end of the quarter.

The six KPIs each model should be measured on

1. Retained: shortlist diversity and seniority. Four to six finalists, female representation on every senior search, candidates from outside your sector. Below this bar you are paying retainer rates for a list.
2. Retained: one year retention of placed candidates. The single most important metric for any executive search vendor. Use the same scrutiny our CFO India 2026 hiring guide recommends for the finance leadership team.
3. RPO: time to fill and offer accept rate by role family. Track separately for engineering, product, design, sales, and operations. A blended number hides systemic problems.
4. RPO: 90 day and one year retention of RPO-hired cohorts. Higher than your in-house cohort? The vendor is adding real value. Lower? You are buying speed at a cost the company will pay later.
5. RPO: ATS hygiene and data quality. Did your funnel become measurably more reliable in the first 90 days? If not, you have hired a body shop, not an RPO partner.
6. Both models: behaviour during a bad quarter. When the search runs long, when the hiring plan slips, when an executive hire does not work out, does the vendor show up the next time without renegotiating fees? This is the only reliable signal of partnership.

When to use which (and when to use both)

1. Use retained for any leadership hire above ₹1.5 crore total comp. The opportunity cost of a mis-hire is months of strategic drift. Retained is cheaper than the drift.
2. Use RPO when you have 25 plus hires per quarter in roles where market mapping is repeatable. Engineering, product, design, customer success, and operations. Volume justifies the embedded model.
3. Use both, sequenced, for a leadership team build plus headcount push. Retained for the CXO and direct reports; RPO for the team they will hire underneath. This combination is the most common Indian Series C playbook in 2026.
4. Use neither when you have fewer than five hires per quarter and an internal recruiter who is performing. Both retained and RPO have meaningful fixed costs. Below that volume, the math does not work.

Retained vs RPO vs contingency vs in-house

The cleanest mental model: retained is calibrated process, RPO is managed volume, contingency is speculative outcome, and in-house is fixed cost. Founders confuse retained with contingency because the headline percentages look similar; the real difference is that retained covers the work even when the role does not close. RPO and in-house overlap on the org chart because the RPO team often sits inside the company, but the contract structure and the accountability model are very different. For a parallel example in marketing, the CMO India 2026 hiring guide walks through a similar build-or-buy decision for senior marketers.

How to choose (and the four traps)

1. Trap one: blending both models into one contract. A combined retainer-plus-RPO contract sounds like efficiency on paper and becomes a finger-pointing exercise inside six months. Keep them as separate engagements with the same vendor at most, and ideally with two vendors.
2. Trap two: paying RPO fees per hire without a monthly floor. The vendor will optimise for easy roles. Always include a minimum monthly retainer that funds capacity, not just closures.
3. Trap three: signing RPO without ATS readiness. If your ATS is messy, the RPO team's first 60 days will be spent fixing data. You will pay for that work and blame them for the slow start. Clean your ATS before signing.
4. Trap four: not naming the senior partner on the retained side. A senior partner sells; an associate executes. For a CXO mandate, get a written commitment on partner days. The same back channel discipline our CHRO hiring guide recommends for references should apply to your vendor too.

The one thing every Indian CEO should take from this

Retained and RPO are not competing products. They are complementary tools, each with a specific job. Most leadership teams that get hiring right in 2026 use both, sequenced, with clean contracts and named accountability. If you want a second opinion on which model your current hiring plan should be using, we look at this stuff all day.

FAQs

Can the same firm provide both retained and RPO? Yes, but with separate contracts and ideally separate teams. Bundled contracts dilute accountability on both sides.

Is RPO cheaper per hire than retained? Always, by design. RPO is built for volume and unit economics; retained is built for one critical role.

What is the typical RPO contract length? 12 to 24 months in India. Anything shorter and the vendor cannot recover the setup cost; anything longer and the company loses the ability to renegotiate.

Does RPO cover sourcing or full cycle? Both options exist. Full cycle is the norm for engineering and product; sourcing-only is more common for GCCs that already have strong in-house closers.

How fast can RPO ramp? A three to six person team typically takes four to eight weeks to be fully effective inside your ATS and funnel. Below that, the vendor is overselling.

Should the RPO team report to my HR head or to the vendor? Dual reporting is the norm. The vendor manages performance and rotation; the HR head sets priorities and quality bar.

Can I switch from RPO back to in-house? Yes, but plan for a 90 to 120 day knowledge transfer. The RPO team owns muscle memory that does not document itself.

Is retained justified for a Series A founding team replacement? Almost always. The cost of a wrong founding hire is existential at this stage.

What is the most common reason an RPO engagement fails? No internal owner with authority. The vendor cannot make decisions about the funnel or process; the company never assigns the empowerment to fix it.

What is the most common reason a retained search fails? Misaligned mandate between the CEO and the board, surfaced only after the shortlist is ready. Always lock the mandate before kickoff.