Why Lovable Becomes Worthless

There is a specific category of AI startup that looks like a rocket ship right now and is, in fact, a sandcastle at low tide. Lovable is the cleanest example, but the argument applies equally to Bolt, v0, Replit Agent, and the dozen other “describe an app, get an app” products that raised at unicorn valuations in 2024 and 2025. A structural argument about where value accrues in the AI stack — and where it does not.

There is a specific category of AI startup that looks like a rocket ship right now and is, in fact, a sandcastle at low tide. Lovable is the cleanest example, but the argument applies equally to Bolt, v0, Replit Agent, and the dozen other “describe an app, get an app” products that raised at unicorn valuations in 2024 and 2025. They will not exist as standalone businesses in three years. Here is why.

What Lovable actually sells

Strip away the marketing and Lovable is three things stacked on top of someone else’s model. There is a system prompt that turns “build me a recipe app” into structured instructions a frontier model can execute. There is a code execution sandbox that runs the output, shows you a preview, and lets you iterate. And there is a deployment pipeline that takes the resulting app and pushes it somewhere a customer can actually visit. The model — Claude, usually — does the hard part. Lovable does the wrapping.

This is a real product. It solves a real problem. The problem is that none of the three layers is defensible, and the company that owns the underlying model can replicate all three of them in an afternoon.

The wrapper problem

Every wrapper company eventually faces the same question: what stops the model provider from eating you? For most of software history this question had good answers. The cloud provider doesn’t want to be in the CRM business. The database vendor doesn’t want to build dashboards. Specialisation was protective. AI labs do not respect this boundary, because their product is general-purpose intelligence and every vertical application is, from their perspective, just a prompt and some UI.

Anthropic shipped Artifacts. OpenAI shipped Canvas. Both let you generate working applications inside the chat interface, with previews, with iteration, with no separate subscription. The labs are not pretending they will leave the application layer alone. They are actively colonising it, because the application layer is where the revenue lives and the model layer is racing toward commodity pricing. Lovable’s entire surface area is now table stakes inside ChatGPT and Claude.

The capability problem

Lovable’s second moat is supposed to be that it does this one thing better than a general chatbot does. The prompting is tuned. The scaffolding is opinionated. The output is more reliable. This is true today and will be untrue within twelve months.

Frontier models improve on a curve that flattens specialised wrappers. The gap between “Claude in a chat window” and “Claude inside Lovable” is currently maybe a 20% reliability difference on app generation tasks. Next year it will be 5%. The year after that, Claude’s native interface will be better at building apps than Lovable is, because Anthropic has more telemetry, more compute, more researchers, and a direct financial interest in closing that gap. Lovable’s engineering team, however talented, cannot outrun a frontier lab on the lab’s home turf.

The substitution problem

Even setting the labs aside, Lovable faces a second commoditisation pressure from below. Open-weight models — Llama, DeepSeek, Qwen, whatever ships next quarter — are now good enough to build simple CRUD apps. The scaffolding required to wrap them is open source. Within a year, a competent developer can self-host a Lovable equivalent on a $200/month GPU instance and pay nothing per generation. The Kigali teenager I keep thinking about can build and sell a Lovable clone targeted at their local market, in their local language, at a tenth of the price, with margins Lovable cannot match because Lovable is paying retail API rates to Anthropic.

This is the part the current valuations do not price in. Lovable is not just competing against the labs above it. It is competing against every developer who can string together an open-weight model, a code sandbox, and a Vercel deploy hook. That competition arrives faster than people expect because the AI itself accelerates the cloning.

The user problem

There is one more layer, and it is the one that ultimately decides this. Lovable’s customers are not loyal. They cannot be loyal. The product is a thin layer over a model, and the customer knows it. The moment a competitor offers the same thing for half the price, or the moment ChatGPT does it for free, the switching cost is approximately one signup form. Software-as-a-service businesses survived on switching costs — your data is in our system, your team is trained on our UI, your integrations point at our endpoints. Lovable has none of these. The output is an app you own and host yourself. There is nothing to switch away from because there was never anything locking you in.

What the cap table assumed

Lovable raised on a story about a new category of software creation, with the implicit assumption that being early to that category would compound into a durable position. This is the SaaS playbook applied to a market that does not have SaaS dynamics. Figma got durable because design files lived in Figma and teams collaborated inside it. Notion got durable because companies put their knowledge into it and could not easily extract it. Lovable produces exports. The whole point of the product is that you leave with something. There is no equivalent of the Notion workspace or the Figma file pulling you back in.

The valuation only makes sense if you believe Lovable becomes the default interface for non-technical people building software, and stays that way, and the labs decide not to compete, and open-source stays behind, and switching costs somehow materialise. Each of those is a coin flip. Multiply them together and you get a low single-digit probability supporting a multi-billion dollar valuation.

What happens next

The endgame is not dramatic. Lovable does not collapse. It gets quietly outcompeted on three fronts simultaneously — by the labs above it bundling the same capability into their flagship products, by open-source clones below it offering the same capability for free, and by vertical specialists carving out the segments where domain knowledge matters more than generic app generation. Revenue plateaus. The next funding round happens at a flat valuation, then a down round. The team is acquired by one of the labs for the talent. The product is sunset eighteen months later.

This is what commoditisation looks like in practice. It is not a crash. It is a slow leak in a market that briefly believed wrappers could be platforms.

A falsification schedule

The piece’s claim that Lovable will not exist as a standalone business in three years is the kind of prediction that gets stronger by being wrong on a calendar. Here is the schedule against which to mark the publication’s working.

By Q4 2026: Lovable announces a flat round, or a down round, or postpones its next round on the grounds that “market conditions” have changed. ARR growth slows to under 50 per cent year-on-year, having previously been over 100 per cent. If none of these happen and the company raises a clean up-round above its 2025 valuation, the piece is starting to look wrong.

