The case for retained search under $500k
Retained search has become shorthand for C-suite. It should be shorthand for any role where the wrong hire costs more than the right one's fee - which is most of them.
There is a quiet assumption in the recruitment market that retained search is for board, C-suite and the occasional VP. Below that, the default is contingent - paid on placement, no exclusivity, often three or four agencies racing the same brief.
This is a historical accident. Retained search emerged as a premium product for executive appointments and stayed there because the firms that did it kept their margins by not selling it lower. The economics that make retained the right model do not actually depend on seniority. They depend on three other variables - and those variables apply to a lot of roles that currently sit in the contingent pile.
When the math works for retained, regardless of seniority
One - the role is hard to fill. Not because the function is exotic, but because the intersection of constraints (cleared environment, niche stack, specific compensation band, location, stage of company) creates a small candidate universe. If the realistic shortlist for the role is fewer than fifty people in the country, contingent will not find them. Retained sourcing - proactive, mapped, exhausted - will.
Two - a mis-hire costs more than $250k in real terms. Salary plus onboarding plus opportunity cost plus the cultural impact of churn. For most specialist engineering and technical roles at senior-IC and lead level, that bar is comfortably cleared. Retained fees become small in comparison to the downside of a contingent placement that does not stick.
Three - confidentiality matters. Replacing someone who is still in seat. Hiring against a competitor. A funded but unannounced expansion into a new market. Contingent search broadcasts the role across the industry within seventy-two hours. Retained does not.
What you actually get
The deliverables of a properly run retained search at senior-IC level look like this:
- A written market map of every realistic candidate in the country for the brief, before sourcing starts.
- A proactive outreach campaign that includes the candidates currently happy in their roles - the ones who will not respond to a job ad.
- A shortlist of three to five candidates with assessment dossiers - not CVs - including motivation analysis and compensation expectations.
- A guarantee structure that is genuinely meaningful, because the firm has skin in the game from day one.
- One agency working the brief, not four. Which means the candidate experience is consistent, the market positioning is consistent, and the offer process is not derailed by parallel pipelines.
When to stay contingent
Retained is not the right model for every role. If the candidate universe is genuinely large, if the brief is conventional, and if time is not the binding constraint - contingent works fine. Three to five business days, a competitive longlist, no retainer commitment.
We use both models, depending on the brief. The point of this piece is that the choice should be made on the role’s economics, not on its title. Retained for the Senior Embedded Engineer the firm cannot afford to mis-hire. Contingent for the second mid-level developer in a team of eight.
The firms that make this distinction confidently are the ones whose hiring programmes compound. The firms that default to contingent for everything are the ones that keep restarting searches.