EN
11 June, 2026

Building With Customers, Not For Them: How Cross-Program Collaboration Drives Automotive AI Innovation

Blog Series: The Value between the lines — Part 2 of 6

This is the second article in a six-part series exploring the capabilities that distinguish leaders in automotive AI — the technical, organizational, and ecosystem factors that financial metrics alone don’t capture. Read the first part here. 

Some of the most interesting developments in automotive AI happen when the same technology is applied in different ways. A capability designed with one specific use case in mind may later be seen through a completely different lens in another vehicle program, opening the door to applications or possibilities that were not obvious at the start. 

Through these collaborations, something powerful often happens. Customers bring fresh perspectives that reveal new dimensions of what technology can do. The most effective partnerships go beyond transactional exchanges and become collaborative problem-solving efforts, where technology providers and customers work side by side to explore solutions that work not only for one program, but across many. 

Over time, this process begins expanding the technology itself. A capability that may have started with a very narrow purpose can gradually evolve into something much broader as it is integrated across different customers, architectures, and interaction models. And in some cases, entirely new use cases begin emerging that were never part of the original design intent. 

Different Programs Reveal Different Possibilities 

Working across many vehicle programs simultaneously creates a unique kind of development environment. Different manufacturers often approach the same technology from very different perspectives. One OEM may focus heavily on safety and regulatory readiness, while another is more interested in user experience, HMI interaction, or how the system fits into a broader software-defined vehicle architecture. 

When those perspectives begin overlapping across multiple programs, technology often start evolving much faster than it would within a single customer integration alone. 

Eye tracking is a good example of this. In one context, gaze may initially be used to support driver monitoring and distraction detection. In another, the same underlying capability may begin supporting interaction with displays, contextual awareness, or adaptive HMI experiences. Even within the same organization, different teams may end up applying the same underlying technology to very different challenges. As those integrations expand across programs, the technology itself can also begin expanding into broader applications. 

How Cross-Program Collaboration Accelerates Innovation 

In some cases, those developments create entirely new opportunities. Smart Eye’s in-car AI assistant Sheila is one example of how technologies and insights from different domains begin combining into something larger. By combining in-cabin sensing, driver monitoring, emotion sensing AI, and generative AI, Sheila is able to interact with occupants based on real-time awareness of attention, activity, and behavior inside the vehicle. 

The underlying technologies already existed independently. But applying them across different vehicle programs, sensing systems, and interaction models helped create entirely new ways for AI systems to interact with vehicle occupants. This is one of the reasons cross-program collaboration becomes such an important driver of innovation. The value is not only in solving the immediate challenge in front of a single customer, but in applying lessons, integrations, and capabilities across many different environments – allowing technologies to evolve beyond their original purpose. 

Innovation Does Not Happen in Isolation 

For Smart Eye, this process is also accelerated by the fact that we operate across multiple technology areas and business domains simultaneously. Insights from automotive programs influence other parts of the company, while experience from eye tracking research, multimodal behavioral studies, and human-machine interaction research feeds back into automotive applications. 

That broader exposure creates opportunities to combine technologies and perspectives in ways that would be difficult inside isolated product teams or individual customer programs. Capabilities evolve not only as they’re applied across more vehicle programs, but through interaction with entirely different research areas, industries, and use cases. 

Where Cross-Program Experience Leads Next 

Working across many vehicle programs simultaneously also changes how we approach platform development over time. Instead of solving the same challenges repeatedly for individual programs, insights from across customers, integrations, and regions continuously feed back into the broader technology roadmap. 

Real-world deployments, ongoing customer conversations, and evolving integration challenges all contribute to shaping where the technology goes next. Some capabilities become more refined and scalable over time. Others expand into broader applications or create entirely new opportunities that were not visible in the original use case. 

As a result, rather than relying on abstract predictions about where the industry might go, Smart Eye’s roadmap is shaped by how these technologies are actually being applied, adapted, and expanded across real vehicle programs and real-world environments. 

Matt Remijn

Written by: Matt Remijn

VP of Product – Automotive Solutions at Smart Eye, with over 20 years of experience bringing complex technology products to market across automotive, defense, and industrial automation. Before Smart Eye, he held senior product roles at Xperi and Gentex Corporation, where he led cabin sensing and biometrics product lines. In this series, he draws on that experience to explore what it really takes to bring driver and cabin monitoring technology into production at scale.

Back to top