When an OEM should outsource vehicle development — and when it shouldn't
How large manufacturers decide which programs to run in-house and which to hand to an outside development partner.
The capacity question is rarely the real one
Most OEMs first reach for an outside development partner because the internal team is full. That is a real trigger, but it is a poor decision criterion on its own — adding an external team to a program the internal organisation still wants to own usually produces two competing engineering groups and one very confused supplier base.
The better question is whether the program is strategically core. A derivative of the flagship platform belongs in-house. A new light EV category, a regional variant, or a clean-sheet architecture that does not share a single carryover part is exactly the kind of work an outside team can carry end to end.
Three patterns that work
Full program ownership: the partner runs design through SOP with the OEM holding gate authority. This is the fastest route for a vehicle outside the core platform family.
Single workstream: battery integration, vehicle software, or homologation is carved out cleanly with defined interfaces. This works when the interface documents are genuinely stable.
Advisory and surge: senior architects embed with the internal team for a defined phase. Lowest commitment, lowest leverage — useful for de-risking a concept before the real program is funded.
What makes it fail
Outsourced programs fail on governance far more often than on engineering. The common causes are a split risk register, unclear sign-off authority, and specifications written as wish lists rather than verifiable requirements.
The fix is unglamorous: one risk register, one requirements baseline, named decision owners on both sides, and a standing weekly review that the OEM's program director actually attends.
The cost comparison nobody runs
Internal development looks cheaper because headcount is already on the books. The honest comparison includes the opportunity cost of the programs that internal team is not running, the ramp time for disciplines the OEM does not currently staff, and the redundancy cost after SOP.
On the programs we see, an outside team is usually cost-neutral to modestly cheaper — and materially faster, which is normally the number that matters.
Working on a program like this?
We help OEMs and venture-stage teams take EV programs from sketch to production.
Talk to LAND Labs