AI in RPO Delivery: What Changes When You Are Embedded in the Client

An agency grows by placing more people at the same fee. An RPO usually cannot, because the contract fixes the price. Growth has to come from delivering more with the same team, which makes throughput a margin question rather than a productivity one. That is the structural reason automation matters more in RPO than in contingency, and it is also why RPO tooling requirements are genuinely different.

Last reviewed July 2026. Delivery observations from Sortinghat customer base, stated as directional.

Why the economics are different

In contingency work, more placements means more revenue. Effort and income move together, which means adding recruiters is a rational growth path even at flat productivity.

In RPO the fee is agreed in advance for a scope. Delivering the scope with eight recruiters instead of twelve is the entire margin story. That inverts how tooling should be evaluated: a platform that costs more per seat and lets you run the account with fewer seats is straightforwardly cheaper.

Most RPO providers still evaluate software the way an agency does, on licence cost per user, which is exactly the wrong lens for their own P&L.

Working inside the client's process

An agency runs its own process and presents the output. An RPO adopts the client's, which creates requirements no agency platform was designed for.

Per-account configuration. Each client has its own stages, scorecards and submission formats. A platform with one global workflow forces every account into the same shape and quietly loses you the account that does not fit.

Client-branded candidate experience. The candidate believes they are talking to the client, not to you, which affects every touchpoint including automated ones.

Their approval chain, not yours. Delivery speed depends on a decision process you do not control, which makes your own speed the only variable you can improve.

Separation, and why it is a contractual issue

Permissions in an agency are about commission. In RPO they are about contract compliance.

A recruiter working Client A must not see Client B's candidates, pipeline or notes. That is frequently written into the agreement and it is checked in audits. A permission model that only separates by desk rather than by account is insufficient, and discovering that during a client review is expensive.

The workable answer is configuration at organisation level, set by your own management team to reflect the contracts you have actually signed rather than a vendor's default.

Where automation genuinely moves the number

Sourcing and first-pass screening. A recruiter running manual screening manages around 40 calls a day and finds three or four worth submitting. Filtering first produces roughly 10 submission-ready profiles in hours. On an RPO account that is the difference between eight recruiters and twelve.

Reporting. SLA performance assembled weekly by a coordinator is a permanent cost. Generated from pipeline data it is free, and more accurate in front of the client.

Record keeping. Notes written automatically from calls and messages means an account survives a recruiter leaving, which matters more in RPO because the client notices immediately.

What automation does not fix in RPO

A badly scoped contract. If the fee was wrong at signature, throughput improvements only reduce the loss. Scope discipline is upstream of everything here.

A slow client. If the approval chain takes three weeks, submitting in four hours does not shorten time to hire. What it does is remove any argument that the delay is yours.

Stakeholder management. An RPO relationship involves more people with more opinions than an agency one, and none of that is automatable.

What this changes on a staffing desk

Market analysis is only useful if it changes something on Monday. Four practical consequences that follow from everything above.

Your prospect list is probably built from history

Most staffing firms sell to the accounts they already know, which means the client list reflects where demand was five years ago rather than where it is now. Rebuilding a prospect list against current hiring activity rather than past relationships is unglamorous and it is usually the highest-return week a founder can spend.

Speed matters more than it used to

In contingency and RPO, the firm that submits first usually gets paid. A recruiter working manually manages around 40 calls a day and finds three or four people worth submitting. Filtering before dialling changes that arithmetic: a pool search on a volume role surfaces around 1,200 relevant profiles, narrows to a ranked 300 contacted across call, WhatsApp and email in parallel, and produces roughly 10 submission-ready profiles in hours.

Your own database is the cheapest source you have

An audit of one firm's 3 million records found roughly 10 percent duplicates, 10 percent unusable and 80 percent real people whose records were simply out of date. Making that 80 percent findable took job portal spend from about $100 a role to $60. Most firms are paying to source strangers while sitting on people who already know them.

Definition beats effort

Most wasted submissions are a briefing failure that surfaced three weeks later, not a sourcing failure. Generating weighted evaluation criteria from the job description, and agreeing them with the client before the search starts, removes more waste than any increase in activity.

Frequently asked questions

The calculation worth doing on your largest account

Take your biggest RPO account and work out the fully loaded cost per role delivered. Then work out how many of those hours went to sourcing and first-pass screening rather than to judgement, client conversation or candidate management.

That percentage is your margin opportunity, and on most accounts it is considerably larger than anything available through renegotiation.