When you need both RPO and MSP, and why some companies will

It is well known that a Recruitment Process Outsourcing manages the sourcing, screening and hiring of permanent employees while a Managed Service Provider programmes manage the sourcing, engagement and compliance of contingent, temporary and contract labour. Some organisations need both regardless of size, because RPO and MSP solve two different problems that never stop interacting: how you hire people, and how you govern everyone you have not hired. Scale determines how expensive it gets to ignore that interaction. It does not determine whether the interaction exists.

That distinction matters, because most vendor content collapses the two triggers into one. The honest version has two separate answers. Some companies need both because they run enough contingent volume that a Vendor Management System pays for itself in spend visibility alone. Staffing Industry Analysts’ Contingent Workforce Buyers Survey found that large organisations, those with 1,000 or more employees, reported an average contingent workforce share of 22 per cent back in 2016, and SIA’s own projections put that figure closer to 29 per cent by 2030. At that share of headcount, running contingent labour without a managed programme is not a minor gap. It is the second largest line item on the workforce budget with no governance attached.

 Other companies need both for a reason that has nothing to do with volume. If a business converts contractors to permanent staff at any meaningful rate, or scales project teams up and down against fixed-term client work, permanent and contingent hiring are not two separate activities. They are two stages of the same pipeline. A business with a hundred contingent workers and a high conversion rate needs the same data continuity between RPO and MSP as a business with ten thousand. Size changes the cost of getting this wrong. It does not change whether the two functions are structurally connected.

What an RPO actually does

 RPO solves a permanent hiring problem: volume, quality, time to fill, employer brand consistency, and the cost of running recruitment as a scattered activity across dozens of hiring managers with their own private processes. A provider typically owns sourcing strategy, candidate screening, interview coordination and offer management, and in stronger partnerships contributes to workforce planning and employer brand execution directly. The logic is efficiency. Centralise a repeatable process, apply technology most internal talent acquisition teams cannot justify building themselves, and cut cost per hire and time to fill while quality of hire holds or improves.

 RPO assumes the organisation already knows, in broad terms, what permanent roles it needs and roughly when.

What a MSP actually does

 MSP solves a different problem: visibility, compliance and cost control across a contingent workforce that becomes a governance liability the moment nobody is watching it. An MSP manages supplier relationships with staffing agencies, runs the requisition and approval workflow through a Vendor Management System, enforces rate cards and worker classification rules, and reports on spend, tenure and supplier performance across the programme. This is a risk function as much as a talent function. John Nurthen, who leads SIA’s global research, has pointed out that claims of contingent labour reaching half the workforce are considerably overstated once informal and gig-adjacent categories are stripped out; agency work penetration globally sat close to 1.8 per cent in 2023. Real contingent volume in most large employers is smaller than the headlines suggest, but where it exists, misclassification exposure is real and does not wait for a convenient audit cycle.

 MSP assumes the organisation already has, or is building towards, contingent labour volume large enough to justify managed oversight.

Where they diverge:

 These sit in different budgets, answer to different stakeholders, and are usually procured through unconnected processes with no shared data. That gap is where the real cost hides.

Two routes to needing both an MSP and an RPO

 A ten thousand employee business with fifteen per cent contingent headcount will eventually feel three specific failures if RPO and MSP run as unrelated programmes, and none of them stem from poor execution by either provider.

The first is budget arbitrage without workforce logic. A hiring manager facing a permanent headcount freeze routes the requirement through the contingent channel instead, not because that is the right workforce solution, but because that budget line happens to be open. Contingent spend inflates for reasons that have nothing to do with strategy, and neither provider can see why the mix is shifting, because each only holds half the picture.

The second is conversion friction. A business with any technology, project or seasonal workforce component will convert contractors to permanent staff, and needs a clean handoff between a contingent worker’s tenure history and the permanent hiring process. Run RPO and MSP on separate systems and that handoff becomes manual and informal. The organisation loses the cost efficiency of converting a known quantity, and the compliance record of how that conversion was evaluated.

The third is the workforce planning blind spot, and it matters most to a CFO or CHRO trying to answer one question: what does this piece of work cost to deliver, and what is the fastest, lowest risk way to resource it. Nobody can answer that with permanent and contingent labour tracked in separate systems using different definitions of cost, tenure and utilisation. The organisation makes resourcing decisions on half the relevant data, every time it makes one.

Below a business with meaningful contingent volume or conversion activity, this blind spot costs little because the mix rarely shifts. Above it, the blind spot is not a one-off inefficiency. It is a permanent tax on decision quality.

What happens when you only run one

Run MSP without RPO and the organisation usually has strong control over contingent spend but no equivalent discipline on permanent hiring, so the two categories drift to different standards and the arbitrage problem above goes unchecked.

Run RPO without MSP, more common and more dangerous. A well run RPO programme can make permanent hiring look efficient and well governed while contract and temporary spend grows through informal agency relationships with no rate discipline and no consolidated classification view. This is exactly the setup that produces expensive legal exposure when a labour authority or an internal audit eventually asks how many contractors have effectively functioned as employees for two years without formal review.

How to know you are ready for both an MSP and a RPO

Base the decision on evidence, not aspiration. Look for contingent labour representing a share of total workforce spend that finance actively tracks rather than estimates. Look for real movement between employment types: conversion, project-based scaling, seasonal flexing, the kind of movement that creates friction when permanent and contingent sit in unrelated systems. And look for visible tension between HR and Procurement over who owns workforce budget, usually the clearest sign that the current operating model has run out of road.

An organisation that combines RPO and MSP without meeting this bar tends to pay for governance overhead on a contingent workforce too small to justify it, or bolt RPO onto a provider whose technology and expertise were built for contingent management rather than permanent recruitment quality.

The governance model that makes it work

Where combining the two earns its cost, the shared element is rarely a single contract signed for its own sake. It is a shared data layer and one point of accountability for workforce planning, sitting above both programmes, able to see requisitions, cost and tenure across both employment types and recommend whether a piece of work should be built, borrowed or bought. Whether that sits with one provider running both services or two providers integrated through shared reporting is a secondary question. The primary question is whether anyone in the organisation currently holds the authority and the data to make that recommendation at all. In most large organisations that have not yet combined the two functions, they do not.

—

Anne Rutledge, Executive Director of Talent Solutions, notes that the organisations asking the sharpest questions about RPO and MSP integration are rarely the ones with a workforce problem. They are the ones whose finance function has started asking why total labour cost and total labour risk cannot be reported on together, which is usually the point where the conversation stops being about recruitment and starts being about capital allocation.