ConfX Global
InsightXOverviewReportsSector BriefingsLeadership PulseKnowledge SessionsInterviewsArticlesTools
Sector briefing · Digital transformation

Software-defined vehicles change the value chain

New revenue models and the skills automakers are hiring for.

ConfX editorial24 July 20263 min readAutomotive and mobility
Download PDF

Why it matters

Vehicles are increasingly defined by software that can be updated over the air, with centralised computing replacing many separate control units. This changes how carmakers develop vehicles, work with suppliers and earn revenue after sale.

The shift affects organisation as much as technology. Carmakers need software release processes, cybersecurity management and long-term support for vehicles in the field, while suppliers move towards software and integration roles.

By the numbers

72%of consumers in China would keep a vehicle longer if it received regular over-the-air updates 1
52%of US consumers say the same, and 36% in Germany 1
73%in China would pay extra for connected emergency assistance, against 58% in the US 1
Would keep a vehicle longer with regular over-the-air updates
India
84%
China
72%
Southeast Asia
72%
South Korea
59%
US
52%
UK
47%
Germany
36%
Japan
32%
Source: Deloitte, 2026 Global Automotive Consumer Study, January 2026

What's changing

  • Centralised electrical architectures reduce the number of electronic control units.
  • Over-the-air updates allow features and fixes after delivery.
  • Carmakers are building in-house software capabilities and new supplier partnerships.

How leaders are responding

  • Separating hardware and software development cycles.
  • Investing in software talent, tooling and platform teams.
  • Testing paid features and subscriptions carefully against customer expectations.

What good looks like

  • A central vehicle architecture that can be updated over the air
  • Software teams organised around features customers pay for
  • Clear revenue models for features after the point of sale

What to watch

  • Consolidation of vehicle operating systems and middleware.
  • Over-the-air update rules and type-approval practice.
  • New partnerships between carmakers and technology companies.

Where to start

Define which customer experiences depend on software you control, and align architecture and sourcing decisions to those experiences.

Questions for your leadership team

  1. Which software capabilities should we own, and which should we source?
  2. How do we validate and certify frequent updates?
  3. Which services after sale will customers value enough to pay for?