The question almost always arrives in the same shape: is it cheaper to outsource this or keep it in-house? And it almost always gets answered with two numbers that are not comparable. On one side, the monthly salary of the people doing the work today. On the other, the rate a provider quoted. The subtraction produces a result, the result goes to a committee, and the decision gets made on a badly framed comparison.
The problem is not arithmetic. It is scope: a salary is one part of what it costs to have someone doing the work, and a provider's rate does not always cover everything that happens in-house today. Before comparing, both figures have to be built on the same basis.
The base mistake: comparing a salary to a rate
A salary is a payroll line. A BPO rate is the price of a service that includes staff, supervision, replacement, infrastructure, administration and margin. Comparing them head-on means comparing an input to a finished product.
An honest comparison means lifting the internal cost to the same level: what it actually costs to get an hour of work done, not what one person is paid. That exercise usually surprises people, and not because of the provider's margin.
What sits inside the cost of your own person
The list varies by country and by company, but the blocks repeat:
- Pay and associated charges. Beyond the salary, everything the applicable labour law requires to be accrued and paid on top of it. It should be calculated by whoever handles accounting under current rules; none of this is legal, employment or tax advice.
- Supervision and support functions. The team lead, whoever does quality control, whoever builds the roster, whoever runs payroll, whoever handles IT support, whoever recruits. Those hours exist even when nobody charges them to the process.
- The workstation. Space, furniture, equipment, connectivity, or the equivalent if the setup is remote.
- Licences and tools. Every additional user on the service platform, the telephony, the CRM.
- Recruiting and replacement. Posting, screening, checks, onboarding. It repeats every time someone leaves.
- Training and ramp. The time between someone joining and producing at full pace is a cost, and it is paid again with every replacement. How long it actually runs is covered in agent training and ramp-up.
The block most often underestimated is attrition. An operation where people leave frequently pays for recruiting, training and low productivity permanently, not occasionally. The real causes are in attrition in BPO, and they apply just the same to an in-house team.
The unit of comparison is the productive hour
Nobody buys headcount: they buy the ability to get work handled. A person on the payroll does not give all their hours to the process. Between the contract and the output sit holidays, sick leave, training, meetings, breaks and offline time. That deduction is shrinkage, explained in shrinkage and adherence.
If the internal cost is divided by contracted hours while the provider's rate is expressed in hours actually covered, the comparison is skewed before it starts. Both sides have to be brought to the same unit, and that unit has to be named: productive hour, resolved case, or seat covered across a defined window.
What the provider's rate does not always include
The same distortion happens in reverse. The price per hour or per seat is not the full cost of the service. There is usually setup and transition, licences passed through, reporting outside the standard package, and extra capacity for peaks. Each item has its own calculation rule, and if it is not written down it shows up later. What to look at before signing is in how to read a BPO quote in Colombia, and how it translates month to month is in BPO invoicing.
The pricing model matters too, because it decides who carries volume variation. A per-seat rate and a per-transaction rate do not compare the same way against a fixed internal cost; the difference is laid out in BPO pricing models.
The costs that stay on your side
Outsourcing does not remove the work of managing. There is still a contract owner, still an operations meeting, still the tools that belong to the client, still your own quality review, and still the hours spent answering questions during the first months. That cost is real and it belongs to the outsourced scenario, not to the in-house one. The way to size it is to look at the calendar proposed by contract governance and count the hours it consumes.
If the outsourced scenario is presented with zero management hours on the client side, the number has been built wrong.
Once versus every month
It pays to separate what gets paid once from what gets paid forever. Transition brings process documentation, initial training, access setup and, often, an overlap period where both operations run at the same time. That is a real cost and it does not belong to a single month: it is amortised over whatever horizon makes sense, usually the expected life of the contract.
The opposite mistake exists too: loading the whole transition onto year one, concluding it is not worth it, when the decision is being made for three.
How to build the comparison
- Define the exact scope. Which tasks, in which hours, at what volume. Without this, every quote answers a different question.
- Measure what happens today. Volume, handle time, hours covered. If the data does not exist, that is the first finding.
- Add up the full internal cost over twelve months, using the blocks above and the attrition you actually have, not the one you want.
- Convert both sides to the same unit and write the assumptions down.
- Run two volume scenarios, one low and one high. An in-house team is a fixed cost facing variable demand; that is usually where the real difference sits.
When the number is not what decides
Some factors do not fit in the spreadsheet and sometimes weigh more: how fast you can grow or shrink, what happens if the only person who knows the process leaves, how much management attention a small team consumes, and whether the process is where the company wants its focus. That discussion comes before cost, and it is in when to outsource a process.
It is also worth remembering that outsourcing is not the only arrangement available. Depending on the case, dedicated staff under the client's direction or hiring through a third party may fit better, with different costs and different responsibilities: the three are compared in BPO, EOR or staff augmentation.
How smartBPO works it
When a client asks us for a quote to compare against their own operation, we ask about scope and volume first, because without those the number means nothing. We hand over the assumptions alongside the rate: coverage hours, billing unit, what is included and what is invoiced separately. We say which work stays on the client's side, so the outsourced scenario does not look artificially clean. We split one-off from recurring. And when the comparison does not favour outsourcing at the scope proposed, we say so, because a contract that starts from a badly built number gets argued about every month.