Rivian at Evercore’s 9th Annual ADAS, AV & AI Forum: autonomy push

Rivian outlined an R2 production ramp toward 4,000 vehicles per week at its Normal, Illinois plant, with R2 bill-of-materials costs targeted at roughly 50% of the R1 and combined Normal/Georgia capacity planned above 500,000 vehicles annually. The company expects initial point-to-point autonomy rollout by year-end 2026, broader availability in 2027, and a late-2028 Uber robotaxi launch under a $1.25 billion partnership that includes a contingent 10,000-vehicle commitment. The outlook is constructive on lower-cost scale, proprietary autonomy technology and software monetization, but supply-chain constraints, rising lithium and DRAM costs, regulatory fragmentation and still-small software revenue remain execution risks.

Analysis

The investable issue is not the autonomy narrative but whether R2 reaches a repeatable gross-margin inflection before fixed-cost absorption and Georgia spending reaccelerate cash burn. A materially simpler platform can create substantial operating leverage if volume rises, but launch-period supplier shortages would reverse that leverage quickly: missed builds reduce revenue while labor, depreciation and launch engineering remain largely fixed. With long-end yields rising, RIVN will trade as a duration-sensitive financing story until investors can underwrite positive unit economics rather than assign optionality to 2028 autonomy revenue.

The Uber arrangement should be valued primarily as milestone-financing and validation of RIVN's stack, not as a near-term revenue backlog. The fleet purchase and utilization-linked licensing economics are contingent on an L4 threshold that has technical, regulatory and liability gates; therefore the key near-term catalyst is cash receipt at the next technical milestone, while the key risk is that ambiguity around milestone definitions masks a slip. UBER benefits from retaining asset-light fleet ownership through partners, but has limited earnings sensitivity before service commercialization.

RIVN's vertical stack creates a potential share donor to MBLY at the high end of advanced-driver-assistance content, particularly if third-party OEM interest follows successful Volkswagen deployment. However, sensor redundancy raises hardware cost and could make RIVN less competitive with TSLA on consumer pricing unless internally developed compute offsets the added sensor bill. The contrarian view is that the market may be over-crediting software optionality while under-crediting the near-term R2 cost-down: a clean volume-and-margin ramp matters far more to equity value over the next 12 months than autonomy attach rates from a small installed base.

Key Decisions for Investors

• Maintain RIVN as a catalyst-driven watch/accumulate only after the first full-quarter R2 production data confirms sequential build growth without a deterioration in vehicle gross margin. A position should be sized for high financing sensitivity; exit or reduce if production guidance is cut, supplier constraints persist into the following quarter, or liquidity runway falls below management's stated capex plan.
• Express the core execution thesis as long RIVN / short TSLA in a modest 1-3 month pair only after R2 ramp evidence, rather than outright RIVN ahead of data. RIVN has a company-specific cost-down catalyst while TSLA remains more exposed to EV price competition and a higher autonomy valuation bar; stop the pair if TSLA demonstrates a material FSD monetization acceleration or RIVN misses weekly production targets.
• Avoid underwriting Uber robotaxi economics before disclosed technical milestones and unit licensing economics. Set an event alert around the next committed funding tranche: receipt is a near-term positive liquidity signal, while deferral would likely expose the contingent nature of the commercial commitment and warrants a short RIVN tactical hedge.
• Monitor MBLY for a 6-18 month competitive read-through rather than shorting on this disclosure alone. A confirmed RIVN point-to-point rollout and a successful Volkswagen software launch would strengthen the case that OEMs are selectively insourcing; MBLY's offset is its broader customer base and lower-cost ADAS positioning, so a contract-loss or guidance-revision catalyst is required before acting.