Rivian’s Also delays TM-B e-bike deliveries to 2026 citing supply chain and regulatory hurdles

Rivian’s Also TM-B e-bike was positioned as a software-defined mobility product, but its complexity has led to unexpected delays. The bike’s reliance on custom PCBs and integrated circuits has collided with supply chain disruptions, particularly in sectors prioritizing AI hardware. This mirrors broader challenges in sourcing specialized components for niche applications, where demand from larger industries can outpace supply. For engineers, the delay serves as a reminder that even well-funded projects can face bottlenecks when dependent on constrained or oversubscribed materials.

The TM-B’s battery and power delivery system introduce regulatory hurdles that compound the delays. The 240W output exceeds current e-bike standards, forcing Also to collaborate with standards bodies to define new testing protocols. This process is inherently slow, as it requires consensus across manufacturers, safety organizations, and government agencies. The situation illustrates how innovative designs can outpace existing frameworks, creating friction between ambition and compliance. Engineers working on power-dense systems should anticipate similar challenges when pushing beyond established norms.

The pedal-by-wire drivetrain, a core differentiator for the TM-B, has proven difficult to scale. The system replaces mechanical linkages with software-controlled motors, requiring tight tolerances in manufacturing. Also’s admission of a “slower production ramp-up” suggests that early prototypes may not have fully accounted for mass-production constraints. This is a common pitfall in hardware development, where lab-tested designs encounter yield or assembly issues at scale. The delay underscores the importance of designing for manufacturability early, even in high-margin or low-volume products.

Also’s public apology on Reddit reflects a shift in how companies handle delays, particularly in consumer-facing hardware. The transparency about supply chain and engineering challenges may mitigate customer frustration, but it also sets expectations for further revisions. For engineers, this highlights the growing need to communicate technical constraints to non-technical stakeholders. The apology’s focus on maintaining quality over timelines suggests a strategic choice to prioritize long-term reputation over short-term revenue, a calculation that may resonate with other hardware startups facing similar trade-offs.