Find me on https://lovable.dev/@lazarjovanovic and learn Lovable on https://february.lovable.app/

Lazar Jovanovic

Professional Vibe Coder at Lovable | L5: Diamond Certified

Next stop - Lovabletown! ❤️ 

Dream it -> Ship it

Am I still crazy for saying no one will need to code 6 months from now? 
Am I still crazy for saying that PMs and designers do not need to learn how to code to build production grade software? 

Am I crazy? Or am I just trying to shake you from your roots? Make you do something about it? 

Not freak out by any means - but by all means take action and start doing something. 

It's entirely your choice and within your reach, please please please listen to Lenny Rachitsky and Boris Cherny dive deeper into this topic. 

Don't listen to me. Watch me as an example it is possible, and do something! 

https://lnkd.in/eK5jAdwq

Open video: Head of Claude Code: What happens after coding is solved | Boris Cherny on youtube.com

Head of Claude Code: What happens after coding is solved | Boris Cherny

Trying to come up with a good caption for this one.

This lesson is probably going to be very polarizing so I need your opinions on this in the comments. 

My POV:

The real leverage isn't in building more apps. 
It's in building fewer apps that can become many.

I used to think every project had to be unique. 
A new idea, a new market, a new everything. 
That is backwards.

Most beginners build apps. 
Builders build templates.

I don't mean a generic boilerplate. 

I mean a repeatable solution to a repeatable problem. 
Because most people in the same niche need the same things.

Take fitness creators. 
They all need workout delivery, progress tracking, and community features. When you build it, the pitch isn't "I have an idea for an app." 
The pitch is "I already built this. It just needs to look like you."

Or look at podcasters. 
They have audience and trust, but they lack products. 
You build a companion app once with searchable content and AI summaries. You use the same structure and simply swap the identity for the next creator.

The math changes everything:

Build one solid template in two weeks. 
Customize it for a client in two days. 
At $2,000 per branded app, five clients is $10,000 from that same initial week of work.

To find your own template, look for these four things:
1. A niche where people share the same needs.
2. A stable structure where only branding and content change.
3. A market where people are already spending money.
4. A clear way to reach that audience.

Your best work isn't just for one client. 
It is proof that you can deliver something premium, and that proof can be replicated.

Find a repeatable need, build once, and customize many times.

Catch Day 26 and the full lesson at https://lnkd.in/eWZShRpu and tell me if you agree about this being the easiest way to start monetizing your Lovable builds?

I think most people are still using AI at the surface level.

They use it to generate something faster. 
A document. 
Some code. 
A summary.
A deck. 

And that’s fine. 
It already feels magical.

But the real shift for me wasn’t speed. It was structure. I stopped thinking of AI as a tool that produces output and started treating it like a thinking partner.

Now I use it to pressure-test ideas before they become expensive.
1. To argue with me.
2. To ask me the uncomfortable questions.
3. To simulate edge cases I wouldn’t have thought about on my own.

The biggest unlock isn’t “write code for me.”
It’s shortening the feedback loop between idea and clarity.
That’s the part that changes how you work.

Vibe coding is just problem-solving under new constraints.

People hear the term and think shortcuts or laziness. 
In reality, it is the natural next step in the history of software development.

In Day 27 of 28 Days of Lovable, Marija Milosevic Lovable Ambassador and a former software engineer with 10 years of experience writing Java joins us to reframe how we look at AI-powered building.

If you zoom out, the pattern is logical:
- We moved from binary to functions.
- We moved from machine commands to readable languages like Python.
- We moved from manual coding to visual low-code builders.
- Now, we describe functionality in natural language and let the system generate the structure.

Every time we build on top of a new layer, we give up a bit of control in exchange for leverage. 

That has always been the deal. 
But faster execution does not mean less thinking. 
If anything, it means your thinking matters more. 

Thinking, judgment, and taste are what keep you calibrated when the tools move fast.

