Never wrote a line of code, now a $6.6B unicorn : the vibe coder - Lazar Jovanovic [Lovable]

2 Apr 2026 · 1 h 1 min · 31 chapters

Ask about this episode

Ask anything about it. ChatGPT or Claude reads this page and answers with the times it was said.

Connect VO and ask about every podcast you hear, including the moments you saved. Add to ChatGPT · Add to Claude

In short

“Vibe coding” (AI app building) and how non-coders can ship production software faster, plus Lovable’s product strategy and long-term software maintenance.

Guest

Lazar Jovanovic, Lovable’s “world’s first official professional vibe coding engineer.” Lovable reportedly reached $100M ARR in 8 months and is valued at $6.6B. Lazar claims he has never manually written a single line of code, yet ships production apps daily. He emphasizes AI clarity/taste/design and says ignorance can be an advantage.

Key claims

By end of 2026, “nobody’s going to need to write code” (coding becomes optional/art). Engineers aren’t disadvantaged; non-engineers gain by quickly trying tools. Maintenance bottlenecks will ease as models improve, but users must document features (PRDs + “source of truth” dependencies) so agents can maintain/break-fix. Biggest remaining problems are “why build” and distribution/attention, not coding. Interfaces won’t disappear; chatbot + UI will combine.

Notable examples

Claude Code used to vibe code Claude Cowork in seven days; Lovable internal GTM tools built with an interface plus chatbot layer; a baker built a Shopify-integrated cake business to ~$150k/year; “SheBuilds” women’s build-a-thon (Mar 8).

Written by AI. May contain mistakes. Listen to the episode to check what was said.

Chapters

Tap a time to open that second in VO

The Rise of Vibe Coding

0:46 to 2:10

Discussion on how vibe coding disrupts traditional software development.

“Yet, he ships production apps daily faster than senior engineers.”

The Role of Non-Technical Creatives

2:11 to 3:20

Exploration of how non-technical individuals can leverage AI in coding.

“And sometimes go against the rules, which is great because if we are all honest with each other, we don't know what the capabilities of the models powering these apps that are AI app builders are even capable of.”

Understanding the Vibe Coding Approach

3:21 to 5:28

Lazar discusses his unique method of building software without traditional coding.

“because a lot of people, when I talk about this in public, they think that I'm saying that being an engineer is a disadvantage.”

Addressing Maintenance and Longevity in Software

5:29 to 7:58

Insight into the challenges of maintaining software and best practices.

“and where it's kind of hard to maintain the code long term?”

Lovable's Mission and Target Audience

7:59 to 10:20

Lazar outlines Lovable's vision for empowering non-coders.

“How are we going to get that in front of their eyes?”

The Future of Software Development

10:21 to 12:37

Discussion on the fast evolution of software development practices and mindset.

“Another use case that I think we're starting to really become good at is internal tooling.”

The Acceleration of VibeCoding

14:00 to 15:00

Explore how VibeCoding is rapidly changing the software development landscape.

“to do to traditional software development.”

The Importance of Jumping In

15:00 to 16:00

Learn why entering the tech space now is advantageous for new founders.

“But that's also for anybody listening and thinking, well, does it make sense for me to then jump in on this?”

Breaking Down Gatekeeping in Tech

16:00 to 17:00

Discussion on how gatekeeping has historically affected software development and startups.

“It felt like a kind of, you know, Christmas Eve, like when you have like the calendar with like all the chocolates and every day it's something new.”

Personal Experiences with Fundraising

17:00 to 18:00

Insights into the speaker's challenges and experiences with fundraising and company growth.

“No, to your point, I think whenever you wanted to build a company and the reason why most people wanted to go through the VC route, which was my case, because you were pro-boostrapping, etc.”
Show all 31 chapters

The Evolution of Building Software

18:00 to 19:00

A look at how the process of building software has changed over time and the misconceptions that persist.

“Maybe some of it was just finding new ways to do things.”

The Future of Coding and AI

19:00 to 20:00

An exploration of whether coding will still be necessary in the future given advancements in AI.

“Yeah, it's not that people, nobody's forbidding you to do it, but it takes a while, you know, to, I feel, and this is another kind of a touchy subject that people have polarizing opinions of.”

AI as an Opportunity, Not a Threat

20:00 to 21:00

Discussion on how AI can be seen as a tool for empowerment rather than a job replacement.

“The way I see it is, it's going to take me five years, maybe 10 years of learning how to code just to be at the level where AI models of today are.”

Trust and Human Interaction in Tech

21:00 to 22:00

The importance of human relationships and trust in the tech industry amidst AI advancements.

“I see this as a massive opportunity unlock.”

Market Reactions to AI Innovations

22:00 to 23:00

Analyzing how recent AI announcements have affected the software market dynamics.

“they will never know what argument the judge appeals to because an attorney works with that judge on dozens of cases before.”

The Balance of Interfaces and Chatbots

23:00 to 24:00

Exploring the interplay between user interfaces and AI-driven chatbots in software design.

“Like I showed them and they're like, you know, they're not builders in their hearts.”

The Future of Software Interfaces

24:00 to 25:00

Discussion on the potential future of software interfaces in relation to emerging technologies.

Designing for the Future: Interfaces and Wearables

28:00 to 29:24

Explore the evolving landscape of user interfaces and the debate around future technologies.

“So I think today, at least I can say, I see it as not one or the other, but both.”

Lovable's Forward-Looking Culture

29:24 to 30:55

Learn how Lovable prioritizes user needs and innovation to stay ahead in the industry.

“And then I saw something elliptical, almost like metal.”

Measuring Success Beyond Revenue

30:55 to 35:16

Discover how Lovable tracks user engagement and success through unique metrics.

“If they get like meetings and they're happy, they're staying forever and that's awesome.”

Scaling Adoption in Enterprises

35:16 to 41:49

Understand the strategies Lovable employs to drive internal adoption within organizations.

“We understand that we want to see people building and we want to see them being active, actively introducing features that people want to use.”

Balancing Consumer and Enterprise Needs

41:49 to 42:05

Examine the different demands of consumer and enterprise products and Lovable's approach to both.

Hiring and Organizational Changes

42:05 to 42:35

Learn about the hiring strategies and organizational shifts at Lovable.

Balancing Consumer and Enterprise Needs

42:35 to 44:35

Examine the different demands of consumer and enterprise products and Lovable's approach to both.

“I think, you know, it's not easy, right?”

The Aladdin and Genie Analogy in AI

44:36 to 46:41

