The Rivian CFO has made several announcements at the recent Bank of America Securities Summit, enticing investors and fans alike.
Rivian is finally catching its stride following a successful first quarter of the year, and coming off this excellent production ramp; the automaker is headed toward a whole new set of challenges, relating to everything from its second-generation R2 vehicle to its profitability to its ongoing R1 truck ramp. Luckily, the company’s CFO, Claire Rauh McDonough, released new information covering these points at last week’s Bank of America Securities Summit.
@RivianUpdates initially reported the tsunami of Rivian announcements on Twitter in a lengthy thread covering the numerous statements. Still, they can essentially be boiled down to three main points, R1 production updates, the Van production ramp, and R2 updates, along with a couple of minor updates.
Rivian’s CFO revealed a TON of important information via BofA Securities Summit: $RIVN ?#Rivian @Rivian @RJScaringe
• Rivian anticipates achieving a POSITIVE gross profit by H2 of 2024
• Rivian is aiming to build 85K R1s in 2024.
• R2 production capacity will be 200K units… pic.twitter.com/YZiyz02aUN
— Rivian Updates (@rivianupdates) April 7, 2023
R1 Production Updates:
Perhaps the most notable announcement from the BofA summit is the news regarding the company’s premier truck offering, the R1 lineup. Foremost, Rivian remains on track to achieve profitability by the second half of 2024, motivated essentially entirely by R1 and van deliveries. Further, while McDonough did not disclose the total number of backlog orders, the company anticipates completing all of its pre-March price increase orders by mid-2023. It has a backlog extending “well into 2024” with orders from after the price increase.
On top of this sales success, Rivian is learning some surprising things about its newest customers, primarily their price point. Rivian’s CFO notes that the automaker has seen the average purchase price of its trucks steadily increase, indicating that more premium buyers are coming to the automaker, who are typically more willing to purchase the optional add-ons. However, following these comments, the company executive noted that Rivian does not currently plan to increase the base price of its R1 vehicles.
Looking to the future of the R1 vehicles, the CFO notes that Rivian plans to produce 85,000 vehicles annually by 2026, a production number that the automaker has previously stayed tight-lipped about.
R2 Design and Production Updates:
As the Rivian R1 vehicles have continued to age, the anticipation for the company’s next generation “R2” trucks has built. And while Rivian CEO RJ Scaringe has noted the business plans to make the upcoming truck a more affordable model, other details have yet to be revealed.
Most surprising to investors was the CFO’s bold estimation of R2 production, which is anticipated to begin in the 2025-2026 timeframe. Rivian aims to produce 200,000 R2 trucks during 2026 and will then seek to double that number as its next production goal, though a timeframe for that upgrade was not shared.
Regarding the upcoming truck’s market position, sadly, Rivian remains secretive. However, the CFO noted that the new vehicle would aim to compete with other luxury volume sellers like the Tesla Model Y. With this information, many now anticipate the truck to start at around $40,000.
Finally, Rivian’s CFO pointed out that R2 aims to be both a volume seller and a global vehicle, meaning it will be available in numerous markets. Currently, Rivian has been supply constrained and hence, a strictly North American brand, but that may change in the near future, with Europe likely being the company’s next target.
Electric Delivery Van Announcements:
Despite Amazon’s recent announcement that it would be decreasing the number of vans it would be buying this year, Rivian remains entirely focused on the production ramp of its offering. One of Rivian’s top priorities has been the production of its Electric Delivery Van (EDV), which has been taking the streets of the United States by storm. Highlighting this focus, the company CFO noted that the van takes “enduro-motor” priority over the dual-motor R1 vehicles. Moreover, the van received two notable production upgrades in Q1 of this year, integrating the new motor and Rivian’s new LFP battery pack.
Other Announcements:
Besides these amazing announcements on its most exciting products, Rivian also revealed updates coming to its Adventure Network charging infrastructure. To aid its rapid development, Rivian will now be looking to join the “Federal Charging Fund” in the United States, making it eligible to receive incentives from the federal government to place its charging network. However, as a result, Rivian will be forced to open its network to other EVs. Nonetheless, with the feds willing to put up as much as 80% of the cash required for installation, many would consider Rivian foolhardy to decline the offer.
What do you think of the article? Do you have any comments, questions, or concerns? Shoot me an email at william@teslarati.com. You can also reach me on Twitter @WilliamWritin. If you have news tips, email us at tips@teslarati.com!
News
Tesla Robotaxi takes over for Uber credits and loaners at Service locations
Tesla is now utilizing its in-house Robotaxi platform to give those waiting for their vehicles during Service visits rides instead of offering Uber credits or Loaner vehicles.
Tesla owners in Austin who bring vehicles in for service are receiving in-app prompts to use the company’s Robotaxi network while their cars are being worked on.
One recent notification, sent during a frunk repair, carried the heading “Try Robotaxi During Your Service Visit” and stated that while the vehicle is being serviced, the customer can take an autonomous Robotaxi ride to the next destination in Austin and download the Robotaxi app to get started.
Interesting. While my frunk gets fixed Tesla suggests taking a Robotaxi 😇 https://t.co/QiUbAmrp4a
— Wadesmith (@LanceWade) November 17, 2026
The suggestion arrives as Tesla has long relied on two main ways to keep customers mobile during longer service visits. Service centers have typically offered loaner vehicles drawn from a limited fleet; when those vehicles were unavailable, centers have issued Uber or Lyft credits. Uber credits were widely eliminated years ago, but some locations will still give them out.
Both approaches carry costs: loaner cars occupy inventory that could otherwise be sold, and third-party credits generate recurring expense.
Code discovered in Tesla app version 4.60.5 in September 2026 already listed “sv_transport_robotaxi” among the transportation options available for service appointments, alongside paid loaners and other alternatives, indicating the company had been preparing to route customers through its own autonomous fleet.
Your Tesla could be in the Robotaxi fleet next month, Elon Musk claims
Austin provides the clearest early example. The city remains Tesla’s primary Robotaxi market, with unsupervised Model Y and Cybercab vehicles operating across an expanded zone of roughly 400–440 square miles and running 24/7 since November 11. Public driverless service is also live in Dallas, Fort Worth, Houston, San Antonio, Miami, Orlando, and Tampa.
Directing service customers into this network keeps the vehicles utilized and reduces reliance on external rideshare credits, while giving owners practical experience with the Robotaxi app and vehicles during the repair window. Once service is complete, the same network can be used for the return trip without a staffed loaner handoff.
The Austin notification is the first public instance of the capability the September app code previewed. As Robotaxi expands into additional U.S. markets and the fleet grows, service centers in those cities are positioned to follow the same pattern, presenting autonomous rides as a primary transportation option during the service appointment rather than defaulting to loaner vehicles or third-party credits.
For customers, the change preserves mobility without the logistics of arranging a temporary car; for Tesla, it links the service operation more tightly to the expanding Robotaxi business.
Elon Musk
Sean Duffy fires back at Elon Musk over free Starlink
Sean Duffy says the FAA picked a ground network over Starlink, and Musk isn’t impressed.
Transportation Secretary Sean Duffy has responded to Elon Musk’s claim that the Federal Aviation Administration turned down free Starlink terminals before last week’s nationwide ground stop, saying the department chose a ground-based network after running into problems with an earlier version of the satellite service. Musk’s reply was a single emoji: “🤦♂️.”
Speaking at a press conference, Duffy said Starlink had been useful in some parts of the system. “I’ve worked well with Elon, and he, Starlink was a great solution for some of our assets in Alaska, but we sent Starlink, in one of its prior iterations, to our tech lab, and, there was some issues that we had to navigate, and we thought that the best method is to have a network that’s based on the ground,” Duffy said, according to a transcript published by ZeroHedge. “Now, I think what he’s doing with Starlink and the speed is remarkable, but, our airspace is very big. We have assets everywhere. And so, again, we used him for different parts of the airspace.”
Duffy did not dispute that the offer was made. He also did not say what problems the FAA found during testing.
The exchange started Monday, when Musk wrote on X, “Free Starlinks for FAA were offered to Sec Duffy, but he said they were not needed. As it turns out, they were,” as Teslarati reported. That post came three days after the FAA grounded departures nationwide on November 13, when its legacy equipment became unstable as data flooded its telecommunications network at 1,000 connection attempts every four to five seconds. The FAA traced the flood to a radar site in Amarillo, Texas, and a radio site in El Dorado, Arkansas, where L3Harris had been installing a new router. Roughly 12,462 flights were canceled that day.
As I was saying …
Free Starlinks for FAA were offered to Sec Duffy, but he said they were not needed. As it turns out, they were.
— Elon Musk (@elonmusk) November 16, 2026
Duffy has also signaled frustration with L3Harris, which runs the FAA’s current network. “I want to get away from L3Harris and get to a new one, but they own the network,” he said. “I can’t cancel the network that they own.” He has asked Congress for $50 billion to modernize air traffic control, arguing against “a patchwork, a fix to a system that’s critical for every single family.”
The FAA’s position on satellite links predates this week. In a July 2025 letter to lawmakers, FAA Administrator Bryan Bedford said the agency “would not use Starlink (or any satellite service) as the sole communications technology” for safety-critical air traffic services. Reuters reported at the time that the FAA was not considering replacing its L3Harris and Verizon contracts with Starlink. Verizon’s FAA Enterprise Network Services contract, awarded in 2023, is valued at up to $2.4 billion over 15 years.
Musk first pressed the issue in February 2025, while he was leading the Department of Government Efficiency, writing that “the Verizon system is not working and so is putting air travelers at serious risk” before correcting himself days later to blame L3Harris. SpaceX said at the time it was supplying Starlink kits to the FAA at no cost and had no intent to take over any existing contract.
Elon Musk
Tesla gears up Cybercab with Starlink for public debut, but with notable changes
Tesla is gearing up Cybercab, its all-electric and fully autonomous ride-hailing vehicle, for a very public debut as it plans to start customer deliveries in December. However, the units that rolled out of Gigafactory Texas this morning seem to differ from what we have seen previously.
Aerial images captured by drone photographer Joe Tegtmeyer at Giga Texas on November 18 reveal a noticeable update to the appearance of Tesla’s Cybercabs equipped with Starlink. Rows of gold production vehicles sit in the outbound lot, each carrying a flush-mounted Starlink V5 terminal on the rear hatch that looks more refined than the version first shown months earlier.
When Tesla first unveiled the integration in July and displayed a physical example in August, the Starlink hardware appeared as a relatively distinct rectangular panel on the hatch. Later September footage of large numbers of Cybercabs leaving the factory still showed a lighter, more obvious rectangular cover that roughly matched the vehicle’s gold paint:

