| Best for | You want people who work only on your business, sit in your tools, and take direction from your managers. | You want a partner accountable for turnaround, quality, and improvement against agreed measures, without directing daily work yourself. | You have high-volume, standardized work and want it run as a contracted process, often priced per transaction or volume. | You have repetitive, rules-based steps a tool can handle reliably, with people still reviewing exceptions. |
|---|
| What you manage | Priorities, workflows, quality standards, and day-to-day work direction. | The outcomes, service levels, and approvals you want to hold the provider to. | The contracted process, volumes, and service levels. Less day-to-day direction of individual people. | The process definition, data and system access, exception rules, and who signs off on changes. |
|---|
| What the provider manages | Recruiting, local employment, benefits, workplace, HR, and local leadership and escalation. | Staffing, the operating process, quality controls, reporting, and continuous improvement for the agreed scope. | The end-to-end process as specified in the contract, including the people who do the work. Delivery models vary by provider. | The build, integration, and — if agreed — ongoing operation of the tool, with human review designed in. |
|---|
| Typical pricing basis | Per person. A fully loaded team cost should include employment, workplace, and local support. Confirm what's included when you compare quotes. | Per outcome or per process — tied to volume, service levels, or an agreed scope, not just headcount. | Per transaction or per volume. | Per tool and build — implementation, then license or usage. Ongoing support is usually separate. |
|---|
| Time to start | Most roles can be placed in 3–5 weeks, depending on how general or specialized the skills are. Access, workplace setup, and how documented the work is also affect the start. Full volume comes after a planned ramp, not on the placement date. | After the process, service levels, and handoff plan are agreed. Documented processes start faster than undocumented ones. Staffing for most roles still follows the same 3–5 week placement window. | After the process is specified and volume and service levels are contracted. Timing varies by provider and how defined the work is. | After the process is documented and systems and data are accessible. If the work isn't already well defined, plan for that first. This is a build, not a hire, so the timeline is set during scoping. |
|---|
| Main risks | You still need management time and clear procedures. A messy process stays messy after it moves. | You have less direct control of daily work. Scope and measures need to be clear up front. | Work can become a black box. Shared teams and rigid scripts can struggle with exceptions or changing volumes. Some delivery models place people individually, working from home in different locations, with little connection to a team. | Automating a messy process usually automates the mess. Unclear exception handling and data issues are the usual failure points. |
|---|