Understand the limitations of AI using the Aladdin analogy to illustrate token constraints.

“So the Gini and the Aladdin analogy is great because I think it explains two of the biggest challenges that anybody building in AI is facing today as we record this.”

Optimizing AI Execution and Research

46:42 to 48:50

Learn how to optimize the balance between research and execution in AI tasks.

“But I'd say, and I'm not educated on this, so whatever I say, it's probably not true, but I'm just looking at it delusionally and thinking rationally.”

Using Lovable vs Other AI Tools

48:51 to 52:08

Discover why Lovable is preferred for specific tasks over general AI tools.

“the amount of effort for research versus execution, try to guide the agent as much as humanly possible.”

Learning Through Self-Awareness

52:09 to 55:33

Emphasize the importance of self-awareness in identifying personal skill gaps.

“on the try to fix button in Lovable to get the bugs fixed.”

Integrating ChatGPT with Lovable

55:34 to 56:03

Explore the workflow of integrating ChatGPT with Lovable for project management.

“You can actually have ChatGPT send a prompt on your behalf to Lovable to start building something.”

The Future of AI and Agentic Workflows

56:03 to 58:15

Explore the implications of AI-driven tools and workflows on the future of work.

“And I know we are almost like out of time.”

Becoming a Vibe Coder: Take Initiative

58:15 to 1:00:22

Learn how to create opportunities for yourself as a vibe coder without waiting for official job descriptions.

“one of the most common questions I get from people is how do I get hired as a vibe coder?”
Hear the part that matters, and keep it.Open this episode in VO. Double tap your headphones to save a moment as you listen.
Get VO free

Transcript

Automatic transcript. May contain errors.

0:00I think what you did to VC with bootstrapping is what vibe coding is going to do to traditional software development. The only people that should be afraid is people that watch me and you today and do nothing about it. Then you should be afraid. You have to put your ego aside. It is always the human fault. If you're waiting for a job description, you're not optimizing for the right thing. Today, your competition is zero. I don't think anybody's going to need to write code by the end of 2026 already.

0:25Lazar Jovanovic:Today on Billions, I'm sitting down with Lazar Jovanovic. Lazare is the world's first official professional Vive coding engineer at Lovable. A startup that hit 100 million dollars in ARR in just 8 months. Faster than any software company in history. Here's what's wild. Lazare has never written a single line of code manually. Not one. Yet, he ships production apps daily faster than senior engineers. From Lovable merch store to internal tools used by a company now valued at 6.6 billion. His weapon, AI, clarity, and of course, taste. Lazar, thanks a lot for being here. Thanks a lot for having me, man.

1:04It's a pleasure.

1:05Lazar Jovanovic:I mentioned also taste because you're really good at design and you've done some amazing things when it comes to design, I feel, because, you know, with AI and AI generated, it was more or less all the same, but we'll get back to this later. As my first question, I want to start, you know, you were mentioning that non-technical people, they can also have like an advantage over engineers because ignorance is kind of like a superpower. So how exactly does that play out, you know, day to day? Yeah, 100%. So I will start with a quote on this one. It comes from Warren Mason and it's about Kurt Cobain.

1:47Everybody hopefully knows who Kurt Cobain is, former Nirvana lead singer. He said about Kurt that he has this neyvet about not knowing musing theory at all and what goes together, which is great because he doesn't then have to make the right moves. He just has to make it different. And I think that's exactly how I look at this now, which is people that don't know the rules make up the rules as they go. And sometimes go against the rules, which is great because if we are all honest with each other, we don't know what the capabilities of the models powering these apps that are AI app builders are even capable of.

2:30I don't think that even creators of these models know. One of the proofs of that is that Claude Code was used to Vibe Code Claude Cowork in just seven days. in theory that would be impossible like it would be impossible in theory to even think that something of such a high production value that is now shipped to people as an enterprise-grade product is vibe coded by the tool itself um i think that people at open ai and i i may misquote them but like uh from my understanding the 5.3 the latest open ai model was largely written by the previous model. So again, if models can write models, why can't I do whatever comes to my mind, right?

3:16Or at least try. I think that's the key here. I meet with a lot of engineers and I don't want to get, because a lot of people, when I talk about this in public, they think that I'm saying that being an engineer is a disadvantage. No, absolutely not. Like if you're an engineer, that's a 10X engineer that is experienced and accepts these tools as the reality of what's today and what's coming tomorrow, you're unstoppable. I can't compare with you because you have all the layers of experience. What I'm saying is that for us that are non-engineers compared to a traditional engineer that just simply doesn't want to accept the reality of the moment we live in, we have this huge advantage of just like immersing ourself really quickly and leapfrogging in the sense of like, if you just know a little bit about software architecture, That doesn't mean you need to know how to write code.

4:06So I don't write code. You're right. Your intro was 100 % correct. But that doesn't mean I don't know how startups are built. That doesn't mean I don't know how software is built. You have to have some level and some degree of knowledge. But I think the big advantage is really not going into the nuances and just try, right? Just try. Prompt it. See what happens. And I think the way that plays out for people today in tools like Clovable or any other tool is really opening up capabilities for them to unlock their creativity without having to wait for resources or permission to do so. And that's pretty exciting to me today.

4:43Lazar Jovanovic:Yeah, definitely. And something that a lot of people have been talking about is the fact that you might be able to create software, you might be able to create apps, you might be able to use Lovable to create your own application, whether it's on your phone, on your computer or whatever. But what's hard about software is maintaining the software and making sure that as it evolves, things don't break. Like, I mean, we've seen it at Lemlist, you know, eventually all software company goes through a phase where you have technical debts and then it slows you down a lot and you have to rebuild kind of from scratch and go.

5:22Lazar Jovanovic:So what's kind of your vision with all these AI tools, you know, where something like can eventually break and where it's kind of hard to maintain the code long term? I think as the models get better, this will no longer be the bottleneck. Right now, it is a little bit. And for you to scale, at least from my point of view and looking at projects that I was able to scale, you can't just vibe code your way to that. You need to have a system. You need to have a framework that I'm trying to get people to adopt. Like, in a way, you're in this position where you need to start treating these tools not just as AI coding tools, but also almost as like technical co-founders and working alongside them as a companion rather than you bossing them around what to do.

6:13What that means in practice is this. Whenever you're trying to develop a feature that will require future maintenance, you need to properly document it, both forwards and backwards. That basically means that before you build something, you need to be very clear and very specific how that is supposed to look and work, document it. And usually I do that in the form of PRDs, which are for non-technical people. That means a product requirement document. Basically, just a breakdown of what we're building. Then when I'm done building it or where the tool is done building it, I try to back up the knowledge of defining the source of truth of how was it built?

