Rivian's software chief thinks you don't need CarPlay or buttons

28 May 2026 · 1 h 10 min · 19 chapters

Ask about this episode

Ask anything about it. ChatGPT or Claude reads this page and answers with the times it was said.

Connect VO and ask about every podcast you hear, including the moments you saved. Add to ChatGPT · Add to Claude

In short

Rivian’s Chief Software Officer Wasim Ben-Sayed explains Rivian’s software-defined vehicle approach, the Rivian–Volkswagen joint venture (RV Tech) structure, and the AI-powered Rivian Assistant—especially why it won’t use CarPlay/buttons and how “agentic” voice works.

Guest backgrounds

Wasim Ben-Sayed is Rivian’s Chief Software Officer and co-CEO of RV Tech, a Rivian/Volkswagen platform joint venture. RV Tech is responsible for the electrical architecture and operating system for future Volkswagen Group EVs (including Audi and Scout). Co-CEO is Volkswagen CTO Karsten Helbing.

Key claims

  • Legacy automakers can’t integrate end-to-end features fast enough due to many suppliers/ECUs; zonal computers centralize control.
  • Volkswagen’s JV succeeds because it’s a clean-sheet cultural and talent shift, not “band-aids.”
  • RV Tech builds 80–90% of the platform; brands customize via hooks.
  • Rivian Assistant is integrated “connective tissue,” not a chatbot overlay; safety-regulated functions are blocked.
  • Voice should be primary; buttons are an “anomaly,” and foundational models enable conversational control.
  • Assistant can run locally/edge (R2: up to 200 sparse TOPS) and in the cloud depending on task.

Notable examples

  • Digital key + lighting + profile setup in ~15 seconds.
  • Assistant can change drive mode/ride height, but won’t control wipers (safety block).
  • Assistant refused a back-seat sensor detail (described as a bug).
  • Google Calendar agent flow: QR pairing, reading/adding/removing events, then text/summary actions.

Written by AI. May contain mistakes. Listen to the episode to check what was said.

Chapters

Tap a time to open that second in VO

Rivian's Unique Software Culture and Joint Venture

3:50 to 6:40

Exploration of Rivian's software culture and its joint venture with Volkswagen.

“You're the Chief Software Officer at Rivian.”

The Shift to Software-Defined Vehicles

6:40 to 10:10

Discussion on the transition to software-defined vehicles and its industry implications.

“And a lot of recipes did not really work.”

Challenges and Opportunities in Automotive Software

10:10 to 14:00

Insights into the challenges legacy OEMs face in software integration and Rivian's approach.

“I mean, when you walk to your Rivian, and I know you're currently having a Gen 2 quad, you have your Apple, let's say, digital key.”

The Future of Rivian's Software Development

14:00 to 26:58

Explore Rivian's innovative approach to software and car development.

“And then you also need a deep cultural change with really very different way of approaching the car and the overall development.”

Decision-Making Frameworks at Rivian

29:49 to 30:48

Explore how Rivian's Wasim Bensayed makes effective decisions.

“I think the number one rule, I mean, obviously, my job every day is making decisions.”

The Importance of AI Development

30:49 to 33:36

Discuss Rivian's strategy on AI development versus third-party solutions.

“Show that you went through an analysis, have multiple options, and then make a recommendation.”

Rivian Assistant's Capabilities

33:37 to 36:28

Understand the features and limitations of Rivian's car assistant.

“I've been playing with it for a few days now.”

Safety and Functionality in Assistant Design

36:29 to 39:21

Examine the balance between safety regulations and assistant capabilities.

“And that's honestly, that's one of my favorite features.”

Voice Interaction in Vehicles

39:22 to 41:24

Learn about the future of voice technology in car interactions.

“system so in theory uh i mean with the integrations that we have built unless we have a bug like the one that you have, you should be able to do everything.”

Understanding Agentic Integration

41:25 to 42:05

Delve into the concept of 'agentic' in the context of Rivian's features.

“I don't need to tell the car, open the front.”
Show all 19 chapters

Future of Digital Integration in Vehicles

42:05 to 46:32

Explore how Rivian Assistant integrates with personal apps and enhances user experience.

“And I hope you tried our Google Calendar agentic integration.”

Rivian's AI-Powered Voice Assistant

48:51 to 56:01

Delve into the capabilities and future of Rivian's assistant technology.

“We're back with Rivian Chief Software Officer with Sim Ben Sayed, discussing the ins and outs of the company's new AI-powered voice assistant.”

Inference Costs and Model Architectures

56:01 to 58:30

Learn about the architecture and inference costs of AI models in vehicles.

“Because I could probably make up a spreadsheet to win an argument.”

Voice vs. Buttons in Car Interfaces

58:31 to 1:01:14

Explore the debate between using voice commands versus physical buttons in cars.

“I mean, you have to pay a monthly fee for the connectivity package to access assistant, but then I might burn way more tokens than that fee could ever pay for.”

The Case Against CarPlay

1:01:15 to 1:03:59

Discuss Rivian's stance on not integrating CarPlay and the rationale behind it.

“I have to ask you about CarPlay here because it strikes me just as you imagine this future of the car where it's connected to your calendar.”

Reimagining App Interactions in Cars

1:04:00 to 1:06:23

Understand how AI will change app interactions and user experiences in vehicles.

“is just another reason why I deeply believe that RJ and Rivian, we made the right choice in terms of investing into our own technology and our software.”

The Future of Assistant Integration

1:06:24 to 1:10:01

Learn about the potential for seamless integration of personal assistants in cars.

“So you're saying I've got, we'll use Google because Gemini is more present on an Android phone than Siri is currently on an iPhone.”

Seamless Digital Experiences

1:10:01 to 1:12:46

Explore how voice commands can create seamless integrations in digital ecosystems.

“your account is already configured, and then the assistant will pick the destination, will get you to your favorite restaurant.”

Show Closing and Listener Engagement

1:12:46 to 1:13:22

Learn how to engage with the show and the production team behind it.

“Our editorial director is Kevin McShane.”
Hear the part that matters, and keep it.Open this episode in VO. Double tap your headphones to save a moment as you listen.
Get VO free

Transcript

Automatic transcript. May contain errors.

0:00Nilay Patel:Support for this show comes from Adobe Acrobat. We all know sending a file is easy. Making sure your clients understand the file is the hard part. But with PDF spaces and Adobe Acrobat, you can give your clients the full picture with custom intros, audio summaries, and a helpful AI assistant. So if you want to stop the endless follow-ups, do that with Acrobat. Need to make your dots crystal clear? Do that with Acrobat. Want to make sure your clients get everything they need to hear? Do That With Acrobat. Learn more at adobe.com slash do that with Acrobat. Support for this show comes from Klaviyo.

0:41Nilay Patel:Imagine hiring two brilliant employees. The first takes your marketing from idea to full campaign, email, SMS, push, and the time it takes to describe it. The second handles every customer conversation 24-7, answering questions, recommending products, handling orders, both on brand and always on. Your next hires, Klaviyo's AI agents. Get started at klaviyo.com.

1:14Nilay Patel:Support for the show comes from ServiceNow. Now. AI is moving fast across the enterprise, but without visibility, it's just chaos. Different tools, different models, different teams using AI in completely different ways. ServiceNow turns that chaos into control. With the AI control tower, you see all your AI across the business in one place. What it's doing, what it's done, and what it's about to do. So you stay in control. To put AI to work for people, visit servicenow.com.

