Project Outsourcing
Definition
Project Outsourcing
Project outsourcing is contracting a provider to deliver one defined piece of work with a start, an end, and an agreed result. The provider carries the schedule risk and the delivery method, and the buyer accepts or rejects the output.
Risk transfer is what distinguishes it from buying capacity — when a project runs late under a fixed-price contract, that is the provider’s problem to solve.
The trade is flexibility — a fixed scope resists change by design, so every alteration becomes a variation with a price attached to it.
Acceptance criteria carry more weight than anything else in the document — written vaguely, they turn the end of the project into a negotiation rather than a delivery.
Key takeaways
- The provider owns schedule risk under a defined scope.
- Acceptance criteria must be specific, testable, and agreed upfront.
- Change control is the mechanism, and it should be priced in advance.
- Handover deliverables belong in the contract, not in a closing email.
How it works
The buyer defines the outcome, the constraints, and the acceptance criteria. The provider proposes an approach, a schedule, and a price, then delivers against milestones with agreed reviews. Payment usually follows accepted milestones rather than elapsed time.
Pricing follows how well the scope is understood. Fixed price suits well-defined work, time and materials suits exploratory work, and a capped model splits the difference between them.
Contract types are formally categorised. FAR Part 16 sets out the range from firm-fixed-price to cost-reimbursement, each allocating risk between the parties differently.
| Model | Buyer risk | Provider risk | Best for |
|---|---|---|---|
| Fixed price | Low | High | Clear scope |
| Time and materials | High | Low | Exploratory work |
| Capped time and materials | Medium | Medium | Partly known scope |
| Milestone-based | Medium | Medium | Staged delivery |
| Outcome-based | Low | High | Measurable results |
Verification practice is published for software. The NIST Software and Systems Division maintains work on measurement and assurance that acceptance clauses can reference.
Change control needs its own price list. Agreeing the rate for variations before the project starts prevents a negotiation at the exact moment bargaining power has shifted.
Handover deliverables should be listed explicitly. Documentation, source material, and access details are far easier to obtain before the final payment than afterwards.
Examples
Project outsourcing suits defined work with a clear end point, from system builds to physical delivery. Four cases show how the risk was actually allocated.
A retailer. A store systems rollout across 90 sites was contracted at fixed price with milestone payments tied to sites accepted.
A manufacturer. A production line upgrade ran on capped time and materials, because the condition of the existing equipment was genuinely unknown.
A public body. A website replacement was contracted with staged acceptance, and each phase required a passed assessment before the next began.
A financial firm. A data migration ran at fixed price with a defined reconciliation standard as the acceptance criterion for every batch.
The fourth is the pattern worth copying. A numeric acceptance criterion removed all argument about whether the work was finished or not.
Related terms
Project outsourcing is one contracting shape among several, so it borders the capacity models it is defined against and the delivery lanes it uses. The list below marks the boundaries.
- IT Staff Augmentation: buying capacity you manage rather than a delivered result.
- Development Outsourcing: contracting engineering work under any commercial model.
- Software Outsourcing: the broad category most projects of this kind sit in.
- Project Manager: the role running delivery on the provider side.
- IT Project Manager: the technology-specific delivery role.
- Agile Outsourcing: iterative delivery where scope flexes within a fixed capacity.
- Custom Software Outsourcing: bespoke builds delivered to one client’s specification.
FAQ
When should a project be fixed price?
When the scope is genuinely well understood. Fixed pricing on vague requirements produces either a padded quote or a dispute, and often both.
Who carries schedule risk?
The provider, under a fixed-price contract. Under time and materials the buyer does, which is why the two models suit different kinds of work.
What makes good acceptance criteria?
Specific, testable statements agreed before work starts. A numeric standard removes argument; a subjective one guarantees it.
How should change be handled?
Through a written change process with rates agreed at the outset. Negotiating variation pricing mid-project rarely favours the buyer.
What should be handed over at the end?
Deliverables, documentation, source material, and access credentials, all listed in the contract. Ask for them before the final payment.
How is this different from agile outsourcing?
Agile fixes capacity and time while scope flexes. Project outsourcing fixes scope and price, which resists change by design.
Compare vetted project delivery partners in the Outsource Accelerator directory.
Independent