6:58What are the relationships and dependencies with this new feature, new menu or new option? And like simply by documenting, you're already steps ahead of the curve. And even if something breaks, you could then point your agent in a direction where it's supposed to look and that way make the job of maintaining software easier. Now, is this a perfect workflow? Probably not. Like, does it help being technical when things start to break? Yes, most definitely. But I just feel that the underlying models are key. their context memory windows which means like the amount of workload that they can take in a single request are constantly expanding um i mean just two days ago we had the big uh sonnet 4.6 launch from entropic massive model amazing biggest context window ever best reasoning for coding ever i just the way i feel is like it's a problem but a problem that will be easier to solve than some other problems that vibe quarters are experiencing and the two bigger problems actually in my book are like why are you even building the thing that you're building like what's the idea behind it what's the reason behind it which is like a lot of us that are like just shipping a lot need to start asking ourselves should we ship this in the first place who is going to even need this that's number one then number two if we know that people are going to need this.

8:27How are we going to get that in front of their eyes? So distribution, again, same problem as we always had. I have a good friend, she always says it, like if coding was the problem, every developer would be a millionaire. But because they're not, that's just another proof that coding was never the issue. It was always something else. And I think we just made it easier for us to get to a point of solving the biggest problem in the book, which is attention, you know and getting your product in front of people's eyeballs and that's why like always try to shift away from making these discussions too technical because that's not the problem or if it's a problem today i i'm in that tribe of thinking that six to 12 months from now it

9:13Lazar Jovanovic:definitely won't be anymore and yeah i 100 agree with what you're saying and things are moving like so fast that is just every problem that people are raising now they're not gonna be a problem and to your point you know of uh developing like by trade i'm like an engineer so when i started i was doing like c as a language which then you had like different layers and javascript and so on and so forth back in the day you had assembler so obviously you know it's just like layers that are getting less and less abstract and now people with just language can essentially like get their app which but you still need the logic as uh as you mentioned and and something that um that i was curious about lovable is your your strategy and your target audience like do you want people who are using lovable to essentially like build their business and make revenue out of it or is the main target let's say like i don't know just a kind of consumers who want to create like cool apps for their friends and just like have fun or like what's kind of the the strategy and the people you're targeting the most i'd say if i'm honest like we just want to empower anyone to build anything they want um if you just want to make a game for your son because they're yelling in the car you can do that in lovable if you want to build a business as you pointed out that can make you some money you can do that in lovable as a solo founder if you are an enterprise and And you're looking for better ways to prototype internally so that you can reduce the time frame and shorten the cycles from an idea to a production grade software.

10:53Again, you can use Lovable for that. Like we're amazing at that use case. Another use case that I think we're starting to really become good at is internal tooling. And I'm serious level enterprise grade internal tooling for like engineering and non-engineering teams. So I think we are on this mission and trajectory to empower the 99 % who don't know how to code. I think that's kind of the overarching mission of like, if coding was your bottleneck, we will solve for it. But I also feel that that doesn't mean that engineers shouldn't or couldn't use Lovable. And we have a lot of engineers who are saying that, hey, maybe I won't use it today for something production grade, mostly because the not because the tool isn't capable, but because Lovable is kind of constrained a little bit on the tech stack.

11:46You mentioned a couple of different languages. So Lovable uses React framework as its primary framework. And I understand that in some companies, that's just not that it's not applicable to whatever stack they're using. But that doesn't mean they can't just come in and vibe code a good looking user interface connected to their database and do some data visualization. Maybe something like, you know, maybe you're not building features on Lovable, but you can build a feature adoption tool on Lovable. You plug it in, pull in all of your A-B tests, for example, add an AI model on top, and then you can see how are people commenting about your features or how are they adopting them, for example.

12:23So I think the mission, from my point of view at least, is clear. This is the future and the present. I think that, and this will resonate with you too, probably. I think that vibe coding will do to software generation, to what bootstrapping did for VC. So, you know, I know your story and your background, right? And like 10 years ago, you were probably considered the craziest guy ever getting into one of most competitive spaces, email, right? Against well-funded companies with$1 ,000 in your pocket and an idea. You had no prior experience doing something like that. you had no prior success, no prior personal brand.

13:07Like you were just like, hey, I'm just gonna do this my way. And not just that, I'm gonna go and not do anything corporate, the way I hire, the way my people that I hire behave. I will never forget one post, someone from, I think it was your customer support lead. It was like five, six years ago, but it still stayed in my mind. She was talking about how, you know, if people attack you as a support manager, as a brand, you can just tell them to piss off. You don't need that type of a customer. I was like, wow, like six, seven years ago, that was not the standard. Now everybody's doing that. Now everybody's protecting the culture, protecting the brand.

13:49Everybody wants to be a solo bootstrapped founder. But when you did it, everybody thought you were crazy. And I think what you did to VC with bootstrapping is what Vibecoating is going to do to traditional software development. Everything that I'm saying is going to become normal. The only difference is this. It took you a while to become the smart guy in the room. It took a minute, right? You were crazy for a long time. I think with VibeCoding, that is just going to get shrunk completely. So let's say, I don't know, I think it took people to understand the power of being a Bootstrap solo founder for about five or six years.

14:27With you, Peter Levels, Mark clue all of the people making it mainstream with vibe coding i think we're talking in terms of maybe two years you know like everything is just going to happen faster because the models are getting developed faster because everybody's attention is is now moving much faster like if i if personally if you ask me in 2023 how long is it going to take i would tell you that it's going to take at least 10 years to get to where we are right now and it's like just early 2026 i I just think everything is shifting in such a fast pace that is super hard to keep up. But that's also for anybody listening and thinking, well, does it make sense for me to then jump in on this?

15:08I'd say 100 % yes, because that is actually an advantage. Because everything moves so fast, everything that I know today and talk about today is almost irrelevant six months from now. Like I will have to relearn my job and reapply for my job in six months again with another skill set. So if you jump in today and let's say you watch my, I'm doing this interesting series called 28 Days of Lovable where like I'm recording videos every day. You just watch that and you start building. Me and you are almost at the same level, really. So you're not that behind, right? So I think that was a really good project, actually.