1:51Nilay Patel:Hello and welcome to Decoder. I'm Neil I. Patel, Editor-in-Chief of The Verge, and Decoder is my show about big ideas and other problems. Today I'm talking with Wasim Ben-Sayed, the Chief Software Officer at Rivian and the co-CEO of Rivian's platform joint venture with Volkswagen, which everyone just calls RV Tech. That joint venture kicked off about a year and a half ago with a nearly$6 billion investment from Volkswagen, and it effectively puts Wasim in charge of the operating system and electrical architecture for every future EV from Volkswagen and its associated brands, including familiar names like Audi, but also new companies like Scout.

2:22Nilay Patel:There's a lot of decoder ideas in there. I really wanted to know how that joint venture works, and how it's structured to preserve Rivian's unique software culture, which you'll hear Wassim talk about is the core element of the entire thing. I also wanted to know where the lines were. What parts of Rivian's software get to be just for Rivian, and which parts of the core technology are shared across both the smaller company and the behemoth that is Volkswagen crew. And, of course, I wanted to understand how Wasim navigated the tension between the two. You know, classic decoder bait. It's also a big moment for Rivian in general right now.

2:52Nilay Patel:The company is gearing up to deliver the more affordable Rivian R2, which is the first vehicle based on this new architecture, and the company also just shipped the AI-powered Rivian Assistant in its R1 vehicles. You'll hear Wasim talk about the Assistant as the beginning of a big bet for Rivian, as it tries to create a more agentic software platform in its cars. I actually got to spend some time with the Rivian Assistant in an R1S ahead of my conversation with Wasim, and I found it to be a fascinating experience. It's certainly powerful and engaging, but at the same time, it's frustrating in a lot of really interesting ways.

3:22Nilay Patel:So, of course, I had a bunch of feature requests, bug reports, and questions about the future of AI and assistants in cars. We talked about his prediction from just a few years ago that buttons in cars were just an anomaly, and of course, how he's feeling about Android Auto and CarPlay these days. You'll hear it, but spoiler alert, don't get your hopes up. This is a really fun episode of Decoder. It's really in the weeds of a lot of my favorite things to talk about. Okay, Waseem Ben-Sayed, Chief Software Officer at Rivian and co-CEO of RV Tech. Here we go.

4:04Nilay Patel:What's up, Ben Said? You're the Chief Software Officer at Rivian. You're also the co-CEO of a very important software joint venture between Rivian and Volkswagen, which is just straightforwardly called Rivian Volkswagen Group Technology. Welcome to Decoder. Thanks, Neil. I'm super excited to be I am very excited to talk to you. I have a lot to talk to you about. It occurred to me as we were doing the prep for this episode that you're in charge of building a new kind of software for cars, but also because of the joint venture in charge of building a new kind of software company that builds the new kind of software for cars.

4:34Nilay Patel:It is the most fractal decoder I think we've ever had. Awesome. There's a lot here. Let's start with the organization. So you're the chief software officer at Rivian. I think a lot of people understand what that means. You're the guy that they can yell at about CarPlay. Don't worry, we'll come to that. There's new Rivian Assistant, which is an intelligent agent inside the car that I've been playing with that I want to ask you a lot of questions about. Then there's RV Tech, which is the joint venture with Volkswagen. You're building a new zonal architecture for a bunch of cars. I believe the R2 is the first car that's going to run that new architecture.

5:09Nilay Patel:How does that all work? What are the lines between RV Tech and your role there, the co-CEO there, and your role with Rivian? And what is the boundary between the software you build in the joint venture and the software you build at Rivian? All right. Before we dive into RV Tech and the joint venture, I think it's really important to talk about the overall industry landscape. The automotive industry is really going through a major disruption. The amount of software content in the cars with technologies like electrification, connectivity, autonomy is significantly increasing. And that is creating a big divide between traditional OEMs and then new tech forward companies.

5:56And consumers now have really much higher levels of expectations in terms of the overall experience and convenience in the cars. And multiple OEMs have tried really hard to get software content, but it's not easy. It requires a very different type of talent. It requires, in some cases, really complete cultural change because you're not only developing software, but then you need to adopt different methodologies, different ways of doing things. You need to be much more agile. And when you look at the industry, companies have tried to do that in-house. Some of them tried to partner. Some of them tried to use tier ones.

6:47And a lot of recipes did not really work. And that was really the genesis of the great partnership that we have now with the Volkswagen which has really taken the Rivian technology stack, taken software, the electrical architecture, the Rivian DNA and culture as well, and then marrying that with the incredible scale that the Volkswagen Group has. And it really provides a fantastic opportunity for both companies because now we can have a solution that can not only underpin the Rivian vehicles, as you mentioned with the r2 as the first um car that the joint venture is uh shipping but then uh eventually in the future every single electric model and the vw group and think about it from your premium cars um and audi for example to luxury cars with porsche bentley lamborghini to the mass market cars.

7:52And that suddenly provides an opportunity of scale. But then also it exercises the technology in very different ways and really puts us in a wonderful position so that we can build an architecture and operating system for the entire industry.

8:12Nilay Patel:So that question of architecture and operating system, it feels very complicated. As you said, the industry is moving to software-defined vehicles, which is a great buzzword. And every car executive that I talk to very clearly has a different definition of what software-defined vehicle means. What is your definition of what software-defined vehicle means? First of all, I hate that buzzword. You brought it up. I actually, I can't find a better name. So I admit that I'm also using the same in the lack of a better definition. But think about it this way. I mean, when you look at older architecture cars, they're really an aggregation of multiple mechanical components.

9:02And then underneath that, There's, in some cases, hundreds of electronic units, which are meant, each one of them is meant to do one thing. And generally, that's actually mirroring the way those cars are built because they are developed using different tier ones and then different suppliers. And in that world, integrating an end-to-end vehicle feature requires a ton of coordination between many of those suppliers. It requires very long development cycles. And that approach kind of worked in the past when the expectations of consumers were not super high in terms of end-to-end features in the cars.

9:51But I think with the advancement of EVs, with the types of user experiences that the Teslas and the Rivians and the Chinese cars are offering now, that's no longer really an option for any car manufacturer. And I'll give you just a small example. I mean, when you walk to your Rivian, and I know you're currently having a Gen 2 quad, you have your Apple, let's say, digital key. You walk to the car, and then the car will recognize you. And then there's a lighting sequence. And then you get to the car, and your entire profile is configured. And then whether it's the seats, whether it's the steering wheel, whether it's the infotainment system, whether it's the HVAC, everything is configured for you.

10:46That sequence is probably just 15 seconds. But doing that in the traditional world requires the coordination of more than 10 different suppliers. You need to talk to the seed supplier. You need to talk to the door supplier. You need to talk to the HVAC supplier. You need to talk to the entertainment supplier. You need to talk to the security system. You need to talk to the cloud. You need to talk to the third party for the digital key. And then just imagine that for whatever reason, you want to slightly change that sequence. Then you're going again for another cycle of changes. And this is why that old model really doesn't work anymore.

11:33Cars now are integrated systems with what we call zonal computers and thinks about them as this is general purpose, powerful compute that we place in the middle of the car. And they become the centralized brain of the different functions. And then the more software you can move on those zones, the more it provides the control of those end-to-end features for the customers.

