Bolt.new grew from $0.7 million ARR after seven years to more than $20 million ARR shortly after launch, with a team of fewer than 20 people.
2
A small team with shared context, high trust, and low overhead can move faster and survive longer while searching for product-market fit.
3
Bolt scaled support with AI, weekly public office hours, and user community programs instead of rapidly adding headcount.
Summary
Eric Simons describes how Bolt.new went from a company preparing to shut down to more than $20 million in ARR shortly after launch. The product launched as a very small and brittle MVP, while fewer than 20 people handled tens of thousands of customers and a large support burden. Simons attributes the result to a team that had worked together for years, shared context, low ego, and enough trust to act without permission. He argues that low headcount preserves runway and lets a company take more product shots before finding product-market fit. The team also made hard choices about which problems to address, communicated directly with users through weekly office hours, and used AI support software to handle most tickets. Simons is candid that the first two months were unstable. His advice is grounded in the company's specific operating habits: keep teams small, decide independently, lead visibly, and get products into users' hands quickly.
Bolt.new arrived after seven years of trying to find a commercial path
StackBlitz had been operating for seven years before Bolt.new launched. In October of the previous year, the company had reached only $0.7 million ARR, and the team had fewer than 20 people. Simons says they were preparing to shut down because they could not find a commercial offering that made sense at venture scale. Their hope for the new product was modest: adding $100,000 ARR by the end of the year would have felt like a major win. The launch instead produced a clean growth curve that went far beyond those expectations.
A small team can move quickly because each person carries more context
Simons says the team operated with a small number of people who had more context per person. That gave them agency to build without asking for permission or passing decisions through a chain of command. He connects this approach to the company's earlier bootstrapped experience, when he and his co-founder had to stretch every dollar while living on couches. Keeping headcount low also reduced burn. In his view, that gives a startup more time to take product shots while it searches for product-market fit.
Simons compares finding product-market fit with an enterprise sales pipeline. A company needs to talk to many potential users because only some will become warm leads and only some of those will convert. That process requires time, which makes burn rate important. He gives the example of a former IDE competitor that was acquired and stripped for parts two weeks before Bolt launched. Simons believes the competitor could have mattered in the market, but it did not have enough runway to reach the other side.
The team needed trust and resilience during the support crisis
The launch created a situation where tens of thousands of customers were arriving while no one on the team had support in their job title. Simons and his chief of staff handled many support tickets themselves. He says the company managed this because the team had worked together for seven years and already operated with alignment, speed, and lean habits. He also names low ego, high trust, user focus, grit, and resilience as traits needed when a startup is under sustained pressure.
When many parts of a startup are failing or demanding attention, Simons uses the image of one fire truck in a town that is entirely on fire. The team must choose the high-impact areas, including the infrastructure and people that most need attention. Some fires will remain unsolved because a small team cannot address everything. He argues that focusing on roughly 10% of the available work can produce most of the result that matters, while also forcing clearer decisions about where time goes.
Founders should make decisions from their own view of reality
Simons warns against automatically following startup fashion. He describes how remote work was dismissed around 2017 and 2018, became widely promoted during the pandemic, and then began shifting back again. He also recalls investors urging companies to raise more money and hire aggressively in 2021, followed by demands for layoffs and spending cuts in 2022. Simons says his company kept its headcount and spending relatively low instead of following those changes. He supports independent thinking, while acknowledging that some repeated advice is sound.
Visible communication helped keep early users from leaving
The first week after launch was unstable because the product was brittle. Simons believed users would churn if the team stayed invisible while it worked through the problems. Bolt started weekly office hours on YouTube and X, where the team showed what it was building, acknowledged user feedback, and gave estimates for when changes might arrive. He calls this an example of doing things that do not scale. Direct contact helped users maintain belief in the product while the team continued to improve it.
AI support and community reduced the need to add staff
During the first two months, Simons and his chief of staff were the main support people. The company then adopted the AI assistant SAM from Parah Help, which Simons says automatically handled 90% of their tickets. He contrasts this with the staff they might have needed in an earlier period. Bolt also built AI into the product to help users succeed, and used community spaces where users could learn from one another. Simons presents these efforts as part of the whole customer-success experience, rather than only as AI product features.
Bolt's product process depended on personal excitement and fast launches
In the question period, Simons says the company tried about five different things in the previous year. Products that worked for him usually began with something he personally found exciting, rather than an idea chosen only because it sounded like it might increase ARR. Bolt was one of the ideas he was deeply excited about. Early users also responded well, but Simons cautions that early feedback can look similar across products with very different outcomes. The practical test is to launch, see what happens in the world, and iterate quickly.
"You want to have these sort of bets that you make, and I don't want to say it's you don't want to be contrarian for contrarian sake."10:43
Who should watch
You are running a startup with limited runway and need to decide whether another hire will create more value than more time to iterate.
Your small team is overwhelmed by support, infrastructure problems, or competing priorities during a sudden growth spike.
You are choosing a product direction and want a founder's account of why personal conviction, public user contact, and fast launches mattered.