15:43Lazar Jovanovic:Like congrats on that. It's very awesome. I saw it like on LinkedIn and I think it was really cool. I actually shared it with our CMO because I think the way you're like showing and, you know, having people do it with you and within like this contest. And it was really, really cool. It felt like a kind of, you know, Christmas Eve, like when you have like the calendar with like all the chocolates and every day it's something new. And yeah, so very cool. Yeah. Yeah. No, and I just want to like put a full circle on the subject of like where we're at. Again, I don't know if you agree or disagree. You're longer in this than I am.

16:22But again, that's just my feeling. Bootstrapping really disrupted certain things. And even if it's not in monetary terms, it just disrupted the way the world works. I think the key word here is permission. I'm not saying that either founding a company was ever gatekept or learning how to build software was. But if we're honest with each other here, there was a little bit of a gate there. There's definitely gatekeeping. Yeah, yeah, definitely. You want to build a company?

17:00Lazar Jovanovic:Yeah. Yeah, go ahead. No, to your point, I think whenever you wanted to build a company and the reason why most people wanted to go through the VC route, which was my case, because you were pro-boostrapping, etc. like the the reality is i tried to fundraise when i got started and i got rejected so many times so it's like of course it got easier like once we reached like 10 million in arr and then sold like 20 of the company for 30 million and then we scared like to 40 50 million in unrecring revenue everything gets easier but the reality is like when i got started no one would talk publicly about what numbers, how they would acquire customers, how they would do things.

17:46Lazar Jovanovic:So everyone would say, you need to go VC because that's what the press talk about. That's what you read on TechCrunch at what. And eventually for me, I got lucky because it started working. So I'm like, okay, at least I can share the stuff I do. And maybe some of it was luck. Maybe some of it was just finding new ways to do things. And I feel what you're doing with Lovable is definitely the same. you know it's like building software feels gatekept because even if you look at you know like I know so many people in France who build websites for businesses and for a long time you know when you had to actually be a developer and know like HTML, CSS and people had to work to create a website these guys like the developers they were spending like time they need to you know like check where the website was hosted sometimes they were issue with hosting platforms so they had to to spend a bit of time but eventually you know there was that phase where a lot of people didn't know that you could go on whatever website buy a template edit it yourself and then that's it you know you don't have like maintenance on anything and these persons were actually making good money making people believe that every time they need to make a change it's actually super complex and you need to be a crazy developer etc and this for me is like the worst gatekeeping ever and i feel like with vibe coding it's exactly the same like lots of people still believe that you need an army of developers to build things well actually as you say so well i think your your motto is like demo don't memo which which i think is great and very cool and And you can build like a lot of things by yourself.

19:31Yeah, 100%. You saw, you summarized it. You hit the nail on the head there. Yeah, it's not that people, nobody's forbidding you to do it, but it takes a while, you know, to, I feel, and this is another kind of a touchy subject that people have polarizing opinions of. I get asked, should I learn how to code, right? And my answer is a definite no. And people always like that are developers, they say, no, that's the wrong way. People should know how to code. The way I see it is, it's going to take me five years, maybe 10 years of learning how to code just to be at the level where AI models of today are.

20:11I really don't think that five or 10 years from now, anybody's going to write code. And if I'm honest, I don't think anybody's going to need to write code by the end of 2026 already. It's going to be a thing of your own choice. If you want to write code, great. Eventually, as I said this before, writing code will be like calligraphy. It will be a form of art. It will be something that if you want to fine print your code, do it by all means. Nobody's going to prohibit you to do so. It's just not going to be needed or efficient. So for me, that layer of permission has gone away. And now there's probably different levels of gatekeeping that we need to solve for,

20:48Lazar Jovanovic:which is, again, a lot of people feel like this is a doom and gloom moment, which is AI is coming for all of us, especially in tech. Everybody who's sitting behind a computer, they're going to be out of a job a year or two from now. And I feel completely the opposite. I see this as a massive opportunity unlock. I also think that as we progress further down this path of everything fake, for the lack of a better term, right? Fake videos, fake images, fake this, fake that. We are number one going to start to value again in-person events, in-person meetings, in-person deals and everything done human to human.

21:27And I think same way taste is the currency, the key currency will become trust, right? There was a big polarizing moment. I don't know if you saw that on LinkedIn between two authors of very viral posts. One of them was something big is happening and the other one was called something messy is happening. It was like a clash of two worlds where one guy is saying, you know, if AI didn't knock on your door yet, you know, you better be ready. It's coming for you, right? It was a bit of a, you know, dystopian reality of like, oh my God, like we're all done. And it's all doom. And the other one was a little bit of an opposite of that, which is acknowledging that AI could be coming for people's jobs, but that it's not actually like that and that people don't hire people only because they're efficient.

22:22The person tried to compare, to use an analogy of law, like you can teach AI everything about Anglo-Saxon law, for example, and you can represent you in court, but AI will never be able to read the room, the jury, to see what they respond to. they will never know what argument the judge appeals to because an attorney works with that judge on dozens of cases before. So it has all of that context, right? So there are certain layers in which I think this may seem like a COVID moment where like it's a major cut off, but I don't think it is because with COVID, we went into lockdown everybody on the same day.

23:05We were mandated to stay at home right so the shift was for everybody all at once yeah yeah now it's like people still get to decide whether they want to adopt this and you wouldn't believe how many people are actually still on the sidelines i live in a very small bubble intentionally i only expose myself to builders i i'm on discord of lovable i'm on linkedin only following builders so to me it seems like oh the whole world is building then i go outside uh and play volleyball with my friends and nobody knows the name of my company. Nobody knows what my company does. Nobody knows what by-code coding means.

23:40And most of them don't care. Like I showed them and they're like, you know, they're not builders in their hearts. And it's fine. You know, things will shift. But I think what I'm trying to say is, you know, things are definitely progressing fast. Maybe you don't need to learn how to code to take advantage of all of this, but you also shouldn't be afraid to make a step. you're not far behind you're actually still super early and don't worry if you the the only people that should be afraid is people that watch me and you today and do nothing about it then you should be afraid like if you listen to me and follow me and you still don't feel like you should do anything about it then my friend it's if anything does happen to you it's it's kind of your fault it's not the fault of ai but if you just take a couple of steps really just minor ones vibe code whatever or not even vibe code just start using ai in your day-to-day life a little bit more you will not just find it interesting and fun but you will be prepared for what's coming yeah i think

