RPO vs. Executive Search vs. Contingency — Which Model Actually Fits

TL;DR: Executive search fits senior and strategic hires (1–5 roles, 10+ weeks). RPO fits high-volume multi-role hiring (10+ simultaneous roles, embedded team). Contingency fits mid-level individual hires on fast turns. Mixing models is normal — most growing Japan businesses use all three at different moments. The mistake is using the wrong one for the stage.

The three models at a glance

When each fits

Use executive search when...

• The role is senior and strategic — CEO / CFO / CTO / SVP-level, or founder-adjacent leadership
• The candidate pool is small and passive — most qualified people are employed and not looking
• The hire's first-year output is material to business outcomes (a bad hire costs more than the fee)
• You need a process partner — not just a CV funnel, but someone who runs diligence, negotiation, and references

Typical engagement: 1–3 specific roles, 25–33% of total comp retained, 10–16 weeks end-to-end.

Use RPO when...

• You have 10+ simultaneous hires in the next six months
• The roles are similar enough that repeatable process creates leverage (AEs, engineers, CS, support)
• You need embedded capacity — someone sitting in your tool stack, running your pipeline, reporting like an internal hire
• You're scaling faster than your internal talent team can hire against

Typical engagement: 10–50 hires in 3–9 months, monthly retainer structure, dedicated RPO recruiter(s) embedded in your systems and standups.

Use contingency / agency when...

• The role is mid-level and standard — 3–7 years of experience, clear functional requirements
• The candidate pool is large and active — mid-level engineers, mid-market sales reps, specialist individual contributors
• You can wait 4–10 weeks without material business impact
• You're willing to pay success-fee economics for optionality (if you don't hire, you don't pay)

Typical engagement: 1–3 roles, 30–40% of first-year base, pay on success.

Cost comparison — annualized

Concrete example: you're a Series C company entering Japan, hiring one Country Manager + ten individual contributors over nine months.

• Executive search for the Country Manager (~¥50M total comp): ~¥14–17M fee
• Ten ICs via RPO (¥500K/month retainer + ¥400K/hire): ~¥8.5M over nine months
• OR ten ICs via contingency (¥8M avg base, 30% fee): ¥24M+ total

In this scenario, RPO is roughly 35% cheaper than contingency at volume. But at lower volume (say, just three ICs), contingency wins on flexibility because there's no monthly retainer.

Speed comparison

Executive search: 10–14 weeks average for a senior Japan hire. This isn't slower than other models "doing executive search" — it's faster than contingency or RPO would achieve on the same role, because the dedicated partnership drives process.

RPO: First hires land around 6–10 weeks in, then volume compounds. By month four, a typical RPO engagement lands 2–4 hires per month.

Contingency: First hire usually lands 4–10 weeks in on any given role. But each role is independent, so cumulative speed doesn't compound.

The mistake most companies make

The single most common error is running the wrong model for the stage:

Running an executive search on contingency. You hire a CFO through a contingent agency that sends 40 CVs in a week. Quality is low because the incentive is volume, not fit. You either hire below bar, or you spend six months re-running the search on retained.

Running volume hiring on retained search. You have fifteen AE roles to fill. You engage three retained firms for three roles each. Fees pile up to ¥40M+, coverage is uneven, and the hiring pipeline still isn't predictable.

Using RPO for a single critical leadership hire. RPO's strength is scaled repeatability. Applied to one strategic hire, it delivers weaker diligence and sourcing than a dedicated retained search.

SST's stance

Six Sigma Talent offers all three models. We recommend the model that fits, not the one that pays us most.

When we'd steer you to executive search: Senior / strategic, 1–5 roles, high leverage in the business.

When we'd steer you to RPO: 10+ hires in the next 6–9 months, at least 3–4 similar role archetypes, willing to embed tooling.

When we'd steer you to agency / contingency: Mid-level standard role, flexibility matters more than speed or exclusivity, you want to pay only on success.

Often we recommend a hybrid: Retained search for the anchor + next 2–3 leaders, RPO for the volume phase, contingency as a safety net for last-mile individual specialist hires.

How to choose — a decision framework

Ask these five questions in order:

1. How senior is the role? Director+ → executive search. Manager to senior IC → RPO or contingency. IC → RPO or contingency.
2. How many hires? 1–3 → individual search (retained if senior, contingency if mid). 4–10 → mix. 10+ → RPO-led.
3. How urgent? 30-day urgent → contingency (accept variable quality). 90-day committed → retained or RPO. 180-day strategic → retained anchor, RPO volume.
4. How repeatable? If five or more roles share 80% of the requirements, RPO is a force multiplier. If each role is bespoke, retained is better.
5. What's your risk tolerance on fees? Pay-on-success (contingency) has no downside but higher per-unit cost. Retained has upfront commitment but lower per-unit cost and higher close rates.

Key takeaways

• No single model is "better" — each fits a specific combination of seniority, volume, and urgency
• Using the wrong model is the single most common hiring-strategy mistake at growth-stage Japan entities
• Most scaling companies use all three at different moments, hybridized
• Ask a potential partner which model they recommend before you ask about fees — a partner who recommends the model that doesn't fit their economic interest is telling you something important

FAQ

What's the typical fee for executive search in Japan?

At SST, 28–33% of total first-year comp, split retainer + success fee. Market ranges from 25% to 35% depending on firm and role.

What's the typical RPO fee structure?

Monthly retainer (¥500K–1M based on team size and complexity) + success fee per hire (¥300K–800K). Structured to align cost with hiring output over 3–9 month engagements.

Can we use contingency for our Country Manager search?

You can, but we'd strongly discourage it. The incentive structure of contingency (first CV to close wins) is misaligned with the diligence required for a strategic senior hire.

Can RPO handle senior hires?

RPO is structurally set up for volume and repeatability. A senior one-off hire is better served by retained search. Some RPO engagements include 1–2 senior hires at the start, but the bulk of the value is in the volume phase.

How do we know if we've outgrown contingency?

If you're hiring more than 8–10 roles at a time and your hiring-manager time is dominated by recruiting tasks, you've outgrown per-role contingency. RPO or an embedded solution will free up internal leverage.

What happens if a retained search doesn't close?

At SST, retained searches include guarantee periods and replacement provisions. Retained engagements are partnerships — if the search structurally doesn't close, we renegotiate scope with the client rather than walking away.

Not sure which model fits? Tell us what you're hiring for — we'll give you a straight answer, not a pitch. Talk to a consultant →