Over the last 27 days, the goal hasn't been to master a tool, but to master a loop:
1. Identify a problem.
2. Understand the constraints.
3. Design a system to solve it.
4. Execute as cheaply as possible.
5. Review honestly.
6. Decide deliberately.

When you look at an app like Uber, it feels like magic. 
But when you break it down into driver location, your location, distance, and a recalculation loop, it stops being mysterious. 

It becomes a system. 
And once you see the system, it is buildable.

Good builders don't wait for perfect tools. 
They see limitations early and design around them. 
That is what transfers. 
That skill doesn't expire when the tools change.

Catch Day 27 and the full lesson at https://lnkd.in/eWZShRpu

Community spotlight time! 

I asked -> you shared -> now it's my turn :) 

I cannot be more grateful for all of you that kept sending me Lovable app links for the past week. 

I hate singling anything out - but these are the 3 that popped for me. 

Keep sending stuff that you build and I'll do my best to feature you. 

https://meucv.online/ by Diego Ruzzinenti - simple (love that) application, the reason why I really loved it is because he took advantage of everything that AI development can offer. Check out the animation of how the app works on the page. That is a game changer. You no longer need to record videos of your demos or get people onto the waitlist. Just show them. 

https://lnkd.in/e8disuhJ by Erik Willemse - very cool for getting a bit of perspective in life, in case you ever asked yourself the question I've been asking myself a pretty decent chunk of my time on earth, which is, "Would my life be any different if I was born elsewhere?" 

https://lnkd.in/ezm3xJ88 Michael Tippett - Most people come to me, and when I ask them why they haven't used Lovable, they tell me they don't know what to build. I think this is one of the best apps to solve for the "cold start problem" that I've seen recently. 

Keep shipping, keep sharing, and I'll keep giving you the spotlight. 

Happy Friday!

Tomorrow, to end the lesson portion of 28 Days of Lovable - I have another surprise guest to announce! 

She's a Lovable Ambassador, a wearer of all hats one could put on their head and the best person I could think of explaining what I believe vibe coding is really about - problem/constraint solving! 

Stay tuned for an amazing 15 minute session from Marija Milosevic! I was on the edge of my seat for this one, and am convinced you'll be as well 🙂 

(and you'll hear a few amazing few quotes too)

Everyone talks about how AI makes you faster.
That’s true.
But something else happened that I didn’t expect.

It made me more exposed.

When you can ship in days instead of months, there’s nowhere to hide.

If the idea is weak, it shows immediately.
If your taste is average, it shows immediately.
If you don’t understand the user, it shows immediately.

Before, you could blame timelines.
Or dependencies.
Or engineering bandwidth.
Now the bottleneck is you.

AI removes friction.
And friction used to hide mediocrity.

That part is uncomfortable.
But it’s also the opportunity.
Just depends on where you stand. 

We're all producing faster. The question is what - magic, or garbage.

Most projects don't die because the idea is bad. 
They die because the structure collapses.

On Day 22 of 28 Days of Lovable, we are discussing the uncomfortable truth: sometimes a project isn't worth fixing. 

When fixes start breaking other fixes, you are no longer progressing. 
You are fighting entropy. 
And entropy always wins.

Starting over is not quitting. 
It is optimizing for leverage.

If you find yourself re-explaining the entire system to the AI just to make one change, you are past the point of efficient repair. 

The professional move is to extract what worked, identify what caused the breakdown, and move the good components into a fresh build.

You do not owe a project completion.
You owe yourself systems that can evolve.

Watch the full lesson on structural failure and how to restart intentionally in this video

For a long time, building something felt like training for a marathon.

You would prepare for weeks.
Write specs.
Align stakeholders.
Wait for engineering bandwidth.

By the time something shipped, so much time had passed that it almost felt detached from the original idea.
Now it feels more like going to the gym.
You have an idea in the morning.
By the evening, there’s a working prototype.
And that changes something fundamental.

When building is slow, you can hide inside planning.
You can say, “We’re still refining the strategy.”
You can live in Notion and feel productive.

When building is fast, that shield disappears.
If the idea is weak, you find out quickly.
If users don’t care, you know within days.
If the execution is sloppy, it’s visible immediately.

AI didn’t just make me faster.
It removed the space where I used to overthink instead of finish.

And finishing and shipping something real, however imperfect - is becoming the actual edge.
Not intelligence.
 Not credentials.
Just the discipline to turn thoughts into things.

Don't watch this video at all! 

Day 21 is about building, and this post is for my own consistency purposes - your only purpose for the day should be to create! 

And then visit https://lnkd.in/esnAfSXh to submit what you created as I plan to share it tomorrow. Stop reading! Go ship!

Finally on Android!! 

Shane Spencer let's get to 1M faaaast 😎 Bobby Siegfried can't be the only one!

I was literally thinking this morning - if we're all solving for software, how will the hardware keep up? 

Perhaps this is the answer!?

This result is just mind-numbing. When you can generate 1M toks/min (which corresponds to say 3-4k pages of a book, or a pretty large codebase) - what new AI applications become possible? :)

