WhoBuilt

We Were Going to Shut Down Our Company…Now We’re Worth $700M

Feb 23, 2025· 48 min· 4.4K views·Watch on YouTube

Speaker

Eric Simons, CEO of Bolt, joins Peter Yang to demonstrate Bolt and discuss how StackBlitz went from considering a shutdown to rapid growth.

Build and refine apps with Bolt

Simons demonstrates Bolt turning prompts into web and native mobile apps, including a Spotify-style app and a meditation app. He shows a live phone preview through Expo Go, image-guided UI changes, and how to undo edits or refresh a broken development environment.

Plan work in small steps

For production work, Simons recommends planning pages and behavior, then splitting the plan into concrete tasks. He suggests building and checking the UI first, then adding databases, authentication, and other functionality in chunks. When repeated bug fixes fail, he advises stepping back to gather context or asking for help.

A browser technology bet meets better models

Simons traces StackBlitz to a long effort to run a development environment inside the browser. After struggling to find a viable business, the team revisited Bolt as models improved, greenlit it on July 1, and launched in October. He says Bolt reached $20 million in ARR in its first two months.

Local execution and open source shape the product

Simons says Bolt runs its computing on users’ devices rather than provisioning a cloud VM for each person, which he connects to lower latency, offline editing, and a more generous free tier. He says opening Bolt’s core and system prompts helped the community test models, improve prompts, and contribute features.

Build for fast customer feedback

Simons says Bolt aims to serve developers as well as product managers, designers, and entrepreneurs, while keeping the tool powerful and reliable. Because models may quickly make some product work obsolete, he weighs which investments will last. He sees rapid prototyping as a way to get ideas in front of customers sooner and learn whether they solve a real problem.

Takeaways

  • Write down the pages and behaviors you need, then give the coding tool one concrete task at a time.
  • Finish and review the UI before adding authentication, databases, and business logic.
  • If repeated bug fixes fail, pause and gather more context instead of retrying the same prompt.
  • Use prototypes to get customer feedback early, before investing heavily in implementation.
  • In fast-changing AI products, prioritize work that remains useful as models improve.

Mentioned in this talk

Search inside this talk

What was claimed 15

Related talks