Retained, contingent or RPO: choosing a search model for institutional hiring
For an investment-leadership seat at an asset owner, the search model you choose shapes the outcome before the first candidate is met. Retained search fits the roles where a mis-hire is materially damaging; contingency and RPO solve different problems. Match the model to the stakes and the volume — and don't run a CIO search like a mid-level one.
The three models, briefly
| Model | You pay for | Best when |
|---|---|---|
| Retained search | An upfront retainer + a dedicated, thorough process with direct outreach to passive candidates and regular reporting | C-suite, board and confidential roles where a bad hire is materially damaging — CIO, deputy CIO, investment leadership |
| Contingency | Nothing until a placement is made | Filling multiple or less-specialised roles quickly, where speed matters more than a bespoke process |
| RPO | Recruiting capacity, process, technology and analytics across part of the hiring function | Recurring, multi-role, multi-location hiring — standing up or scaling an office |
Which model for an asset owner
For the seats that define an investment office — CIO, deputy CIO, heads of function, senior private-markets and risk leadership — retained search is almost always right. These are confidential, high-stakes, passive-candidate markets, and the retainer is what buys the dedicated, discreet process and the market mapping such roles demand. Contingency suits occasional mid-level openings where the pool is deeper and speed is the priority. RPO earns its place when the fund is building out or scaling — recurring analyst and associate hiring across teams or locations, where the problem is a reliable hiring engine, not a single search. Many owners run a sensible hybrid: retained at the top, contingency for occasional mid-level roles, RPO for programmatic hiring.
What the retainer actually buys
Beyond effort, retained search changes the candidate pool. Because the firm is paid to run a complete process, it can reach passive candidates — people not on the market — who historically show lower turnover. For a long-horizon institution that needs a leader to stay and build, that retention difference is part of the value, not a nicety.
What this means for you
Decide by stakes and volume. For a CIO or investment-leadership hire, commission a retained search and hold the firm to a defined scorecard and reporting cadence. Use contingency only for lower-stakes, deeper-pool roles, and RPO when you're running a recurring hiring programme. Don't let a critical, confidential search default to a contingency scramble.- Sources:
- Digital Colliers — RPO vs retained vs contingency: which model fits
- WorkRocket — What recruiting fees buy: contingency vs retained vs RPO
- Hanover Search — Retained vs contingency (passive candidates, retention)