Kingy AI
Work with Kingy
AI News

Lovable Says Its Annualized Revenue Has Passed $600 Million. What Is Driving the Growth?

September 24, 2026 AI News
Lovable annualized revenue

A big number from an Amsterdam stage

Lovable co-founder and chief technology officer Fabian Hedin had a striking update for an audience in Amsterdam: the AI app-building company had passed a $600 million annualized revenue run rate.

Hedin gave the figure during a HumanX conversation on September 23, 2026. The Next Web reported on the conversation the following day. TechCrunch also reported the new figure on September 24. In June, Lovable had said its annualized run rate was around $500 million.

The jump gives Lovable another remarkable growth headline. It also points to a change in how the company talks about itself. Lovable began by making it easier to turn an idea into an app. Now its leaders increasingly describe a platform for building, launching, and running products—even businesses.

That is a larger job than generating a promising first version. People have to keep using the software. Customers must trust it. Someone must fix what breaks.

So the interesting question behind the $600 million figure is this: can Lovable turn a fast-growing app builder into a dependable place to run what its users create?

What annualized revenue actually means

First, a quick translation. Annualized revenue run rate takes revenue at a recent pace and expresses what that pace would amount to over a year if it continued. It is a snapshot extended forward, not the amount Lovable has already earned during a completed 12-month period.

For illustration, a company bringing in $50 million in one month would have a $600 million annualized run rate if you multiplied that month by 12. That does not establish that Lovable’s revenue in a particular month was exactly $50 million; the company has not provided the underlying calculation in these reports.

It also does not tell us Lovable’s profit, operating costs, or how much revenue will ultimately arrive over the next year. Growth can accelerate, slow, or reverse. The figure deserves attention, but it needs its proper label.

The comparison with June is still meaningful. Lovable then reported a run rate above $500 million. Hedin now says it has passed $600 million. Those are company-reported snapshots, not a set of independently audited annual accounts. Read that way, the update shows Lovable saying its current business pace has risen substantially in a few months.

From a prompt to a working product

Lovable belongs to the wave of tools commonly called “vibe coding.” A user describes what they want in everyday language. AI helps turn that description into software. You can refine the result through conversation instead of writing every line of code yourself.

That can change who gets to try an idea. A founder might test a service before hiring a development team. A marketer might build a campaign tool. An operations employee might make an internal dashboard tailored to a problem they know well.

Hedin argues that the finished product matters more than the code generated along the way. At HumanX, he pointed to Lovable’s work on hosting, deployment, and scaling—the tasks involved in getting an app in front of users and keeping it available. He also described additions such as payments and tools that help businesses reach customers.

That pitch is more ambitious than “type an idea, get a demo.” Lovable wants customers to keep building on its platform after the first burst of excitement. A useful prototype can win applause in an afternoon. A useful business tool has to turn up for work on Monday, then do it again on Tuesday. Software, inconveniently, does not consider itself finished just because its creator has clicked Publish.

Big companies are entering the picture

Hedin said people at roughly two-thirds of Fortune 500 companies now use Lovable. That wording matters. TechCrunch clarified that the claim refers to people inside those companies using the platform. It does not establish that two-thirds of the companies have bought company-wide subscriptions.

Hedin described a pattern in which employees discover the tool themselves. Later, their organizations notice that staff have created many apps and begin asking how to manage them. Lovable then has an opening to discuss visibility, permissions, and other controls with those organizations.

The company named Microsoft, Nvidia, and Deutsche Telekom among customers or organizations where its product is used. In an August company announcement, Lovable also described employees at nearly two-thirds of Fortune 500 firms using the platform. These are Lovable’s claims about adoption; neither report supplies a breakdown of paid contracts at each company.

Still, the pattern explains Lovable’s enterprise focus. An employee who can solve a small problem with an app may create value quickly. Multiply that by many employees, and a company needs to know what has been built, who can edit it, and what information each app can reach.

When employees build their own tools

Lovable annualized revenue

Hedin offered an example from Uber Eats. He said a sales leader who understood the restaurant pitch process used a Lovable-built tool to create pitches tailored to individual restaurants. According to his account, the first version took hours or a day to make; later changes could take roughly 10 minutes. That is a customer example presented by Lovable’s co-founder, not an independently measured average for users.

It illustrates why companies might be interested. The person closest to a task often understands its awkward details better than anyone else. Traditional software requests can take time to move through a busy engineering queue. Giving that person a way to build a first solution could make an overlooked problem easier to tackle.

Lovable’s August funding announcement offers other company-supplied examples, including internal tools at Zendesk, Handshake, and Checkr. Their uses vary, but the theme is consistent: employees want software fitted to the way their teams actually work.

There is a catch. A useful tool built by one employee can become a shared dependency surprisingly fast. Once colleagues rely on it, the organization needs an owner, sensible access rules, and a plan for maintenance. The ability to build quickly makes those questions arrive sooner.

Nearly a billion visits, according to Lovable

Hedin also said apps created with Lovable now attract nearly one billion visits a month. That describes traffic to the collection of apps users have built, not visits to Lovable’s own website. The company’s August announcement put the figure at more than 900 million monthly visits and said users had created more than 60 million projects since Lovable’s November 2024 launch.

