Cursor bets on developer augmentation
Cursor
Cursor is betting that the biggest AI coding market is not software that replaces engineers, but software that lets one engineer do the work of several while still owning every important decision. That shows up in the product itself. Cursor lives inside the IDE, works on an existing codebase, and has moved from autocomplete toward agent mode, terminal actions, and web search, while still keeping the developer in the loop. Meanwhile tools like Lovable, Bolt.new, and Vercel v0 are built to get a non engineer from prompt to app fast, then hand the project off when real code editing starts.
-
The workflow split is concrete. A non technical user can prompt Lovable or Bolt.new to generate a working app, export the repo to GitHub or a local folder, then move into Cursor for real editing, debugging, and iteration. That makes app generators a top of funnel for software creation, and AI IDEs the place where serious maintenance begins.
-
Cursor’s revenue base reflects this developer first wedge. It reached about $100M ARR by the end of 2024 from roughly 360,000 mostly individual developers paying $20 to $40 per month, then doubled to $200M ARR by March 2025. This is bottom up adoption by working engineers, not classic enterprise automation sold to business users.
-
Platform risk is real because the model labs are moving down the stack into coding products. OpenAI reportedly agreed in May 2025 to buy Windsurf, and Google launched Jules in public beta in May 2025 as an autonomous coding agent. Cursor’s answer has been to deepen the product layer with default agent mode and built in web search, so the IDE stays the daily home for developers even if the underlying models change.
This split should harden into a two layer market. One layer will turn ideas into first drafts for anyone who can describe a product. The other will own the ongoing work of changing, testing, reviewing, and shipping production code. Cursor is positioned to own that second layer, which is also where retention, enterprise spend, and long term control of developer workflow are likely to concentrate.