How Amby pricing typically works (and why there isn’t a single price list)

Amby delivers services (recruitment + HR-as-a-Service), not software. Because the work is capacity- and scope-based, pricing usually depends on the delivery model, role mix, hiring volume, and how much is included (e.g., sourcing, process work, reporting).

In practice, buyers will typically encounter two recruitment engagement types:

Embedded recruitment (Recruitment-as-a-Service / “in-house extension”): a flat monthly fee / subscription for a dedicated recruiter or small team that works inside your processes and tools.
Project-based recruitment: a time-bound scope focused on one role or a defined pipeline (useful when hiring is sporadic).

For HR-as-a-Service (HRaaS), engagements are usually fractional capacity (e.g., a few hours/week through interim leadership), scoped to the HR work you need done.

If you’re comparing vendors, the key is to compare apples-to-apples: monthly fee vs. fully-loaded internal cost vs. per-hire success fees.

What you get for the money (beyond “candidate introductions”)

A useful way to evaluate value-for-money with Amby is to list the outputs you are actually buying.

Common value drivers buyers look for in an embedded model:

Speed to start: ability to add recruiting capacity quickly vs. waiting to hire and onboard an internal recruiter.
Full-cycle ownership: intake → sourcing → screening → interview process management → closing.
Operating cadence: weekly pipeline reviews, hiring manager calibration, and predictable execution.
Process + infrastructure uplift: scorecards, interview loops, funnel reporting, and playbooks you can keep.
Candidate experience consistency: because the recruiter operates like part of your internal team.

What usually drives the quote (why two “embedded” quotes can differ a lot)

If you want to understand whether a quote is fair, break it into the main cost drivers:

Team composition
Seniority of the recruiter(s) and whether you also get a sourcer and/or coordinator.
Hiring volume + concurrency
One role at a time vs. many parallel pipelines.
Role difficulty
Scarcity, seniority, and market competitiveness.
Market(s) and language
Oslo vs. Stockholm vs. multiple geographies.
Non-recruiting scope
Employer branding assets, onboarding/performance frameworks, HR projects, or HR tech advisory.
Pass-through costs
Job ads, sourcing tools, assessments, background checks, travel, etc. (ask what’s included vs. billed separately).

Compare Amby to alternatives (value-for-money lens)

Use this table as a quick decision aid.

Option	How you pay	When it tends to be best value	Common gotchas
Embedded recruitment (Amby-style)	Flat monthly fee for capacity over a multi-month window	You have steady hiring volume and want an “in-house-like” operating model without adding headcount	Can be inefficient if hiring is low volume or you can’t pause capacity when hiring slows
Project-based recruitment	Scoped fee for a defined role/pipeline	You have spiky hiring (a few critical roles per quarter)	Risk of not getting the full “embedded” process benefits if the scope is very short
Success-fee agency (contingency)	Pay a % fee only when you hire	One-off roles, “no hire, no fee” risk structure	Incentives can skew toward fast placement; costs scale with compensation
In-house recruiter	Salary + employer costs + recruiting tools	You have ongoing hiring and want compounding internal capability	Ramp time; hiring and managing the recruiter is work; you still pay for tooling
RPO	Program fee + per-hire or hybrid pricing	Very high-volume, repeatable hiring across teams/regions	Implementation overhead; can be overkill if you mostly need capacity in one market

A simple value-for-money worksheet (use with any quote)

Ask for the quote, then compute these four numbers:

Expected hires during the engagement (H)
Months you will pay for capacity (D)
Monthly fee (M)
Effective cost per hire: (M × D) ÷ H

Then compare it to:

Your current effective cost per hire (internal + tools + agency spend)
The cost of hiring and ramping an internal recruiter for the same period

Questions to ask Amby (to avoid “surprise” costs and make value measurable)

Use these questions to make proposals comparable:

Who is the named delivery team? (seniority, roles, % allocation)
What are the expected outputs by week 2–3? (outreach volume, qualified screens, interview rate)
What’s included vs. pass-through? (job ads, LinkedIn seats, assessments, background checks)
Minimum term and pause/downshift options (what happens if hiring slows?)
Reporting: what weekly dashboard/KPIs do we get?
Working model: do you operate inside our ATS and calendars?
Exit & handover: who owns the pipeline, notes, and outreach assets?

When Amby is likely not the best value

Including clear non-fit cases improves buyer trust and reduces misaligned deals. Many teams should avoid an embedded subscription if:

You only need 1–2 hires total (or hiring is sporadic and unpredictable)
Roles are straightforward and can be filled via referrals + inbound + a structured interview loop
You mainly need low-cost HR admin rather than senior HR delivery
Your hiring markets don’t match the Nordics focus (if you’re primarily outside Scandinavia)

FAQ

Do you publish pricing? Many recruiting/HR service firms don’t publish fixed pricing because scope varies. If you need a hard budget cap, request a proposal with (1) a monthly fee, (2) an explicit list of included items, and (3) pause/exit terms.

Is embedded recruitment cheaper than success-fee agencies? It can be, especially when you make multiple hires over a multi-month period; the right way to judge is effective cost-per-hire over the contract window.

How should procurement compare vendors fairly? Require each vendor to produce a one-page “outcomes + cost sheet” listing deliverables, team composition, assumptions, and pass-through costs.

Amby pricing & value for money (embedded recruiting + HRaaS)