The traffic figure helps explain why Lovable wants to talk about finished products. Some user-built apps clearly reach people beyond their creators. If an app serves customers every day, hosting, reliability, and security become part of its value.

But traffic is only one measure. A visit does not reveal how many individual apps attract an audience, whether visitors return, or whether their creators make money. Likewise, a project count includes more than established businesses. People experiment, abandon ideas, and start again. That is part of building software.

Lovable’s numbers suggest considerable activity across its platform. They do not tell us how many projects become lasting products. For that answer, observers would need more detail about active apps, retention, and the outcomes builders achieve over time.

The funding behind the expansion

Lovable has attracted large investments alongside its reported revenue growth. In December 2025, it raised $300 million at a $6.6 billion valuation, according to TechCrunch. In August 2026, the company announced a $400 million Series C at a $13.3 billion valuation, led by Menlo Ventures and co-led by the Scaleup Europe Fund managed by EQT.

The new $600 million run-rate figure is not another funding round. It is an update on the pace of Lovable’s business. The $13.3 billion figure, meanwhile, was the valuation attached to the August financing. Revenue run rate, capital raised, and valuation measure three different things; a headline can make them look like one giant pile of dollars.

Lovable said the August investment would support work on its product, infrastructure, security, and team. It also laid out plans to make the platform more useful for running businesses, including deeper connections to organizations’ existing tools.

That direction fits the latest revenue story. Quick app creation brings people through the door. Giving them good reasons to stay—and helping companies manage what they build—could support a more durable business. Whether Lovable can deliver that at scale remains the harder question.

Security moves from footnote to main event

A restaurant pitch tool and an app that handles sensitive company data do not carry the same risks. As Lovable reaches more workplaces, its customers need to decide which employees can build apps, who can publish them, and what data those apps may access.

Hedin acknowledged the concern at HumanX. He said Lovable works with company technology leaders on permissions and on deciding who should build what. He also said the platform uses AI to scan projects for security problems. Those are descriptions of Lovable’s approach; they are not evidence that every user-built app is free of vulnerabilities.

In its August announcement, Lovable highlighted security scanning, publishing controls, workspace insights, and other governance features. The company presented those additions as part of its effort to support software that people use beyond the prototype stage.

Speed makes this work more urgent. When more people can create apps, more apps may connect to customer records, company accounts, or outside services. A business needs to know who owns each one and who will review changes after launch. A fast build is delightful. An unnoticed permission mistake is considerably less so.

Building is the beginning

Getting an app to work once can feel magical. Keeping it useful is a different craft.

Features change. Outside services update their systems. Dependencies develop flaws. Users ask for improvements the original builder never imagined. Even a good app needs somebody to notice when it stops meeting the needs it was built to serve.

That distinction surfaced in TechCrunch’s June coverage of Lovable’s earlier $500 million run-rate claim. The publication questioned whether software created quickly with AI would endure, noting that maintenance—not the first build—is a major part of software ownership. (TechCrunch)

Lovable’s response, in effect, is to take on more of that ongoing job. Hedin pointed to hosting, deployment, scaling, and security work. The company has also been adding ways for builders to connect apps to other services and manage them inside organizations.

The proof will emerge over time. Do successful apps remain useful? Can a team hand one to a new owner? Can problems be found and fixed without turning every change into a fresh project? Those questions sound less thrilling than creating an app from a sentence. They are exactly what matters once real people depend on it.

“Vibe coding” may be getting too small a name

The phrase vibe coding captures the fun of telling an AI what you want and watching software take shape. It also risks making serious product work sound like a casual experiment.

Hedin said he prefers “agentic coding” as a description of where the field is heading. His point is that the work now extends beyond a prompt and a chunk of generated code. Lovable is trying to help users build, publish, connect, and maintain products.

That does not erase the appeal of a simple prompt. Ease of entry is why many people tried these tools in the first place. It does change what Lovable must deliver after the first session. A new user may forgive an imperfect experiment. A paying customer running a business will expect the app to work reliably.

The terminology will probably keep evolving. The more useful distinction is between making something quickly and making something that lasts. Lovable’s reported revenue suggests many customers see value in its approach today. Its longer-term standing will depend on how well it supports the second half of that sentence.

A European company with global ambitions

Lovable annualized revenue

Lovable was built in Sweden, and Hedin told the HumanX audience he sees advantages in continuing to build from Europe. The company is also expanding internationally. Its August funding announcement described plans to hire in Stockholm and other cities, including London and several US locations.

The geography matters because Lovable is chasing a global opportunity. The people who understand a business problem are spread across countries, industries, and job titles. Many do not write software for a living. A platform that lets them make and improve their own tools could reach well beyond the traditional developer market.

That is Lovable’s vision, and the $600 million run-rate announcement puts a sizable number beside it. Yet scale creates its own pressure. The platform must serve individual builders and large organizations without making either group wrestle with unnecessary complexity.

The next chapter will reveal whether Lovable can keep those strengths together: an easy place to begin, a capable place to grow, and a trustworthy place to keep a product running. Plenty of people can describe an app they wish existed. Lovable’s test is helping them live with it after launch day.

Sources