24:42Lazar Jovanovic:it's quite insane like i'm i'm actually like um launching a new business and um it's it's really funny to see how things have changed because you know i've been like a ceo of 150 plus people etc for like for for years and now you know i'm started like uh alone you know like i mean with my uh my actually partner and and girlfriend and you know we have to do all the things from the start like build a website like uh do slides marketing and then i'm like i remember how much time you know it took back then in 2018 and i'm like with the eyes this is like so freaking fast and you can do like so much more and it's just uh it's just insane and it's like uh it's a real pleasure to be able to build.

25:27Lazar Jovanovic:And I was quite curious to get your thoughts on, you know, like we're talking about Saspocalypse. Like you've seen probably it on Twitter, like stock market going down for all software companies, etc. Especially after Anthropik announcement of Cloud Co-Work, all these things. On your side, like lovable, like the clear positioning has been like the last piece of software. So it's like anyone can build whatever they want. But if people build things, it's still a software with an interface. If we like kind of hear like what's happening on the stock market, etc. With AI agents doing everything and essentially their view is like you will never need an interface ever again apart from a chatbot.

26:17Lazar Jovanovic:Like what's kind of your view about it? Is it something you're talking about internally at the company? Like what's the long term vision? I mean, it ties back to what I was just saying. I think anything that is as extreme as like you're only going to need X is probably not going to be entirely true. People still live in spreadsheets. People still live on pen and paper. You know, you go to a doctor here in the U.S. You don't even get there's no electronics like you just write with your hand, like everything. Right. Patient intake forms will, I don't know when they're going to go online even. So it's like, you know, I feel, you know, maybe it's a vision of the future.

27:01And yes, I feel like that synergy between an interface and a chatbot is probably a closer reality, which is the software is a little bit more personalized to your liking and your experience. I think that's the big benefit here that when you design software and you build software in the past, because of the maintenance that you mentioned earlier, you kind of have to strategically make certain tradeoffs and say, look, we're going to have to go in this path. Whereas here, like I can just build features on top of features in seconds, in minutes. So like this is the way I build, for example, one of the internal software that we use at Lowable that I built for our GTM team.

27:42I built it as an interface originally because I needed that so that we can interact and learn which things can be automated, which things pull more or less inefficiencies in day-to-day workloads. And wherever we could, we introduced a chatbot layer that you can just dictate into it to make decisions for you. But it's based off of that interface. So I think today, at least I can say, I see it as not one or the other, but both. You can just marry the two and have the best experience. I don't even know, like there are people, for instance, on Lovables Discord that I talked to about this stuff. Like there are a lot of people thinking, oh, we're designing for phones is stupid.

28:26We're not going to use phones in a year or two. We're going to have a wearable. We're going to have glasses. Like we should design interfaces for that. So like everybody has an opinion about this. What's interesting again is the question is what do I do about it for the viewer? and again that's why i say don't be afraid look at how many opportunities there are there are so many potential ways that this can develop just pick your lane pick any lane and you will likely succeed because i think some people will decide they don't need monitors or phones they're going to use wearables and glasses other people are going to go the other way they're going to keep the traditional setup there's maybe going to be i'm seeing mentions of like uh that open ai wanted to launch a Super Bowl ad for like a physical device of some kind.

29:17But then last minute, they backed out of it. So there's this whole mystery around what's that going to be about? So I don't know. They did like a partnership.

29:25Lazar Jovanovic:They bought like Johnny Hive, no? Was it like the company? Yes, exactly. And then I saw something elliptical, almost like metal. And I don't know, maybe it was even fake. Maybe it was a fake video. Like that's the problem today. You don't know what's real. So what I think is that the answer is really, if I'm honest, nobody knows what's going to happen. We internally at Lovable have this, you know, kind of a great forward looking culture. And everybody in the company is a very early adopter. Lovable is not number one by accident. You mentioned all the numbers. Getting those numbers can only be done if you have the best talent in the world.

Read the full transcript

30:09And I genuinely believe we do. So wherever the direction is, we will be one of the first movers in the industry. And I feel, you know, we're listening to the user. Our obsession for 2026 is all about what they need and what they want and unlocking potential even further, right? Helping people introduce payments to their apps, email to their apps, you know, basic functionalities, really, because again, there's a gap, I feel, you know, there's a gap between people that are so forward-looking versus people that are just getting started and you have to kind of dance between those two lines where you're opening up new frontiers but at the same time you have to help the mom and pop shops on main street you know become digital without as you said needing

30:54Lazar Jovanovic:to hire a super expensive developer no i agree and and i think like um there are two points i on the touch base but the first one is uh to me you you measure like the the quality and the impact of a b2b business usually by the amount of value it generates from the end user so typically in our case like with lemlist people pay like a subscription monthly and then you know like they're gonna stay with us if they start getting more and more meetings with their dream customers That's how they measure the ROI. If they get like meetings and they're happy, they're staying forever and that's awesome. If they don't and they're unhappy, they're going to turn.

31:39Lazar Jovanovic:In your case with Lovable, because you have so many people building businesses and launching these businesses, is it something that you manage to track the actual revenue that people are making or is it still too early to actually know whether... Because sometimes I see, You know, like Elena last time was talking about like, I think it was a company that did almost like a million in sales or something like this with Lovable. And there are like some really cool success stories. But internally, is it something that preoccupies you and where you spend time on? Or, yeah. It's an obsession. Like for us, that is what we obsess about.

32:22Because as you said, in the end, if we're not generating the value for the end user, what are we doing? We're just consuming tokens for nothing. I think, you know, we talked about it earlier. Building is one part of the equation. And it's probably, if we're honest, the easiest to solve. We are trying to work a lot on understanding the blockers of distribution and trying to put more emphasis and provide more, I guess, spotlight to founders. So you mentioned Elena. One thing that she will do on March 8th is do the biggest women's build-a-thon ever in history for International Women's Day called SheBuilds is our third season, right?

33:09Nice. Where all the spotlight is on women founders and trying to empower them. You mentioned that we featured success stories on our YouTube channel. I think at least once a week, there's a founder that's being interviewed. like the one of the latest stories was like there was a guy i think that was building cakes right and he just needed a way to distribute them so he had kind of a market but he he just didn't venture into online because he was not technical at all the guy's a baker right he went to lovable built the entire infrastructure i think he he was making a hundred and fifty thousand dollars a year making cakes like so it doesn't have to have to be just a digital product you know lovable integrate with Shopify natively, pretty much, and seamlessly.

