Embedded Recruiter vs Staffing Agency vs RPO: Which Hiring Model Fits

An embedded recruiter works inside your team as temporary headcount, billed monthly. A staffing agency works outside it and is paid a percentage only when someone is hired. RPO outsources the whole hiring function under a longer contract.

Hiring volume is the deciding factor. Agencies are cheapest when you hire rarely. Embedded and RPO get cheaper per hire the more you hire.

Below is how each model actually works, and the arithmetic that tells you which one fits what you are really doing this year.

	Embedded recruiter	Staffing agency (contingency)	RPO
How you pay	Monthly fee for dedicated capacity	Placement fee per hire, commonly 15-30% of first-year salary	Fixed monthly or per-hire under contract
You pay if nobody is hired	Yes	No	Yes
Where the recruiter sits	Inside your team, your tools, your meetings	Outside, working several clients at once	Outside, running the function for you
Best at	Sustained hiring across several roles	One-off or hard-to-fill roles	High volume across regions or departments
Commitment	Often month to month, 3-6 month pilots common	None	Longest, frequently annual
Breaks down when	Hiring stops and you are still paying	You need ten hires and fees stack up	The volume never arrives to justify the contract

An embedded recruiter is a recruiter you rent rather than employ. They work in your systems, sit in your hiring meetings, and work only your roles for the length of the engagement. The output resembles an in-house recruiter. The commercial arrangement resembles a contractor.

The distinction that matters is this: you are buying capacity, not a transaction. You are paying for recruiting hours pointed at whatever needs filling this quarter, rather than a bounty on one specific head.

A contingency agency is paid on success. No hire, no fee. That is genuinely attractive when you have one role open and no internal recruiting function, because your downside is zero.

The tradeoff is alignment. An agency recruiter works several clients simultaneously and is rewarded for closing a placement, not for improving your hiring process. They do not learn your product in depth, they are not in your calibration debates, and the relationship usually ends when the offer is signed.

For a single hard-to-fill role, that is a perfectly good trade. For sustained hiring, it is an expensive one.

Recruitment process outsourcing hands over the hiring function itself, covering sourcing, screening, coordination and sometimes onboarding, under a defined contract. It is built for volume and for organisations that want the process run externally rather than supported.

RPO is usually the wrong shape for a company making its first handful of hires, because the contract structure assumes a pipeline that keeps flowing.

At contingency rates of roughly 15-30% of first-year salary, one $150,000 hire costs somewhere between $22,500 and $45,000. One hire, one fee, and no cost at all if nobody starts. For a single role, that is the cheapest option available.

Run the same maths at six hires and it inverts. Six placements at 20% of $150,000 is $180,000 in fees. A dedicated embedded recruiter working those same six roles over the same months costs a fraction of it, because you are paying for time rather than per head.

The rough rule:

• Under about three hires a year, contingency usually wins
• Above about five or six sustained hires, embedded almost always does
• In between, it depends on how hard the roles are and whether you need the process fixed or just the seat filled

The most expensive mistake is committing to a fixed-cost model before the volume exists to justify it. The second most expensive is paying contingency fees six times in one year because nobody did this arithmetic first.

Hiring models fail most often because they are matched to the company a founder wants to be running rather than the one they are actually running.

Early, first key hires, no HR function. One or two hires, fragile systems, no interview infrastructure. Contingency is usually right, or a single embedded recruiter if the roles are genuinely hard and you want the process built properly the first time.

Scaling, consistent revenue, several roles open at once. This is where embedded earns its keep. Multiple open roles, no internal recruiting team, and a real weekly cost to every empty seat.

Established, high volume, existing People team. RPO, or embedded capacity supplementing the internal team rather than replacing it.

1. Count the roles you will genuinely open in the next six months. Not aspirationally, the number you would defend to your board.
2. Multiply by 20% of expected salary. That is your contingency cost.
3. Compare it against a monthly embedded fee across the same period.
4. Ask whether you need the process fixed or just the role filled. If your interviews are inconsistent and offers keep getting declined, a per-placement agency will not solve that. It is a process problem.
5. Pilot before committing. Three months of an embedded engagement tells you more than any contract negotiation will.

The Chum Effect runs the embedded model as Recruitment Squads: a recruiter, or a small team, working inside your company for the length of the engagement rather than working your roles from the outside.

We also do straightforward agency placement when that is genuinely the better fit, which for one or two roles it usually is. The volume arithmetic above is the same one we will walk through with you, and it frequently points away from the more expensive engagement.

The part we do differently is evaluation. Every candidate is interviewed live by a person, and those interviews are recorded, so you review the actual reasoning rather than a written summary of it. We also match the approach to your company's stage, because the hiring process that works for a fifteen-person company actively fails at a hundred and fifty.

Tell us how many roles you are opening and we will tell you which model costs you less.