In August 2026 SpaceX closed its acquisition of Anysphere, the company behind Cursor, for an implied $60 billion in stock (Wikipedia, Techzine). The same month Lovable raised $400 million at a $13.3 billion valuation (Dealroom). In March, Replit raised $400 million at $9 billion (Trending Topics).
Those are headlines. What matters for developers is what the numbers say about where value is moving, and what that means for the things we choose to build.
The numbers, with sources
| Company | Revenue signal | Latest capital event |
|---|---|---|
| Cursor | ARR of $100M in Jan 2025, $500M in Jun 2025, over $1B around Nov 2025, about $3B in May 2026 | Acquired by SpaceX, closed 14 Aug 2026, implied $60B |
| Lovable | $200M ARR in Nov 2025; run rate near $600M expected by end of Aug 2026 | $400M Series C at $13.3B, Aug 2026 |
| Replit | About $265M ARR at end of 2025; company targets $1B by end of 2026 | $400M at $9B, Mar 2026 |
Sources: Cursor figures from Wikipedia (citing Bloomberg and company statements); Lovable from Wikipedia and Dealroom; Replit from Trending Topics.
Two details stand out.
Cursor went from $100M to roughly $3B ARR in about 16 months with a team Wikipedia put at roughly 300 people in August 2025. That is an unusual revenue per head for a developer tool.
Lovable started as an open source project. Anton Osika first built GPT Engineer, an open source code generation tool, before turning it into the commercial product in late 2024 (Wikipedia). Open source core, product layer on top, then distribution. That pattern keeps repeating.
What this tells us as builders
1. Writing code is no longer the scarce part
When the tools that generate code are worth tens of billions, the code itself is getting cheaper. A CRUD dashboard, an auth flow, a Stripe integration: these are now hours, not sprints. If your product's main value is "we wrote the software", you are competing with a prompt.
2. The moat moved up the stack
What is still hard, and therefore still valuable:
- A specific workflow in a specific industry. "AI for dental clinic billing" beats "AI app builder #47".
- Proprietary context. The documents, integrations and data your users already have, wired in properly.
- Reliability. Evals, fallbacks, observability and cost control for LLM calls. Demos are easy; the 95th percentile request is not.
- Distribution. Owning a channel to your buyer.
3. Generic builders get you to a prototype, not always to production
Lovable, Replit and Cursor are excellent for getting something working. The gaps usually show up in the same places:
| Layer | What tends to break |
|---|---|
| Auth and roles | Multi-tenant permissions, SSO for B2B buyers |
| Data | Migrations, backups, row-level security |
| Payments | Usage-based billing, proration, tax |
| LLM features | Prompt drift, no evals, runaway token cost |
| Ops | Logging, alerting, background jobs, rate limits |
None of these are exotic. They are just the boring 20% that decides whether a paying customer stays.
A practical architecture for an AI product in 2026
Here is the shape we see working for small teams shipping fast:
Frontend (Next.js / React) -> API layer (typed, versioned)
|
+---------------------+----------------------+
| | |
Postgres (RLS) LLM gateway (Claude + Job queue
+ object store fallback model, caching, (retries,
per-tenant cost limits) webhooks)
|
Eval suite on real traces
Three choices that matter more than framework debates:
- Put an LLM gateway in front of every model call. One place for retries, caching, logging and per-customer spend caps. It turns model swaps into config changes.
- Store traces from day one. Every prompt, response, latency and cost. Your eval set is built from these, and so is your answer when a customer says "it got worse".
- Keep the AI feature narrow. One job done reliably beats ten done at 70%.
Where to point your next build
If code generation keeps getting cheaper, the opportunities are where AI meets a real workflow that someone pays for today: intake and scheduling, document review, outbound follow up, reporting, internal search over company knowledge. Pick one buyer, one painful job, and ship a version they can pay for in weeks.
At Axionry, an AI product development studio, this is the work we do every day: taking an idea or a prototype from a tool like Lovable or Cursor and turning it into a production product with auth, billing, evals and monitoring. If you are sitting on a prototype that needs to become a business, book a call.
What is the hardest part of taking your prototype to production? I read every comment.
Top comments (0)