33:52So it's super easy to now build an online business, an online shop. All we do is really talk to users as much as it's physically possible. I always say to people, if you want to get in touch with me, just send me your lovable apps or your lovable ideas into DMs. I always respond. And everybody that follows me can testify that that is true because I obsess my personal obsession you mentioned February the 28 days of lovable thing that was something that I built like it's not a company-wide instruction nobody told me hey go and build this like we want to educate people we want to teach people because I do believe genuinely that the best entrepreneurs and people with best ideas are probably not technical and again I know I'm going to take a beating by engineers for saying it but I genuinely feel that it's true to this day the best two ideas for lovable that i received personally one of them came from a landscaper the other one came from a radiology technician no neither of the two guys i don't know if they even owned a laptop like they just had the best ideas because it's like ideas are not something that requires you to be technical it just requires you to be a little bit delusional a little bit you know having a knowledge about something or curiosity and that's about it and i think we're appealing to that demographic and as you pointed out in your question we obsess over their success um i'm not probably supposed to talk about some internal metrics and stuff like that but i can tell you the main metric for lovable in 2026 is not is not monetary at all we don't care about the arr i know everybody talks about it you know it's the news it's the media it's what gets the views sometimes and I get it and we're proud of the fact of how fast we're growing but internally for us that number is is not relevant at all all we care about are a couple of internal metrics that are 100 user-centric they have nothing to do with the company

35:53Lazar Jovanovic:can you share some of the metrics you track or is it uh confidential so one of the one of the ones is like daily active apps, for example. I can say that. We understand that we want to see people building and we want to see them being active, actively introducing features that people want to use. And then there are a couple of other ones, including understanding how they monetize. Obviously, when people integrate a third-party service to process their payments, we don't have an oversight of the money side there. We don't know what happens on their Stripe. But like soon enough, we will provide people with options to use Lovable to handle bits and pieces of that.

36:38That's some stuff that I, again, I can't talk about just yet. But like we want to give people two things. We want to give them an easier path to build, an easier path to monetize their apps and then provide us more easily with an insight how helpful we are for whatever their metric of success is. and try to optimize all of our attention towards that.

37:02Lazar Jovanovic:And the second point I wanted to discuss, you know, because I think a risk whenever you're growing like extremely fast and you have like different kind of users because obviously you have like the B2C kind of users who are like coming, as you mentioned, like you want to build like a game maybe for your kids. We also know kids, you know, like they're going to have fun with the game for like two weeks and then they forget about it and they have a new game and so on and so forth so the the risk when from a business perspective that I see with this kind of customer and we've also seen it you know at Lemnys with people launching a business and trying to make it work is that 90 percent or 90 plus percent of businesses fail which technically means that if people have no business anymore they're not gonna still like purchase your product and hence your churn is quite high you mentioned that one of the other like target market is people building tool internally and also people building tool for enterprise internally like doing enterprise grade tool i think the the company that's done it like uh amazingly like the distribution of their tool at the enterprise level through partners is Salesforce.

38:26Lazar Jovanovic:So the question I have to you is, are you internally thinking of building some sort of lovable agencies of people who would basically go and see all the enterprise out there to help them build lovable products internally and therefore do like the same kind of fee split that HubSpot or Salesforce is doing for agencies to actually help out these companies build their internal tools? Yeah, that's a very good question. So internally, we're scaling our go-to-market very rapidly as well right now. We have a lot of inbound, right? Everybody wants to at least try Lovable. So we're trying different ways of getting Lovable into organizations.

39:15I can't name companies, right? But I can tell you, leading companies in the ride-sharing world, telecommunications world, manufacturing of graphics ships world, and banking, they are unlovable. They use lovable. They are our customers, right? So we are now trying to obviously satisfy the need of the inbound, which again, we're getting a lot of it. But at the same time, you're right. Just because somebody wants to do it doesn't mean that internally they have the means to drive adoption. Thus, the education becomes very important and relevant. And most times, I'd say that this movement, at least in our world, is kind of a, not just, not B2B, but it's like B2C2B.

40:02You actually have someone in that company that discovered LoL and built their golfing app or wine cellar app or something. They got obsessed and they started talking with coworkers and championing it with managers. And that's how then that inbound comes in. So a lot of times our biggest partner is actually an internal champion, somebody who's a lovable power user, because that way we can distribute in that organization much faster. It scales faster because you have somebody internally who is very invested and, by the way, can actually elevate their career as being forward thinking and AI first builder.

40:40right um we are establishing obviously if there is anybody watching and they're like i want to be a lovable partner i want to help with distribution by all means there's a partners page that lovable has anybody can come in there with their proposal depending on whether they're a vc fund a private equity fund or whatever like if they're just seeing an opportunity here yes lovable does have a pipeline where we are working with uh different organizations as well and partnering with them on this but as i said for us i think it's super important not just to put the logos on but drive internal adoption that's that's the obsession same way like on the consumer side we want to help people build things that other people want to use it's it's very similar on the enterprise side just because they bought a contract doesn't mean that they are that we succeeded the only way we succeed is if 90 of them are building every day and that they're actually not just building but getting value out of it and then coming back to us with feedback on how can we make the product even better and so it's a bit of a you know it's very much so in motion i have to say i personally work in in the go-to-market team right now so like my role is is hybrid like as a vibe quarter you you can build anything so i do a little bit of work for marketing for growth whatever but um if we talk about my role today i am sitting in the b2b go-to-market team and i can say you know it's it's very exciting you know the adoption that i'm seeing the feedback that we're getting i think we we're getting really good traction in in enterprise but yeah as you said i acknowledge that there are organizations that did it amazingly before and you know i think lovable um similarly to how we have the best talent for engineering i want to say we have the absolute best talent for go-to-market as well that's why we are hiring though yeah we are hiring though i have to say anybody watching look at our open positions.

42:34We're always hiring for people that are great. But yeah, we'll get there, right? We're working on it. I think, you know, it's not easy, right? In a way, consumer product is what got lovable very far, right? But consumer and enterprise are not the same thing by any means. Like the needs of the two avatars are completely different. So it's very fun to balance things when, you know, resources are scarce, right? No matter how much and how fast you hire, you always need more people. We're, I think, in a people business now. People think we're solving for AI. I think we're still solving for humans. So again, I'm super optimistic when I see how many different opportunities can people have in these AI companies like Global.

43:19So I think as we scale, we will likely further and further expand and provide people with a way to participate.

