Shadow Team Pricing

Shadow team pricing covers the period when two teams run the same work at once, usually while knowledge moves from an incumbent to a successor. Somebody pays twice during that overlap, and the contract should say who, and for how long.

It appears in almost every transition and is budgeted in almost none — buyers plan the new team’s cost and forget that the old one keeps running alongside it.

The overlap has a real purpose. Watching the work being done is how undocumented process knowledge actually transfers, and no amount of documentation replaces it.

The commercial question is straightforward once it is asked — who funds the duplication, at what rate, and what event ends it.

Key takeaways

• Parallel running duplicates cost for a defined period and must be budgeted.
• Shadow rates are usually discounted, because the shadow team is not yet productive.
• The overlap should end on a competence trigger, not on a calendar date alone.
• Reverse shadowing, where the new team leads, is the stage that proves readiness.

How it works

Transition normally runs in four stages: observation, reverse shadowing, supervised delivery, and independent delivery. Each stage changes how much value the incoming team produces and therefore what it should cost.

Pricing follows that curve. A common structure charges nothing during observation, a reduced rate during reverse shadowing, and the full rate once the incoming team is delivering independently.

The arrangement is capacity being held rather than output being produced, which is exactly what a level-of-effort contract buys. Such a contract requires “a specified level of effort, over a stated period of time” for a fixed amount, regardless of results.

Exit triggers matter more than durations. A competence test, an error-rate threshold or a volume target ends the overlap on evidence rather than on a date somebody guessed at.

Government guidance on contract design applies squarely here, asking that arrangements “minimise perverse or unintended incentives” — and a shadow period billed at full rate with no exit trigger rewards a slow handover.

Continuity shadowing is the other use of the term. Some buyers fund a permanent mirror team at a second site for resilience, which is a different purpose and a different price.

Examples

Transition overlaps are where budgets quietly break, because the cost is real and nobody owns it in the business case. These four cases show the spread.

A bank runs a twelve-week overlap with tiered rates and a competence test at week eight. The test passes early, the incumbent is released, and the transition comes in under budget.

An insurer budgets for the new team only. Three months of duplicated cost appear in the accounts as an overspend, and the programme is judged a failure on economics alone.

A retailer agrees a fixed twelve-week overlap with no trigger. The incoming team is ready at week six and the buyer funds six weeks of unnecessary duplication.

A utility funds a permanent shadow team at a second site for continuity. The cost is deliberate and budgeted, which makes it a resilience decision rather than a transition overrun.

Related terms

Transition and duplication costs are described with several overlapping terms, and each one sits at a different point in the handover sequence. The entries below separate them, because the cost behaviour differs at every stage.

• Staff augmentation: the model most shadow arrangements are billed under.
• Offshore staffing: where the incoming team usually sits.
• Training outsourcing: the formal instruction that shadowing supplements.
• Full-time equivalent (FTE): the unit shadow capacity is counted in.
• Service delivery outsourcing: the steady state the overlap leads to.
• Multi site outsourcing: the structure a continuity shadow team sits inside.
• Contract lifecycle outsourcing: where transition triggers and exit dates are managed.

FAQ

Who pays for the overlap?

Whoever the contract says, which is why it should say. Most buyers fund it, but a discounted shadow rate shares the cost sensibly between both parties.

How long should a shadow period run?

Long enough to reach independent delivery, which varies by complexity. Eight to sixteen weeks is common for process work, and longer for technical estates.

Should shadow time be billed at full rate?

Not during observation. An incoming team that is watching rather than working is not producing value, and full-rate billing invites a slow handover.

What ends the overlap?

A competence trigger, ideally. An error rate, a throughput target or a passed assessment beats a calendar date that was set before anyone saw the work.

Is reverse shadowing necessary?

It is the stage that actually proves readiness. Watching someone work demonstrates nothing about whether you can do it unsupervised.

How is a continuity shadow team different?

It is permanent and exists for resilience rather than handover. That is a standing cost, not a transition cost, and should be budgeted separately.

Compare providers who publish tiered transition rates in the Outsource Accelerator directory.