Building Got Cheap, Running Did Not
Lovable, which lets people build software and web applications through natural language prompts, has raised 400 million dollars at a 13.3 billion dollar valuation — double the figure from eight months earlier. Reported as a funding round, the more telling number sits elsewhere: more than 60 million projects have been created on the platform since its launch in November 2024. Producing software is ceasing to be a developer’s job.
The usage profile has shifted too. The platform spread first among individuals and start-ups, then moved into enterprises. According to company statements, teams at Klarna, HubSpot, Adidas, NVIDIA and Deutsche Telekom use it to build internal workflows, replace ageing tools and turn side projects into revenue.
You are not a software company. But this story describes something that changes what your work is worth: building a site or application got cheap; running one did not.
What Happened
BU BÖLÜMÜN ÖZETİ
- Valuation doubled in eight months
- The revenue curve is steep
- Project count is the real indicator
- Enterprise use has spread
The figures show how fast a category is growing.
Valuation doubled in eight months
A 330 million dollar round in December 2025 valued the company at 6.6 billion dollars; by August the figure was 13.3 billion. The round was co-led by Menlo Ventures and the Scaleup Europe Fund, established by the European Commission and managed by EQT.
The revenue curve is steep
According to company statements, annual recurring revenue stood around 200 million dollars at the end of 2025 and reached 400 million within the first months of the year, with a stated target of 600 million by the end of August.
Project count is the real indicator
More than 60 million projects have been created since launch. That measures production volume rather than user count, and points to where the real change sits.
Enterprise use has spread
Usage moved from individual projects into corporate IT, with teams at large companies building internal workflows and replacing ageing tools.
What the Numbers Mean
BU BÖLÜMÜN ÖZETİ
- Production moved inside the business unit
- Building got cheaper, maintaining did not
- Volume creates its own problem
- Competition moved from building to running
What matters here is not price but where the work now happens.
Production moved inside the business unit
Instead of queuing with the IT department for an internal tool, the team that needs it builds it. That brings speed while transferring responsibility for standards, security and maintenance to that team — usually without anyone noticing.
Building got cheaper, maintaining did not
Producing an application became inexpensive; keeping it secure, updated, data-consistent and compliant did not. Total cost does not fall; the line items move.
Volume creates its own problem
Sixty million projects says nothing about how many survived. Fast production can also mean abandoned applications and scattered data.
Competition moved from building to running
If your competitor can build at the same speed with the same tool, no advantage forms in building. The difference remains in measurement, visibility, data discipline and sustainability.
Who This Affects, and How
BU BÖLÜMÜN ÖZETİ
- Those who gain
- Those who lose
- Those largely unaffected
- The indirect chain
The effect starts wherever a business’s digital presence is managed.
Those who gain
Businesses with ideas but limited budgets. A company that previously requested quotes and waited months can now test an internal tool within days. Cheaper experimentation reduces the number of untested ideas.
Those who lose
Service providers defining their work as producing pages. A model priced on production cannot compete with these tools. Demand is rising, however, for those defining their work through measurement, visibility, data discipline and maintenance.
Those largely unaffected
Work requiring complex integration, high security and regulated processes remains outside these tools’ scope. That boundary narrows slightly with each release.
The indirect chain
Production gets cheap, application count rises, data scatters, reporting gets harder and the single correct figure needed for a decision disappears. Easier production creates harder management.
What to Do About It
BU BÖLÜMÜN ÖZETİ
- Ask one question before building
- Keep an internal tool inventory
- Separate what customers see
- Distinguish cheap building from durable investment
None of these requires abandoning the tools; they organise their use.
Ask one question before building
Where will this application’s data live, and who maintains it in a year? Every fast build without an answer becomes a tool nobody can touch six months later.
Keep an internal tool inventory
List which team built which tool. Without that list, a departing employee takes an operating tool with them.
Separate what customers see
Fast production is reasonable for internal use; customer-facing pages and applications require measurement, accessibility and data discipline. The two should not run to the same standard.
Distinguish cheap building from durable investment
Fast production is the right tool for testing an idea. When the test succeeds, continuing on the same structure is a mistake; taking a prototype into production is the most expensive shortcut available.
The Digital Side
BU BÖLÜMÜN ÖZETİ
- Visibility is separate work
- Data discipline does not arrive by itself
- Without measurement there is no evaluation
- The operating burden is rising at the same time
What fast-built sites most often skip is everything that comes after building.
Visibility is separate work
A page existing does not make it findable. On pages built with these tools, heading structure, address layout and basic configuration frequently remain at their defaults.
Data discipline does not arrive by itself
Where product and customer data live, with which fields and to what consistency, is a design decision. In fast production it usually goes unmade, and the migration cost surfaces later.
Without measurement there is no evaluation
If nobody measures whether an application built in three days is working, nobody can decide to retire it six months later. In process and e-commerce consulting this is the most common gap we encounter.
The operating burden is rising at the same time
While production gets cheaper, headings such as visibility measurement and content usage terms are getting heavier. The hours saved are being requested back under another line item.
A Solid Digital Foundation
BU BÖLÜMÜN ÖZETİ
- Content generated in the browser may be unreadable
- You can run the check yourself
- Address structure belongs at the start
- Cheap building should not mean cheap outcome
Pages built with these tools can behave differently from conventional ones, and that difference affects visibility directly.
Content generated in the browser may be unreadable
Where page content is assembled in the visitor’s browser after loading, systems attempting to read it may see an empty page. How to check whether content can be processed is explained in the Google Search Central documentation. Text you see on screen does not mean text exists in the page.
You can run the check yourself
Viewing the page source and searching for the text is enough. Information visible on screen but absent from the source does not exist as far as systems are concerned.
Address structure belongs at the start
In fast-built applications addresses can be generated automatically and meaninglessly. Correcting them later costs links; setting them correctly at the start costs nothing.
Cheap building should not mean cheap outcome
The tools are good; what is missing are the configuration decisions. Which decisions those are is set out in our approach to digital consulting.
Frequently Asked Questions
Sık Sorulan Sorular
They suit prototypes and internal tools well. For customer-facing corporate structures, visibility, data discipline and maintenance decisions need making separately.
Models priced on production are under pressure. Demand for measurement, visibility, data architecture and sustainability is rising; the work is not ending, its definition is changing.
For internal use it is generally beneficial, provided an inventory exists and the question of where data lives has an answer.
It can, at cost. Rebuilding when moving from test to production is frequently cheaper.
Because the builder may not be a technical specialist, access permissions and data retention decisions can be overlooked. Both need checking separately in every tool.
Interest in the category is strong and funding arrives quickly. Which tool endures is uncertain, which is why data should not be left inside a tool.
Source: Lovable Series C announcement, 12 August 2026; company statements and reporting by Webrazzi, Bloomberg and other outlets. Revenue and project figures are those published by the company.