Lenny's Podcast
Lenny's Podcast

Inside Bolt: From near-death to ~$40m ARR in 5 months—one of the fastest-growing products in history | Eric Simons (founder and CEO of StackBlitz)

Eric Simons is the founder and CEO of StackBlitz, the company behind Bolt—the #1 web-based AI coding agent and one of the fastest-growing products in history. After nearly shutting down, StackBlitz launched Bolt on Twitter and exploded from zero to $40 million ARR and 1 million monthly active users

Featured Speakers

Lenny Rachitsky HostEric Simons Guest

Topics Discussed

Episode Summary

Executive Summary: Eric Simons explains how StackBlitz’s seven-year investment in browser-based development tech (WebContainer) enabled Bolt’s explosive growth as a text-to-app tool. Bolt hit massive ARR and user growth after launch because it’s fast, reliable, and runs entirely in the browser, while the conversation explores why AI coding is changing product development, org charts, and the roles of PMs, designers, and nontechnical founders.

Main Topics: Bolt’s explosive growth and scale (Priority: 5/5): Eric and the host discuss Bolt’s unprecedented revenue and user growth shortly after launch, emphasizing that the company went from near shutdown to one of the fastest-growing products in startup history. WebContainer as the foundational technology (Priority: 5/5): The core technical bet behind StackBlitz was building a browser-based operating system/runtime that powers Bolt’s speed, reliability, and free-tier economics. Why the launch worked: product-market fit plus timing (Priority: 5/5): Bolt succeeded because frontier models like Anthropic’s Sonnet finally made code generation reliable enough for production-grade use, creating a step-change in utility. Startup survival, conservative execution, and team structure (Priority: 4/5): Eric argues that staying alive long enough, keeping burn low, and relying on a small, high-trust, long-tenured team were critical to surviving until the right opportunity appeared. How Bolt changes product development (Priority: 5/5): The discussion highlights how PMs, designers, entrepreneurs, and nontechnical users can now build real software, prototypes, and even production apps directly from prompts. Prioritization, workflow, and company operating cadence (Priority: 4/5): Eric describes a highly synchronous company process, daily all-hands zooms, lightweight PRDs, and a mix of customer feedback plus founder instinct to choose what to ship. Future org charts and skill needs in an AI-native world (Priority: 4/5): The episode projects fewer routine engineering tasks, more leverage for PMs/designers, and a growing need for people who can define problems, direct AI, and unblock it when necessary.

Key Arguments: Bolt’s growth is real and demand-driven, not just hype; customers use it because it materially reduces cost and time to build software. The seven years spent building WebContainer were the true prerequisite for Bolt’s success; Bolt is an overnight success seven years in the making. Browser-based compute is the right scaling model for mass-market app building because it is faster, more reliable, and avoids cloud VM bottlenecks and costs. Conservative spending and small-team intensity preserved the company long enough to find the right product-market fit. The best hires are people with high trust, low ego, and broad agency—not title-driven specialists. AI coding tools are shifting software creation from engineers being the primary builders to PMs/designers/founders defining and directing work. LLMs are especially suited to coding because software is deterministic, making code generation easier to train and validate than many other domains. Future product orgs may center around smaller pods with more PM/design leverage and fewer developers focused on routine UI work. Bolt is best used like a developer coworker: users should be specific, thoughtful, and willing to iterate with prompts. Current limitations are mainly large existing codebases and the need for human help when the AI gets stuck on edge cases.

Data Points: ARR at launch (first two months): $20 million - Bolt went from zero to $20M ARR in its first two months after launch. ARR at time of recording: $30M–$40M ARR - Eric says they crossed $30M ARR and are approaching or expected to hit $40M soon. Annual forecast: $100 million ARR - Eric says the company’s forecast for the year is $100M ARR. Registered users: Over 3 million - Bolt’s total registered user count in the discussion. Monthly active users: Around 1 million - Eric estimates Bolt’s monthly active users at roughly one million. Team size: 15–20 people - Eric repeatedly notes that Bolt is being run by a very small team. Support team size: 3 people - He says support is handled by about three people despite massive growth. Launch-day ARR: About $60K ARR - On day one after launch, Bolt added roughly $60K ARR. Next-day ARR: About $80K ARR - The day after launch, ARR rose again by roughly $80K. Build time for Bolt: 90 days - Eric says the Bolt product itself was built in about 90 days. Users who are not developers: 67% - Eric says 67% of Bolt users are not developers. First person built use case: CRM in 3 weeks - A user built a CRM with AI and Stripe in three weeks using Bolt. Agency quote comparison: $30,000 vs. $300 - The CRM example contrasted an agency quote with Bolt’s much lower cost. Mobile app beta launch timing: Last week - Eric says mobile app support was launched in beta the week before recording. Frontend timeline comparison: 1–2 years expected, but not yet - He says current model quality changed the calculus for mobile and web app creation. Early personal burn rate: $1/day - Eric recalls living on a dollar a day while starting out in Silicon Valley. AOL office period: 4–5 months - He says he lived/squatted in the AOL office for several months as a broke founder.

Pivotal Quotes: "“Bolt’s this overnight success, seven years in the making.”" — Eric Simons: Describing the product’s launch as the result of a long foundational technology investment. "“Most importantly, it’s been the people.”" — Eric Simons: Explaining why a tiny team was able to scale so quickly and survive the pre-launch years. "“Talk to this thing like you would a Linear ticket or a Jira ticket.”" — Eric Simons: Advice for new Bolt users on how to prompt effectively and get better results.

Implications: AI coding is shifting value from implementation to problem definition, product taste, and iteration. PMs, designers, and founders gain leverage; teams that master browser-native, AI-assisted workflows may ship faster with fewer engineers.

🔓 Sign Up for Unlimited Episode Search

About Lenny's Podcast

Lenny Rachitsky interviews world-class product leaders and growth experts about building products and growing careers.

View all episodes from Lenny's Podcast