
Loading summary
A
I'm an engineer, of course, so there's a lot. It's currently used by everyone. But the focus is that it has to be so simple that anyone can use it.
B
Do you see coders also using Lovable in the future?
A
I think you should see it as an Apple device. For Lovable, it just works. It starts very simple, which makes sure you can focus on what's most important. People who are engineers, but loveable makes their work so much faster. Creating new products, creating new websites, trying out different tools.
C
There's a moment every software builder remembers. It's the first time we made a computer do something. Now, for many of us, that moment was the hello world moment. We wrote one line of code and suddenly the computer talked back. It was a very short moment, but it flipped a switch in our brain. Now we felt we could build. And that first moment is getting dramatically upgraded. Right now, with one line of text, you can ship a working product, a game, a website, even a full e commerce service. And here's the real shift. Today, less than 1% of the world can code. So the next wave is about empowering the other 99% to build as well. One of the most prominent companies pushing this future forward is Lovable. And today I'm joined by Anton Osica, the co founder and CEO of Lavabo. Now, people call this Vibe coding, but Anton's framing is much more direct. This isn't about vibes, it's about leverage. It's about speed. It's about who gets to build. In this conversation, we get into the principles behind Liveable's product choices and why simplicity is the hardest decision to defend. What the next magic moment could look like as building becomes more accessible to more people. The real trade offs behind AI driven software creation, especially the chasm from prototype to production. And why Anton believes the most underrated moat in AI is trust manifested as brand love. So let's get into it.
B
Anton, it's great to have you on the show again. Thank you so much for joining me. I always love our conversations. Fun tidbit, by the way. This is our third Swedish originated company. On the podcast, the other ones were, I think Ikea and Spotify. I don't have a bias for Sweden, but apparently maybe there's a subconscious bias. But those are household names. I'm sure Lovable will be one day a household name. So it's pretty cool. It's cool to have you here.
A
Thanks for having me. We are all thinking about how do you make our product as good as possible and create a team that can facilitate creating that product and then what? I think that's by having that focus where we expect people to be talking about lovable, our grandchildren to be using lovable in 40 years into the future.
B
I love the idea of grandkids. Before we go to lovable, I wanted to start with you. So your kind of personal journey, you actually started as a researcher. You learned math and physics before you became a builder. And as a builder, you focused primarily in startups. You were a founding engineer in a startup, then you became a CTO and a co founder. With Lovable, you're the CEO and co founder. What was the journey there? This move from research into building and specifically going to startups in an area like Sweden and Stockholm.
A
Yeah, I heard that you were also building computers when you were a kid. I was and I was the same. Like I had a bit of that hacker take things apart approach to everything and doing physics is a bit similar. You learn this way of thinking where you break everything down into the fundamental pieces of how things work and then you have a set of hypotheses or you create hypothesis to be able to explain observations and you test those hypotheses in the real world and you're very open to being wrong all the time. I wasn't CERN doing particle physics with a particle accelerator there. And one of the realizations for me was that I can have more impact working out in the real world, taking ideas to change real people's lives. So I'm very happy about that insight. And the other one that's big, awesome experience is that I've always been around people who are creative. Like my mom has a lot of great ideas, designers, people in products specifically, who can clearly see problems in the real world and want to make those ideas into reality. They haven't been able to do so because of how difficult it is technically. And I always felt like this feels artificial, it should be easier. And that frustration and wanting to solve that problem for all of these people is also a big part of how I got to starting lovable with the idea, deliberate idea from the get go to build a product that just works for people who don't know they don't have a background in coding or building software, which is a very rare skill set to be able to do that end to end and build full products.
B
How would you define what lovable is for people?
A
So Lovable lets you take any idea and make that into reality as working software. And it's used by a lot of different type of people. We have a Lot of people in product that are now not held back by engineering backlogs. They can just build out full prototypes or even ship in some cases straight to production and be able to move things around. We're also seeing a lot of founders that are building for the first time and they can have lovable literally as their technical co founder that does the product building and in some cases a lot more things. And we're seeing people in operations, finance, marketing be able to not be held back by engineering backlogs, but just align what to build faster, validate and ship all the way to the production.
B
Love it. So instead of companies you're seeing all those functions use it really well in
C
founders as well in the industries that
B
you see it gravitate towards, people are using it in certain industries.
A
I mean it's used across all types of companies. It's Fortune 100 companies. It's just some tiny small companies, mom and pop shop that are creating their websites with lovable and adding an AI chatbot to the website to be able to answer questions. And I always, every single week I'm stunned by the problems that people have been solving using our tool.
B
I'm curious for you. When you think about your time as a researcher, your time as an early founding engineer, and then multiple kind of founding experiences, what principles you got from that that really made Lovable what it is today?
A
I think about my role is to create an environment, environment where people who have good judgment and like to think end to end of solving problems can just go out and execute. So that's what I learned from all the startups that I've been a part of building. And then the other thing is about testing ideas very quickly while still understanding that there's a few core things that you should really, really focus on to get to not just do them 80, 20 and then leave it a bit half assed, but keep focusing until you really make things really good. And there's an expression in product development that is building an MVP is not enough. You have to build a minimum lovable version of that product to actually really get something that you should be launching to customers for real.
B
Love it. I think about the early days of it was to be about, you know, the first hello world kind of thing. When you write your first program and the computer responds with hello world and now you can write in a sentence but you want to build and laughable would create it for you. And you have this like, oh my God, that was unbelievable. Where do you see that in three, five years?
A
I'm Learning what are different, many different wow moments of using Lavabol from our users. I was at the dinner yesterday and people had been building AI applications with their kids and that was like wow moment for both the kids and the parents. I heard about a founder that likes their pets and they have been starting to AI generate and deliver physical frames of their dogs to people around the world. And we picked up this fact that they were making $100,000 per month on this. Apparently it's $300,000 per month. So they're all founder stories where I'm getting aha moments hearing from the customers.
B
Maybe to your point, it's not just about like oh this thing can build, it's like I can create a business.
A
There's a new economy where there's thousands, tens of thousands of founders that wouldn't be able to start a business before and now they can use Lovable. They are using Lovable as their technical co founder and succeeding as being an entrepreneur. Some of them make it to being financially independent on that. The side hustles regardless are helping them learn how to solve problems, build software, but all of the problems that you need to solve to make a business successful.
B
I love that framing. In many ways people think of this as an app development capability, but really it's an economic tool.
A
I mean it's evolving everyone's role at work now where anyone can actually be someone that builds high quality software if they put their mind to it. And then what that results in is that if you think end to end and you think in terms of how does this fit into everything else, then you can just absolutely shape the trajectory of the company you're working at. I'm hearing people getting promoted because they were able to re architect their entire marketing website and someone in marketing and be able to have their organization move on cycle lengths that used to be weeks to just hours.
B
I've heard you talk about when Today less than 1% of the world population can code and it's really about enabling the rest, 99% to be able to tap into software tools, but really it's economic tools that can help them build their business. Is that the audience you're thinking about like top of mind? Was that from the beginning the hypothesis around like how do I help designer product managers but then people who are completely non technical to go and build.
A
That was the idea. So there's 30 million developers globally and there's even fewer that can kind of take an idea and build it end to end the full products. We from the get go decided we're going to build something that has to be so simple that anyone can understand it and that it just works. And that has been a big advantage for Lovable and our users that it seems extremely simple. We simplify something that's very complex and then if you are a technical developer, you can dig into the code and change the code if you want to.
B
Do you see coders also using Lovable in the future or this is not meant for them like you're building directly for the non technical ones. They don't want to see files, although there is a way to see files today.
A
I think you should see it as an Apple device where for Lovable it just works. It starts very simple which makes sure you can focus on most important people who are engineers but loveable makes their work so much faster in creating new products and creating new websites, trying out different tools.
B
You gave Apple as an example and Apple makes they're very opinionated about how the product should work versus e.g. android will give you all the options or many of the options and then they kind of push the complexity to the user to decide. But there's more freedom. So you can decide where you want your product to be. You can be. I'm going to make it super simple but I've been on the back end so I'm going to make decisions for you or I'm going to give you the freedom to choose how you want to use the tool. But then it might be slightly more complex to use it and then I think Lovable is a little bit more if there's like a middle more towards the opinionated. But obviously that made the product very, very simple. But it's going to work really well for non technical folks. But if you are very technical, maybe be more complex versus other tools. Yeah.
A
In fact the reason we've been successful as well is that we have previous CTOs that are thinking a lot about what is the right technology to use for building applications for Lovable to build applications for a customer. And sometimes it depends. But there are a set of choices that work really well together which in turn makes Lovable more reliable than any other way to build web applications. They ensure that the application can scale and we have encoded how do we ensure that there are security checks. Security is built in from the start in a way where if you just go to a ChatGPT or just talking to an AI, it will take decisions that oftentimes doesn't give the same coherent experience in the end because the piece is that it evolves to some Technology architecture that hasn't been as swapped out from the start as if you're using navabool.
B
Any example that comes to mind to you? When there was like a, you know, there was a discussion among the team around, should we expose this to the user or not?
A
Yes, definitely. Like, one thing is like, should you be able to choose if you want a fast response or a slow response? Should you be able to choose between different AI models and different capabilities like that? We fundamentally think that it's on our side to choose what's best for users at large. Because we simplified that much, we can run much more experiments where we are switching out the AI, we're making it, instructing it to be faster or slower, and we see what users prefer. And we are also making it more adaptive.
B
There's a lot of vibe coding tools out there today. And, you know, everybody chooses a path of where do you want to. They want to want to Excel. And it sounds like for Lovable, it's like, no, no. I am trying to make the simplest product possible for the end user.
A
Yeah, it's an interesting craft to work on where we are fundamentally adding a lot more capabilities all the time, like adding ways for the agent to be sending emails, payments, creating agents with Lovable. And we have to make sure that at every step, the amount of complexity for the user preferably remains the same or even reduces. And it's a very interesting balance.
B
Any kind of one decision you made once that really upsetted power users to a point and you had to rethink again.
A
We've taken some features that were formal for power users and put them before we had more of a formalized launch process. We decided, no, let's take this feature and put it under the research the Labs toggles, where you have to toggle it manually. I don't think we've had to make such a hard decision. We are careful to make sure our power users can kind of keep the functionality that we're simplifying if they really want to. And that's also an interesting trade off.
B
I'm curious if we kind of zoom out to the whole category of kind of vibe coding. Do you like that word, by the way? Vibe coding. Does it resonate with you or do you think that's.
A
I think vibe coding is polarizing in the sense that it sounds like it's very casual. It doesn't create high quality. We're seeing companies like Xpreality has 80,000 real estate agents globally and they're in dozens of countries. The marketing leader there VP marketing built on Lovable. They were planning to replatform all of these websites, hundreds of websites. It would take a year. And then the marketing leader finds Lovable and they take a few weeks with two more people I think and they build everything on Lovable and they could save so much time and it looks much better actually. But they had a chatbot integration on previously they cost them $1 million per year. And now with Lovable they're just paying the underlying price, which is I think 1% of all of that. So this is real enterprises that are delivering things to their end customers. And the fundamental shift is that anyone can now create high quality software.
B
I'm curious, what do you think people misunderstand about Vive coding today? What do they get wrong about it?
A
One thing that stands out to me is how people think people are losing their jobs. And fundamentally to me I think there are. It's not like a one size to a pie and things are being changed in the distribution, new pies are being created and we are going to change our way of working. We're seeing founders that were not able to build companies before. Alan built a AI healthcare staffing platform and in five months he reached $1 million in revenue on that platform and he would not have been able to hire developers in the past.
B
Where do people hit the wall like in your experience? Because if you've seen like I'm sure you have at this point, a lot of users who are using the tool and you see a few kind of breaking through and building like a real business. Where is that wall for moving from a demo to building a business?
A
The biggest frustration for me to some extent is that people don't know how powerful the capabilities of Lovable if you use it in the right way. So I think there is a lot on that internal because they don't know what to ask.
B
Lovable.
A
If you're talking about the business specifically, you need to make other people care about what you built. And the AI Lovable can help with that as well, of course. But it's one of the many bottlenecks to make a successful business. If you think in terms of building software generally you have to come to terms with that to make something lovable, really high quality product, you need to keep testing it and finding the issues and being a bit structured in how you develop your product so that it doesn't have bugs and it fully serves the problem of your customer. And that doesn't take the first version usually does not hit that level of polish that customers expect. So it's more about the mindset. It's a very intelligent system that is building the software for you.
B
Some people might still think of Lovable as this consumer products playground. I build consumer products with it. But you're actually investing in enterprise. Enterprise development is a massive business. Ultimately, there's tremendous impact to be had, both from a lovable perspective, both for Lovable, but also for the companies themselves. Was there like an enterprise wake up call for you or was that there from the beginning?
A
What we're seeing is of course, that the people who use it at home, who use it for themselves, they are bringing it into the workplace and the other way around as well. If you have a job and you're thinking about starting a company, then you want one tool that you learn and that you like and you should have your work inside of. So to us it was just obvious, let's make the product enterprise grade secure, which we did in the first half of the last year. And then making all of the administrative functionality for enterprises to be extremely successful with Lovable both on what you've been talking about, designers, product managers, anyone with an idea can show and demo don't memo. Companies are running their internal tools. Finance and operations are doing their forecasts in Lovable. That's like changing how the company operates on top of what we like to talk about as compounding software. Lovable is run on five different internal tools built on Lovable and they're being evolved every single day by the people who use those tools.
B
Do you feel like it's in a way challenging who your audience is from the beginning? Like where in the beginning it was, somebody has a great idea, they can take it out. But now you have teams involved, you have it involved, they have demands.
A
How I see it is that you have this system and the agent that you're talking to that gets work done for you, pulls in context from Slack and other tools into Lovable. So you can ask for anything, it can read it. And then we need to do two things. We need to keep things very simple and they just work and make it opinionated so it is high quality. And then we add in capabilities.
B
When you think about people's reactions to building right now, what do you think people are overrating as moats? They're thinking, this is a real moat right now. I can build on it. You're like, no, that's not a moat. That's going to go away. On the flip side, what potentially looks like unscalable today, but is exactly the right thing to invest in I think
A
fundamental moat is trust from people who where you've lived up to their expectations, you've been able to create value and you show that you have their best at heart and everything else, you know, it's not really a moat if someone has my data, I mean I have to be able to access my data first of all, otherwise it's not valuable. So I will over time want to interface with a system that is the one that creates as much value for me at the price that is not absurd, which in some cases SaaS has absurd prices for the cost of what is actually delivering. And we're going to see that companies really have to adapt now that anyone can create high quality software and users and what they think and what they want to use is the biggest moat. And the most important thing for a company is how team and culture enable to continuously deliver on those expectations from customers. And that's how you build a strong brand. It's the product and the service and that's how you build a strong brand. Everything else I think can be disrupted by a company now, especially with age of anyone be able to create software and AI.
B
As a serial entrepreneur yourself, very successful one, what advice would you give entrepreneurs who are thinking about what do I build right now or where are they now Opportunities to think about to build something really remarkable as a service to people.
A
It's good. I think you should just try the tools and building as much as possible and make sure you have a tight feedback loop with users out there. And there are different ways of getting that feedback loop. You can have it online. I think in person is actually the best way to have that feedback loop. I think being purely digital is harder to differentiate. I think you're building. Taking AI and this better software into something that is also physical is a place where you can. There's more like untapped innovation to be had.
B
Yeah. What's an example that comes to mind for you?
A
Seeing nurses building patient journey apps and healthcare is of course an extremely physical in person thing. We're seeing a lot of innovations. Very large AI E commerce company in Sweden was built on lovable and E commerce is in part physical where you need to get the right sizes, you need to get, you know, convey how an item would look on anyone, on yourself if you will try it out. And this company was built on level made hundreds of thousands of er after only a few months. And that's the type of examples where you're bridging the gap. You're able to take a problem which is harder to solve with software because it's in part in person, in physical. Just try as many things as possible is the short answer for me.
B
Anand, this was great. I would love to end on a rapid fire question if you're up for it. If you could solve one product problem at Lovable right now by just snapping your fingers, what would that be?
A
I think it would be how to learn how to use the tool as productive as possible.
B
What is your favorite non digital, non software product?
A
I think my AirPods are really nice with the noise cancellation.
B
Cool.
A
I'm traveling.
C
What's a product you did not think
B
would be successful but actually surprised you and was successful or the opposite? You think it would be successful but it was not successful?
A
I think AI glasses would be actually super powerful and they still haven't taken off any of the AI glasses feels like they've taken off. So the wearable technology, maybe it's still doomed, I don't know because we like to have a screen in front of us.
B
Do you have one?
A
No, I'm not using any of that technology. But that's when you would expect I would expect it to get more usage.
B
Cool. And then for all the aspiring builders out there, what would you advise them doing? Given your journey, how would you advise them going into it?
A
I mean it depends. Things are changing very, very fast. There's a lot of opportunities. So if you can do something that you're uniquely good at, being inspired by all the possibilities and being like have a positive energy is the most important thing to get in the mindset of action. And I think building a company is a good way to learn. I think working at a company with really a lot of talent, a lot of skills, which is also like a growth journey is in some cases an even better way to learn. It's only a question of working at Lovable. We're hiring of course that's a great option if you are considering starting something. I would put yourself in a social setting like having a co founder that matches your energy that makes you just enjoy your day to day and all the things you're going to go through together.
B
So the right mindset. Start building and iterating and surround yourself with people you love working with and you can learn from 100% love it. And then this was wonderful. Thank you so so much.
A
Likewise. Thank you.
C
I really enjoyed my conversation with Anton. Now there's a temptation to frame tools like Lavable as a coding story, but it's not. It's a power story and a few takeaways stand out. First, Anton's ambition is a cultural force. He's unapologetically explicit about his vision. He wants Lavable to be something people are still using decades from now. Feasible or not. That grandkids ambition he was talking about sends a very clear message to his team. We're not building a feature, we're building something very enduring. Second, Lovable's strategy is simplicity over knobs. Inspired by Apple, Anton and his team are deliberately opinionated. They spend cycles making the hard technical decisions for the user which models architecture or defaults to use because they believe the core customer doesn't want tools, they want outcomes. The North Star is the future app creator who doesn't have the time, desire or background to wrestle with software complexity. Third, AI doesn't remove the work, it moves the work. Anton pointed out that people sometimes give up too quickly when it comes to AI products. Lovable gets dramatically better as you iterate and learn how to use it and work with it over time. And this is true across many AI products. Even with great tools, you still have to put in the cycles you have to test, tighten and iterate and learn how to ask for what you actually need. 4. Lovable builds the product, but there is a real opportunity in building out the whole ecosystem. Now Lavable can help you create the most important part of your company, the product itself. But turning that into a business requires distribution, go to market operations, legal support and trust, and so many other things. Anton's economic tool framing hints at a much bigger wave. We're going to have an ecosystem around AI enabled building and there's a tremendous opportunity in that. Lastly, the promise of this technological shift is simple. We are going to have more builders, more people testing ideas and participating in the economy as creators of companies, not just users of companies. That's what I'm most excited about. I'm Tomer Cohen. Thank you for listening and watching and keep building.
D
You've been watching Building One. Our show is hosted by Tomer Cohen. Building One is produced and edited by Mason Cohn and the team at Coastal Production Works. This episode was mixed by Tim Boland at LinkedIn. Our team includes Rachel Karp, Sarah Storm, Dave Pond and Alicia Mann, with support from Alex Kuznetsova and Mujib Merdad. Until next time, keep building.
Episode: Building Lovable With Anton Osika: The Power Of Simplicity, AI As A Technical Co-Founder, And Why 'Vibe Coding' Needs A New Name
Date: March 10, 2026
Host: Tomer Cohen, LinkedIn CPO
Guest: Anton Osika, Co-Founder & CEO of Lovable
This episode explores the power and promise of Lovable—a platform designed to make software building accessible, fast, and "lovable" for everyone, not just engineers. Anton Osika shares Lovable’s product philosophy, the role of AI as a technical co-founder, and the radical potential of empowering more people to build. The discussion covers simplicity-driven product development, real-world impact stories, and the evolving meaning of "vibe coding."
Researcher to Builder
Anton began as a physicist at CERN, learning to break down complex systems and test ideas—a discipline he now channels into startups.
“Doing physics is a bit similar. You learn this way of thinking where you break everything down into the fundamental pieces of how things work … and you’re very open to being wrong all the time.” (03:29)
Desire for Impact
Spurred by creative communities, Anton became frustrated seeing non-technical people unable to build their ideas due to technical barriers. That led to Lovable’s inception—a product so simple anyone can use it.
“It should be easier. And that frustration and wanting to solve that problem…is a big part of how I got to starting Lovable.” (04:15)
Definition & Audience
“Lovable lets you take any idea and make that into reality as working software... Product managers, founders, people in operations, finance, marketing—none held back by engineering backlogs.” (05:20)
From Side Hustles to Enterprise
Lovable is used by major Fortune 100 companies and mom-and-pop shops alike. Users include founders launching businesses, marketers revamping company websites, and operators solving bespoke problems.
“Every single week I’m stunned by the problems that people have been solving using our tool.” (06:17)
AI as Technical Co-Founder
For some, Lovable enables entrepreneurship:
“There’s a new economy where…founders that wouldn’t be able to start a business before … are using Lovable as their technical co-founder.” (09:01)
Product Principle: Minimum Lovable Product
Anton distinguishes between an MVP and building something truly “lovable”:
“Building an MVP is not enough. You have to build a minimum lovable version.” (06:56)
Apple-Inspired Approach
Lovable is intentionally opinionated, making tough technical decisions for the user so the product “just works.”
“I think you should see it as an Apple device... it just works.” (11:21)
Simplicity as Strategy
Lovable prioritizes ease and reliability even as capabilities grow (e.g., agents, payments, integrations). Complexity is hidden; power users can still dig deeper if needed.
“At every step, the amount of complexity for the user preferably remains the same or even reduces.” (14:25)
On the Term “Vibe Coding”
Anton is critical of the term:
“Vibe coding is polarizing … It sounds like it’s very casual. It doesn’t create high quality.” (15:41)
Enterprise Impact Example
A real estate firm rebuilt hundreds of sites in weeks on Lovable, ultimately lowering yearly chatbot costs from $1 million to a fraction.
“They took a few weeks with two more people…and they could save so much time and it looks much better actually.” (15:41)
Barriers to Success
The main challenge isn't Lovable’s capability, but users’ understanding of what’s possible and their ability to iterate.
“Biggest frustration … is that people don’t know how powerful the capabilities of Lovable [are] if you use it the right way.” (17:45)
From Prototype to Production
Success depends on using the tool to iterate and polish, not on the first version (“demo to real business”):
“To make something lovable…you need to keep testing it and finding the issues and being a bit structured in how you develop your product.” (17:59)
AI Doesn't Eliminate Work
“AI doesn’t remove the work, it moves the work.” (26:48, Host summary)
Lovable as an Economic Tool
The platform enables not merely apps, but new business models and entrepreneurship:
“Some…make it to being financially independent … All of the problems that you need to solve to make a business successful.” (09:01)
Blending Physical & Digital
Anton encourages integrating software with the physical world—like nurses building patient apps, or e-commerce innovations.
“Taking AI and this better software into something that is also physical is a place where you can...find more untapped innovation.” (22:58)
The Grandkids Ambition
“We expect people to be talking about Lovable, our grandchildren to be using Lovable 40 years into the future.” — Anton Osika (02:37)
Economic Shift
“Today, less than 1% of the world can code. So the next wave is about empowering the other 99% to build as well.” — Tomer Cohen (00:36)
On Lovable’s Value
“It starts very simple, which makes sure you can focus on what’s most important. People who are engineers, but Lovable makes their work so much faster.” — Anton Osika (11:21)
On Team & Product
“The most important thing for a company is how team and culture enable to continuously deliver on those expectations from customers.” — Anton Osika (21:22)
For aspiring builders, Anton leaves practical advice: “If you can do something that you’re uniquely good at, being inspired by all the possibilities and have a positive energy is the most important thing to get in the mindset of action.” (25:37)