The numbers tell a story that boardrooms can no longer ignore.
In September 2025, Bosch announced plans to cut 13,000 positions in Germanyâ10% of its domestic workforce. Days later, ZF Friedrichshafen revealed 7,600 job cuts in its electrified drivetrain division alone, with total reductions potentially reaching 14,000 by decade's end. Continental is shedding 7,150 positions globally. These aren't isolated restructuring events. They're symptoms of a fundamental shift in how value flows through the automotive supply chain.
The uncomfortable truth? The era of steady growth for Tier-1 suppliers is over. As Roland Berger and Lazard concluded in their Global Automotive Supplier Study 2025: "We believe that a more volatile environment will continue to put pressure on earnings and profits."
The Core Problem: Tier-1 suppliers are being squeezed from above by OEMs pulling software in-house, and from below by semiconductor and software platform providers capturing architectural control. The result is a structural margin crisis that no amount of traditional cost-cutting can solve.
The Uncomfortable Sandwich
For decades, Tier-1 suppliers occupied a privileged position. They mastered complexity, delivered integrated modules, and often captured better margins than the OEMs they served. "Black boxes" were toleratedâdeliver the function, keep the IP, transparency optional.
That model is collapsing.
Top-Down Pressure from OEMs
Open software architectures are becoming the new baseline. OEMs are pulling software layers, user experience, data, and over-the-air update capabilities in-house. They're demanding visibility into what was once proprietary. Roland Berger reports that in-vehicle software budgets have risen nearly 50% since 2021, reaching $38 billion by 2025âwith projections of $59 billion by 2030. OEMs aren't spending that money to remain dependent on suppliers.
Bottom-Up Pressure from Platforms
Perhaps more threatening: SoC providers like Qualcomm, NVIDIA, and Horizon Robotics increasingly define the rules of the game. They're not just selling chipsâthey're selling software stacks, development tools, and reference architectures. Meanwhile, solution houses and new entrants are bypassing traditional supply chains entirely, forging direct relationships with OEMs.
The net effect? Tier-1s are being asked to carry more integration risk with less architectural control. The value pools are migrating elsewhere.
The Margin Reality
| Metric | 2016-2017 | 2023 | 2024 | Change |
|---|---|---|---|---|
| Global Supplier EBIT Margin | 6.7% | 5.3% | 4.7% | -30% |
| European Supplier EBIT Margin | 5.8% | 4.2% | 3.6% | -38% |
| Chinese Supplier EBIT Margin | 5.5% | 5.5% | 5.7% | +4% |
| South Korean Supplier EBIT Margin | 5.0% | 3.8% | 3.4% | -32% |
Source: Roland Berger/Lazard Global Automotive Supplier Study 2025
The data tells a clear story: Western suppliers are suffering. European margins have dropped 38% from pre-COVID levels. And these aren't cyclical dipsâthey reflect structural changes in how the industry operates.
Key Insight: Chinese suppliers recorded the healthiest EBIT margins in 2024 at 5.7%, while European (3.6%) and South Korean (3.4%) suppliers are falling behind. The competitive pressure isn't coming from traditional rivalsâit's coming from an entirely different operating model.
The Software-Complexity Trap
At the heart of the margin crisis lies an efficiency problem that few suppliers have solved: the growing gap between software complexity and development productivity.
McKinsey's 2025 analysis reveals a stark imbalance: software complexity is growing at 40% annually, while productivity gains remain stuck at just 6%. Over the past decade, this has compounded to a 4Ă growth in complexity against only 1.0-1.5Ă productivity improvement. For complex modules like infotainment and ADAS, productivity is 25-35% lower than traditional embedded software.
For a deeper dive into how this complexity-productivity gap impacts requirements and testing, see our analysis: The $1.35 Trillion Requirements Crisis.
Modern vehicles contain over 100 million lines of code distributed across 70-100+ ECUs, exchanging up to 2 million messages per minute. As one company leader warned McKinsey: "Software maintenance alone will rapidly use up all software R&D resources if complexity continues to grow while productivity remains unchanged, leaving little room for innovation."
The testing burden alone is staggering. For a complete analysis of how testing costs are impacting automotive development, see: Testing Consumes 20-30% of Automotive Budgets: The Efficiency Imperative.
The Three Futures
Every Tier-1 is being pushed toward one of three futures. The question is whether you choose deliberatelyâor let the market choose for you.
đ Integrator
Own architecture, validation at scale, and lifecycle delivery. Become an indispensable partner, not a replaceable vendor.
- Control E/E architecture decisions
- Own validation and certification
- Deliver OTA update capability
- Capture recurring software revenue
đŻ Specialist
Own a defensible module or stack with real IP advantage that can't be easily replicated or commoditized.
- Deep domain expertise (ADAS, battery, etc.)
- Protected IP and algorithms
- Unique manufacturing capability
- Premium margins on differentiated value
â ïž Commodity
Win on cost, capacity, and manufacturing excellence alone. The default pathâand the slowest death.
- Race to the bottom on price
- Squeezed margins every contract cycle
- Easily replaceable by competitors
- No leverage in negotiations
The Critical Insight: Both the Integrator and Specialist paths require one thing in commonâsoftware efficiency. You cannot own architecture without mastering software delivery. You cannot maintain IP advantage without rapid, compliant development cycles. The path to survival runs through software.
The Efficiency Imperative
Here's what the research shows about the efficiency opportunity:
McKinsey's January 2025 analysis of generative AI in automotive software development found that product managers with access to the right AI tools could save up to 39% of time spent creating and refining requirements. Quality assurance measures showed 44% productivity improvement when using AI for test creation and automation.
A German Tier-1 supplier achieved 70% productivity gains using AI to generate test vectors for full branch coverage and MCDC testingâincluding human review time. Requirements engineering showed 30% productivity improvements.
A German OEM implementing compliance copilots realized 20% efficiency gains and eased workloads for several hundred engineers, with continuous enhancements for ISO norm checking contributing additional time savings.
"Overall, the introduction of a standardized, state-of-the-art development toolchain is a key enabler to unlock 30 to 40 percent of productivity potentials from automated testing and agile methods." â McKinsey, "When Code is King: Mastering Automotive Software Excellence"
The Chinese Speed Advantage
China's new EV-focused automakers have slashed development time to approximately 24 months from concept to launchâhalf the 40-50 months required by traditional OEMs. They achieve this through:
- 65% virtual testing (vs 40-50% in other regions)
- 75% test automation (vs ~66% elsewhere)
- Centralized E/E architectures with software decoupled from hardware
- Smaller, focused product portfolios reducing complexity
McKinsey estimates that maximizing virtual testing can cut physical prototypes required by 50%. Some Chinese companies are pushing through new e-drive platforms within two years at 20-30% of the cost of conventional European suppliers.
Where to Focus: The High-Impact Opportunities
Not all efficiency investments are equal. Here's where the research shows the highest returns:
1. Requirements Engineering Automation
McKinsey surveys show requirements engineering is the most frequently targeted area for AI application in automotive R&Dâand for good reason. Poor requirements are the root cause of 56% of software defects, and fixing defects in production costs 30-100Ă more than catching them at requirements stage.
2. Documentation and Compliance Automation
Administrative costs can be lowered by using AI to complete documentation tasks required by regulations (ISO 26262, ASPICE, ISO 21434), freeing developer capacity. One McKinsey-cited copilot automatically extracts norms from ISO documents, consolidates them, and checks for adherenceâreducing compliance preparation time significantly.
3. Test Generation and Validation
Testing and homologation processes show 20-30% improvement potential through automated reporting and scenario-based simulation. The 70% productivity gain achieved by a German Tier-1 in test vector generation demonstrates what's possible.
4. Traceability and Gap Detection
Architecture erosionâwhere implemented code gradually drifts from designed architectureâis one of the most common ASPICE audit findings. Software architecture "suffers from the lack of proper documentation, leading to heightened risks of architectural drift and erosion, as well as increased costs and a decrease in software quality."
The new ISO/PAS 8926 standard specifically addresses pre-existing software qualification, making traceability even more critical. Learn how this impacts legacy code documentation: ISO/PAS 8926: The Documentation Crisis in Pre-Existing Software Qualification.
The Opportunity: AI-powered gap detection between code and documentation can identify compliance issues before audits, reduce rework, and ensure traceabilityâthe foundation for both Integrator and Specialist positioning.
The Cost of Inaction
The consequences of software inefficiency extend far beyond slow development cycles:
- 44% of 2024 vehicle recalls were software-relatedâ15 million vehicles in the US alone
- Software recalls surged 80% from 2023 to 2024 (112 to 202 cases)
- $64.8 billion in global warranty reserves in 2023âa record high
- Top 7 OEMs spend âŹ25+ billion annually on recalls, breakdowns, and quality issues
Ford projected $5 billion in costs for 2025 related to quality issues. The Boeing 737 MAX software-related failures exceeded $27.8 billion. These aren't just OEM problemsâthey flow directly to suppliers who lack the documentation and traceability to demonstrate compliance.
How GapLensAI Helps Tier-1s Escape the Commodity Trap
The path to Integrator or Specialist status requires mastering software efficiency. GapLensAI provides continuous gap detection as an integral part of your development processâkeeping code synchronized with the left side of the V.
Gap Detection in CI/CD
Every commit checked for documentation-code drift. Quality is built-in, not audited-in at the end.
Code-to-Requirements Traceability
Automated bidirectional traceability ensures every code element maps to requirementsâthe foundation OEMs demand.
Audit Firefighting
When docs stay in sync with code continuously, audits become status checksânot scrambles to reconstruct missing evidence.
Documentation Sync Status
Always know if your SRS, SAD, and SDD are in sync with code. Fix gaps when they're small, not when auditors find them.
The V-Model Advantage: Left Side Quality Enables Right Side Automation
The automotive V-model depends on high-quality documentation on the left side (requirements, architecture, design) to enable effective testing on the right side. When documentation drifts from code, test automation failsâregardless of how sophisticated your testing tools are.
GapLensAI keeps code synchronized with the left side of the V:
- Requirements (SRS) stay aligned with implemented functionality
- Architecture (SAD) reflects actual component relationships
- Design (SDD) matches code implementationâno drift, no gaps
The Result: High-quality left side documentation enables AI-powered test automation at scale on the right sideâtest case generation, coverage analysis, and regression testing that actually work.
Legacy & Platform Software: Document Generation per ISO/PAS 8926
For pre-existing software that lacks documentationâplatform code, legacy modules, acquired IPâISO/PAS 8926 requires documentation to be reconstructed. This is the one scenario where document generation is appropriate:
- Generate Missing Documentation: Create SDD, SRS, and SAD from existing code with 100% traceabilityâturning legacy code into documented, auditable assets per ISO/PAS 8926 requirements.
- Establish the Foundation for Active Development: Once documentation exists, switch to gap detection modeâkeeping docs and code in sync as the platform evolves.
- Enable AI Test Automation: With high-quality documentation in place, AI testing tools finally have the inputs they need to generate test cases, analyze coverage, and automate regression.
- Qualify for Reuse Across Programs: Documented platform software can be reused across vehicle programs without re-qualificationâthe ROI that justifies the initial documentation investment.
The Bottom Line: For active development, GapLensAI detects gaps continuouslyâkeeping code and documentation in sync so quality is built-in, not audited-in. For legacy code per ISO/PAS 8926, GapLensAI generates the missing documentation that unlocks platform reuse and AI test automation.
The Path Forward
Surviving the Tier-1 squeeze requires a deliberate strategy built on software efficiency:
1. Choose Your Future Deliberately
Decide whether you're pursuing the Integrator or Specialist path. Each requires different investments, but both depend on software capability.
2. Automate the Efficiency Bottlenecks
Focus on requirements engineering, documentation, test generation, and complianceâthe areas with highest proven ROI.
3. Invest in Traceability Infrastructure
Bidirectional traceability from code to requirements is no longer optional. It's the foundation for audit readiness, change management, and OTA update capability.
4. Build AI-Augmented Workflows
The 30-70% productivity gains documented by McKinsey require more than toolsâthey require integrated workflows with human-in-the-loop validation for safety-critical outputs.
5. Close the Complexity-Productivity Gap
Chinese competitors have demonstrated that 24-month development cycles are possible. The gap isn't in talentâit's in process efficiency and tooling.
"Suppliers must refocus on product segments and technologies where they can maintain sustainable competitiveness, while exiting areas where they lack a clear right to win." â Christof Söndermann, Managing Director, Lazard
Conclusion: Efficiency Is the New Moat
The Tier-1 supplier industry is undergoing a structural transformation that cannot be reversed. The old model of capturing value through complexity and opacity is ending. The new model rewards speed, efficiency, and demonstrable compliance.
The suppliers who surviveâand thriveâwill be those who master software efficiency. Not as a cost-cutting measure, but as a strategic capability that enables them to choose the Integrator or Specialist path rather than defaulting to commodity status.
The data is clear. The path is visible. The only question is execution.
Author: Krishna Koravadi
References
- Roland Berger & Lazard, "Global Automotive Supplier Study 2025," May 2025. Link
- Bain & Company, "Automotive Profitability: How OEM and Supplier Margins Are Faring," Q3 2025. Link
- McKinsey & Company, "From Engines to Algorithms: Gen AI in Automotive Software Development," January 2025. Link
- McKinsey & Company, "Automotive R&D Transformation: Optimizing Gen AI's Potential Value," February 2024. Link
- McKinsey & Company, "When Code is King: Mastering Automotive Software Excellence," February 2021. Link
- McKinsey & Company, "Automotive Product Development: Accelerating to New Horizons," August 2025. Link
- Oliver Wyman, "How Automotive Suppliers Can Navigate Key Challenges in 2025," February 2025. Link
- Automotive Manufacturing Solutions, "German Auto Suppliers Cut 20,600 Jobs," October 2025. Link
- Roland Berger, "Driving the Future: Commercializing Automotive Software," 2025. Link
- MHP Consulting, "The Uncomfortable Sandwich: Tier-1 Supplier Positioning," LinkedIn, 2025.
- NHTSA Recall Data, 2024 Calendar Year Analysis.
- Capgemini World Quality Report 2024-25.