My launch went out unfeatured and got 0 upvotes. What should I check before the next one?
I'm a solo developer. In August I launched a small side project here, and it was never featured, so it couldn't rank at all. It finished with 0 upvotes and 1 comment. My earlier launch, a job-search tool, got only a few upvotes back in July.
Looking back, I think I made two mistakes. I launched without checking whether it would be featured, and I didn't spend any time in the community beforehand. Since then I've been active here daily for about three months.
For makers whose launches were featured: what did you change in your listing (tagline, gallery, first comment, topics) that you think made the difference? I'm especially curious whether anything specific helps a niche or experimental product get featured.
When does adding more features start hurting your product instead of improving it?
We kept listening to customer feedback and adding features to make our product more useful. Every request seemed reasonable and shipping new functionality felt like progress. But over time the product became harder to navigate. New users struggled to understand where to start while existing users only relied on a small portion of what we had built. It made us question whether we were solving more problems or simply making the product more complicated.
For founders building SaaS products how do you decide which feature requests deserve attention and when is saying no better for the product?
From $0 to $5k after a year Indie Hacking. The biggest takeaways.
At what stage did manual founder-led support start slowing down your actual product development?
Answering every support ticket directly as a founder gave us incredible insights into real user bugs and UX confusions early on. but now that active accounts are growing, spending three to four hours a day answering repetitive onboarding questions is completely pulling focus away from core development.
for small teams, how did you transition from answering every query manually to building scalable self-serve help centers without losing that personal human touch?
I Tracked Every "Quick Question" for a Month. 74% Took Over 10 Minutes.
I started timing every interruption I labeled a "quick question." Slack messages, DMs, taps on the shoulder.
The average was 11 minutes. The longest was 40. Most of them required context I had to rebuild from scratch because I had been in the middle of something else.
I took 14 freelance projects in one year. Tax season showed I'd worked twice as hard for less money.
Every project felt like an opportunity small ones underpriced ones ones outside my expertise. My calendar was full and I felt important. Then the numbers came in. I started declining anything below a rate I set in advance. Income went up hours went down.
The opportunities weren't bad. I was using busyness to avoid the scary work of pricing myself properly.
For those who've started saying no: was it the requests' fault or your inability to prioritize? And what are you doing right now that you'd drop immediately if you were honest about its value?
Why do coding agents always try to be over helpful instead of just doing exact task you assigned?
You ask for a quick script addition, and suddenly background logic, helper functions and folder structures are completely rearranged without permission.
It feels less like a coding assistant and more like a coworker who won't stop uninvited cleanups.
How do you lock down your agent workflows so they only touch what you explicitly point to?
how much of your product roadmap do you share publicly before actually shipping?
sharing weekly progress and feature roadmaps on public forums creates incredible community excitement and gives us early validation before writing complex code. however, last month a larger competitor built a toned down version of a feature we teased publicly weeks before our own release was ready for beta testing.
how do you balance the momentum of building in public with protecting unique feature concepts until they are fully polished?
I Asked the Agent to Plan Before It Coded and Saved Three Days
I used to describe a feature and let the agent build immediately. It felt fast. It wasn't. The architecture got decided implicitly by whatever the agent tried first.
When that first approach was wrong, everything built on top of it was wrong too.