BPO Strategy

BPO Pricing Models Explained: Per-FTE, Per-Task, and Outcome-Based Pricing

| November 19, 2026 10 min read
Two business professionals reviewing a BPO pricing proposal next to a laptop showing a cost breakdown spreadsheet
Quick Answer
What are the main BPO pricing models?

Three structures cover almost every outsourcing quote: per-FTE (a flat monthly rate for a dedicated person, regardless of volume), per-task or per-transaction (a unit price for each ticket, call, record, or item processed), and outcome-based or gain-share (payment tied to a result, like a resolved case, a collected balance, or a booked meeting). Real contracts usually blend two of the three rather than picking one in isolation. Each model shifts volume risk to a different party, and that shift, not the headline rate, is usually what separates a good deal from a bad one. See the full cost picture, including red flags and regional comparisons, in our 2026 BPO pricing breakdown.

  • Per-FTE still covers the majority of BPO contracts industry-wide
  • 6,236 hires placed for 257 US companies since founding
  • Resumes delivered in 2 to 5 business days, zero upfront fees

The Three Core BPO Pricing Models, and Why They All Still Exist

Ask five outsourcing providers how they price a contract and you’ll get five different answers that all circle back to the same three underlying structures. Per-FTE charges a flat rate for a dedicated person. Per-task charges a unit price for each thing completed. Outcome-based charges for a result, independent of how many hours or tickets it took to get there. None of the three is objectively better. Each one simply moves volume and quality risk to a different side of the table, and that’s the detail most sales decks skip right past.

A seat-based rate protects you from a slow month. Every seat you staff is covered whether volume spikes or dries up, but you carry the cost if the provider’s team is inefficient. A per-task rate protects you from paying for idle capacity, but it rewards speed over quality unless the contract has real QA penalties baked in. An outcome-based rate sounds the most aligned on a sales call, “we only get paid when you win.” Analyst firm HFS Research has tracked strong buyer appetite for exactly that pitch for years. The catch, covered further down, is that outcome pricing only works cleanly when the outcome is actually inside the provider’s control.

Kore BPO runs mostly per-FTE engagements. We’re not going to pretend that’s a neutral recommendation. It’s also, by a wide margin, the easiest model to audit, since the rate card maps directly to a named person’s time rather than a formula someone else built. If you’re comparing a quote right now, our companion piece on red flags in a pricing proposal walks through exactly where providers hide margin inside any of these three structures.

Per-FTE Pricing: One Person, One Predictable Number

Business professional working at a dual monitor workstation, representing a dedicated FTE seat billed on a flat monthly rate

Per-FTE (full-time equivalent) pricing bills a flat monthly rate for one dedicated person working your hours, in your tools, reporting into your workflow. The number bundles base pay, statutory benefits, a management or QA layer, and the provider’s margin into a single line item. It’s the model Kore BPO runs for most of the offshore and nearshore roles we staff. Customer support agents, bookkeepers, recruiters, data annotators, and software engineers all fit here, because consistency matters more than raw throughput for most of those jobs.

Real Rate Bands by Geography

Rate bands vary a lot by geography and role complexity. A dedicated offshore support or back-office seat typically lands in the roughly $1,200 to $2,500 per month range. A nearshore equivalent usually runs higher, reflecting a smaller wage gap to the US and tighter timezone overlap. Specialized functions, developers, accountants, legal case managers, shift those bands up considerably.

For scale, the US Bureau of Labor Statistics puts the mean hourly wage for a US-based customer service representative at $20.92, or roughly $3,625 a month before benefits and overhead. That gap is the entire business case for per-FTE outsourcing. It’s also exactly why a quote that looks too low deserves a second look at what got stripped out.

The honest limit of this model is simple: you pay the full rate even in a slow week. If your volume genuinely swings 40% month to month, a pure per-FTE contract will either leave you overstaffed or scrambling. A hybrid structure, a smaller fixed FTE base plus task-rate overflow capacity, usually fits better than forcing one model to do both jobs.

