Bolt’s Shift to Agent Teams
Eric Simons, CEO of Bolt, on consumer vs. B2B vibe coding
Bolt is trying to turn AI app building into a manager dashboard for digital labor, not just a faster code editor. The important shift is from one agent helping one person write code, to one product team member directing many specialized agents that can draft demos, build landing pages, wire up auth and databases, and produce code that fits a company’s existing design system and codebase. That is how Bolt moves from consumer experimentation into sticky B2B workflow software.
-
Bolt’s wedge is not generic agent chat, it is enterprise context. The product is built to ingest a company’s codebase and design system so a PM can click around visually and generate production ready app work, where Bolt says tools like Replit and Lovable are still stronger for throwaway prototypes or top of funnel consumer use cases.
-
The business logic behind the agentic team idea is retention. Bolt says consumer users arrived fast but churned, while product and engineering teams showed classic B2B SaaS retention. B2B revenue is around 25% of revenue today and expected to pass 50% within the year, which makes the long term prize not hobby projects but software budgets inside companies.
-
This mirrors a broader market split. Cursor and Claude Code are becoming tools for professional developers inside existing workflows, while Bolt, Lovable, and Replit started by letting non engineers generate apps from prompts. The category is now converging on multi agent workflows, but the durable winners look more like work software with context, deployment, and team adoption than pure prompt boxes.
The next step is a broader work operating layer where each function gets its own packaged agents, starting with product and engineering because that is where the budget, workflow depth, and retention are strongest. If Bolt keeps owning the handoff from prompt to real shipped software, it can expand from app generation into a full agent management surface across the company.