By Q4 2027: Acquisition discussions become public, or one of the major labs (Anthropic, OpenAI, Google) launches a direct competitor inside its flagship product that captures a meaningful share of Lovable’s use cases. ChatGPT’s native app-building feature, or Claude Artifacts extended to deployment, would each count. If by this date Lovable is still independent, still growing, and the labs have not crossed materially into its surface area, the piece is wrong.

By Q4 2028: Lovable has been acquired (most likely by a lab for the team), has sunset its core product in favour of a pivot to a different segment, or is operating as a profitable lifestyle business at a fraction of its former valuation. If by this date Lovable is a public company or a unicorn at higher valuation than its 2025 round, with positive net revenue retention and a defensible market position, the piece’s entire diagnosis was wrong and the publication owes the company an apology.

The publication’s prediction is not that Lovable goes to zero. It is that the company’s pitch-deck story — durable category leader, platform economics, defensible moat — gives way within three years to a story that looks like a normal venture outcome at a much lower price. The dates above are how to check.

Why some vertical wrappers will survive when Lovable will not

The diagnosis above is sharper if it can explain why the same wrapper structure has, in some cases, produced durable companies. Three of them are worth naming.

Cursor is a wrapper around frontier coding models, exactly the structure the piece argues is doomed at the application layer. Cursor has nonetheless reached over a hundred million dollars in ARR and shows every sign of durability. Why? Because the wrapper is doing real engineering work that the underlying model is not doing — multi-file context management, indexing of large codebases, agent loops that operate over project structure rather than over single prompts, deep IDE integration that the model labs would have to rebuild from scratch. Cursor’s product is not “Claude in a code editor.” It is a code editor whose context engine is the actual product, with the model as one input. The labs can ship code-generation features inside their chat interfaces, and they have, but they cannot easily ship an IDE.

Harvey is a wrapper for the legal profession. It looks superficially like Lovable: model on top, prompt scaffolding, vertical UI. The difference is that Harvey has built distribution into the top fifteen US law firms by hiring the people who already had those relationships, has integrated with the document-management systems those firms actually use, and has accumulated training data and feedback loops from inside privileged client work that a general lab cannot easily replicate. The model is interchangeable; the distribution and the workflow integration are not.

Perplexity wraps frontier models for search, again the structure the piece argues is doomed. Perplexity survives because it has built a brand and a habit in a specific use case (research-grade search with citations) that the general chat interfaces have not, by default, prioritised. The labs could compete here and to some extent are doing so, but Perplexity has run faster on the specific product and has built distribution — partnerships with browsers, mobile app placement, an Apple-Intelligence integration — that the labs do not automatically inherit.

The pattern across these three is the same. Cursor, Harvey, and Perplexity each do something other than the model that is genuinely hard, that the labs do not automatically do, and that compounds with use. Lovable, on the analysis above, does not. The system prompt is replicable, the sandbox is replicable, the deploy pipeline is replicable, and there is no workflow integration, no domain data, no distribution relationship, no compounding context engine. The diagnosis the piece offers is not “all AI wrappers die.” It is “wrappers without one of distribution, domain integration, or proprietary context die, and Lovable has none of the three.”

Distribution as the real moat, when there is one

The piece’s earlier paragraphs treat distribution as one factor among several. It is the central factor, and deserves its own section, because the actual defensibility argument for AI-application companies — where it exists — runs through distribution rather than through technology.

The labs have one weakness, and only one. They sell horizontally. Their distribution is “anyone with a credit card and a browser.” This is enormous reach but it is also undifferentiated reach. When a customer is a Fortune 500 legal department, or a hospital system, or a state government, or a sovereign-wealth-fund family office, the lab’s horizontal product cannot easily meet the specific compliance, integration, procurement, and trust requirements those customers impose. Vertical wrappers that build those distribution relationships acquire something the labs cannot replicate in an afternoon: a customer base that requires a person on the other end of the phone, a service-level agreement, a procurement record, and a working integration with the customer’s existing data systems.

Harvey has this. Hippocratic AI has this for hospital systems. Tessl has it for enterprise software development. Anduril has it for defence. In each case, the technology is replicable; the distribution relationship is not. A lab can ship a feature that does the same thing, technically, but cannot ship the procurement contract or the integration debt or the years of relationship that made the customer comfortable signing.

This is what Lovable is missing, and the absence is not accidental. Lovable’s entire pitch is that it removes friction — sign up, type a prompt, get an app, deploy. The product is built for self-service, which means it has, by design, no distribution moat. Self-service is fast to acquire and infinitely fast for the labs to copy. The companies that survive the wrapper apocalypse will be the ones whose customers cannot, by the nature of those customers, be self-served. Lovable’s customers can. That is the whole story.

The broader lesson

The interesting question is not whether Lovable specifically survives. It is what the existence of products like Lovable tells us about where value accrues in the AI stack. The answer, increasingly, is not at the application layer for general-purpose tools. Value accrues at the model layer if you can stay at the frontier, at the infrastructure layer if you sell compute, and at the user layer if you bring distribution the model does not have. The middle — generic wrappers selling access to someone else’s intelligence with a prettier interface — is the worst place to be. It is too far from the model to capture the margin and too far from the customer relationship to capture the loyalty.

Lovable is not the villain of this story. It is the canary. The same logic flattens every company whose pitch deck includes the phrase “we use AI to…” without a serious answer to the question of what happens when the AI does the using itself.

For the companion structural argument about productivity and the cohort the UK tech ecosystem depends on, see The Race Against Itself. For the argument about why venture economics are themselves a particular kind of bet, see Venture Capital Is Good for Society and Bad for Most Founders and The 33%. For the publication’s standing on these questions, see the about page.