The software-defined vehicle has become a central test for Germany's car industry because more value is shifting into operating systems, driver assistance, connectivity and over-the-air updates. Hiring more software engineers is only part of the answer.
What the evidence establishes
Software spending does not prove software quality. Carmakers must integrate code with safety-critical hardware, supplier modules and long product cycles. Organisational boundaries can slow delivery even when individual teams are strong.
The commercial reading
The competitive gap is partly architectural. A simpler electronics stack reduces integration work and allows features to be updated more quickly. Legacy supplier structures and model-specific systems make that transition harder.
What to watch next
Follow platform consolidation, update frequency, software revenue and development delays. Judge progress by deployed capability rather than programme names or headcount announcements.
How to use this analysis
Automotive evidence crosses registrations, production, deliveries, revenue and cash. Those measures differ when vehicles are imported, exported or sold through joint ventures. Model mix, incentives and plant allocation can move earnings even when unit volumes look stable, so no single series should carry the whole conclusion. Wolfsburg is closely tied to Volkswagen, but consolidated group sales and employment are not municipal economic statistics.
Source and verification note
The reporting base for this article is Volkswagen Group reports and Mercedes-Benz Group reports and BMW Group reports. The link is provided to the source page or release so readers can check the reporting period, definitions and later revisions. Figures are not extended beyond the source's geographic or institutional scope, and forecasts remain labelled as expectations until an official release records the outcome.