Rivian’s software chief thinks you don’t need CarPlay or buttons
Rivian's chief software officer Wassym Bensaid leads a $6 billion joint venture with Volkswagen (RV Tech) that will supply the operating system and electrical architecture for every future VW Group EV, including Audi and Scout. The partnership must preserve Rivian's distinctive software culture while sharing core technology across both companies. Simultaneously, Rivian is launching its AI-powered Rivian Assistant in R1 vehicles and preparing the more affordable R2 on the new shared architecture—
Deep Analysis
The RV Tech Joint Venture: Culture as the Core Asset
The article reveals something counterintuitive: Volkswagen invested nearly $6 billion not primarily for Rivian's codebase, but for its software engineering culture. Bensaid repeatedly frames the joint venture's central challenge as preserving the speed, autonomy, and iterative mindset that define Rivian's software team. This is remarkable because it suggests that in the EV era, organizational DNA may be more valuable than intellectual property. A legacy automaker with decades of institutional inertia essentially acknowledged it cannot internally replicate the way a smaller company builds software, so it bought access to that way of working.
Boundary Drawing: What Stays Rivian-Only vs. What Gets Shared
One of the article's most revealing tensions is the deliberate effort to define what parts of Rivian's software remain exclusive to its own vehicles versus what migrates into the shared RV Tech platform serving VW Group brands. This is a classic co-opetition problem:
- Shared layer: Core electrical architecture, zonal architecture, foundational operating system — the plumbing that runs beneath every vehicle
- Rivian-exclusive layer: Brand-specific experiences, user-facing features, and products like the Rivian Assistant
The strategic logic is clear: Rivian gets massive scale and revenue from VW's investment, while VW gets modern software infrastructure. But the differentiation boundary is where competitive advantage lives. Drawing that line too broadly in either direction could either commoditize Rivian's brand identity or starve VW of the features it paid for.
The Agentic Bet: Rivian Assistant as Platform Strategy
The Rivian Assistant launch is positioned not as a mere feature but as the opening move toward an agentic software platform — cars that anticipate needs, execute multi-step tasks, and behave more like intelligent assistants than passive dashboards. Bensaid's framing suggests Rivian sees the vehicle's software layer as a long-term revenue and engagement platform, analogous to how smartphones evolved from communication tools into app ecosystems. The fact that the interviewer found it simultaneously "powerful" and "frustrating" signals this is genuinely early-stage — functional enough to demonstrate potential, immature enough to generate friction. This is exactly the position a platform needs to be in during its first iteration.
The Apple CarPlay Question: Strategic Refusal
The article makes clear that despite persistent user demand, Bensaid remains uninterested in supporting Apple CarPlay and Android Auto. This is not a technical limitation but a deliberate strategic choice. By keeping the infotainment layer in-house, Rivian maintains control over the data, the user relationship, and the agentic future it's building toward. Integrating CarPlay would mean ceding the most user-visible layer of the software stack to Apple — precisely the layer where Rivian wants to build its platform moat. The "don't get your hopes up" line signals this position is firm, regardless of consumer pressure.
Buttons as Anomaly: A Philosophical Commitment to Software-First
Bensaid's long-standing view that physical buttons in cars are "just an anomaly" reflects a deeper philosophical alignment with Tesla's approach: the car is a software platform, and physical controls are legacy artifacts from an era of limited computing capability. This stance is risky — many users and safety advocates push back on touch-screen-dependent interfaces — but it's internally consistent with Rivian's entire architecture philosophy. If you believe the car's intelligence should be adaptive, contextual, and continuously updated, then fixed physical buttons become dead weight.
The Fractal Decoder Problem
The interviewer's observation about "fractal" organizational complexity is apt. Bensaid simultaneously navigates: Rivian's internal software roadmap, RV Tech's cross-company architecture work, the cultural integration challenge with VW, and the emerging AI platform strategy. Each layer contains its own set of stakeholders, timelines, and trade-offs. The fact that one person holds coherence across all of these suggests either extraordinary organizational talent or a structure that hasn't yet been stress-tested at full scale — likely both.
Disclaimer: The above content is generated by AI and is for reference only.