On Product Hunt, I can see many people launching their products using "vibe-coding tools" like @Lovable , @bolt.new , or@Replit

I reckon many people who created something with them are usually developers who didn't have enough time for building a side idea before, but with AI, they could make it happen.

I keep going back and forth on this. Write out a tight spec first (user story, edge cases, acceptance criteria) and the AI output gets a lot more predictable, but it also kills a chunk of the speed that made vibe coding appealing in the first place. Skip the spec and just describe the vibe, and I end up rewriting prompts three or four times to fix things a spec would've caught upfront. Where do people here actually land? Full spec, loose bullet points, or just winging it and iterating in the chat?

Last summer, the idea for my SaaS, Xolora, started to take shape. Around the same time, the concept of vibe coding was blowing up. As a non-technical founder, it sounded like a dream come true. No coding experience? No problem, just let AI handle it.

The beginning was incredibly promising. Using Emergent made me feel unstoppable. I was seeing my idea come to life.

Vibe coding a personal project that works on your laptop is one thing.
Building a tool your team opens every morning to manage projects, serve customers, and run the business is another.
Suddenly there s shared data.
Different people need different levels of access.
Your teammates need to understand how the app works so they can change it too.
And the app needs to keep evolving without turning into a black box nobody wants to touch.
At that point, would you be comfortable letting AI change anything it wants?
We ve been thinking about this a lot while building WeWeb MCP (launching on PH tomorrow!)
Agents like Claude, ChatGPT, Cursor, and Gemini can now build apps directly inside WeWeb.
Across the frontend & backend from: UI, data, workflows, integrations, permissions, and more.
But the important part for us was making sure the builder stays in control of both the app and the AI building it.
That s why we built guardrails into the way AI works inside WeWeb:

• Before AI builds: choose what AI can and can t touch: pages, components, workflows, tables, APIs, and more.

• After AI builds: see exactly what changed in the visual editor. Tweak it yourself, keep iterating with AI, and publish when you re ready.

So AI gets room to move fast, without getting free rein over the whole app.
I m curious how you think about this: Would you give an AI agent access to everything?
Or are there parts of your app you d always want to lock down?

Hey everyone,

I've built my product around traditional SaaS pricing (monthly tiers), but I m starting to wonder if that model is getting outdated, especially with more AI-powered and compute-heavy tools entering the market.
That shift requires real architectural changes, instrumentation, metering, billing logic, and UI changes, not just pricing tweaks. It s something I m starting to seriously think about for my own product.

In particular, AI usage has real COGs (every prompt costs money), and I m seeing more platforms experimenting with usage-based models, or hybrids like SaaS base + usage + overage.

For those of you building AI or compute-intensive tools:

Building used to be the bottleneck. Now I can get a working app faster than I can write a good landing page copy for it. So the "idea guy with no code skills" excuse is basically gone.

But almost none of my vibe-coded weekend projects have real users, and I don't think that's a coding problem anymore.

For those of you actually getting traction - what's eating your time now that building isn't the bottleneck?

Daily reality: Claude Code in one pane, Codex in another, Cursor in a third, plus a few shells. An agent stops and waits for "yes". By the time I find the right pane, 20 min gone.

Just me? What's your setup notifications, layout tricks, or you've accepted the tax?

It doesn't even have to be a big dramatic failures, more the small moments where something clicked and you went from trusting the output by default to double checking everything. For me it was watching an agent confidently rename a function across twelve files, then leave the original function untouched in a thirteenth file it apparently didn't search, with zero indication anything had been missed. It wasn't even a hard case, the file just wasn't in the directory it happened to grep first.
What was your moment? And did it actually change your workflow afterward, or did the trust creep back in after a week like it always seems to for me?

AI dev tools are evolving crazy fast , every few weeks there s a new must-try for vibe coders.

Some people are building full products with @ChatGPT by OpenAI and @Replit , others swear by @Cursor and @Claude by Anthropic , and a few are mixing @Lovable + @v0 by Vercel + @bolt.new to ship apps in record time.

I ve been refining my own vibe stack lately, trying to find that sweet spot between speed, control, and creativity.
It made me wonder ,what does your setup look like right now?

I still design in Adobe first. It's in my fingers, like being used to writing notes with a pen and then having to do everything on a computer.

After that I bring it to life with AI, which opens up a lot I couldn't do on my own before. But I don't want to skip the first part. That's where I actually think.