Ljubisa Bajic a fellow Serbian and former co-founder of Tenstorrent, is building a new AI ASIC at Talaas.

When we spoke last February, he told me this was exactly the direction he was heading in - and now a year later, he’s shipped it.

The ultimate chip specialization: burn the weights of the transformer directly into the chip. Why even deal with software (at least at that level of the abstraction)?

When you're providing the intelligence infrastracture at planetary scale (and given how much the LLM architecture has converged)  this can be a very viable economic model. You tape out a chip that can support 3-6 months of inference - and then you ditch it after that.

Keep in mind that these numbers are for an 8B heavily quantized model (so the quality is somewhat lower) - but then again this is just an "MVP". :) We'll soon be able to do this at a much larger scale.

Check out their blog post here: https://lnkd.in/gEXdXBKs

You can apply to try it out.

Most challenges reward outcomes. This one rewards process.

Today is Day 28 of 28 Days of Lovable, and we are closing the program by opening the 7 Day Buildathon.

Starting now, you have one full week to build and ship a project using Lovable. 

But I am not looking for the prettiest UI or the biggest scope. 
I am looking for clarity of thinking and constraint awareness.

I am judging five specific pillars of execution:

1. Deliberate Starting Point
Show why you chose your entry point. 
Did it come from a real problem, a remix, or a template? 
Day 1 through Day 5 were all about this.

2. Intentional Documentation
You must demonstrate context preservation. 
I want to see your Forward docs (what you planned) and your Backward docs (what you actually built and the decisions you made along the way).

3. Agent-Oriented Execution
Show how you designed for execution, not just prompting. 
This means structured task breakdowns and phased builds with verification steps.

4. Systems Over Memory
Demonstrate how you avoided relying on one-off prompts. 
Show the system you used to keep the project aligned as it grew in complexity.

5. Reflection
This is critical for builder maturity. 
What broke? What limitation did you hit? How did you work around it? 

A month ago, you might have hesitated to start or feared breaking things. 
If you have done the work, you are not that person anymore. 
You have practiced the loop: identify a problem, design a system, execute cheaply, review honestly, and decide deliberately.

That loop is yours now. 
It does not depend on any single tool. 
The thinking transfers.

Submissions close next Friday. Winners will be announced next Saturday.

Catch Day 28 and get the full Buildathon briefing at february.lovable.app

P.S. I am proud of you. And proud of myself for showing up every morning in February. It's now the best month of the year for me ❤️

I see through the bullshit.
I see your greatness.
I see you.

Operating at the intersection of strategy and execution, I stand as a Fractional COO and OBM Agency Owner with a fervor for driving organizational excellence.

My clients often regard me as their 'silver bullet' – an unwavering ally with the depth of expertise they can lean on. Heralded as the 'gold standard' in the business, I've consistently turned challenges into opportunities, bringing both startups and established enterprises to unparalleled heights. 

