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.
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.
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:
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 spent most of my career doing non-technical work, and I now build our product, @HeyNews. I got there by talking to AI coding agents night after night. The catch: the agents are good company right up until 4am, when you're still hitting approve every thirty seconds and what you actually want is sleep.
So I built a loop I can walk away from and wrote up exactly how it works: https://blog.heynews.co/afk-codi...
Last year we hired a design agency to build our marketing site for @Basedash. They did an incredible job. The headline makes it sound like I'm dunking on them, but I'm not. The site was genuinely great. They built it in Framer so we could manage content ourselves, which was a completely reasonable bet at the time (and something we explicitly asked for).
disclaimer: I'm not an engineer. i do growth and marketing.
when people talk about vibe coding they usually mean shipping a product. an app, a saas, a tool with real users. that's the version that gets posted. but it's not where things actually changed for me.
AI coding tools seem to come in two main flavors: IDE-based, like @Cursor and @GitHub Copilot, and terminal-based setups, like using @Claude Code to generate commands, scripts, or entire files. Both have their fans, but which one actually helps you move faster?
Curious what flow people are sticking with long term, and where you see the most gains (or frustrations).
I might be missing some but I've been pretty much in love with @Lovable, @Cursor, @bolt.new and have been trying to use @Replit more and I honestly haven't touched @BASE44 too much but have heard good things. @chrismessina has nudged me to use @Windsurf for whenever I build another Raycast Extension! Currently I use: - @bolt.new / @Lovable - @Cursor - @Warp Curious what everyone thinks is the top one so far!
