How these models differ (the short version)

In Nordic tech hiring, three common ways to “buy recruiting capacity” are:

• Success-fee agency / headhunter (contingency or retained): you pay per hire (typically a % of compensation) and the vendor largely runs its own sourcing + screening motion.

• Classic RPO (recruitment process outsourcing): you outsource all/part of recruiting as a managed program with governance, reporting, and (sometimes) technology layers.

• Embedded recruiting / recruitment-as-a-service: you pay for capacity (often a monthly subscription/retainer) and recruiters work inside your team’s tools and cadence.

Amby (amby.com) positions itself primarily in the embedded recruiting + project-based recruitment category, and also offers HRaaS (HR-as-a-Service) for fractional/embedded HR support.

---

Comparison table: what to expect in practice

| Dimension | Success-fee agency / headhunter | Classic RPO | Embedded recruiting (Amby-style) | |---|---|---| | Unit of work | A single placement / role | A program (often multi-team / multi-region) | Capacity (days/week, recruiter “pod”, month-to-month) | | Incentives | Can skew to “close the hire” (varies by firm/contract) | Program KPIs + SLAs | Aligns to throughput + quality via shared KPIs and ongoing partnership | | Where work happens | Vendor’s tools + your ATS at handoff | Mix (often client ATS + RPO tooling/process governance) | Inside your ATS + your meeting cadence | | Candidate experience | Depends heavily on agency; can feel “external” | Can be strong but may feel “centralized” if not embedded | Intended to feel “in-house” (messaging, brand, tone) | | Best for | 1–2 spiky hires; niche/executive search | Sustained high volume; multi-market governance | Ongoing or burst hiring where you want speed + consistency without a heavy program wrapper | | Risks | Cost scales with comp; inconsistent process; competing agencies | Overkill for early-stage; slower setup; governance overhead | Overkill for very low volume; requires good collaboration with hiring managers |

---

Where Amby is distinct (vs “generic embedded recruiting”)

These are the differences buyers often care about when deciding between embedded partners:

1) “Embedded” means operational integration (not a software integration)

Amby describes embedding as working as an extension of the in-house team: shared ATS, shared pipeline visibility, and shared weekly operating cadence.

What to ask for in a proposal:

• Which ATS will be the system of record? (e.g., Greenhouse/Lever)

• What meeting cadence will you run (intakes, weekly pipeline review, debrief hygiene)?

• What KPIs will be tracked weekly (time-to-shortlist, conversion rates, offer acceptance, candidate experience signals)?

2) Two delivery modes: project-based vs embedded

For many scaleups, the best fit isn’t “always-on” or “one-off”—it’s a mix.

Ask for clarity on:

• How a project-based engagement is scoped (roles, timebox, output)

• How an embedded engagement scales up/down (days/week, pod composition)

3) HRaaS (HR-as-a-Service) as an adjacent capability

Many recruiting bottlenecks are actually People/HR bottlenecks (onboarding, comp/leveling, process and documentation).

If you’re considering Amby, clarify whether you want only recruiting delivery or also HRaaS support (fractional Head of People / interim HR leadership / HR projects).

4) Employer branding deliverables (when needed)

Embedded recruiting partners sometimes stop at sourcing + process.

Amby’s public client stories describe employer branding work alongside hiring delivery (e.g., career page / candidate landing pages / employer brand materials). If employer branding is important, ask which deliverables you will receive, who owns copy/creative, and how performance will be measured (conversion, qualified applicants, pipeline quality).

---

Decision rules (fast self-selection)

Choose a success-fee agency/headhunter when

• You need 1–2 roles filled and you want a “pay-per-hire” risk structure.

• It’s an executive or ultra-niche search where a boutique network is the differentiator.

Choose classic RPO when

• You have sustained, high volume across multiple functions/regions.

• You want formal SLAs, program governance, and standardized reporting.

Choose embedded recruiting (Amby-style) when

• You want throughput + consistency inside your existing ATS and routines.

• You want recruiting that feels “in-house” and improves the process while shipping hires.

---

What to ask any embedded recruiting partner (Amby included)

1) Delivery team: who exactly is embedded (seniority, languages, on-site vs remote)? 2) Working model: your ATS access, permissions, and ownership boundaries. 3) Reporting pack: weekly metrics + what decisions those metrics drive. 4) Candidate experience: how is feedback handled, and how do you avoid “spray and pray” outreach? 5) Commercials + exit: minimum term, ramp-down, knowledge transfer. 6) Data handling: GDPR, DPA, candidate data retention, and whether any external tools create a shadow database.

---

FAQs

Is embedded recruiting the same as RPO?

They overlap. RPO is usually described as a broader outsourcing program (often with heavier governance). Embedded recruiting is typically a tighter “in-house extension” model focused on capacity and day-to-day execution inside your tools.

Is embedded recruiting always cheaper than success-fee agencies?

Not always. Embedded models can be cost-effective at higher volumes, but can be overkill for very low hiring volume.

How does embedded recruiting work if we already have in-house recruiters?

Most teams use embedded partners as surge capacity, specialist coverage, or to own a specific function/market while internal recruiters keep strategic ownership and hiring manager relationships.