Hey everyone, been a Product Hunt visitor for years but never signed up, so I thought I'd start by sharing some recent learnings that hopefully other builders will find useful.
For context, we're building FanBase Copilot, an AI assistant for content creators that learns their voice and context over time. The memory layer is critical. It's what makes the AI actually useful after the first conversation.
Had a fascinating discovery call yesterday. Founder showed me their SaaS - built entirely with Cursor in one weekend. Stripe payments, auth, admin panel. Actually works great, they're at $11k MRR.
Two days ago I saw this thread about how we are having more launches in post-GPT era. And a question was born in my head: what quantity is optimal now? Of course, you can often see a trend among builders on X, where they launch a project per month, then roughly 4 months later 1 project takes off and we don't see new projects for the next 6 months because the person is busy scaling (and that's ok, testing a hypothesis shouldn't take much time) But still, what pace should be considered right? 12 in 12 months slow in modern reality. Launch a product in a day? Unrealistic (SEO, ads, app approvals, various settings and optimizations). Theeeeen...48 products a year? Or should we look at this from another angle, where LLMs allow us to create 12 products in 12 months with more features and better quality? What's the community's opinion?
This was a deliberate experiment inspired by my CTO. I wanted to test a simple question: Can a Product Manager ship a real website end-to-end today without handoffs?
Our team pushes code constantly - multiple deploys per hour some days. The problem? Nobody can keep up with what's changing. You check the repo in the morning, grab coffee, come back and suddenly there are 47 new commits.
Good luck understanding what actually matters or how it affects your work. We built Doculearn to solve this with automated flashcards. Here's how it works:
Building my app with AI tools, zero coding background. The magic part - I can ship features in hours. The scary part - I have no idea if the code is actually good.
Step 150 of debugging why a payment does not get saved to a database. Two days on this one bug. And there are plenty more. If you can build somehing that will do the back-and-forth, the "now try this and tell if it... no? Okay, le's do this thn, and this, and that..." Do what Claude Opus 4.5 is tellling me to do, the tens of hours, to get to the solution. Automate that and you have a winer - becuase there are 100K full-stack devs who will do all this more effienctly themselves, yes. but there are 10M non-developers who love what they built, but are getting killed in the debugging, the last 5%.
