Dedicated Team Pricing
Definition
Dedicated Team Pricing
Dedicated team pricing charges one monthly amount for a ring-fenced team, including its lead, quality function and share of support, rather than a rate per person on it. You are buying a capability, not a headcount, and the difference shows at renewal.
The team is exclusive to one client, which is what justifies the price — its members do not rotate onto other accounts, and their knowledge of the client’s systems compounds.
Pricing is built from a named composition. A team of eight might be five practitioners, a lead, a quality analyst and a half-share of an architect, and each line is visible.
What makes the model different from buying eight individuals is the wrapper — recruitment, replacement, supervision, training and continuity are the supplier’s problem, not a set of separately billed line items.
Key takeaways
- One monthly price covers a named team composition, not a list of individual rates.
- Ramp-up, backfill and attrition handling belong in the price, not in a change request.
- Exclusivity is the thing being paid for, and it should be written into the contract.
- Team size changes need a defined notice period on both sides.
How it works
The commercial shape resembles buying a defined level of effort rather than a defined output, which is an arrangement public procurement has had a name and a clause for since long before offshore teams existed.
A level-of-effort term contract requires the contractor to supply “a specified level of effort, over a stated period of time, on work that can be stated only in general terms” for a fixed amount.
That is dedicated team pricing described in regulatory language. The buyer directs the work, the supplier guarantees the capacity, and the price does not move with output.
Because the amount is fixed, the arrangement behaves like a fixed-price contract for the period.
Federal rules note that a firm-fixed-price contract sets a price “not subject to any adjustment on the basis of the contractor’s cost experience”, which is the supplier’s risk here.
| Price component | What it covers | Often disputed |
|---|---|---|
| Named roles | The agreed composition by role and seniority | Substitution rules |
| Team lead | Day-to-day management and reporting | Whether it is billable |
| Quality and support | QA, training, tooling share | The allocation percentage |
| Ramp-up | Recruitment and onboarding period | Who pays for the first weeks |
| Backfill | Replacing a leaver | The allowed vacancy window |
Ramp-up is the first negotiation. A common structure charges nothing for the first two to four weeks of a new joiner, because the client gets little value while systems knowledge is being built.
Backfill is the second — the contract should state how quickly a leaver is replaced and what the buyer pays during the gap, usually a reduced or zero rate after a stated number of days.
Examples
Team pricing rewards stable, ongoing work and becomes wasteful where demand is genuinely lumpy. These four cases show the model fitting, misfitting, and one clause that fixed the attrition problem.
A software company buys a dedicated team of nine for a multi-year product roadmap. Knowledge compounds, velocity improves each quarter, and the price stays flat in real terms.
A retailer buys a dedicated team for a workload that appears in two-month bursts. It funds an idle team for eight months of the year before switching to a project structure.
A fintech buys a dedicated team with no backfill clause. Two departures leave the team short for eleven weeks at full price, with no contractual remedy available.
An insurer writes a clause suspending charges for any vacancy beyond fifteen working days. Replacement speed improves immediately, because the cost of delay sits with the supplier.
Related terms
Team-based buying is described with several overlapping terms, and the differences come down to exclusivity and to how much of the wrapper is bundled into the price. The entries below separate them.
- Full-time equivalent (FTE): the per-head unit this model deliberately bundles away.
- Staff augmentation: individuals added to a client team, without the wrapper.
- Offshore development center (ODC): the facility version of the same exclusivity idea.
- Managed service pricing: buys an outcome and lets the supplier size the team.
- Offshore staffing: the broader practice of hiring delivery capacity abroad.
- Dedicated virtual assistant: the single-person version of exclusivity.
- Agile outsourcing: the delivery method dedicated teams are most often bought for.
FAQ
What should the team price include?
Named roles, the team lead, a stated share of quality and support, tooling, and the supplier’s recruitment and replacement obligations. Anything excluded should be listed.
How is this different from FTE pricing?
FTE pricing quotes a rate per person. Team pricing quotes one figure for a composition including management and support, which are usually unbilled overhead in an FTE model.
Who pays during ramp-up?
Usually nobody, for the first two to four weeks. Charging full rate for a joiner still learning the systems is the most common source of early friction.
What happens when someone leaves?
The contract should say. A vacancy window with charges suspended after a stated number of days puts the cost of slow replacement where it belongs.
Can the team be resized?
Yes, with notice on both sides. Thirty to sixty days is typical, and the notice period should be symmetric rather than favouring the supplier.
Is exclusivity real?
Only if it is written down. Without a contractual exclusivity clause, a dedicated team can quietly become a shared one.
Compare providers who will publish a team composition and a backfill clause in the Outsource Accelerator directory.
Independent
