Mercedes-Benz is working towards shorter vehicle development cycles as it advances its software-defined vehicle (SDV) strategy, with a focus on separating technology platforms from individual vehicle programmes. The approach is intended to allow hardware, software and vehicle development to progress at different speeds, enabling the company to introduce new products and features more frequently.
Speaking exclusively to Autocar Professional on the sidelines of Vector Informatik’s NEXT HORIZONS 2026 event in Germany, Steffen Tacke, Director R&D, Mercedes-Benz AG, said traditional vehicle development cycles can range from 44 to 60 months, while newer automotive manufacturers are working with considerably shorter timelines.
Tacke referred to development cycles of 36 months and even 18 months among newer manufacturers, with the possibility of reducing them further to 12 months in the future. He said the industry needs to separate the development of technology platforms from individual vehicles to achieve faster product development.
“We need to separate parts. We need to have some things that have a different cadence, like a platform, like a technology platform, and some things, which is the product itself, which can be developed very fast out of the given platform,” he said.
Tacke compared the approach with Apple’s technology ecosystem, where hardware, operating systems and applications evolve through different development cycles. He said a similar structure in automotive engineering would allow manufacturers to develop new products and introduce software features without having to change the underlying technology platform at the same pace.
Asked whether faster vehicle launches were becoming a priority for automakers, Tacke said, “Faster time to market. With new features, with new products, absolutely.”
“We have beautiful cars, and I like them every four or five years to see a new beautiful car. But I would love to have us, let’s say, even in two years, a new car, which shows, let’s say, what we can do,” he said.
He added that new capabilities need not always involve changes to vehicle design. Software features could evolve more frequently, allowing manufacturers to introduce improvements during a vehicle’s lifecycle.
MB.OS Development
Discussing Mercedes-Benz Operating System (MB.OS), Tacke said the company has established the ability to develop, standardise and deploy its operating system across its vehicle portfolio.
“What we have achieved is, let’s say, the realisation of a software-defined vehicle. So we know how to create the operating system. We know how to standardise it, know how to roll it out over a whole fleet,” he said.
The next phase will involve separating the underlying technology platform from individual vehicle programmes, allowing different product categories and technologies to evolve according to their respective development cycles.
Tacke said Mercedes-Benz has already demonstrated a fully realised software-defined vehicle, referring to the vehicle showcased at the event. The company is continuing to develop its software capabilities, with greater integration of digital services and customer applications forming part of the next stage.
He cited music and video streaming services as examples of how customers increasingly expect digital experiences to continue across different devices. Bringing similar continuity into vehicles would require closer integration between software systems and the wider digital ecosystem.
According to Tacke, achieving this will depend on creating software architectures that allow application developers to access underlying technologies through standardised interfaces. This would enable developers to create customer-facing functions without having to work directly with every element of the vehicle’s technology stack.
He also highlighted the importance of platform-based development, where software applications can be developed and updated independently of the underlying hardware.
Supplier Collaboration
Tacke said suppliers will continue to play an important role as Mercedes-Benz develops its software-defined vehicle architecture. He emphasised the importance of involving technology partners early in the development process and maintaining close technical collaboration.
“That’s exactly the point about partnering, about engaging early with them, into deep exchange on what needs to be done,” he said.
He added that Mercedes-Benz would look to work with suppliers capable of contributing to its future technology development and helping the company address evolving engineering requirements.
The transition towards software-defined vehicles will also require manufacturers to adopt different approaches to organising vehicle development. Tacke said technology platforms, software applications and individual vehicle programmes would need to follow different development cycles, allowing manufacturers to respond more quickly to changes in technology and customer requirements.
“Recognise where you are today and disrupt,” Tacke said, adding that the world is changing faster than many anticipate.