12:02Nilay Patel:So this is the pitch that every sort of pure play car startup has been making for a long time, right? The way that the OEMs built cars was dumb, and you shouldn't have 1 ,200 ECUs from 1 ,200 different suppliers. And that was fine for gas cars that were pretty dumb, where the only computer was like my old Pioneer head unit that had the screen that folded out. By the way, I love that head unit. If you could bring that back, that would be great for me. I have fond teenage memories of my dumb old car with that head unit. Now the whole cars are computers and you expect a lot of things to happen. And that integration is too hard.

12:35Nilay Patel:What I would say broadly is that the legacy OEMs have known this for years. They have been on their own journey to solve this problem, to cut down on the number of ECUs. I don't know. Jim Farley was on the show from Ford five years ago being like, too many ECUs. We're going to cut it down. and volkswagen in particular had its own giant project to do this that failed i think we can now now there's enough distance you're a year and a half into the new jv we can say karyad which volkswagen had started failed why do you think the new jv and the infusion of rivian culture is going to be successful where volkswagen's attempt to do it on its own did not meet any kind of positive results you're getting me in trouble you know that's my job that's what i do here uh i think really uh what i personally appreciate in terms of the Volkswagen group decision is the recognition that developing what is called software defined vehicles requires a complete clean sheet approach.

13:39You cannot approach it just by band-aids and then just by trying to have some level of software content into the car. And as we said, the Volkswagen Group have tried. Actually, they have tried twice. But really deep inside, there's two things which are really important here. One is you need to have talent who are able to develop true software, not abstracted functions like what the automotive industry are using with things like probably you have heard about Autazar, but like a true hand-coded operating system. And then you also need a deep cultural change with really very different way of approaching the car and the overall development.

14:34At the old traditional model, cars are defined many, many, many years in advance. People claim that they know about the software features four or five years in advance. And then it's a very fixed, waterfall approach. The way we design cars at Rivian, for example, is we actually really designed the car around the electrical architecture and around software and around the adaptability of software. So software and technology is at the table since very early. It actually impacts the overall packaging of the car. And we really use that platform and that operating system mindset so that we have a car that can evolve over time and that get better and better for our customers.

15:30And such changes are so deep where really to do it well, you either need to have the right partner or you go with a clean sheet approach. And I think the Volkswagen Group has made the right decision to really partner with Irvian in this case and not only embrace that technology that we built from the ground up, but then also embrace the culture, the approach, and then the DNA of Irvian as a company.

16:06Nilay Patel:How is the joint venture structured? I know you have a co-CEO. It's Karsten Helbing, who's Volkswagen's CTO. So you're the two co-CEOs. How is it structured underneath that? And during that, there's a technical team. So software engineering, electrical engineering, the technical team refers to me. And then Karsten is my partner in crime. He takes care of the operations. And then he's also the main interface to the Volkswagen Group. group, there's a ton of complexity in terms of managing different requirements, different inputs from the brands, really doing all that arbitration so that we continue pushing towards a platform approach.

16:44And then we reduce the overall complexity of the portfolio that we're supporting with the VW Group.

16:51Nilay Patel:So one of the questions I have here is you described it as an operating system. It seems like a good framework. People understand what operating systems are. I realize car operating systems are vastly more complex than people give them credit for, but it's an operating system. Then there's expressions of the operating system. And I know that our audience, they think of the software in the car and they think of the infotainment screen and that's it. That's just one expression, right? The user interface that Rivian is running. There's going to be other expressions for Volkswagen, for Scout, I presume for Lamborghini, all running the same core operating system expressed in different ways.

17:24Nilay Patel:That is a real push and pull dynamic, right? Where do the features live? Who gets to build what feature? What are the core capabilities of the operating system and the platform versus what does Lamborghini want that it doesn't want Rivian to have? How do you make those decisions? Yeah, great question. I mean, really, first of all, I think what's important for us is to clarify the role of the joint venture. So we're responsible of the underlying electrical architecture and then the operating system. And what that means exactly is, I mean, when you look at a modern car today, pretty much every single interaction you have with the car is powered by software.

18:05And in lots of cases, you don't realize it. I mean, people tend to associate software to the infotainment, to what they see on the UI and the screen. But there's software everywhere in the car. I mean, the way the car navigates, the way the car drives, the way the car saves energy, the way the car does cabin comfort, all of that is actually managed through software. So the way to think about this is our role is to, first of all, build an electrical architecture with as less as possible of computers in the car so that we simplify the overall packaging, we simplify the overall bill of materials.

18:42This is the brains of the system. And then on top of that, we develop software that the different brands can use so that they express their own identity. And think about it in a way where we do 80%, 90 % of the hard work. And then we provide customization hooks so that an Audi drives like an Audi and then a Lamborghini presents a different UI than a Rivian. But then what's happening under the hood, what's happening behind the scenes is based on the same platform.

19:19Nilay Patel:When you think about that underlying electrical architecture and zonal computers, and we're going to cut down the number of computers but have fewer, more powerful computers, one of the things that it seems like an obvious opportunity for Rivian and maybe way more complicated for Volkswagen is that you have a big battery that can just power those computers all the time. They can be online. They can be functional. They can be available. Volkswagen also makes gas cars and hybrids. There's some pendulum swing in the industry between electrics and gas vehicles, particularly here in the United States.

19:49Nilay Patel:Is that a challenge or are you just not thinking about their gas cars at all? The scope of the joint venture for the time being is really powering all the electric vehicles. I mean, this is the agreement that we have with Volkswagen. and honestly a big part of it is one of the main reasons personally I joined Rivian is I joined Rivian for the mission and I think the joint venture provides us with an extraordinary opportunity so that we can get this technology to accelerate electrification into many more cars around the world. One of the first products that we're building with Volkswagen Group is the ID1 which has taken our technology to a mass market vehicle.

20:36I mean, this is a car that will sell for less than$25 ,000 and really opening the technology, opening that rich feature set to many more consumers around the world. Now, can the technology be used for non-EBs? Can it be used for hybrids or eyes? Obviously, the answer is yes. But for the time being, this is not the priority of the trend venture.

21:03Nilay Patel:How big is RV Tech? How many people? We're about 1 ,500 people. And then how is that split between Rivian folks or Volkswagen folks? Are they, do you have, is it employees of both companies or are they employees of RV Tech? They are employers of RV Tech. Actually, we started with about 800, 900 developers coming from Rivian. And then we had about, call it, 50 colleagues who joined us from the Volkswagen group. And then the rest, this is developers and engineers that we hired in the past 18 months. So everybody's RV tech. The reason I ask that is you mentioned at the very beginning that it's an infusion of Rivian's culture.

21:52Nilay Patel:But now they're not Rivian employees. But then you were also the chief software officer of Rivian. How does that culture persist if the thing is its own entity and it's not as directly connected to Rivian or they're not Rivian employees? I think the way I probably define my job and probably my priority number one is help the company grow and build on our two main assets. And I think our two main assets is one, technology, and two, our people and culture. technology. I think we have a wonderful opportunity now by taking that technology into many more cars across a wide range of portfolio and trims.

22:39And then culture, that's my daily obsession, which is really making sure that we continue to have the same DNA of agility, being nimble, prioritizing, action, quick decision making, and really iterating really fast so that we are at the forefront of innovation.

23:03Nilay Patel:One of the reasons I asked that is, you know, there's Rivian decisions that maybe Volkswagen won't make. Rivians right now, they run Unreal Engine, right, is the graphics and the infotainment. It's really fun. I'm not sure that every single Volkswagen is going to run Unreal Engine, right? That's a decision that feels like, at least as I understand it, the different brands can make for themselves. But you're the chief software officer at Rivian. You're like, we need better support for the Unreal Engine interface. And then maybe the platform doesn't want that. And you wear that hat too. How do you reconcile those tensions?

