Compare
Embedded vs contingency vs retained search
Three ways to pay for recruiting, each creating a different incentive and built for a different problem. The comparison below includes where our own model is the wrong choice.
The difference
Contingency recruiting pays only after a hire and rewards speed of submittal; retained search pays for committed research depth on one scarce seat; embedded recruiting gives you a dedicated recruiter working inside your team across a role set. The choice depends on how many hires you need and whether the market has already been mapped.
The rule
One replaceable hire in a market with supply: contingency. One scarce or senior hire where failure is expensive: retained. Three or more hires, or any hire tied to an energization date: embedded. Roles not yet defined well enough to count: run talent intelligence before you buy any of the three.
Weighing specific kinds of provider instead, such as a large staffing firm, an RPO, your own in-house team or job boards? See data center recruiting alternatives compared.
Comparison
Side by side
Ten dimensions, including where each model breaks down.
| Dimension | Contingency | Retained | Embedded |
|---|---|---|---|
| Engagement shape | Paid only if a hire is made. | Committed research on one senior seat, invoiced in stages. | Dedicated recruiting capacity for a defined role set. |
| Purchase | Access to whoever the agency already has, fast. | A committed search on one role, with research depth. | A recruiter working inside your hiring team across a role set. |
| Best fit | One replaceable role, deep local supply, no urgency. | A single scarce or senior seat where failure is expensive. | Multiple roles, a site build, or sustained hiring over months. |
| Cost at volume | Scales one hire at a time, so the budget resets after each close. | Also scales per role, which suits selective leadership searches. | More efficient across a role set because the research compounds. |
| Incentive | Submit fast and wide; whoever is placeable first, wins. | Complete the search as specified. | Fix the hiring process, because the recruiter stays through the result. |
| Market coverage | Whatever the agency's existing network happens to cover. | A mapped pool for that one role. | A mapped pool for the whole role set, maintained over time. |
| Research ownership | The agency. It leaves when the search ends. | Usually the agency, sometimes shared. | You. Maps, benchmarks and pipelines transfer to your team. |
| Exclusivity pressure | Multiple agencies on the same role, contacting the same people. | Exclusive by design. | Exclusive by design, with one accountable person. |
| Candidate experience | Variable; candidates often hear from three agencies about your role. | Controlled. | Controlled and consistent, under your brand. |
| Limits | Scarce roles with no ready supply, and anything requiring market mapping. | Volume hiring, and situations where the role definition is still moving. | Single one-off hires, where a flat monthly fee is the wrong shape. |
Economics
Cost crossover
The comparison that decides the budget.
One hire
Contingency can fit a single replaceable role with real local supply and low schedule pressure.
A role set
The models converge as the map, calibration and outreach can be reused across multiple related seats.
Team build
Embedded is usually the cleaner fit because each seat depends on the same market map and reporting cadence.
Run your own numbers rather than taking ours. The cost of vacancy calculator prices the delay alongside the search cost. The delay is usually the larger figure.
FAQ
Questions
- What is the difference between embedded recruiting and contingency recruiting?
- Contingency recruiting pays an agency only when a hire is made, so the agency is incentivized to submit quickly from candidates it already knows. Embedded recruiting puts a dedicated recruiter inside your hiring team across a role set, so the incentive is to build a durable pipeline and improve the hiring process rather than to close one placement.
- Which model is cheaper?
- For one hire, contingency usually is, because you pay nothing if nothing happens. As the role set grows, embedded often becomes more efficient because the same map, calibration and reporting compound across seats. The crossover point depends on your salary levels and the scope you would otherwise buy.
- Is contingency recruiting ever the right choice?
- Yes. For a single, replaceable role in a market with genuine local supply and no schedule pressure, contingency is efficient and low risk. It is the wrong instrument for scarce disciplines like commissioning, or for a site build with a dozen sequenced hires.
- How is embedded recruiting different from a contract recruiter?
- A contract recruiter is usually a pair of hands executing a process you already own. Embedded recruiting as we run it includes the market mapping, compensation benchmarking and process design as well as the execution, and the research is handed to you rather than retained.
- What about retained search?
- Retained search is the right shape for one scarce or senior seat where a failed hire is expensive and you need committed research depth on that specific role. It sits between the two on cost and above contingency on rigor. It is not built for volume.
- Can we start contingency and switch?
- Often the sequence runs the other way in practice: a contingency search stalls, the schedule pressure becomes real, and the engagement converts to embedded. Deciding earlier costs less.
- How do we decide right now?
- Count the hires you need in the next hiring phase. One, use contingency or retained depending on scarcity. A role set, or any hire tied to an energization date, points toward embedded. If the roles are not yet defined well enough to count, run talent intelligence first.
Model fit
Tell us the role count, the market and the dates. If contingency is the right answer for your situation, we will say so.