Lovable Doubles to a $13.3 Billion Valuation

Is a company that doubled its valuation in eight months genuinely worth twice as much?

Stockholm based Lovable confirmed a $400 million Series C on August 12, valuing it at $13.3 billion. Menlo Ventures and the Scaleup Europe Fund co-led, with more than a dozen other investors joining. In December 2025 the company raised $330 million at $6.6 billion, in a round Menlo also led.

The numbers the company is putting forward

Lovable belongs to the category people have started calling vibe coding: you describe the application you want in plain language and the platform produces a working interface.

The reported figures are aggressive. As of June 2026, $500 million in annualized run rate revenue, 60 million hosted projects, 900 million monthly visits and a million new projects created every week. The company runs its own in-house model alongside frontier models from other labs, and a multiyear Google Cloud agreement signed in June reportedly reflected a fivefold jump in usage.

Which of those figures survives contact with reality?

A million new projects a week is a striking number that leaves the important question open: how many are still running three months later? Creating a project on these platforms costs essentially nothing, so the count may be measuring curiosity at least as much as demand.

Annualized run rate deserves the same scrutiny. It takes a single month's revenue and multiplies by twelve, which flatters a company that is accelerating and punishes one that has started to slow. It is a snapshot presented as a trajectory.

One more detail belongs in the file: the same fund led both rounds. An existing investor re-leading can signal genuine conviction, or it can signal that no outside party stepped up to set a new price. The next round is what tells you which.

An honest read from a software company

Dismissing these tools has become fashionable and it is wrong. We use them. Getting an idea in front of a client in hours rather than weeks is a real gain. For prototypes, internal tools and one-off dashboards, describing what you want is entirely sufficient.

The divide shows up later. Shipping the first version of a system and keeping it alive for three years are different jobs. Once software carries customer data, integrates with finance systems, falls under data protection review and is worked on by six people at once, the cost does not appear on day one. It appears in year two.

The pattern we see repeatedly: a company builds its internal tool on one of these platforms, runs happily for six months, then asks us to take it over as it scales. That handover is sometimes harder than a rewrite, because nobody ever chose an architecture. The choices simply accumulated.

So use them for the prototype without hesitation. But for the system your business actually runs on, settle three things on day one: who owns it, where the data lives, and who maintains it two years from now.

Sources: TechCrunch