23:32Nilay Patel:Does Rivian's needs always win? What wins is how can we do the software in a way that allows different expressions? And I think in this case, Rivian's interface will show up through Unreal Engine, but then we need to have hooks in our framework. So that's a question. I know you will ask me that Volkswagen cars can have CarPlay and the team will develop that even though Rivian will not adopt CarPlay. So it's really about creating those different hooks into the operating system so that we allow different ways to express the user interface. It strikes me, just talking to you about this, that there aren't a lot of models in an industry as big as the auto industry like this, where the big player is letting the smaller company define the culture and the opportunity, define the architecture, which will define its roadmap in the future.

24:34Nilay Patel:What things have you looked at that are similar that you say that's successful, we should build the model based on this and operate like this? And what versions of this have failed that you've looked at where you're like, I want to avoid those mistakes? Yeah, great question. And I think lots of people look at joint ventures, and I think there's probably maybe more failure stories than success stories. And this has been really one of the guiding principles. And we spent a lot of time discussing with the VW leadership before we engaged in such partnership. Now, really what made RJ and myself lean heavily into this partnership is one, the opportunity.

25:16and then to the honest and constructive partnership from the Volkswagen Group leadership. I mean, first of all, we are talking about taking the Rivian technology into the second largest OEM in the world. This is by far the biggest licensing deal in the automotive industry. And as RJ and I started the discussions with Oliver Blumer, his number one priority was we need to keep the Rivian way of doing things. We realized that you are bringing not only a software IP, you are bringing not only an electronics IP, but you are bringing a different process. You are bringing a different culture. And we need that change from the inside for the VW group.

26:17And I think across the past 18 months, I mean, obviously, in some cases, there are daily tensions. I mean, there are cases where, as you mentioned, one brand might request a different requirement than another brand. But what really helped us to continue is that support that we have from the highest levels of the leadership in the Volkswagen group to really help drive that transformation and that cultural change in the group.

Read the full transcript

26:47Nilay Patel:We need to take a quick break. We'll be right back.

26:58Nilay Patel:support for this show comes from shopify starting something new isn't just difficult sometimes it can be truly intimidating you're putting in all of this time and energy without knowing for sure if it's going to pay off but there's always another way to look at it what if it does work what if your gut has been right the whole time that's where shopify comes in Shopify powers millions of businesses around the world and accounts for nearly 10 % of all e-commerce in the U.S. Everything from established names like Allbirds and Heinz to brand new businesses just starting out. Their design tools make it easy to build exactly the kind of online presence you're imagining.

27:37Nilay Patel:With hundreds of templates ready to go. And with built-in marketing features, you can spin up email and social campaigns in just a few clicks. So you're reaching customers where they already are. Start your business today with the industry's best business partner, Shopify, and start hearing. Sign up for your$1 per month trial today at shopify.com slash decoder. Go to shopify.com slash decoder. That's shopify.com slash decoder.

28:12Nilay Patel:Support for this show comes from Adobe Acrobat. We all know sending a file is easy. Making sure your clients understand the file is the hard part. But with PDF Spaces and Adobe Acrobat, you can give your clients the full picture with custom intros, audio summaries, and a helpful AI assistant. So if you want to stop the endless follow-ups, do that with Acrobat. Need to make your dots crystal clear? Do that with Acrobat. Want to make sure your clients get everything they need to hear? Do that with Acrobat. Learn more at adobe.com slash do that with Acrobat. Support for this show comes from Doppel.

28:53Nilay Patel:Maybe that ping you just got is an urgent message from your CEO. Or maybe it's a deepfake trying to target your business. Doppel is the AI-native social engineering defense platform fighting back against impersonation and manipulation. As attackers turn to AI to power increasingly sophisticated strikes, Doppel uses it to fight back. Their digital risk management dismantles attacker infrastructure, while human risk management builds team resilience through simulation and training. With automated takedowns, multi-channel coverage, and AI defenses that build intelligence with every fight, Doppel works relentlessly to protect people, brands, and trust.

29:31Nilay Patel:Doppel, outpacing what's next in social engineering. Learn more at doppel.com. That's D-O-P-P-E-L dot com.

29:49Nilay Patel:we're back with rivian software chief wasim bensayed before the break we were discussing his role as co-ceo of rivian's joint venture with wokswagon and how that organization is structured now i want to ask the other decoder question how does wasim make decisions let me ask you the other decoder question and i want to turn to the software itself uh i ask everybody this question we've talked about a little bit how do you make decisions what's your framework making decisions? I think the number one rule, I mean, obviously, my job every day is making decisions. But there's a number of guidelines that I try to apply.

30:23First of all, in terms of coaching with my team, I tried to push decisions as much as possible to the lowest levels of the organization. And I think really one of the anti patterns that I see in a bunch of companies where they try to bubble up decisions to the highest levels of executives. And that tends to create a culture where things are slow and then employees don't feel really empowered. Now, in cases where I personally have to make the decision, few guidelines to the team. Never come to me with one option. Show that you went through an analysis, have multiple options, and then make a recommendation.

31:03I want a culture where I empower my team to be really a force of proposal and then come up themselves with recommendations. Now, the rule that I use in terms of how much time should I spend on a decision is really, is it a one-way door decision or is it a two-way door decision? If it's a two-way door decision, then I don't need to spend that much time on it. It doesn't need to be really a hard framework. We don't need to go into an extreme in some cases of collecting tons and tons of data so that we get to a decision. And in some cases, I really just use my gut. and I'm a product builder at heart and I know that some of the decisions, even if the data are against me, then I would go with my feeling.

31:58And in some cases I'm wrong and I'm the first to recognize that. Now, if it's a one-way door decision, then that's a different process which requires much more preparation, requires much more data and then arbitration for how we do things.

32:13Nilay Patel:Give me an example in this context of a one-way door decision at RV Tech and a two-way door decision.

32:24there's multiple of them. And I think probably one of them is like leading to probably the next topic of discussion that we will have, which is our overall approach around AI. And we had a ton of debates internally of whether we should basically just use a third-party AI solution or develop our own solution. And there's a ton of tension because you look at the investments in the AI world and you would think that with everything which is happening, this is obviously a hard problem to solve. Now, it was really clear for me, given the opportunity, given how transformative this is for the entire user experience, that we really need to own our destiny in terms of having a platform that allows us choice, that allows us to change foundation models as we wish and own that integration layer that allows us to power the entire car operating system.

33:41Nilay Patel:So this is Rivian Assistant. I've been playing with it for a few days now. What do you think? Truly had some searching conversations with it. just to push the boundary of what it can do. It's super interesting to have a car where, you know, even in the interface, it does the wavy line on the main screen. It's very much the car is running its assistant, not an overlay. You can tell. The assistant can go and address lots of parts of the car. And then there are places where it can't or it won't. And actually, I think one of the most interesting things about it is that it won't tell you why it can't do things.

34:14Nilay Patel:It is insistent that it won't tell you why it can't do things. Don't worry. I have very specific questions about that. But it strikes me that this is a natural evolution of, okay, the whole car is run by a finite set of computers. And that means our assistant can just run around and talk to those computers and talk to the functions of those computers control in a way that, I don't know, if you try to glue an assistant onto, I have a Cadillac EV. If you try to glue an assistant onto that, it has to like go talk to its CCUs. Like it's just very obvious that something else is happening with Google Assistant in that car.

