Non-technical founder here, built my whole product with Claude Code. Everyone in this forum keeps saying the same thing UI and analytics get the "looks fine, ship it" treatment, but billing and auth get the paranoid line-by-line review. I've lived that.
Here's the twist though: my product IS the billing edge case. It's a tool that recovers failed subscription payments, so the entire thing lives in the messy world of declined cards expired cards, insufficient funds, bank 3-D Secure/SCA challenges that all look similar in the data but need completely different handling. Vibe-coding something where a wrong branch means someone gets emailed "your card was declined" when it actually went through was genuinely terrifying. I couldn't just trust the vibes.
One benefit I see is that it will usually produces something very politically correct that will usually go through the endless censorship that has taken over the internet (personally on the web since beginning of the 90's it was something else entirely, a mix of academic papers & free flowing ideas on clumsy graphics all over the place - oh boy that was so much decentralized and fun).
But then I only see problems: flatness, falseness, shallowness, lack of originality, creativity and most of all the dependency it slowly develops.
We've been listening to your feedback and shipping. Here's what's new:
MCP support Connect Kalendar to Founding.dev, Claude, or Cursor and manage your calendar from chat. Ask your AI agent to look up your clients and bookings, or to create, reschedule, and cancel meetings for you. Just create an API key in your settings and you're connected.