Why the capability gap is widening across automotive and defence, and what leaders are doing about it.
In automotive and defence alike, the products that matter are no longer defined by hardware. They are defined by software, integration, and the discipline to keep complex systems working over decades. Yet across our research, one pattern emerges with striking consistency: the integration layer that makes everything else possible is rarely owned at C-level.
We call this pattern the capability gap, the distance between what a system is claimed to do and what it actually does when it matters. It widens silently across the lifecycle of every complex platform. Five findings describe where it lives, how it manifests, and what closing it requires.
Five patterns recur across software-defined platforms in automotive and defence — from integration discipline and release readiness to over-the-air updates, lifecycle governance and sustainment.
Most mission-critical platforms involve 100 to 300 software and hardware suppliers. Each is held accountable for its own performance. Almost none are held accountable for how their work behaves together. The integration layer sits between functions and below the visibility of most boards, until it fails.
For automotive, software-defined aftermarket is projected to become the largest single revenue stream within a decade. For defence, sustainment already represents 60 to 70% of total programme cost. In both cases the economics depend on the integration discipline established during development.
Over-the-air updates in automotive and capability updates in defence share the same structural challenge: synchronised understanding of what is in the field, what is being introduced, and what can be verified before release. The common cause is not engineering capability. It is integration governance.
Swedish automotive engineering talent has been migrating into defence at an accelerating rate since 2023. Mission-critical software competence is becoming sector-agnostic, and organisations treating it as a hardware-era specialty will lose talent to those treating it as a strategic discipline.
The consistent C-level pain is not a lack of testing. It is the absence of objective insight into how the system will behave once it leaves the lab. This is the difference between assurance and audit, the gap most organisations have not yet closed.
The full preview goes deeper: the industry context, six starting moves leaders are taking this quarter, and the technical foundation behind them. Enter your work email and we'll send it over.
Diadrom is a Swedish systems integrator building mission-critical software for automotive and defence. From Gothenburg, we work where software-defined platforms are made measurable, testable and traceable — the integration discipline, release readiness and lifecycle governance that keep complex systems working long after they ship. Diadrom Holding AB (publ) is listed on Nordic Growth Market (NGM) as DIAH.