34:48Nilay Patel:That's the opportunity. The assistant can talk to the whole car. Then there are places where it just can't for some reason. I'll give you one example. It just struck me as very odd. I was driving in the rain and I said, hey, turn on the back window wiper. And it just won't. And I thought, is that a safety reason? Is that you just don't know how to do it? You're like lost in the zonal architecture. And I asked it and said, I can't tell you why I can't do these things. But here's where the button is, which is really interesting for an assistant at car to do. It's like, I'm not going to do it for you, but the button is on the stock.

35:20Nilay Patel:Push the button. How do you make those decisions in the context of an assistant of what it can and cannot do? Awesome. So there's a lot of things here. I mean, first of all, I think you described it really, really well. Our approach, our philosophy for the Rivian Assistant is not just put a chatbot and then slap it on top of the UI. It's really developing what will become the connective tissue that enables our users to interact with pretty much every single feature in the car. And even more than that, bring their own personal digital ecosystem in the car through the authentic integration. Now, to your question, what it can do and then what it cannot do, us controlling the wiper, it's obviously possible.

36:09And I'm sure that you have seen that it can do way more. It can change your drive modes. It can change your ride height. Right.

36:16Nilay Patel:I could raise and lower the car at 55 miles an hour with the air suspension, which was cool. and it was like the slowest low rider experience you could possibly have. And then I couldn't turn on the wiper. So what is the split? Yeah. And that's honestly, that's one of my favorite features. And the way I like to interact with it is I don't tell it to change the right height. I tell it, okay, give me drive mode with more pep. And then it does it and it changes to sport mode. I mean, this is really the magic of having that true conversational experience. Now, the reason it does not do wiper is by design, we actually block a number of features which are safety related.

36:56And cars are obviously homulated, regulated. So everything related to wipers, things related to windshield controls, things related to highway assistance. Those are regulated functions, which today through our framework, we block them for safety reasons. And safety is really one of the core tenets in how we develop the entire experience.

37:20Nilay Patel:So the other one that struck me, you know, cars have rear seat sensors. We have kids. So every time I get out of my car, it reminds me there might be a kid in the backseat because it has sensed the weight in the backseat. I think this is one of the funniest sensors any car can have because the car seat is always in the backseat. So it's always reminding me that the kid might be in the car. So I asked it, is anyone in the backseat? and it maybe this is just a bug but it said i i'll find out and then it said i can't access that sensor and i said what sensor are you trying to access and it refused and i probably had a five-minute argument with your assistant about why it wouldn't tell me what sensor it was trying to access the reason i'm asking this is not because it's a bug or i really needed to know if anyone had car seat at the time i'm just very curious as you think about building the the assistant that can access all of the sensors and the architecture of how that might work and how we might interact with cars.

38:15Nilay Patel:There's just a moment where maybe it's for safety reasons, or maybe it just can't, doesn't work right now in the version I have, where the LLM has to go talk to another computer and that computer has to give it permission. And I don't know if anyone in any part of the tech industry has figured out exactly how that should work. And I'm just wondering what your point of view is. Yeah. And I think in this specific case, it should have actually told you what's in the back seat. So that's a bug. That's on me. No, it was like, I'm not telling you what sensor I'm trying to get to. And I was like, why?

38:44Nilay Patel:And it was like, I just, I'm not going to tell you what sensor I'm trying to get to. Yeah. That one is on me. And I think the beauty here is that, I mean, we have it even house and then we'll be able to calibrate that answer and then we'll fix the bumper and send you a note here next time. That's very good. Every time we get a car executive on the show, I just complain about the experiences I have. It's perfect but that but that piece where it's how do you talk to the computer and what permission does that other computer give you every assistant at every level is running into that specific barrier and i'm just curious what you think the answer is yeah i mean pretty much i think think about our architecture um this way the assistant has deep integration into the entire vehicle operating system so in theory uh i mean with the integrations that we have built unless we have a bug like the one that you have, you should be able to do everything.

39:35The only functions which are not allowed are functions which are safety related because obviously of the homologation reasons, but then also functions where we think that the level of reliability that we can get from the LLNs does not make us comfortable to expose them to the end users. But that's really like the beauty of the internal in-house orchestration layer that we have built, where we have a ton of guardrails, which allow us to control which functions are exposed by the assistant or not.

40:12Nilay Patel:All right. You mentioned that I was going to get you in trouble. I'm going to get you in trouble again. In 2024, you said using buttons in a car is an anomaly of modern design. And people love buttons in their cars, so you got in trouble for saying that. But the thing you said was that voice should be the future. Okay, this is the first gesture at voice being the future. Is it good enough? Because we're right on the cusp of, are these things actually good enough to build the kinds of products people want? I think we are on the cusp of something really big. And I deeply believe, like when you think about it, you're in the car, you're driving, you're focused on the road.

40:48So in theory, in theory, the primary interface with which you should be interacting with the car is actually your voice. The only reason that drivers and consumers so far did not interact with the car through voice is that, like to put it really bluntly, the technology has been broken. And I think that's really the beauty of what we have now through the technology disruption, which is coming with the foundational models. the foundational models are providing us this wonderful opportunity so that we can truly get to a conversational experience and where drivers can interact with the car in human language.

41:33I don't need to tell the car, open the front. I can say, open the front front, or actually I can say, I have a bag in front of the car and it will actually open the front. And I think that completely changes the way you interact with the car. On top of that, we have now the opportunity with all the agentic framework so that we truly can give people their time back in the car. And I hope you tried our Google Calendar agentic integration. But you can imagine how the experience will be in the future where you're driving and then you should be able to perform operations on your calendar. You should be able to perform operations on your email.

42:24And then in the future, with the framework that we have with the agent to agent integration, you can actually interact with many more apps from your own digital personal ecosystem.

42:36Nilay Patel:Can I ask you about the word agentic in this context? So the way the Google Calendar integration works with Rivian Assistant, just describe it quickly for people. It shows you a QR code. You connect your Google Calendar to it. And then Rivian Assistant can read your calendar, add events, remove events, do calendar stuff. I'm very curious how that's agentic and how it's built such that word agentic is meaningful. Because I have like 500 apps over the past 10 years that can do Google Calendar stuff through the standard API. So one, how is it agentic? Is it MCP? Is it something else? And why build it that way versus just doing a bunch of API integrations?

43:13I mean, you can actually build it with an API integration. I think the advantage of an agency integration is that you can share the context, and then you can perform multiple integrations within the car. And in this case, it's based on, like, this is an MCP integration, which also allows us, I mean, think about it in a way where you can imagine that in the future, instead of having that mono access to every single app on your car, or honestly, to that extent, even on your smartphone, you can start aggregating and connecting many of those apps through the agentic framework and have them present a unified user experience.

44:01and this is how we're able to connect the navigation to calendar, for example. Like I can go to the assistant now and I can tell the assistant, okay, I want to plan a trip from San Francisco to San Diego and I want to have two charging stops. I want them to be close to an Italian restaurant. I love Italian food. The assistant would go and play that and then I'll say, okay, okay, print the summary and add it to my calendar and then send it as a text to my wife. And this type of integrations, when you have behind the scenes, the agentic framework can really allow many more capabilities, which in the future as well, and this is where agentic can be even further utilized.

