Project vs Dedicated Team vs FTE BPO Pricing

One of the easiest ways to create confusion in a BPO deal is to mix up the pricing model with the delivery model.

That is what often happens in this comparison.

People use terms like:

• project-based
• dedicated team
• FTE pricing

as though they all describe the same thing.

They do not.

They overlap, but they solve different commercial problems.

The short answer

Here is the cleanest practical distinction:

• Project-based pricing fits defined, time-bounded work with a clear scope and end point.
• Dedicated-team pricing fits ongoing work where continuity, context retention, and stable staffing matter.
• FTE pricing fits capacity-based service models where labor availability is the main commercial unit.

The right answer depends on:

• how stable the scope is
• whether the work is one-off or ongoing
• how important team continuity is
• how much uncertainty you expect during delivery

Why buyers confuse these models

They confuse them because all three can involve people doing work for a client.

But the real commercial logic is different.

Project-based pricing asks:

• what is the defined deliverable?

Dedicated-team pricing asks:

• what stable team do we need to keep this service healthy?

FTE pricing asks:

• how much capacity are we buying?

That distinction helps immediately.

Project-based pricing

Project-based pricing works best when the work has:

• a defined scope
• a specific objective
• a time-bounded delivery cycle
• a clearer finish line

Examples can include:

• process documentation projects
• transition support phases
• data-cleanup initiatives
• workflow redesign work

In these cases, it makes sense to price the effort as a project because the buyer is not really buying steady-state service capacity.

They are buying a bounded outcome.

Where project-based pricing works well

It works well when:

• the scope is stable
• the deliverable can be clearly defined
• both sides understand what "done" means

Where project-based pricing breaks

It breaks when:

• the work keeps evolving
• operational exceptions are higher than expected
• the project really turns into an ongoing service

That is when fixed-fee or project-style models often start leaking cost and creating change requests.

Dedicated-team pricing

Dedicated-team models are common when the buyer wants a stable service pod that learns the process and keeps context over time.

This often matters for:

• ongoing customer support
• back-office operations
• blended services with recurring exceptions
• accounts where consistency matters more than temporary throughput

TechTarget's contact-center outsourcing coverage is useful here because it notes that shared resources often cost less while dedicated resources tend to cost more.

That is the tradeoff.

Dedicated models usually cost more visibly because they preserve:

• continuity
• account knowledge
• closer alignment

But they may create better total value when the work is too nuanced for a rotating shared pool.

What buyers are really paying for here

They are paying not only for labor.

They are also paying for:

• team stability
• lower relearning cost
• clearer accountability
• often better service consistency

Where dedicated-team models work best

They fit best when:

• the service is ongoing
• the work benefits from retained process knowledge
• the buyer wants higher visibility into staffing and role structure

FTE pricing

FTE pricing is the capacity-based model many buyers know best.

It usually means pricing the service by the number of full-time equivalents or equivalent labor units assigned.

This model is often attractive because it is:

• simple to understand
• easier to budget
• familiar to procurement and finance teams

But it is not identical to a dedicated-team model.

A dedicated team is an operating choice. FTE is a commercial measure.

Sometimes they line up neatly. Sometimes they do not.

For example, a provider might price by FTE while still running:

• pooled support layers
• shared QA
• shared leadership

That means the buyer needs to understand what the FTE price actually includes.

The relationship between dedicated team and FTE

This is where most people get confused.

A useful way to think about it is:

• Dedicated team describes how the service is organized.
• FTE pricing describes how capacity is charged.

A dedicated team might be priced:

• by FTE
• by team retainer
• by hybrid commercial model

An FTE model might support:

• a dedicated team
• a partly shared model
• a blended staffing arrangement

So do not assume the label answers more than it really does.

How to choose between the three

Use this simple decision filter.

Choose project-based when:

• the work has a defined start and end
• the deliverable is clear
• steady-state support is not the main need

Choose dedicated-team when:

• service continuity matters
• learning curve and context matter
• the work is ongoing and operationally nuanced

Choose FTE pricing when:

• capacity is the cleanest commercial unit
• labor planning matters more than pure transaction pricing
• the service needs predictable budgeting

What can make each model expensive

This is the part buyers often miss.

Project-based can become expensive when:

• the scope keeps changing
• the "project" hides ongoing service
• change requests accumulate

Dedicated-team can become expensive when:

• demand is highly inconsistent
• the team is oversized for the real workload
• the buyer is paying for continuity it does not really need

FTE pricing can become expensive when:

• the model rewards capacity without enough productivity visibility
• the role mix is inefficient
• support layers are unclear

This is why Hidden Costs in BPO Contracts Explained is a key companion page.

Why this differs from unit pricing

This lesson also connects naturally to Per Agent vs Per Ticket vs Per Minute Pricing.

That page is about what unit you charge against.

This page is more about what kind of commercial relationship and delivery structure you are creating.

Those are related, but not identical, decisions.

The real question behind the comparison

The real question is not:

• which model is cheapest?

It is:

• which model best matches the shape of the work?

If the work is dynamic but ongoing, forcing project-based pricing can create constant friction.

If the work is highly stable and low-context, overbuilding a dedicated team can create unnecessary cost.

If the work needs continuity but is bought as generic FTE capacity, accountability can become soft.

The bottom line

Project-based pricing is best for bounded work. Dedicated-team pricing is best for continuity-heavy ongoing work. FTE pricing is best when capacity is the right commercial unit.

From here, the best next reads are:

• BPO Pricing Models Explained Clearly
• Per Agent vs Per Ticket vs Per Minute Pricing
• Hidden Costs in BPO Contracts Explained

If you keep one idea from this lesson, keep this one:

the best pricing model is the one that matches how the work actually behaves after launch, not just how the proposal reads before signature.