43:28Lazar Jovanovic:Yeah, and I think to your point, the organization changes a lot when you're focusing on b2c2b or like b2b and then enterprise like we we made that move like to start going up market a little bit and you know things get now you have contract you know it's no more self-service so you need like legal and then you know it's like longer sales cycle and then you need like dedicated features and then you need to onboard now not one person by themselves but 20 30 people you need roles you need like all these things so yeah it's uh it's different things but uh also like uh really exciting and um something that i think could be cool is i remember your analogy you know about um when you develop something and you hit a bug um what i think you said it's 100 your fault and i'm guessing you were using like the aladdin and the genie kind of analogy so maybe like can you explain a bit what's that analogy about and also give like a mini playbook on how you should do things so it works.

44:35Yes. Okay, great. So the Gini and the Aladdin analogy is great because I think it explains two of the biggest challenges that anybody building in AI is facing today as we record this. This will be completely different six months from now, as I said, but today there are two problems and two constraints. One is the machine problem. The other one is the human problem. And this is how the analogy goes. Everybody watch the Aladdin. There's a genie in the bottle. You rub the lamp. Genie comes out and tells you, I'm a genie. I do magic. I can grant you three wishes. And that's the first part of the bottleneck.

45:14The genie can only grant you three wishes, not 3 ,000 wishes, not 3 million, right? There's only a finite amount of things that you can ask for in a particular request when you rub the lamp. Same is true for AI and LLMs. Only it's not denominated in wishes, it's denominated in tokens. We talked about, we mentioned briefly this concept of context memory window. What that means is I come to an AI tool, lovable, whatever, claw, doesn't matter. And I have a request. I have a wish that needs to be fulfilled. Now, if I ask one thing, likelihood of it being capable of doing it is super high. The token windows, these token limits are now getting extended further and further.

46:02And the way these models consume tokens is you make a request and then the first part of the consumption goes to acquiring more context about, okay, what is the user asking for? Then the second part is like, okay, now that I know what they're asking, what should I read more on? What are the files? Should I browse the web? Should I take some screenshots of the app? Like I'm trying to determine still, like it's still in this research phase, so to speak. Then there's the planning phase and then there's the execution phase. The execution phase is what we need to optimize for and what your desire is because you made a request you want the tool to execute.

46:42But I'd say, and I'm not educated on this, so whatever I say, it's probably not true, but I'm just looking at it delusionally and thinking rationally. AI tools can spend 80 % of their energy on research phase and 20 % on their execution, or they can spend 20 % on research and 80 % on execution. It is up to you to determine which of the two is true. And that is the second problem. Let's go back to the Aladdin and to the wishes. I come to the genie. I say, okay, my first wish is to be taller, right? And that's all I want. And what happens is, in my analogy, the genie makes you 13 feet tall. Or for people in Europe, that's roughly four meters, maybe five.

47:31When you're five meters tall, I mean, you know, I'm a big fan of Wemby, you know, as the basketball player, but that would be a lot even for basketball terms, right? Like you wouldn't be able to fit into a car, you would hit walls, you would hit, you know, whatever, you would hit obstacles, right? And that's the part where you did, you were not specific enough. And that's, that's our role. Like, because we can't solve us, the user, we can't solve for the first problem, because the context windows, token sizes, quality of the models, that is determined by the lab, meaning Entropic, OpenAI, Google, whoever builds the model, it's their output, right?

48:14Because I can't control that. What I can control is how these tokens are consumed. So when I'm making my wishes, rule number one, don't ask for more than like two or three things and make sure that they are somehow related, right? Meaning that if you want to make a change, focus on making three changes on one page versus making 17 changes across seven pages. That's never going to work. The tool just can't get enough context. It's going to spend all of its time doing the research and leave very little energy for execution. On that note, to reverse the amount of effort for research versus execution, try to guide the agent as much as humanly possible.

49:01And the way to do that is, number one, by building good documentation. We talked about it a little bit earlier, forwards and backwards documenting, making sure that when the agent needs to do the research, it doesn't have to look for stuff. They are already there. You're pointing it in the right direction. Secondly, when bug fixing and when talking about bug fixing. Referencing is key. Tagging files, taking screenshots, sketching on those screenshots what's broken, providing longer prompts and context. People always think, oh, the longer my prompt, the more tokens get consumed. No, tokens do not get consumed based on the number of characters you're sending.

49:42They get consumed based on the amount of effort the agent needs. your job is to reduce that effort and to reduce the research part and then leave it up to the agent to execute right if you're on a tool that allows you sorry to interrupt but on that point

49:59Lazar Jovanovic:i think do you i was just wanted to know if you use like other llms to actually like help you build all this front because sometimes you know it's hard for people to actually communicate efficiently or clearly what they want. So do you sometimes, I don't know, use like Cloud or ChatGPT just to just type in all your ideas and what you want to change and then have them rewrite it so eventually you could use like less token? Yeah, so personally, I use Lovable only because of two reasons. Two reasons, really. Even when I wasn't a part of the company, I use Lovable. Main reason is context. if you go to chat gpt or claude or wherever and you prompt it to help you with something about your project it will not have context about it it doesn't have access to your code base it doesn't know what you're building exactly so it will start guessing things when you're building software you shouldn't guess anything it's pretty deterministic right it's either black or white So for me, I go to Lovable because Lovable number one has planning mode, which you can just click and toggle, which puts the agent only into this research mode.

51:16So there's no execution in planning. So that's a good way to stop for a second and think about things more comprehensively. And then secondly, more importantly, as I mentioned, Lovable has your entire code base, all of your past messages. So it has full context and memory of what's going on. Plus, Lobel has this very powerful project knowledge feature, which basically allows you to dictate the way you want the agent to think, behave, and focus on. That is something, again, that you cannot transfer into a third-party tool. Now, do I go and take console logs, or do I go and take error codes into other tools to learn more about them?

52:02Yes, I do. I think I use a Claude or ChatGPT for education purposes a lot, where I feel that the biggest unlock for me is not just clicking on the try to fix button in Lovable to get the bugs fixed. The biggest unlock for me is when the bug gets fixed, asking the question, okay, number one, how should I have prompted you so that this problem never would have happened in the first place? Because again, it is your fault. You have to put your ego aside. it is always the human fault. AI is more capable of doing this than most of us are. So ask it, what was the mistake that you made? Acknowledge that you did it.

52:41It will explain it to you. Then a lot of times what I'll do, if I see that it's an important piece of knowledge, I ask it to save it into like a rules file so that it remembers next time we're doing a change in that particular part of the app, these are the rules that we both need to be hold accountable for and again chat gpt or claude will not know that conversation took place and that's why i don't use them as much i would go maybe again i remember when i first started off i didn't know what role level security meant like to me it was like i didn't get it at all i didn't know anything about backhand so i spent a lot of time on chat GPT trying to get it to explain it with an analogy and whatnot.

