内容概览
Permanent recruitment, contract staffing and recruitment process outsourcing are three different answers to three different problems: a role you need filled, capacity you need covered, and a volume of hiring you need run. Choosing between them by cost per hire alone is the common mistake, because the models differ most in who carries the management load and who carries the risk when demand changes.
What is the difference between the three models?
Permanent recruitment places a person on your payroll, usually for a fee tied to the hire. Contract staffing places a person who works for you but is employed and paid through the staffing provider, for a defined period. RPO puts a recruitment team inside your organisation, running some or all of your hiring under your brand, paid for the capability rather than per placement.
The practical difference is where the employment relationship sits, and therefore who handles the statutory obligations — payroll, leave, mandatory contributions, termination process — for each market the person works in.
When does permanent recruitment make sense?
When the work is ongoing, the knowledge compounds, and you want the person to still be there in three years. That sounds obvious, and the test that is actually useful is the inverse: if you would be comfortable with a different person doing this work in nine months, you are describing contract capacity, not a permanent role.
Permanent is also the right model when the hire is a decision rather than a resource — a first country manager, a head of function, a role where the wrong person is expensive in ways no notice period fixes.
When does contract staffing make sense?
When the work has an end, a peak, or an unknown. Project delivery, seasonal volume, a parental leave cover, a system migration, a market you are testing before you commit headcount.
It is also the honest answer when budget approval is real but headcount approval is not. That situation is common enough that it deserves saying: using contract staffing to work around a headcount freeze is legitimate, and it should be a deliberate decision with an end date, not a permanent arrangement nobody has re-examined.
- Cost comparison should be like for like: the contractor rate includes employer contributions, leave accrual and administration that a permanent salary line does not show.
- Contract staff in several Asia-Pacific markets accrue rights with length of service. Rolling a twelve-month contract three times is a different legal position from a single twelve-month engagement.
- Decide upfront how conversion to permanent works, and what it costs, before anyone is in the seat.
When is RPO the right model?
When the constraint is not any single hire but the throughput. If you are hiring continuously across the same job families, if your internal team spends more time coordinating than assessing, or if your hiring quality varies by which manager is running it, that is a process problem and a process is what RPO buys you.
RPO is not a cheaper way to do ten hires. It is a way to do a hundred consistently, with reporting that shows where the pipeline actually breaks.
Can you combine models?
Yes, and most organisations at scale do. A common shape: RPO for high-volume operational roles, a contract workforce for project peaks, permanent search reserved for leadership and specialist hires, and executive search for the two or three appointments a year that change the direction of a function.
What matters is that the boundary between them is explicit. When nobody has decided which model owns which role, every requisition becomes a negotiation, and the roles that fit neither model are the ones that sit unfilled longest.
What does each model cost in management time?
This is the part left out of most comparisons, and it is often the deciding factor.
- **Permanent search**: heaviest at the front — briefing, interviewing, deciding — and effectively zero after the guarantee period.
- **Contract staffing**: light at the front, ongoing afterwards. Someone has to manage the person, approve timesheets and decide about extensions.
- **RPO**: heaviest at setup — process design, systems, authority to act — and lowest per hire once it runs.
An honest way to choose: if your team has decision-making capacity but no sourcing capacity, use permanent search. If it has neither, look at RPO. If it has both but no headcount, look at contract.
Where should you start?
Start with the work, not the vacancy. Describe what needs to be done for the next eighteen months, then ask which of these three shapes fits it. We can walk through that with you against the markets you are hiring in — the answer differs between Singapore and Jakarta for reasons that have nothing to do with your business.