RPO Delivery Speed: How Humanity Adapted to a Shifting Candidate Market
Recruitment process outsourcing lives or dies on turnaround.
When the candidate market moves, an RPO team has to find, tag and re-surface the right people faster than the client's hiring demand changes. The source case study's authors note that agency recruiters and general managers often describe how hard it is to find software that fits recruitment rather than generic sales work, and they cite a 2019 figure of roughly half a trillion U.S. dollars in global recruitment and staffing revenue after five years of growth. Humanity, a South Africa-based employee-experience and RPO company, ran into that same search. This page walks through how Humanity approached the problem, what it looked for in an ATS+CRM, and which capability checks a reader evaluating similar software should run.
The delivery problem an RPO team faces
Recruitment process outsourcing is a model in which a client hands some or all of its hiring to a third-party vendor under a contractual relationship. The global recruitment market keeps shifting, and hybrid models have multiplied, so an RPO team has to stay flexible about how it delivers.
Humanity had already run project-based RPO work, particularly high-volume recruiting in the banking space. Engagements have ranged from three months to six months and up to two years. Across that history, the team has worked with all three common RPO models:
- End-to-end RPO: the provider owns the hiring function for a single market, country, region or globally, and may focus on one business division or role, or cover all hiring across the organization.
- Project RPO: the client brings in a team of expert recruiters for a defined need within a set time frame, such as clearing a recruitment backlog, launching a new Customer Success team, meeting an unexpected hiring demand, or building a talent pool and sourcing candidates.
- On-demand recruiter: similar to project RPO, but one or two outsourced recruiters join the client's talent acquisition team for a specific project or period.
Each model puts different pressure on the system of record. End-to-end work needs a single pipeline that can carry every role and client. Project work needs fast setup and clean handoffs at the end. On-demand work needs the outsourced recruiter to work inside someone else's process without friction. When the candidate market shifts mid-engagement, all three depend on the same thing: the ability to find the right people in the database quickly and keep them tagged accurately enough to re-surface later.
Why Humanity selected an ATS+CRM
Humanity's general manager, Annie Osterloh, has been described in the original account as the person who set out the company's requirements and explained why it settled on an ATS+CRM built for recruiting. Humanity's own positioning centres on a positive employee experience, and its work covers talent acquisition, employee engagement, development programmes and culture transformation across South Africa. That context matters when judging software: an RPO team is judged on the experience it gives both clients and candidates, not only on how many records it can hold. The original account also records how much research went into the CRM decision. Plenty of tools on the market are designed for sales pipelines rather than recruiting workflows, and the brief was for something straightforward to operate, not over-engineered, and light enough that a recruiter is not fighting the system all day. The reasons given for the choice were a user-friendly interface, a free Chrome extension, a CRM capable of giving clients and candidates a distinctive experience, a resume parser, a system that is not bulky, strong customer support, a mobile recruiting app, and email integrations with sample templates and related features. Read as an evaluation checklist rather than a verdict, that list is a reasonable starting point: interface clarity, browser-side sourcing, parsing quality, mobile access, support responsiveness and email tooling are all things a buyer can test directly in a trial.
The result
The original account reports that adopting the ATS+CRM improved Humanity's speed of delivery, with the search function and the ability to code candidates named as the capabilities that helped the team keep pace with a continually changing candidate market. The company has also described itself as working towards becoming a leading RPO provider in South Africa. Those are the original publisher's characterisations of one customer's experience, and a reader should treat them as a starting hypothesis rather than a guarantee of what any other team will see. The underlying lesson is more durable than the claim. Delivery speed in an RPO setting is rarely about a single feature; it comes from finding candidates quickly and classifying them well enough to find them again. Search without consistent coding produces a fast first pass and a slow second one, because the shortlist has to be rebuilt by hand. Coding without strong search buries good records behind weak queries. A buyer can test both in a trial: run the same multi-criteria query against a seeded database, then check whether tags survive imports and record updates.
Capability checks for an RPO software evaluation
If you are evaluating an ATS+CRM for an RPO model, the Humanity account suggests a short set of checks. Each one maps to a pressure point described above.
- Search quality: can a recruiter find a candidate by skill, location, availability and history in a single query, and does the result set stay usable as the database grows?
- Coding discipline: does the system make it easy to tag candidates consistently, and does it preserve those tags when records are updated or imported?
- Setup speed for project work: how quickly can a new client, role or pipeline be stood up, and how clean is the handoff when the project ends?
- Fit for recruiters, not sales teams: does the interface assume recruiting workflows, or does it require workarounds borrowed from a sales CRM?
- Bulk and mobile access: can recruiters work from a phone, and does the system stay responsive with a large candidate pool?
- Resume handling: does parsing produce structured fields a recruiter can actually filter on?
- Support responsiveness: who answers when a delivery deadline is at risk?
A worked example helps make the search-and-code pairing concrete. Suppose a banking client needs a batch of shortlisted candidates within a week. A recruiter searches the database for prior banking experience and recent availability, codes the shortlist with the client and role, and then re-runs the search as new applications arrive. If the coding is inconsistent, the second search returns a muddled list and the recruiter rebuilds it by hand. If the search is weak, the coding effort is wasted because the right records never surface. The two capabilities only pay off together.
| RPO model | Typical scope | System pressure point |
|---|---|---|
| End-to-end RPO | Single market, country, region or global; one division or role, or all hiring | One pipeline that carries every role and client without losing structure |
| Project RPO | Defined need within a set time frame: backlog, new team launch, unexpected demand, talent pooling | Fast setup and clean handoff at project end |
| On-demand recruiter | One or two outsourced recruiters joining the client's talent acquisition team | Working inside someone else's process without friction |
Model descriptions reflect the source's own definitions; scope varies by client engagement.
Frequently asked questions
What is recruitment process outsourcing?
It is a model in which clients and companies outsource their hiring needs to a third-party vendor, such as a recruitment firm or an RPO firm, under a contractual relationship.
Which RPO models does Humanity work with?
Humanity has worked with all three common models: end-to-end RPO, project RPO and on-demand recruiter support. It has also run project-based RPO work, particularly high-volume recruiting in banking, with engagements ranging from three months to two years.
What did Humanity look for in an ATS+CRM?
The company pointed to a user-friendly interface, a free Chrome extension, a CRM that could give clients and candidates a distinctive experience, a resume parser, a system that is not bulky, strong customer support, a mobile recruiting app, and email integrations with sample templates.
What result did Humanity report?
Humanity reported an improvement in its speed of delivery. The search function and the ability to code candidates were the capabilities credited with helping the team keep pace with a continually changing candidate market.