44:58you can start going into more autonomous functions in the sense that, let's say, you have an invitation in the calendar with XYZ details, and then you can start having reminders saying, okay, do you want to go to this place? Or you're actually really late to your meeting. Do you want me to start preconditioning your car? So that's the beauty of bringing the depth of the Agentec integration.

45:29Nilay Patel:We need to take on a short break. We'll be back in a minute.

45:40Nilay Patel:Support for the show comes from Upwork. Scaling a business takes the right expertise at the right time. Upwork helps growing teams quickly bring in specialized freelancers so you can move faster and take the business to the next level. Upwork is a one-stop platform to find, hire, and pay expert freelancers, letting you delegate and then just keep it moving. You can find specialized talent across web and software development, data and analytics, marketing, business operations, and more. Browse profiles, review their past work, and get help scoping the role so you can hire with confidence. You can also enjoy the benefits of Business Plus, which gives you access to the top 1 % of talent on their platform.

46:23Nilay Patel:With AI Power shirtlisting, you'll get matched to the right freelancer in under six hours. Skip the endless searching. It's free to sign up and posting a job is easy. Visit Upwork.com right now and post your job for free. That's Upwork.com to connect with top talent ready to help your business grow. That's U-P-W-O-R-K.com. Upwork.com.

46:50Nilay Patel:Support for the show comes from ServiceNow. AI was supposed to handle the parts of the job you hate. Instead, it just describes them, suggests what to do about them, and then leaves you to do it. That's not help. That's homework. ServiceNow's AI specialists are different. They're not a tool. Think of them as digital teammates who actually do the work from start to finish. Cases get resolved, requests get processed, loops get closed, and most importantly, no extra work for you. because when you can truly delegate to AI, you can get back to the work only you can do. The work that requires a person with ideas and judgment, and you know, a pulse.

47:32Nilay Patel:To learn how to put AI to work for people, visit servicenow.com.

47:40Nilay Patel:Support for this show comes from Vanta. If you're a business owner, you've likely noticed more customers asking for proof of security right from the start. It's a sign that risk and regulation are only increasing, and earning that customer trust is essential to closing deals. But that can be difficult, expensive, and a major drain on your time. With Vanta, you can automate compliance by unifying risk, security, and trust in a single AI-powered platform. It takes the manual work out of your security and compliance process and replaces it with continuous automation. So whether you're prepping for a SOC 2 or running an enterprise GRC program, Vanta keeps you secure and keeps your deals moving.

48:20Nilay Patel:Vanta says that companies like Ramp and Writer spend 82 % less time on audits with Vanta. That's not just faster compliance. It's more time for your business to grow. You can get started at Vanta.com slash decoder. That's V-A-N-T-A dot com slash decoder. Banta.com slash decoder.

48:51Nilay Patel:We're back with Rivian Chief Software Officer with Sim Ben Sayed, discussing the ins and outs of the company's new AI-powered voice assistant. So I think I understand that, right? You're in your car. It can go access a bunch of apps and services you have. You can take actions across them. You've collected a lot of data in one place. This brings me to like a very deep sort of existential question whenever anyone talks about ambient computing in this way. Where does the logic live, right? The idea that you're going to have that interaction in your car and not at your laptop or on your phone, that seems like a big jump to me, right?

49:26Nilay Patel:The same way that when the smart speaker companies would be like, you're going to talk to your thermostat. And I'm like, why? I'm going to talk to my phone. I don't feel the need to talk to my thermostat in this way. Do you think people are going to do that in the car? Are you going to bring Assistant to the Rivian app on a phone? Can you compete with the series and Google Assistants in that way? How is that all going to work? I think, actually, like the way I think about it, I think it would be both. And I think this is really the big difference between the old world where we had unique applications and then the new world where we have agentic integrations.

49:59And think about the Rivian assistant as an agent orchestrator, which has privileges because it can deeply integrate with the vehicle controls, with the vehicle operating system. It understands safety, it understands which things to do, which things not to do. And nobody else can develop that better than us because we develop the entire vehicle software. But then at the same time, it has interfaces and connections to other agents. And this is just the beginning. I think, think about it in a way where in the future, you can actually probably be able to bring your own personal favorite assistant and chatbot to the car.

50:47And then it can share context with the Rivian assistant. I mean, this is really the possibilities that this new world, this new type of integrations is allowing us to do.

51:02Nilay Patel:Is the Rivian Assistant the kind of thing that is possible because of the RV tech software stack? And is it possible that we'll see the Rivian Assistant or something just like it in Volkswagen's as well? Or is this special to Rivian? This is special to Rivian. Everything which is AI stack is developed uniquely for Rivian. I mean, this is Rivian's brand priority as we see cars becoming more and more AI-defined. But we're in discussion so that we can have similar technologies for the Volkswagen group. Rivians are sort of famously on LTE. When I first got in this car, I saw the LTE indicator, and I thought, oh, something wants to be wrong.

51:45Nilay Patel:And I drove around, and then I realized, oh, it's just LTE. Is there any latency concern with that, especially with voice and going out in the world and doing whatever inference you need to do? So two things. One, we need to get you an R2. The R2 has 5G. There you go. It's coming soon, and it's amazing. And then two, and I think your touch base really on one of the architecture considerations for the technology, which is when you look at vehicles like the Rivian R1 today, most of the interactions will happen with the cloud. So as you say, it's connectivity dependent and then they will happen best when there's a strong connectivity with the external world.

52:33Now there's a number of interactions that happen locally with the car. And if you tell the car, I am cold, that interaction is being managed by a small language model that sits directly on the edge. Now, the beauty of what will happen next as we get to R2, not only we will have 5G, but then edge AI will be way more powerful and capable on the R2.

52:59Nilay Patel:Just to be clear for the audience, when you say edge, you mean local, right? It's running locally in the car. So meaning that the local computer on the R2 will have up to 200 sparse tops of compute dedicated to AI. I know this sounds like extremely technical, but think about it as this is more capable than some of the self-driving platforms today. And it's more capable than the amount of AI compute that you have in your smartphone. All of that will be available locally in the R2 car, which is coming soon. And that allows, as you mentioned, to basically not face such limitations and issues with connectivity, but truly get to much lower latencies because a lot of the processing will happen directly on the embedded locally and get to a truly conversational experience where it's pretty much instant.

54:02Can I just ask you a very in-the-weeds question?

54:05Nilay Patel:We're talking about putting compute in the car. We're going to do some amount of local inference in the car. GPUs are expensive. RAM is expensive. How much of the bill of materials is RJ giving you to do all this in the car versus, I don't know, bigger motors, bigger batteries? How much of the range can you pull off to do local inference in the car? I mean, this is kind of the trade-off you're talking about. Yeah, I mean, this is what I love about RJ, which is what has always attracted me with RJ is that RJ thinks big things long term. And he knows that in this case that the world is moving to AI.

54:42And this is why, like the way we do decisions, for example, from a material standpoint, it's a very hard process where there's a ton of trade-offs all the time. And you can imagine the tension between people wanting to push for a better exterior part and then people wanting to push for a better interior part and then people wanting to have better technology. And then we have what we call the fun or the differentiation budget in the car. And RJ, absolutely, it was no discussion that we will equip the car with higher inference compute and then higher memory because this is really the future. And it's an opportunity for us to completely reshape the way people interact with their cars.

55:31And actually, in the long run, to be honest, it solves itself from a unit economic standpoint, because as we do more and more interactions locally in the car, we avoid the back and forth with the clouds. We avoid the connectivity costs. And then we also don't have to pay for the inference costs on the cloud. So in the long run, it's actually economically positive as well.

