Lovable is well known as an AI-powered platform to build applications. But ironically, it is now moving towards a future where fewer and fewer people will be using conventional apps. That is, of course, because of the growing impact of agents.
In a recent blog post, Lovable outlined a vision for “a digital brain for your team connecting your daily tools.”
Or as Lovable CTO Fabian Hedin put it in an interview with Latent Space, “you can get to a place where you’re using one entry point to all the work that you’re doing.”
To be clear, Lovable still wants to be the tool you use to build apps — but increasingly, it will also enable you to build what Hedin calls “capabilities.” Lovable defines a capability as a useful part of an application that an agent can call directly; bypassing the need for a human user to open the app.
Lovable can turn a published application into agent-accessible capabilities by exposing selected functions from the app as tools through a hosted MCP server. The result is essentially one application with two interfaces: a traditional human UI and a new agent interface that can be used from ChatGPT, Claude and other MCP-compatible AI clients.
This is how fast an AI business evolves
This shift towards capabilities is the latest evolution from Lovable, in an already fast-moving 3 years in business.
Lovable emerged from GPT Engineer, an open source coding tool that launched in 2023, initially focusing on prototyping. In November 2024, it became a commercial product and the following month, it was rebranded as Lovable.
By that point, they’d begun to notice some of its users building production apps on Lovable — including products that had become real businesses.
“We started seeing people on the platform building not only a prototype, and not only an MVP [Minimum Viable Product], but the actual thing — an actual product that serves real customers,” Hedin said.
Next, Lovable noticed its users creating internal software, in some cases to support a public-facing app and in other cases as an internal app built for an enterprise company.
“People started creating not only software to enable a business, in terms of a customer-facing product, but also the operations behind the company,” Hedin said.
He means tools like a CRM, an admin panel, or a customer-support console.
From app builder to agent platform
So in less than three years, Lovable has become an all-round software creation and hosting company, which means it’s swimming in the same waters as the likes of Vercel and Cloudflare. That said, Lovable is more focused on AI-generated software than infrastructure. But we are seeing crossover in these markets — for example, Vercel’s v0 allows you to generate an app from natural language, just like Lovable.
Also just like the black triangle and orange cloud companies, Lovable has expanded into agentic workflows.
This rapid product evolution has been accompanied by strong user and revenue growth. According to a tweet from Deedy Das, a partner at lead investor Menlo Ventures, the company has surpassed a $500 million annualized revenue run rate, with more than 60 million projects created and over 900 million monthly visits to Lovable-built apps. Lovable also says employees at nearly two-thirds of the Fortune 500 have used the platform.
Unsurprisingly, Menlo Ventures is doubling down on its investment. It led Lovable’s $400 million Series C this month, alongside the Scaleup Europe Fund managed by EQT, valuing the company at $13.3 billion.
Hedin attributes the pace of change to a combination of Lovable’s innovation and the rapidly improving state of LLMs.
“Every few months, we introduce new capabilities at the application layer, while the large language models also continue improving. Those two things compound.”
Lovable’s model of a company brain
The concept of a digital brain for an organization, for Lovable, essentially means a single interface where you can access many different tools and workflows.
“It should have as much context as possible about you, your company and the world around you,” said Hedin. “Then it needs the capabilities to perform both general tasks and actions that are specific to your organization.”
Ultimately, he added, the goal is that “everything that you’re building can be reused in an agentic way.”
In a sense, then, applications are becoming a collection of capabilities that users will increasingly access through an organizational agent — instead of, or in addition to, the actual application.
“Our job as a platform is to ensure that all these separate capabilities are connected through one agent — not that you have to build a different agent for every task,” said Hedin.
As an example, Hedin mentioned an internal application they use at Lovable.
“We built this internal tool to help us grant credits to users [via] our support team, and help manage our platform in different ways. Those capabilities are now available [internally] through the Lovable agent.”
Lovable also wants this company brain to work asynchronously. Its agent can schedule itself to resume a task later — for example to check a deployment or to monitor a recurring process — then return the result to the same conversation.
The competition
Lovable isn’t the only company pursuing a “company brain” vision. Vercel CEO Guillermo Rauch recently introduced its internal agent, called @𝚟. “Every day-to-day job at Vercel now involves @𝚟,” Rauch tweeted. “It’s growing exponentially both in daily interactions and token use.”
Hedin acknowledged that Vercel and other AI companies are building towards a similar vision, but he thinks Lovable’s “wedge” is “being the best place to build the capabilities that agents need.” In other words, Lovable’s focus is on helping their users build the capabilities that a company brain will need.
“Orchestrating these capabilities is the easy part,” Hedin said. “Making sure they are well connected, built correctly and reliable is the hard part.”
He also hinted at why they’re using the word ‘brain’ to describe this shift, rather than just ‘agent’.
“I’m careful about using the word ‘agent.’ It suggests something like an employee performing a task, which is an easy way to think about it. But underneath, it is really about connecting the right context and capabilities.”
Security and connecting to external capabilities
Perhaps the biggest challenge with the agents and capabilities paradigm is security. For instance, if one of your employees creates an app with Lovable that connects to the company Slack, you want to ensure that user doesn’t inadvertently expose their personal messages, or any other confidential information, to the company brain.
Connectors are Lovable’s method of connecting to external tools and services. Hedin said the platform must account for a “kind of permissioning graph” to maintain security and privacy.
As described in a technical article on Lovable’s blog, one connector type, which Lovable calls an “app user connector,” preserves each user’s identity and source-system permissions. Credentials are stored server-side in encrypted form and handled by Lovable’s connector gateway, rather than being exposed to the generated application; the app instead presents a short-lived key bound to the relevant user.
“We separate the connection to external systems from the application code being written,” is how Hedin put it. “The application interfaces with the Lovable platform, but the application itself never gets access to those credentials.”
The future of SaaS
So Lovable is moving to a future where a company brain uses capabilities derived from the apps its users build. That begs the question: what will happen to SaaS apps?
Hedin reiterated that people will increasingly interact with software through an AI layer — the company brain concept.
“People are not going to have as many tabs open in different tools as they have historically. That experience is going to consolidate, but the vertical capabilities those tools provide will remain valuable.”
He recognizes that some traditional SaaS products may “fight” this trend, by sticking with their traditional apps and not adapting, but he says Lovable wants to become a platform for building capabilities.
“We want to build this open platform that anyone can connect to, anyone can use,” he said.
Hedin ended with some advice for SaaS companies, whether existing ones or apps that might emerge on the Lovable platform.
“I think SaaS businesses are going to have to focus more on providing the shovel for AI to use their capabilities.”
Facts Only
* Lovable is an AI-powered platform for building applications.
* Lovable envisions a "digital brain for your team connecting your daily tools."
* A capability is defined as a useful part of an application that an agent can call directly.
* Capabilities are exposed as tools through a hosted MCP server to enable agent access.
* This results in one application with a human UI and an agent interface.
* Lovable evolved from GPT Engineer, an open-source coding tool launched in 2023.
* Users built production apps and internal software on the platform within three years of its emergence.
* The company has surpassed a $500 million annualized revenue run rate.
* Menlo Ventures led Lovable’s $400 million Series C, valuing the company at $13.3 billion.
* Lovable separates external system connections from application code using connectors and a permissioning graph to manage credentials securely.
Executive Summary
Lovable is transitioning from an application builder to a platform for creating agentic capabilities, envisioning a "digital brain" for teams that connects daily tools. The company's evolution stems from its origin as an open-source coding tool and the growing realization among users that they are building full production applications and internal software alongside prototypes. Lovable aims to enable users to build not just applications but also agent-accessible capabilities, defined as functions an agent can call directly without human intervention. This is achieved by exposing application functions as tools via a hosted MCP server, allowing AI clients like ChatGPT and Claude to interact with the application through a new agent interface alongside the traditional user interface.
This shift is supported by significant growth; Lovable has reached an annualized revenue run rate exceeding $500 million and has attracted substantial investment, including a $400 million Series C and subsequent funding rounds. The growth is attributed to the compounding effect of platform innovation and advancements in Large Language Models (LLMs). The long-term vision involves consolidating user interaction through an organizational agent that accesses interconnected capabilities, enabling asynchronous workflows where agents can schedule and resume tasks. Security is addressed by separating application code from external system credentials, using connectors to manage permissions via a permissioning graph.
Full Take
The narrative describes an evolution where the focus shifts from building discrete applications to abstracting them into reusable, agentic capabilities, positioning the platform as the crucial layer for orchestration rather than just execution. The tension lies between Lovable’s goal of creating a unified "company brain" and the practical challenge of ensuring reliable connection and security across disparate external systems. The distinction drawn between an "agent" (an employee performing a task) and a "brain" (connecting context and capabilities) suggests an awareness that the shift is not merely technological but organizational, aiming to reframe how work is structured within an enterprise context.
The implication for SaaS is whether traditional applications will be absorbed into this capability-based structure or if they will resist the consolidation toward AI-mediated interfaces. The assertion that SaaS businesses must focus on providing the "shovel for AI to use their capabilities" suggests a strategic pivot: value moves from owning the monolithic application layer to defining and exposing granular, secure functionalities. This sets up a dynamic where infrastructure providers like Lovable are not just building tools but establishing the meta-layer of connection necessary for future enterprise software interaction.
What alternatives exist to agentic orchestration that do not rely on centralized 'brain' concepts? How does the focus on capabilities—as opposed to the application itself—redefine intellectual property and ownership in this new architecture? If the primary value lies in connecting discrete functions, does the traditional concept of a distinct, bounded SaaS product lose its essential market grip, or does it simply become one modality within the agentic ecosystem?
Sentinel — Human
The text reads as well-researched business journalism, expertly weaving product development narratives with abstract philosophical implications about the future of software interaction.
