What Are You Actually Paying For? Outsourcing Price Structures, Explained

Most buyers negotiate the number and accept the structure. This is backwards. The structure determines what your provider is incentivized to do all day, and no amount of rate negotiation corrects a structure that rewards the wrong behavior.

Four arrangements cover nearly all commercial work of this kind, and providers of contact center services across Philippine delivery sites will quote against any of them.

The four structures at a glance

Structure	You carry	Provider carries	Fits	Fails when
Per seat, per month	Utilization risk — an empty seat bills the same as a busy one	Staffing and attrition within the seat count	Steady volume; dedicated teams; work needing accumulated product knowledge	Volume is seasonal or declining and you pay for capacity you stopped needing
Per productive hour	Definitional risk — what counts as productive	Efficiency within the hour	Variable volume on simpler work	The definition is loose, and eight percent of the invoice turns on it
Per transaction	Mix risk — the unit price assumes comparable units	Throughput and handling cost	Genuinely standardized processing	Contacts vary in difficulty, or automation shifts the mix underneath the price
Outcome-based	Measurement risk — both parties must trust the number	Delivery of the result itself	Mature programs with established baselines	Attempted at launch, before anyone holds operating history

Per seat, per month

You rent a position and somebody occupies it during agreed hours. The honest advantage is that it buys the same people every day. If your work takes three months to learn, a named team is worth paying for even during the quiet hours, and trying to avoid that cost through a more flexible structure usually loses more in competence than it saves in utilization.

Per productive hour

You pay for time actually spent on your work, net of breaks and training. This sounds like per-seat with the waste removed, and it is — provided both sides agree precisely what counts. The entire commercial substance sits in the definition. Is coaching billable? Team meetings? The twenty minutes at shift start spent logging into six applications? Reasonable people answer differently, and the gap between two reasonable answers is material. Settle it in writing, with worked examples, before signature.

Per transaction

You pay a unit price per contact, case or item processed. Buyers find this the most intuitive structure and it is the one that most reliably goes wrong, because it assumes transactions are comparable. They rarely are, and they are becoming less so: when routine contacts resolve automatically, what reaches a person is the harder residue, and a unit price calibrated against last year’s mix is now wrong in a predictable direction. Coverage of the move toward outcome-based pricing for BPO services describes this composition shift and the commercial rethinking it has forced. If you use per-transaction pricing, band it by complexity class and agree in advance how a transaction gets classified.

Outcome-based

You pay against a result — a resolution, a retained customer, a collected balance. Everybody wants this and few manage it, because both parties must agree what the outcome is and how it is measured before either holds operating history for this specific program. Measurement adequate for an internal report becomes inadequate the moment it determines an invoice. The sequence that works is staged: run year one on seat or hourly terms, build the measurement history while the argument about definitions is still cheap, and attach commercial consequence at renewal.

Few mature programs use one structure exclusively. A common and sensible arrangement puts a dedicated core on per-seat pricing, flexes an overflow tier hourly, and attaches a modest outcome-linked component — five or ten percent of value — to two or three measures both sides already trust.

Five questions that matter more than the rate

1. What is included? Supervision, quality assurance, workforce planning, reporting and technology either sit inside the rate or arrive as separate lines. A lower headline rate with four support functions billed separately is not a lower price.
2. What happens when volume moves? Both directions. Most contracts specify an uplift mechanism and are silent on reduction, which is the direction that eventually matters.
3. Who pays for re-ramp after attrition? Ambiguity here surfaces as a dispute rather than a line item, usually in the second year.
4. Does the technology charge survive the term? Platform and integration costs are frequently amortized over an assumed contract length, and shortening the term changes economics that are invisible in a monthly figure.
5. How does the rate change as the mix changes? Newest of the five, and the one most contracts handle worst. A rate card set against a work mix that is actively shifting needs a stated mechanism for revision.

Steady volume with work that takes time to learn points to per seat. Variable volume on simpler work points to hourly, with the definition nailed down. Genuinely standardized processing points to per transaction, banded by complexity. And anything you want priced on results should get there at renewal rather than at launch. Which structure you ask for says more about how the program will run than the number attached to it, and it is the part of the negotiation that is hardest to change afterward.