The most common misconception about retained search is that it's simply the expensive option for companies with bigger budgets. In practice, the decision has much less to do with budget and much more to do with three things: how senior or rare the role is, how much dedicated attention the search needs, and how much risk you're willing to carry if it takes longer than expected.
Contingency works well for roles that are well-defined, reasonably common in the market, and not desperately time-sensitive. You're not paying anything upfront, and because there's no exclusivity, you can run the search in parallel with your own sourcing efforts or another agency. The trade-off is that a contingency search competes for a recruiter's attention against every other contingency search on their desk, so if the role is unusual or hard to fill, it can sit without meaningful traction.
Retained search makes sense once a role is senior, hard-to-fill, or business-critical enough that “eventually” isn't good enough. Because it comes with a partial fee upfront and typically exclusivity, the search gets dedicated hours, not leftover attention, and you get regular pipeline visibility instead of radio silence until a CV shows up. It's the right model for a first country lead, a niche technical specialist, or any role where a bad hire, or a search that drags on for months, costs far more than the retainer itself.
A useful test we walk clients through: if this role sat open for three more months, what would that actually cost the business — in delayed roadmap, in team burnout covering the gap, in a competitor moving faster? If the honest answer is “a lot,” retained is almost always the better trade, even though it feels like the bigger number on day one. If the honest answer is “we'd manage fine,” contingency is the more sensible default. We'd rather have that conversation upfront than let a client default into the wrong model out of habit.