BPO Pricing Models: FTE, Transaction, or Outcome?

The service levels in an outsourcing contract get weeks of negotiation. The pricing model usually gets one meeting with procurement. That allocation of attention is backwards. Service levels describe what you would like to happen. The pricing model determines what the provider is paid for, and providers — like every other rational commercial organization — optimise for what they are paid for. Pricing structure is the single contract decision that determines whether outsourcing actually pays back, because the wrong one puts the vendor's incentives at odds with yours from the first month. By 2009 the market had three main models in circulation, each with a distinct failure mode.

Per-FTE Pricing

You pay for a number of dedicated people at an agreed rate. What it gets right: transparency and control. You know exactly what you are buying, you can flex headcount up and down, and it works when volumes are unpredictable or the process is not yet stable enough to define a unit. What goes wrong: the provider's revenue is headcount. Every efficiency gain reduces their income, so there is no commercial reason to automate, simplify or eliminate work — and considerable reason to explain why the team cannot be smaller. A provider paid per FTE has little natural incentive to chase a stubborn exception or to redesign the step that creates it. Use it when: the process is unstable, volumes are unpredictable, or you are in the first year of a transition and nobody can define a reliable unit of work.

Per-Transaction Pricing

You pay a fixed amount per invoice processed, ticket resolved, record maintained or payslip produced. What it gets right: cost scales with volume, the provider absorbs productivity risk, and automation becomes their commercial interest rather than yours to fund. This is why it became the default for stable, high-volume back office work. What goes wrong: volume is not value. A provider paid per resolved unit has every incentive to resolve quickly and few to resolve well, and quality erosion under speed incentives is the model's recognised weakness. It also creates disputes at the edges: what counts as one transaction, who pays for reworked items, and how exceptions are priced. Minimum volume commitments quietly reintroduce the fixed cost you were trying to escape — as a great many organizations discovered in 2009 when their volumes fell and their floors did not. Use it when: the process is standardised, volumes are measurable, and you can define the unit and the exception treatment precisely.

Outcome-Based Pricing

You pay for a business result: days sales outstanding, close cycle time, recovery rate, cost per order. What it gets right: in principle, complete alignment. The provider wins only when your business improves, and they are rewarded for innovation rather than for maintaining the status quo. Market research has identified hundreds of outcome metrics tying delivery performance to measurable business results, and provider interest has grown for a structural reason: automation is shrinking FTE-based revenue, so outcome pricing is how providers protect value. What goes wrong: attribution. Days sales outstanding depends on your sales terms, your customers' liquidity and your credit policy as much as on collections execution. When the number moves, both sides can argue causation. Outcome models also require a trusted baseline, clean shared data and a genuine willingness to pay more when targets are exceeded — which buyers frequently discover they do not have. Use it when: the outcome is measurable, attribution is defensible, the baseline is agreed in writing, and the provider has enough control over the levers to move it.

The Hybrid Most Mature Deals End Up With

In practice, the structure that survives contact with reality is layered: a base fee covering the stable core, unit pricing for volume-driven work, and a performance component — typically ten to twenty percent of value — tied to a small number of outcomes that genuinely matter. The base gives the provider the stability to invest in your account. The unit component keeps cost aligned with volume. The performance element makes quality and improvement worth pursuing. Splitting risk this way is deliberately unglamorous, and it is why hybrid structures have become standard advice.

Getting the Commercials Right

• Define the unit with painful precision. What counts as one transaction, what happens to reworked items, how are exceptions priced, and who decides when there is disagreement.
• Cap or remove volume commitments. If you must commit, set the floor well below current volume and agree a repricing mechanism if volumes move beyond an agreed band in either direction.
• Build in a productivity commitment. A contractual unit-price reduction each year — typically two to five percent — forces the efficiency gain to be shared rather than absorbed entirely by the provider.
• Measure quality alongside volume. First-time-right rate, exception ageing, query resolution time and rework percentage. Throughput metrics alone reward speed at the expense of accuracy.
• Agree the baseline in writing before day one. Outcome pricing without a documented starting point becomes an argument about arithmetic within two quarters.
• Decide who owns the automation dividend. When the provider automates 40 percent of the volume, does your unit price fall? Silence on this point means the answer is no.
• Review the model annually. The pricing structure that suited a chaotic transition year is the wrong one for a stable fourth year.

The Automation Problem Nobody Solved

The question 2009 could not answer is now unavoidable. When the work is done by software rather than people, per-FTE pricing is a fiction and per-transaction pricing becomes a pure margin exercise, with the provider's cost per unit falling toward zero while your price stays fixed. There are only three honest answers: share the gain through contractual price reductions, move to outcome pricing where the provider is paid for results rather than effort, or take the work back in-house because the automation you are paying a margin on is now available to you directly. What does not work is signing a three-year per-transaction deal at today's rates and assuming the provider will voluntarily hand back the benefit of technology you are not paying for.

Common Questions

Which BPO pricing model is best?

There is no universally best model. Per-FTE suits unstable processes, per-transaction suits standardised high-volume work, and outcome pricing suits measurable results with defensible attribution. Most mature contracts blend all three.

What is the main risk of per-transaction pricing?

Quality erosion. Paying per resolved unit rewards speed, so the contract needs quality measures — first-time-right, rework rate, exception ageing — alongside the volume metric.

Why is outcome-based pricing difficult to implement?

Attribution. Business outcomes depend on factors outside the provider's control, so both sides need an agreed baseline, shared data and a clear view of which levers the provider can actually move.

How should contracts handle provider automation?

With an explicit productivity commitment: a scheduled reduction in unit price, a gainshare mechanism, or an outcome-based structure. Without one, the entire benefit of automation accrues to the provider.

---

Sourcing Commercial Review — Outpace examines how your outsourcing contracts pay providers, models what those incentives produce over the term, and restructures pricing so efficiency gains reach your side of the table.