Backsourcing
Backsourcing is the full or partial repatriation of previously outsourced activities into an internal team. The peer-reviewed literature identifies three exit options from a failing outsourcing relationship - backsource, renegotiate, or change vendor - and models the transition as five parallel workstreams: change management, vendor relationship management, competence building, organizational build-up, and transfer of ownership. Documented drivers are quality problems, cost, and loss of control.
The best-audited large case - Norway’s NAV, which brought 100+ systems in-house - succeeded on delivery speed, ownership, and quality while researchers could not verify the cost savings that motivated it. Plan backsourcing for the benefits that materialize, and pressure-test any business case built purely on per-developer savings.
Related terms
- Build vs. Buy — The decision between building software internally and buying it as a product or subscription - properly a five-option triage, not a binary.
- Total Cost of Ownership (TCO) — The full multi-year cost of owning a system - build, run, maintain, staff, and risk - as opposed to the purchase or build price alone.
- Vendor Lock-In — The condition where leaving a software vendor is prohibitively expensive because of data, integrations, contract terms, or accumulated dependency.
Where this gets applied
- Team & Hiring — Org design for scale, comp band rationalization, hiring rubrics with 92% accuracy across 40+ hires.
- Project Recovery — Stalled programs unblocked. We've rescued $13M and $3M Fortune 500 initiatives in under 30 days.