Am I wrong to think this won't work? Guided vibe coding for non-technical founders

I've been building software since 2018. Scaled our last AI product to 15K+ users, built a complex OCR/AI document extraction SaaS for Moroccan accountants, created an order processing system for a service business, built a nutrition mobile app. I've used code, no-code, low-code - all of it. Led teams, managed backlogs and roadmaps, handled the full product lifecycle.

Lately I'm seeing a pattern: Non-technical founders trying to vibe code their way into an MVP, making mistakes they don't even realize are mistakes. They're stuck in loops asking Claude/Cursor to "fix this", and every time "the issue is fixed" - it still doesn't run.

Arbitrary tech stack choices.
Random folder structures.
Zero notion of security.
Git? what even is git.
Tests? what's that.

I'm not the gatekeeper type - I'm all for people trying things out. They just need a little push in the right direction. It seems they're just oblivious to some things..

So I'm considering offering something like guided implementation:

• 1-2 weekly calls where I review what they're building
• Architecture/stack guidance (is this the right approach for your use case?)
• Help them leverage AI tools properly (how to ask for what you actually need, the jargon to use)
• Basic development knowledge to 10x your efficiency
• Async support when they're stuck
• Code reviews when necessary

But maybe I'm wrong?

Maybe people want to do it themselves, maybe it's "fun" to go through those stages. Maybe adding guidance defeats the whole point of vibe coding. Maybe it's not actually a problem worth solving.

For people who've tried building with AI coding tools - would technical guidance have helped? What have you tried when you got stuck?

What am I missing here?