Per-Task and Per-Transaction Pricing: Paying for What Got Done

Professional reviewing rows of processed tickets and records on a dashboard interface late in the evening

Per-task pricing charges a unit price for each resolved item, a ticket closed, a call handled, a record processed, a field annotated, rather than for the time it took to get there. It fits high-volume, well-defined work where the unit of output is countable and roughly uniform. Order processing, tier-one chat, refund handling, and most data annotation work all price cleanly this way. The provider is implicitly incentivized to move fast without a human sitting idle between items.

What Per-Unit Rates Actually Look Like

Rates track task complexity closely. Simple, scripted interactions run $0.50 to $6.00 per completed unit depending on channel and region. Data annotation sits at the granular end of the same model. Bounding-box labeling commonly runs $0.03 to $0.12 per box. Segmented-image work runs $0.50 to $6.00 per image. Simple text classification can run as low as $0.02 to $0.30 per item, figures consistent with published rate guidance from annotation-focused providers like YPAI’s enterprise pricing breakdown. Multiply any of those by real monthly volume and the math gets large fast. That’s exactly why volume forecasting accuracy matters more in a per-task contract than in either of the other two models.

The failure mode here isn’t the rate, it’s the incentive. A provider paid strictly per item has every reason to move through items quickly, and very little built-in reason to flag the ones that genuinely need a second look. Unless, that is, the contract has an explicit quality floor, a rework clause, or a sampled QA audit written into it. Ask for that language before signing, not after a client complains about accuracy.

Outcome-Based and Gain-Share Pricing: Paying for a Result

Two professionals shaking hands over a signed services agreement on a desk

Outcome-based pricing ties the invoice to a measurable business result rather than hours staffed or items processed. A resolved case, regardless of how many contacts it took. A dollar collected. A qualified meeting booked. Gain-share contracts take this a step further, splitting a defined financial upside, lower cost per resolution, higher recovery rate, between buyer and provider. BPO industry analyst Phil Fersht’s research firm found, in a widely-cited 2022 study covered on Horses for Sources, that roughly two-thirds of BPO buyers said they’d prefer paying for outcomes over paying for staffed hours. That preference has only grown since. Actual signed outcome contracts still lag well behind stated buyer interest.

Where Outcome Pricing Genuinely Fits

The functions where this genuinely fits are narrower than the sales pitch suggests. Collections, appointment setting, certain sales development motions, and resolution-based technical support cover most of them. All four share a trait: the result is mostly inside the provider’s control once a lead or account is handed over. Collections is the clearest case, recovery rate depends heavily on the agent’s skill and persistence. Outcome pricing on a qualified-meeting model typically runs from roughly $150 up to $800 or more per booked meeting, scaling with how strict “qualified” is defined in the contract.

Where it breaks down is just as important. A provider paid on resolution rate for a product with real defects is being asked to own an outcome it didn’t create. So is one paid on sales-development output when your own pricing page is the actual bottleneck. KPMG’s research on value-based contracting flags disagreement over outcome measures and incentive mechanics as one of the leading reasons these deals stall out or get renegotiated mid-term. If you’re being pitched outcome-based pricing, the first question isn’t the rate. It’s whether the outcome depends on variables your own company still controls. If it does, a hybrid base-plus-bonus structure protects both sides better than a pure outcome deal. Our breakdown on why “cheapest” is the wrong question goes deeper on this exact tradeoff between headline price and real risk transfer.

Office workspace background behind a three-model BPO pricing comparison
Per-FTE
~$1,200-$2,500/mo
Offshore dedicated seat, buyer carries volume risk
Per-Task
$0.50-$6.00/unit
Priced per ticket, call, or record; provider carries speed risk
Outcome-Based
$150-$800+/result
Priced per booked meeting or resolution; shared risk, needs clean scope