Backed by a powerhouse team of tech maestros and visionary designers, I guarantee a cohesive journey for our clients. With a dedicated lead project manager and my hands-on COO oversight, we transition you from the granular day-to-day, positioning you at the helm of your venture. 

Ready to amplify your business story? Let's chart a path to excellence together.

Katie Kirsopp

You built this from nothing.
You know every client. Every process. Every password.
You jump in and save things before they break.

It worked. That's the problem.

Because now your team can't move without you.
Decisions sit in Slack waiting for your input.
Nothing gets signed off, started, or finished without a nod from you.

That's not leadership. That's a business held together by one person.

And that person is exhausted.

Here's what founders miss:

The skills that got you to $1M are the exact ones keeping you from $3M.

You don't need to work harder.
You need someone to come in, see it clearly, and build the structure that runs without you in the middle of everything.

Quick test:
How many decisions landed on your desk this week that shouldn't have?

That number is your bottleneck score.
Ask three people on your team what the top priorities are this month.

If you get three different answers, you don't have a team problem.
You have a clarity problem.

And clarity starts at the top.

Scaling & Systems Strategist | Fractional COO | Team Efficiency Consultant | Founder of KatieKirsopp.com | Your Part-Time PA & VA Agency

Not failing.

Not chaotic.

Just… messy.

The kind of messy where:

Projects are technically moving… but nobody fully owns them.
Your team asks good questions… but they still need your answer before they move.
Your Slack looks active all day… but half the conversations end with:
“Just checking with you first.”

From the outside, everything looks like it’s working.
Revenue is coming in.
Clients are happy.
The team is busy.

But behind the scenes, you can feel the strain.
Because every decision still loops back to you.

You approve the client's reply.
You confirm the refund.
You clarify the priority.
You fix the deliverable that “was almost right.”

Not because your team isn’t capable.
Because the structure never gave them the authority to move without you.
So slowly, without realising it, you become the glue holding everything together.

And glue works…
Until the business grows.
Because the bigger the business gets, the heavier that glue becomes.

What most founders assume at this point is:
“We just need more people.”

But after working inside scaling businesses for over a decade, I can tell you this:

The problem is rarely headcount.
Its structure.
When ownership is unclear…
When authority is undefined…
When communication relies on proximity to the founder…
Everything escalates upward.
And eventually the founder becomes the system.

Structure fixes that.
Not more hustle.
Not more hires.

Just a business that can finally move without waiting for you.

From inside it.

Here's the gap nobody talks about:

Your business coach tells you how to grow.
Nobody tells you how to handle what happens when you do.

The team that can't hold the volume.
The backend that was never built to scale.
The founder who's still the single point of everything.

That's not a strategy problem.
That's an operations problem.

And it needs someone who's seen it before, knows what to move, and can move it fast.

No three-month ramp up.
No cookie cutter playbook.
No advice from the sidelines.

Just someone who gets in, sees it, and fixes it.

That's what a fractional COO actually does.

And most founders don't know they need one until they're already drowning.

Ready to hear more - listen here 
https://lnkd.in/g8B9VJPa

Not because they’re not capable.

Because you’ve never fully built the structure that lets them be.

So you stay in the middle of everything.
Not because you want to.

Because every time you’ve tried to step back something fell through.
A client wasn’t handled right.
A decision got made that shouldn’t have been.

Something landed back on your desk that was supposed to be someone else’s.
And so you tighten your grip again.

This isn’t a people problem.
It’s not even really a trust problem.
It’s a clarity problem.

Your team can’t be confident if they don’t know exactly what’s theirs.

They can’t make good decisions without a framework that tells them how.
They can’t hold the standard if the standard only lives in your head.

The CEOs who scale past 7 figures without burning out don’t have better people.
They have better infrastructure.

They’ve built the decision making frameworks.

The clear accountability.
The team culture where people know what winning looks like without asking.

