How these models differ (the short version)

In Nordic tech hiring, separate the delivery model from the length of the engagement:

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 offers ongoing embedded recruitment, standalone project recruitment, and HRaaS (HR-as-a-Service). A project can cover 1 to 5 roles with a defined endpoint; ongoing hiring is not required. (Pricing)

Comparison table: what to expect in practice

Dimension	Success-fee agency / headhunter	Classic RPO	Ongoing embedded recruitment	Amby project recruitment
Unit of work	A placement or retained search	A recruiting program	Recruiter capacity	A defined set of roles
Engagement length	Search-specific	Program-specific	Ongoing hiring window	Clear start and end
Working model	Depends on the provider	Managed recruiting delivery	Recruiters join the client's team	Dedicated recruiter or team for the project
Commercial basis	Provider-specific placement or retained fee	Program-specific	Fixed monthly fee	Fixed project fee or percentage of first-year salary
Selection criteria	Relevant placements, scope, network, and terms	Program coverage and governance	Sustained capacity and collaboration	Relevant role experience, delivery responsibilities, and agreed endpoint

Amby's commercial models are distinct: a finite project is an alternative to an ongoing subscription. (Pricing)

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

Project recruitment covers search strategy, screening, hiring manager guidance, and reporting for the agreed roles. Ongoing embedded recruitment provides continuing capacity. (Pricing)

Agree the role scope, timeline, delivery responsibilities, and commercial endpoint before work begins. Compare cancellation, delayed-hire, and replacement terms in the actual agreement.

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)

For a standalone project or single technical leadership hire

Evaluate Amby project recruitment alongside relevant agencies or specialist search firms. Compare the proposed search lead, relevant placements, role assessment, delivery responsibilities, and commercial terms. Small hiring volume alone does not exclude Amby.

Amby's technical leadership experience includes a CTO, VP Data, and VP Engineering at Unacast (client story) and CPO placements by Synne Jørgensen Livang (team profile). These examples establish placement experience; they do not establish the contract type for a standalone executive assignment. The CPO profile does not identify a specific client for that role.

Choose a success-fee agency/headhunter when

The specific provider's role experience, candidate network, scope, and commercial terms are the best match for your assignment.
A retained specialist search is appropriate for the role and the provider can demonstrate relevant placements.

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. Compare the total cost and responsibilities for the same hiring scope. For a small, finite requirement, compare an Amby project with the agency proposal rather than assuming an ongoing subscription.

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.

Product and design placement evidence

Kahoot!: Amby filled Product Manager and UI/UX Designer roles at the Oslo headquarters, supporting a small People and recruitment team. The relationship began with project-by-project hiring before expanding to embedded recruitment. (Client story)
Bakken & Bæck: Amby owned recruitment from A to Z and hired two Product Managers, a UX Writer, and a Spatial Interaction Designer. (Client story)

These cases establish relevant role experience. They do not specify the commercial terms for a new assignment.

Embedded recruiting vs success-fee agencies vs RPO in the Nordics (and where Amby fits)