Full-Time Equivalent (FTE): in outsourcing, a FTE is the contracted unit representing one agent working a full standard schedule (typically 40 hours a week, around 160 to 173 hours a month), used as the base billing block for dedicated-seat pricing. The number on the invoice describes paid seat capacity, not the hours that agent actually spends resolving your tickets, calls, or transactions.
That distinction is where most buyers get surprised. A vendor sells you “3 FTEs” and you mentally convert that to roughly 520 productive hours a month. In practice you get less, sometimes meaningfully less, because of shrinkage: paid breaks, training time, team huddles, local statutory holidays, sick leave, and bench time between projects. None of that disappears from your invoice. It just disappears from your output.
How Many Hours Is 1.0 FTE, Really?
One FTE is typically billed as 40 hours a week, or roughly 160 to 173 hours a month, but the productive hours you actually get are lower once shrinkage is factored in. A realistic range I’d use for planning is 75% to 85% productive utilization for a well-run offshore or nearshore team, meaning 1.0 billed FTE delivers closer to 120 to 145 hours of actual work in a typical month, not the full 173.
Shrinkage isn’t a red flag by itself. Every vendor has it, and a good one discloses it upfront rather than letting you discover it in month two when volume doesn’t get handled the way the sales deck implied. What I’d push back on is a vendor who quotes 1.0 FTE and lets you assume that number equals full working hours with zero deductions. Ask directly: what’s your shrinkage assumption, and is it already baked into the rate or added on top?
| Scenario | Billed hours/month | Typical productive hours | Shrinkage driver |
|---|---|---|---|
| Offshore support team (India, Philippines) | ~173 | ~130 to 150 | Local holidays, breaks, training cycles |
| Nearshore bilingual team (Mexico, Colombia) | ~173 | ~140 to 155 | Lower holiday count, tighter management layer |
| Onshore US regulated team | ~173 | ~150 to 160 | Compliance training, QA review time |
These are editorial ranges based on how shrinkage typically plays out, not a vendor-quoted statistic. Ask any shortlisted vendor for their actual number and get it in writing.
Is a .75 FTE Considered Full-Time?
No, a .75 FTE is not full-time by definition. It represents 75% of a standard full-time schedule, which at a 40-hour baseline works out to about 30 hours a week, or roughly 120 to 130 hours a month. In a BPO contract, a .75 FTE usually means a shared or part-allocated agent, someone splitting time across your account and at least one other client, or covering a partial shift rather than a full one.
The operational risk with fractional FTEs is coverage continuity. A .75 agent handling your process alongside another client’s queue is more exposed to reprioritization when the other account has a spike. If continuity matters for your process, ask whether that .75 FTE is dedicated-but-part-time or genuinely shared across accounts. Those are very different risk profiles even though the billing math looks identical.
Why FTE Math Matters More Than the Headline Rate
FTE structure matters because it determines whether you’re paying for a person’s time or paying for completed work, and those two things move at different speeds when volume changes. A per-FTE dedicated model gives you predictable staffing and process ownership, but you carry the shrinkage and idle-time risk. A per-transaction or outcome-based model shifts that risk to the vendor, but usually only works for repeatable, well-documented processes.
I would not compare two vendor quotes on hourly rate alone. A $9/hour offshore FTE with 70% real productivity is not cheaper than a $11/hour FTE with 88% productivity once you divide cost by hours actually worked, let alone by issues resolved. Ask for cost per resolved ticket or completed transaction, not just the headline seat rate, and ask what happens to your FTE count when volume spikes for a week versus a quarter.
This is also where dedicated FTE pricing tends to make more sense than pure hourly billing: stable, ongoing volume with a process the vendor should own end to end justifies a seat-based team where the vendor manages scheduling and shrinkage internally, versus a small pilot where per-hour billing keeps things flexible. For teams working across US and offshore or nearshore hours, checking time zone overlap against your FTE’s actual shift matters too. A dedicated FTE technically staffed 24/7 across a handoff isn’t the same as one agent who overlaps with your core business hours.
Don’t outsource a process you haven’t documented and then try to reverse-engineer FTE math from confusing invoices later. Get the shrinkage assumption, the shift schedule, and the management layer in writing before you sign, and compare vendors on productive hours delivered, not the number printed next to “FTE” on the quote.
If you’re sizing a team and want real numbers from vendors who specialize in your process, get outsourcing quotes and ask each one to break out billed hours versus expected productive hours in writing.