Question 1

How do we bring software development back in-house from an outsourcing vendor?

Accepted Answer

As five parallel workstreams, not an event: change management, vendor relationship management, competence building, organizational build-up, and transfer of ownership. Verify repository access and IP terms before giving notice, run knowledge transfer while the vendor is still engaged, and evaluate renegotiation and vendor-change honestly first - in-housing is one of three exits.

Question 2

Should we expect cost savings from bringing development in-house?

Accepted Answer

Plan for control, speed, and quality instead. The best-audited large case - Norway's NAV, 100+ systems - succeeded on those dimensions while researchers could not verify the per-developer savings that motivated it. Pressure-test any case built purely on cost.

Question 3

How do we keep the vendor cooperative during the exit?

Accepted Answer

Manage the relationship as a workstream: commercial terms for the transition period, knowledge-transfer obligations tied to payment milestones, and a wind-down that preserves their reference and your emergency access.

How do we bring software development back in-house from an outsourcing vendor?

The short answer, with operator context.

Outcomes that inform this answer.

What to ask next.

Should we expect cost savings from bringing development in-house?

How do we keep the vendor cooperative during the exit?

Where to go next.

Turn the answer into an operating plan

Should we expect cost savings from bringing development in-house?

How do we keep the vendor cooperative during the exit?

Who owns the source code when an agency builds your software?

How do CFOs reduce SaaS spend without cutting tools teams rely on?

How do I negotiate a SaaS renewal price increase?

Turn the answer into an operating plan