53:31Today, somebody watching this shouldn't stress about it. Lovable or most tools really have no problems writing RLS the right way anymore. Like it used to be a bit of a problem. Now it's not not. But like definitely use any tool in the book for education. I will say I use a lot of tools for design. We talked about it a little bit. And like, I think for me, the biggest unlock today and the biggest thing that I want to level up on is really my sense of taste and understanding what quality looks like. So my personal discovery is all about finding new AI design tools that maybe cannot build apps yet or, you know, they don't have backend, they don't have any front end functionality either.

54:16It's just concepts and then trying to see, is there something there that's interesting? Is there something that I can export and import into Lovable and build, not build from scratch using my own prompts? Because you said in the intro, I'm a good designer, but I would heavily disagree against that. Actually, that's one of my worst skills. I'm pretty embarrassed by how bad I am at it. So I understand that that's one of the bottlenecks for me. So what I do is I go in and seek for tools that will teach me that. So again, to put it as a final answer, be self-aware, but put ego aside and start understanding what is it that you're missing personally.

55:03Is it taste? Is it design? Is it clarity? Is it technical knowledge? Is it a product market fit, go to market, whatever, distribution? and go and learn that. Lovable is maybe not the cheapest place or the best place to learn that, right? Consuming credit just to get a go-to-market strategy is probably not the best use of Lovable because Lovable is primarily a coding tool. But what's good is when you know what gets your product market fit, then you come with that knowledge in Lovable and build it. I don't know if viewers know this, but maybe you don't even know this, but you can go to Chargip team and like chat with it, you know, infinitely about your project, your idea, brainstorm, have it validate your idea, and then you just tag Lovable and that triggers a workflow because Lovable is now a ChatGPT approved app.

55:52You can actually have ChatGPT send a prompt on your behalf to Lovable to start building something. And it's a really powerful workflow because that's how you kind of merge the two worlds the best together today, I think.

56:05Lazar Jovanovic:Yeah, that's really cool. And I know we are almost like out of time. So the final question I have for you is like, what's the project you're most excited about that's coming like during the year or the years to come? Well, I think we're in a different, we're in a bit of a funky moment with this open claw, agentic workflows giving permission to an agent to do everything on your behalf banking details order my stuff on amazon thing like i i'm a little bit scared about all of it like i don't know enough about security to go all in on it but i do acknowledge that is the future um i i i think i thrive and lovable because i found ways to eliminate myself out of the equation people think i'm a good prompter but the actual secret is that i don't prompt at all and that that's why i'm so good at it i found ways to build systems where the tools prompt themselves and i think sometimes getting ourselves out of the equation is not the worst thing in the world either so i think i'm excited about how that future looks like and how will we evolve to work next to ai that is you know pretty much self-intelligence self-correcting uh almost some would say agi i don't know if that's agi or not i some people say we're living it already we just don't realize i don't know but um i think that's exciting that's something that i'm eager to see and not just eager to see it develop i'm eager to see it being actually implemented into day-to-day life i think it's still very niche i think that you really need to be technical and you really need to know what you're doing today to use something like open claw for example but i i'm thinking hey what about six i always think it's six months from now i'm building for what's going to happen not for what it is today these models are the worst they're ever going to be today as they say so i'm very uh much so excited about that and one thing before wrap up that i'm excited about too is like that i just want to touch upon briefly if you allow me is one of the most common questions I get from people is how do I get hired as a vibe coder?

58:26How do I like I'm very excited about that role, but I will say this. If you're waiting for a job description, you're not optimizing for the right thing. You're not supposed to wait for companies to announce this. What you're supposed to do is open up your laptop as soon as you're done watching the episode, list five problems in your company, in your org that need to be fixed. Talk to your peers from HR, marketing, sales, whatever. Then you go and you build them and you just give it away to them and ask them a week or two from then, are they faster? How much money they think they're saving? How much time do you think they save?

59:05How much is the company saving? Then you collect all of that, go to your manager or to any senior manager and ask them for a 15-minute meeting to show them something cool, right? And then show them all of these savings and all of this success. Come in there with proof, not with the idea. And you hire yourself. The reason why this is cool is, number one, there is no job description. So guess what? You get to make up the rules. You get to say what you do every day, which is amazing. Technically, that's what I do, right? I get to say what I do every day, which it's just nuts, right? and then secondly for people in other orbs we are very forward-thinking so we have internal benchmarks but most companies don't have a benchmark how much money a vibe quarter should be making like hours they should be working so you get to to to almost decide how much you're going to be making too which is crazy right so again i just wanted to touch upon that because it's such a frequent question that i get and the answer is simple build just build don't wait for anybody to hire you don't wait because when it becomes a job ad you will compete against a thousand people within your own company today your competition is zero just go and take initiative

1:00:22Lazar Jovanovic:best advice ever and i think best conclusion word where can people like uh follow your updates and follow all the things and the value you share yeah mostly on linkedin i'm very active there as i said I'm posting videos on YouTube as much as possible. So I'd probably say those are the two places. Awesome. Lazar, thanks a lot for all the wisdom you shared. And I'll talk to you soon. Thank you, G. It was a pleasure.

From the publisher

Lazar Jovanovic is the world's first official "Vibe Coding Engineer." Working at Lovable (the AI startup that hit $100M ARR in just 8 months) Lazar is proving that the future of software engineering isn't about syntax; it's about taste and intent.In this episode, we dive into how Lazar ships production-grade apps for a $6.6B unicorn without writing a single line of manual code. We discuss the "SaaS-pocalypse," why ignorance is a superpower in the AI era, and how you can transition from a traditional role to a Vibe Coder.TIMELINE : 00:00 - Meet the world's first "vibe coding" engineer01:06 - Why "not knowing how to code" is your new superpower04:43 - Is software maintenance dead in the age of AI?09:15 - The Lovable story: hitting $100M ARR in 8 months15:42 - The end of bootstrapping? Vibe coding vs. the old way24:16 - SaaS-pocalypse: the future of software interfaces29:47 - Beyond code: the only metrics that matter for AI products37:01 - Will enterprises ever adopt AI-generated code?44:35 - The "Aladdin & Genie" trick for mastering AI prompts56:05 - How to become a vibe coder (no permission required)REFERENCES :

More from BILLIONS

All 31 episodes
Never wrote a line of code, now a $6.6B unicorn : the vibe coder - Lazar Jovanovic [Lovable]BILLIONS · 1 h 1 min
Listen in VO