55:57Nilay Patel:That's not just a spreadsheet you made up to win an argument that actually models out? Kind of. Because I could probably make up a spreadsheet to win an argument. The reason I asked it, because that was my next question, was about inference costs, right? They're going up. There's rate limits at all the big providers. What model are you using right now? What are the frontier models you're using right now? Actually, like the architecture that we have built is not model dependent. So really, one of the foundations of the architecture is it allows us to interact and plug and play pretty much with different foundational models.

56:28and similarly it can use different modalities in the way users can input their requests, whether it's voice in this case, but then it can use vision as well. It can use text if we want to enable that. When it comes to the models themselves, we use currently a combination of internal models for everything that runs locally on the edge And then we use models from Google. We have a partnership with Google. Things are going really well in terms of deep access to the advanced Gemini models, as well as the grounding of results, which is also powered by Google.

57:18Nilay Patel:This is another question. I asked it to just, what are the top five headlines in The Verge? Just to see, can this thing browse the web? and it returned some results. They were just, I think they're 24 or 48 hours old, right? It was our top five headlines from yesterday. Does this thing have like a web browser in the background or is it just pulling from a Google data corpus? How does that work? It actually can, it should in theory connect real time. And then this is where the grounding with the Google results come into the picture. And in theory, it should give you the latest headlines. So if it didn't, then that's another one on me.

57:54Nilay Patel:Well, I was just curious, It's like there's some, you know, lots of people have this experience now where like the data in the model is old. And then there's some cutoff. And I was just trying to find the cutoff. And then I had a long searching conversation with it about we need to buy a new air conditioner. And I was just asking it to do math about air conditioner efficiency. This is very boring, but this is what I talked to your car about for a while. And it just occurred to me, like, I am making it think very hard. Like, I'm burning, like, I am wasting more energy talking about how efficient of an air conditioner to buy.

58:24Nilay Patel:Like, this is not a good ratio of energy spent to save energy over here. How does that work? I mean, you have to pay a monthly fee for the connectivity package to access assistant, but then I might burn way more tokens than that fee could ever pay for. How does that math work out? It really depends. It's a great question. Now, obviously, in these cases, there's all sorts of techniques of what we call rate limiting that we can apply. Like if we have seen in your case that you're spending 20 hours discussing with the assistant, then we may do something behind the scenes. Similarly, in the way we configure the models, we, I mean, given the types of interactions that you have in the car, you would not be interacting with the latest and greatest, say, Opus 4.7 models so that you bring, you burn so many tokens.

59:17And then a lot of it also depends on the aggregation across users in terms of the types of requests, as well as arbitration that we do between the edge and the cloud. And as I mentioned, the more we move to edge and local compute, the better it is for us in terms of overall inference costs.

59:39Nilay Patel:So let me just ask you this question again. Now that you've shipped the software, people are using it. You're getting extremely detailed feedback from me. Do you still think having buttons in the car is an anomaly?

59:52I think, I deeply think that voice has the chance to be the primary interface in the car. I also think that buttons can exist, but then they shouldn't be the primary way with which you interact with the car. I think there's much more that is possible through voice where you can not only do one single function. You don't have to go and fiddle with so many functions. You don't have to go even deep into the touch screen to look into specific features. A great voice experience can really elevate all of that and allow users to talk to the car as a human would do and really take the overall experience to the next level

1:00:48Nilay Patel:are we going to get the h-track buttons back in any future rivians that's really what i'm asking here actually with the r2 we have a great way to have a tactile feedback uh for a big paddles on the wheel yeah yeah they're really awesome uh it's a good pivot but i'm asking are we going to get the fan speed button back in the center stack. In the center stack, no, but we have the same in the Halo wins. It's a great compromise. You knew it was coming. I have to ask you about CarPlay here because it strikes me just as you imagine this future of the car where it's connected to your calendar. It's connected to all this context.

1:01:25Nilay Patel:It has autonomy, which is something you're also working on. You get in the car and it knows it's time to go to work and you just say, let's go. And the car takes off driving. This is when you would use like a vast number of applications, right? This might be when you have the focus to push the buttons again. I'll just make that argument. But this is when you would want a whole number of apps. And I hear from our readers every time I talk to a car executive, the reason I want CarPlay is because there's 5 ,000 apps on my phone and no car OEM is ever going to support them on the built-in infotainment.

1:01:56Nilay Patel:This is where you would say, okay, project your phone to the center stack. The car is driving itself. Have at it. Phone projection all day. Do you think that the tide is turning? Are you still absolutely committed to not having CarPlay and Rivian vehicles? I think, first of all, it's really important to go through our philosophy of how we see software in the car and how we see user interface. The challenge with screen mirroring solutions is that they take over every single pixel in the car. And that's not the way we see ourselves interact with our users. You drove our car four years ago, and you drove the car in the past few days.

1:02:41And I hope you have seen how much change happened in the car. And that's truly by bringing the end-to-end features. I mean, not only changing the user interface, but having your navigation know exactly about your drive mode, know exactly about your efficiency offering that level of convenience is really what is resonating with a lot of our customers. I mean, even if I look at our own internal statistics, five years ago when we first shipped the R1T and the R1S, the number one request from customers was CarPlay. And at the time, like we do all sorts of survey with customers, more than 70 % of customers were requesting CarPlay.

1:03:26In the recent survey, that number is less than 25 % now because with the level of features that we have shipped to customers, with the level of end-to-end integration, with the level of convenience that we are bringing, CarPlay is, or Android Auto to that extent, is no longer the topic of discussion. And I think what we're actually seeing right now with the advancement of AI technologies is just another reason why I deeply believe that RJ and Rivian, we made the right choice in terms of investing into our own technology and our software. Cars are moving from, as you said, the buzzy world of software defined to AI defined.

1:04:22And the possibilities that we have now to have such deep AI integration into the car, it will make the entire car play debate in the future completely obsolete. I really believe that the way you interact with apps, which are monothreaded, single buttons, single icons, a lot of that will be now completely reshaped into a world where it will become an agentic integration that presents itself into a wholesome user experience to the user.

1:05:00Nilay Patel:I buy that in the big picture, but give me an example of that. I'll just put up an idea that I get from our readers all the time for you to react to. There are tons of little apps. They're basically media-playing apps on phones. And it's trivial to push the button and do the CarPlay app. The one that I always think about, we got an email from a reader, and he said, I have a Bible app that is never going to be inbuilt into anyone's infotainment system. It's made by a small developer, and I love it, and that's why I need CarPlay. And I'm always going to buy a car with CarPlay because of it. That is about as small of an edge case as you get.

1:05:31Nilay Patel:but this one customer is going to pick a car based on it. Are you going to make that developer build an agentic AI integration into the Rivian Assistant, or are you just going to lose that customer to CarPlay? I mean, this is the beauty of the technology disruption in which we are today. The answer in that case does not necessarily need to be we will build an agentic integration for that particular app. It can be. If it is like, say, a Spotify or an Apple Music, absolutely. But then if it's a small app, the answer to that could be that from the Rivian assistant, we have an integration to your favorite voice assistant on the car.

1:06:12And then you can ask the voice assistant on the car to play that particular app through Bluetooth audio. That is possible as we open up the framework and as we allow more integrations to bring your own digital ecosystem to the car.

