Rivian used its latest quarterly earnings call less to talk about the vehicle that will make or break its near-term finances and more to talk about the software that it hopes will define its next decade. On an hourlong call, founder and CEO RJ Scaringe spent comparatively little time on the production ramp of the R2 — the midsize SUV the company has staked its balance sheet on — and considerably more on an autonomous driving program that has yet to prove itself in the real world.

The next 24 months, by Rivian’s own framing, are the decisive window. The company plans to roll out a point-to-point hands-free driving feature to its own employees in 2026 for testing and validation, extend it to customers in 2027, and then launch its first robotaxi vehicles in partnership with Uber in 2028. It is an aggressive schedule for a company that has shipped comparatively few vehicles relative to the incumbents it now intends to challenge.

A company repositioning itself as a software play

The framing of last night’s call was not lost on observers. The Verge characterized the earnings presentation as an “autonomy gamble” facing its “first real test,” noting that Scaringe spent more time hyping the company’s “still-unproven autonomous vehicle ambitions” than discussing R2 output. That editorial read reflects a broader investor debate: is Rivian an automaker with a software division, or a software company that happens to build cars?

“In short, the next two years will determine whether Rivian will succeed or fail in its high-stakes quest.” — The Verge

The distinction matters commercially. Automakers are valued on margins, volumes and capital efficiency. Autonomy-adjacent technology companies are valued on optionality — the theoretical size of a future robotaxi market. By foregrounding hands-free driving and a 2028 Uber partnership, Rivian is signaling to Wall Street that it wants to be judged, at least partly, on the second set of metrics.

The timeline: employees first, customers later

  • 2026: Rivian employees begin testing and validating the point-to-point hands-free system on public roads.
  • 2027: The feature is expected to reach paying customers, likely gated by subscription or trim level.
  • 2028: First robotaxi vehicles, developed in partnership with Uber, are slated to launch.

The staged approach — internal fleet first, customers second, commercial robotaxi third — mirrors how Tesla, GM’s Cruise and Waymo have each sequenced their own rollouts, though with sharply different levels of disclosed safety data. Rivian has not yet published the size of its validation fleet, the operational design domain for the feature, or the specific geographies where hands-free driving will initially be permitted.

Canada, conspicuously, is not invited

One of the more revealing details to emerge alongside the announcement was a geographic exclusion: the hands-free driving test program will not extend to Canadian owners. Reporting on the program confirmed that Rivian’s initial testing cohort is limited to U.S. participants, leaving Canadian customers — a meaningful slice of Rivian’s early adopter base, particularly in British Columbia and Ontario — on the sidelines.

The exclusion is likely a function of regulatory divergence rather than technical capability. Hands-free driving systems require jurisdiction-by-jurisdiction approval, and Transport Canada’s framework for conditional automation has moved more slowly than its U.S. counterparts. Mapping and validation work also tends to proceed market by market. Still, for Canadian owners who paid the same price for the same hardware, the omission reinforces a familiar frustration: features arrive north of the border late, partially, or not at all.

The lidar promise slips to the right

Compounding the sequencing questions is a hardware story. InsideEVs reported this week that buyers will not be able to purchase a Rivian R2 equipped with lidar this year after all — a delay to a sensor package that had been positioned as part of the vehicle’s long-term autonomy story.

Lidar matters because it underpins the difference between hands-free and eyes-off driving. Camera-and-radar systems can support supervised highway assistance; higher levels of autonomy, where the driver is not required to monitor the road, generally benefit from redundant depth sensing. Delaying lidar on customer vehicles means the earliest R2 buyers may be purchasing hardware that is not fully future-proofed for the most ambitious features Rivian has promised.

The quieter story: the R2 gets smarter

Not all of the news was about what is late. Forbes reported that substantial R2 upgrades are on the way as Rivian’s EVs become more software-capable, with over-the-air improvements and compute changes intended to make the vehicle’s electronics architecture more extensible over time. That is the less glamorous, more consequential half of the strategy: a vehicle fleet that can receive new capabilities remotely is a prerequisite for monetizing autonomy at all.

Rivian’s Normal, Illinois plant, where R2 production was showcased in May, remains the physical anchor of this plan. Volume there determines whether the company generates the cash required to fund a multi-year autonomy program — a program that will compete for talent and capital with far larger and better-resourced rivals.

What to watch

Three signals will indicate whether Rivian’s gamble is paying off: the scale and safety disclosures from its 2026 employee fleet, the pricing model attached to the 2027 customer rollout, and whether the lidar delay proves to be a one-year slip or a structural retreat. Until then, the company is asking investors to believe that the software comes before the sales — and that the R2 is merely the vehicle through which the real product arrives.