April 7, 2026
Speed run or slow burn?
Moving fast in hardware: lessons from lab to $100M ARR
From lab to $100M—some cheer, others say 17 years isn’t fast and ask if the money repeats
TLDR: A founder says simplifying hardware design helped his car-tech startup hit $100M in recurring revenue; commenters clap back, questioning whether the revenue truly repeats and noting a 17-year journey with big funding. The debate: disciplined design versus survivorship spin—and what “moving fast” really means in hardware.
Founder-engineer Zack Anderson dropped a victory-lap essay on how to “move fast” in hardware: delete fancy requirements, design for real-life use, push complexity into software, and boom—ClearMotion’s ride-smoothing car tech hits “$100M ARR.” But the comments slammed the brakes. Is that revenue really recurring (subscription-style) or just big contracts? One skeptic called recurring hardware revenue “rare,” while others pointed out the company’s 2009 founding, $370M raised, and a billion-dollar deal with Nio—arguing this looks more like a long, expensive slow burn than a sprint.
The hottest take? A charge of survivorship bias: cool philosophy, sure, but it’s easier to preach “simplify, then add lightness” after a decade-plus and deep pockets. Another commenter claimed the company even acquired Bose’s earlier suspension tech, undercutting the “we invented it all” vibe. Still, defenders chimed in with practical wisdom: “Outsource the mature, insource the uncertain,” praising the focus on everyday driving instead of race-track extremes. Meanwhile, the meme machine revved: “17-year speedrun,” “ARR = Actually Recurring Revenue?,” and “Delete requirements, add fundraising.” Whether you see a disciplined masterclass or a glossy post-hoc story, the thread boils down to a single split-screen: fast-thinking vs. fast-shipping—and which one counts as speed.
Key Points
- •Zack Anderson frames speed in hardware as reducing the learning loop, not relying on heroic effort.
- •The article’s first lesson is to delete nonessential requirements to reduce complexity and cycle time.
- •Past active suspension attempts (Bose’s electromagnetic and Lotus’s hydraulic) targeted high peak forces, leading to heavy, complex architectures; Bose’s system, per the article, never shipped.
- •ClearMotion instrumented hundreds of cars and used real-world driving data to set requirements, reducing peak force targets to about 20% of earlier benchmarks.
- •Lower-force design enabled a simpler, faster, and cheaper architecture (about 90% lower cost), moving complexity into software and accepting rare edge-case trade-offs.