Which Model Actually Fits Which Function

The right model is almost never a company-wide decision. It’s a function-by-function one. Customer support with unpredictable volume usually blends a per-FTE core team with per-task overflow for spikes. Data annotation and QA review fit per-task cleanly, since output is countable and uniform, provided the contract protects quality with a sampled audit. Back-office and finance work, bookkeeping, AP/AR, reporting, tends to run per-FTE. The job requires continuity and institutional knowledge that a per-item rate doesn’t reward. Collections and appointment setting are the two functions where outcome-based pricing earns its reputation, assuming the provider actually controls the variables tied to the payout.

FunctionBest-Fit ModelWhy
Customer support (steady volume)Per-FTEConsistency and context retention matter more than raw speed
Customer support (spiky volume)Hybrid: FTE core + per-task overflowFixed base covers steady demand, overflow absorbs spikes without idle seats
Data annotation & QAPer-taskOutput is countable and uniform; needs a built-in quality floor
Back-office & finance (AP/AR, bookkeeping)Per-FTERequires continuity and institutional knowledge, not transaction speed
CollectionsOutcome-basedRecovery rate depends heavily on the agent, not on factors you control
Appointment setting / SDROutcome-based or hybridWorks if lead quality and offer are already solid on your end
Software developmentPer-FTEScope shifts constantly; dedicated capacity beats per-ticket billing

If you’re staffing across more than one of these functions at once, which is most of our clients, expect your contract to legitimately use two or three models at once rather than forcing everything under one rate card. That’s not a provider being disorganized. It’s usually the sign of one that actually thought about where the risk should sit.

How to Pressure-Test Any Pricing Model Before You Sign

Three questions settle most of this before you ever get to a line-item review. First: what exactly is bundled into the rate, base pay, benefits, management, QA, or is some of that billed separately later? Second: who carries the risk if volume swings 30% in either direction next quarter? Third, for anything priced on outcome, does the provider actually control the variables the outcome depends on? Or are they being asked to own your product, pricing, or sales team’s results? A provider that answers all three clearly, without redirecting to “it depends on the deal,” is one worth taking seriously. One that gets vague on any of the three deserves a second conversation before you sign anything.

For a deeper, region-specific version of the same comparison, see our breakdown on US versus offshore versus nearshore pricing, which walks through how these three models shift again once geography enters the equation.

Common Questions on BPO Pricing Models

Which BPO pricing model is cheapest+

None of them is cheapest in isolation, each shifts risk differently. Per-task often looks cheapest on paper for low-volume work, but per-FTE is usually cheaper once volume is steady and high enough to keep a dedicated seat busy full time. Compare total projected monthly cost at your real volume, not the headline unit rate.

Can a BPO contract combine more than one pricing model+

Yes, and for most companies staffing more than one function, it should. A common hybrid pairs a fixed per-FTE core team with per-task overflow pricing for volume spikes, or a per-FTE base with an outcome-based bonus layered on top for measurable wins.

Is outcome-based pricing always better because it’s lower risk for the buyer+

No. It’s lower risk only when the outcome genuinely depends on the provider’s work. If the result also depends on your product, pricing, or internal process, outcome pricing just sets up a dispute later about whose fault a missed number was.

How does Kore BPO price most engagements+

Mostly per-FTE, since it’s the most auditable structure and fits the continuity most of the roles we staff actually need. We’ll walk through a hybrid or task-based structure when the function genuinely calls for it, rather than defaulting to one model for every client.

Brian Hunt
Brian Hunt
CEO & Founder · Kore BPO

Brian Hunt is the CEO and founder of Kore BPO, an offshore staffing firm that has placed 6,236 hires for 257 US companies since founding the company.

Get a Quote Built on the Right Model, Not a Guess

Tell us the function you’re staffing and we’ll tell you honestly whether per-FTE, per-task, or outcome-based pricing actually fits, before you see a number.

Talk to a Specialist