1:06:26Nilay Patel:So you're saying I've got, we'll use Google because Gemini is more present on an Android phone than Siri is currently on an iPhone. So you use Google and they're also your partner. So you're saying you talk to Rivian Assistant, Rivian Assistant knows about your Google account and your Android phone, and it's going to go talk to Gemini. And Gemini is going to go operate your phone and stream Bluetooth audio to the Rivian Assistant. In the future, all of that is possible. Is that better or worse than phone projection, right? This is like a different kind of loop than just saying, put the interface here and let the user do it.

1:06:58It could be possible through phone projection. I think the challenge with phone projection, again, is that, I mean, first of all, you have to go, like, as you're driving, you have to go through your phone. In some cases, you have to press, like, multiple buttons so that you get to the menu of your own app. The other thing is that it takes over the entire screen. and that is a degradation of the experience. Now, is the alternative solution available right now? No, but I think the beauty of the wave of technology in which we are is that we finally have the building blocks so that we can really redefine those type of interactions and we can allow hooks now into your own personal device through a different way of interaction rather than truly integrating end-to-end the app on the car itself or take over the entire screen from your phone.

1:07:58There's a third path now, which is possible.

1:08:01Nilay Patel:I mean, obviously, I think it might be easier with Google. Again, they're your partner. But where would that connection to Google Assistant happen? Would I be like, I don't think I'm holding up my Android phone to the speaker and letting the assistants talk to each other out loud. Although that would be fun. I mean, that would be deeply hilarious to hear the two assistants just have a conversation. Like, can you please play the music app for me? Does that happen in the cloud? Does it happen locally? Where does that integration point between assistants happen? I mean, think about it as the assistant in the car will know how to talk to your, say, Gemini, your own personal assistant.

1:08:38And then in that case, your own personal assistant would be controlling your phone.

1:08:45Nilay Patel:The reason I'm asking this in this way is at some point you have one main assistant and all the other things are sort of like agents that can talk to. And then maybe no one's ever talking to Ravine Assistant again, right? Like this is kind of the, you pull that thread all the way and Gemini is just doing everything for you all the time. Is that a danger or are we just nowhere close to even having to worry about that? Honestly, we don't worry about that because we know the opportunity that we have and we know the level, the breadth of capabilities that we can offer. No other assistant will be able to know as much as there will be an assistant about the car controls.

1:09:23None. Similarly, the fact that we have the surface of integration sitting in our own operating system enables a ton of opportunities in terms of use cases that you cannot simply do with your phone or you cannot simply do by calling another assistant. Like imagine, okay, I'm driving and then in the near future, we should be able with the technology to have an agentic integration with your favorite food delivery. And then you would say, okay, I need to be, the car knows exactly exactly when you will be home, you'll say, okay, order my favorite sandwich from XYZ shop, your account is already configured, and then the assistant will pick the destination, will get you to your favorite restaurant.

1:10:25All of that is integrated. You just need to do it through one voice command. Like those type of experiences where things become so seamless, where things become so easy, as if you're talking to a human, which connects the dots across multiple surfaces of your digital ecosystem, would only be possible through such integrations. All right.

1:10:50Nilay Patel:Listen, we're out of time here. As you can tell, I can obviously talk to you about this forever. I don't think anyone has figured out how all this works, and it seems like you're making some big decisions. So you're going to have to come back as you've learned how this goes after this is shipped to all of your customers and certainly when the R2 is out. There is one question that I have to ask every single Rivian person that I encounter. It is very important to me. When is the R3X coming out? It's here. Do you see it? When can I get one? By the way, it's my favorite car. And like I keep asking RJ that question all the time.

1:11:28Now, you talked about decisions, you talked about trade-offs and us delivering the R2 before the R3X, you can imagine it's a big decision. It's also a hard decision because in our hearts, we all deeply want to have the R3X as soon as possible. Now, we also know that the R2 has the best ingredients to be a wildly successful car. And the U.S. needs another alternative for a great SUV for families. And this is what the R2 brings. And as we ship the R2, as we scale our volume as a company, we will earn the ride so that we bring fantastic and such emotional cars like the R3X.

1:12:18Nilay Patel:I know that that is in one way the right answer. I'm just saying for me personally, come on. Just send me one. It'll be great. You can do it. I'll give you more feedback just like this. I will break your R3X prototype in 10 ,000 different ways. You'll get the bug reports. It'll be great. Tell RJ I made the offer. Awesome. I'll get one at the same time as you. Sounds good. Well, Sim, thank you so much for being on Decoder. This is great. Thank you. I'd like to thank you for Sam for taking the time to join Decoder and thank you for listening I hope you enjoyed it if you'd like to let us know what you thought about this episode or really anything else at all drop us a line you can email us at decoder at the verge.com we really do read all the emails or hit me up directly on threads or blue sky we're also on youtube you can watch full episodes at decoder pod and you can watch clips on tiktok and instagram also at decoder pod that's a lot of fun if you like decoder please share it with your friends and subscribe over your podcast decoder is a production of the verge and part of the doxing podcast network The show is produced by Kate Cox and Nick Stat.

1:13:16Nilay Patel:It's edited by Xander Adams. Our editorial director is Kevin McShane. The decoder of music is by Brickmaster Cylinder. We'll see you next time. Did you know if your windows are bare, indoor temperatures can go up 20 degrees. Turn the temperature down with Blinds.com and get up to 50 % off custom window treatments like solar roller shades and more during the Memorial Day mega sale. Whether you want to DIY it or have a pro handle everything, we've got you. Free samples, real design experts, and zero pressure. Just help when you need it. This is your last chance to shop up to 50 % off site-wide during the Memorial Day Mega Sale at blinds.com.

1:13:53Nilay Patel:Rules and restrictions apply.

From the publisher

Today, I’m talking with Wassym Bensaid, the chief software officer at Rivian, and the co-ceo of Rivian’s platform joint venture with Volkswagen. That joint venture, called RV Tech, is about a year and a half old, so I wanted to ask Wassym how it all works and Rivian’s ongoing relationship with Volkswagen. 

Because it’s Rivian, I also had to ask Wassym about CarPlay. But the company also just launched an AI-powered voice assistant, which I got to try early. So I had a lot of fun digging into that with Wassym, too. This is a fun one – really in the weeds of a lot of my favorite things to talk about.

Links: 

Rivian’s AI-powered voice assistant is ready to roll | The Verge

The R2 is nearly here — can Rivian stick the landing? | The Verge

Rivian’s AI pivot is about more than chasing Tesla | The Verge

Rivian / VW will start testing their first EVs next year | The Verge

Rivian CEO: ‘We’re really convicted’ about skipping CarPlay | Decoder (2025)

Rivian CEO RJ Scaringe says too many carmakers are copying Tesla | Decoder (2024)

Rivian CEO RJ Scaringe isn't scared of the Cybertruck | Decoder (2023)

Rivian’s chief software officer says in-car buttons are ‘an anomaly’ | TechCrunch

Subscribe to The Verge to access the ad-free version of Decoder!

Credits:

Decoder is a production of The Verge and part of the Vox Media Podcast Network.

Decoder is produced by Kate Cox and Nick Statt,. This episode was edited by Xander Adams. Our editorial director is Kevin McShane. 

The Decoder music is by Breakmaster Cylinder.
Learn more about your ad choices. Visit podcastchoices.com/adchoices

More from Decoder with Nilay Patel

All 153 episodes
Rivian's software chief thinks you don't need CarPlay or buttonsDecoder with Nilay Patel · 1 h 10 min
Listen in VO