That’s not luck.
That’s architecture.
And it’s exactly what I build.
If you’re sitting at 7 figures and still not confident your team can hold it without you — that’s not a ceiling.

It’s a gap.

And gaps are fixable.

Have a listen here to the free telegram group  with weekly operational tips 


https://t.me/kkirsopp

No alternative text description for this image

From the outside, the business looked great.

Revenue was growing.
She had a team.
The offers were working.

But behind the scenes?
Every decision still landed on her desk.

Team members waited for reassurance.
Small problems escalated unnecessarily.
Projects slowed whenever she stepped away.

Not because the team wasn’t capable.
Because the structure hadn’t evolved as the business grew.
So she became the glue holding everything together.

And the thing about being the glue is… it feels important for a while.
Until you realise the entire business depends on you being constantly available.

That’s the moment many founders reach out.
Not because the business is failing.
But because it’s working in a way that’s unsustainable.

Over the past decade, I’ve helped founders redesign how their businesses actually run so execution stops relying on them.

- Clear ownership.
- Clear decision pathways.
- Clean communication.

So the founder stops being the operational centre of everything.

That work is exactly why I created the Vision → Execution Intensive.

It’s a focused 3-month partnership where we redesign the operational structure of your business so the team can execute without everything routing back to you.

If you’re at the stage where the business works… but feels heavier than it should…

You can read more here: https://lnkd.in/gXtdJGpC

Things I see within days of entering a business:

→ A project management tool that’s basically a graveyard of good intentions

→ A team asking the same questions on repeat because no one documented the answer

→ A founder who’s the only one who knows how anything actually works

→ SOPs that exist but nobody uses

→ Meetings that could’ve been a Loom

→ A VA doing the job of three people because the roles were never defined

→ Revenue growing. Structure not.

None of this is failure.

It’s just what happens when you build fast without building smart.


It’s all fixable. Usually faster than you think.

Tasks with no owners.
Projects with no deadlines.
Meetings where everyone waits to hear what the founder thinks.

Your team doesn't want flexibility.
They want to know what winning looks like.

That's not a hiring fix.
That's an operations fix.

And it's faster to solve than you think.

Your business was built to survive.

And it worked.

But the structure you built at $300K is quietly breaking you at $800K.

The systems that held when it was just you and two people don't hold at ten.
The decisions you made fast because you had to are now decisions your team is waiting on because no one else can make them.
The processes that lived in your head  now live nowhere.

This isn't failure. This is what scaling actually feels like from the inside.

Here's what founders miss:

You're not building for where you are.
You need to build for where you're going.

That means looking at your business twelve months ahead.
Reverse engineering the structure, the team clarity, the systems to match the version of the business that doesn't exist yet.

Most founders don't do this because they don't have time.
They're too busy running the business, they have to build the one they want.

That's exactly where I come in.

Quick test:
If your business doubled tomorrow... what breaks first?

This is what I’m seeing constantly right now:
Founders who have hired well
Built the team
Filled the roles
And are still the ones holding everything together.

Not because the people are wrong.
Because the roles are.

Someone built for execution is being asked to lead
Someone who thrives with direction is being asked to create
And quietly, everything starts to strain.

The real question isn’t:
“Is this person good enough?”

It’s:
“Is this person set up to be brilliant in this role?”

That’s the shift most businesses haven’t made yet.
And it’s why the founder stays the fallback for everything.

Fix the structure, and the pressure lifts.
Not just from the team, but from you.

If this is what your business feels like right now, you’ll recognise it.
No pitch. Just a conversation.

taplio

The Battle

Lazar Jovanovic

Katie Kirsopp

Followers

Posts

Engagements

Likes

Performance ScoreLazar Jovanovic's LinkedIn Performance

Performance ScoreKatie Kirsopp's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Lazar Jovanovic

Katie Kirsopp

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Lazar Jovanovic's LinkedIn Performance

Performance ScoreKatie Kirsopp's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreLazar Jovanovic's LinkedIn Performance