Images via Joe Tegtmeyer
The newest batch stands out for how cleanly the cover blends into the roof’s character lines. Observers and replies to Tegtmeyer’s post describe the result as tighter and more intentional, sitting flush and following the body contours rather than reading as an added panel.
All of the Cybercabs in the latest images also wear prominent “Cybercab” logos on the doors and rear hatch, confirming these are finished production units rather than early prototypes. They are staged near the factory building, end-of-line areas, and covered transport trailers, with some already lined up for shipment.
The scale and consistency of the installation point to factory tooling rather than retrofit work.
A secondary detail noted in related sightings is a darker tone to the Starlink cover compared with earlier lighter panels. Tegtmeyer himself left open whether the darker finish is deliberate. There are a variety of explanations for it: perhaps for thermal performance, signal characteristics, or simple visual identification—or simply a batch variation still being refined.
Either way, the overall effect is a more integrated, production-ready appearance. For a Robotaxi that relies on Starlink for fleet connectivity, passenger services, and backup data links in areas with weak cellular coverage, the cleaner hatch design is more than cosmetic.
It signals that Tesla is polishing the final visual and hardware details as Cybercab volumes continue to climb at Giga Texas ahead of broader Robotaxi deployment. The vehicles now look to be built with Starlink instead of it being added afterward.