Collapsing Design-to-Code Handoff
Eric Simons, CEO of Bolt, on consumer vs. B2B vibe coding
This reveals that the real fight is not design versus code, but prototype versus production. Figma built its franchise around helping teams sketch, comment on, and hand off interface ideas, while Bolt is trying to collapse that handoff by turning the first draft into working software that can plug into a company’s existing codebase, design system, auth, and data stack. That shift changes who owns the workflow and where software budgets land.
-
Bolt’s strongest evidence for this wedge is where retention showed up. After broad consumer usage churned, it found stickier demand with product and engineering teams, with B2B at about 25% of revenue at the time of the interview and expected to pass 50% within the year. That is the classic pattern of a tool moving from novelty to workflow.
-
The practical difference is whether a PM can make something engineers keep. In Figma, the common flow is mockup, feedback, then rebuild by hand. In Bolt, the goal is to ingest the company’s actual components and codebase so the output already matches how the company ships software. That makes the prototype usable as a starting product, not just a picture.
-
Incumbents still have serious advantages. Figma has huge distribution, about $1.05B of 2025 revenue, and can bundle adjacent tools into existing seats. Bolt has speed and focus, plus browser based infrastructure that supports fast iteration and roughly 70% gross margins, but it has to prove that this workflow becomes standard inside large teams before incumbents close the gap.
The next phase is a split market. Some products will stay visual and lightweight, like the next generation of website builders, while others will become serious software creation tools for product teams. If Bolt keeps turning company context into production ready code, it can move from a fast demo tool into a new control point inside enterprise software development.