Hi there, well :) not much to add here, my Q is what I'm sharing in the title. Maybe just to add a bit of context, I'd like to have smth I won't pay for here :)
I've been building my SaaS for the last 3 months. Biggest thing I've ever worked on. Lost about 4kg, barely slept, basically lived inside this thing.
The whole time I was building, I was confident. Then QA week started and something flipped. Now I keep thinking, what if nobody signs up? What if I launch and it's just silence?
I don't know why the doubt showed up now of all times, right at the end.
Anyone else go through this before their first real launch? Did it pass once you shipped, or is this just part of it?
It feels great seeing high signup numbers every week, but watching 60% of a specific user segment churn after month one is demoralizing.
We realized these users were signing up with expectations our tool was never built to solve. They churn not because the product is bad, but because they were the wrong audience from day one and their feedback was polluting our roadmap.
How do you implement qualification gates or repositioning early in the funnel without turning away good prospects?
When customers ask for features, our instinct is to build them to keep everyone happy. But over time, our core product started feeling cluttered and overwhelming for new paid signups.
The hard truth is that every new toggle or tab adds cognitive load. Users aren't canceling because we lack features; they're churning because the tool started feeling like work instead of solution.
For founders who have pruned their product. how do you balance power user feature requests against keeping the core experience clean and friction-free?
In the vast innovation landscape, some remarkable creations might hide in the shadows, waiting to be discovered. It's time to break the silence and spotlight these hidden gems. Your expertise is the key to unveiling the potential that often goes unnoticed. Have you stumbled upon a groundbreaking product that deserves recognition? Whether it's a sleek app, a revolutionary gadget, or an ingenious solution, we want to hear about it! Your suggestions can make a difference, so drop your recommendations below, and let's amplify the voices of those remarkable products waiting to be celebrated. Let's make Product Hunt the ultimate showcase of innovation!
We won t pretend that the world isn t tense, because relations between countries are increasingly strained. (Coming from a country that never had technological or numerical superiority, we ve mostly become just part of the regime.)
But not everyone is on the same page, and countries are investing in defence.
One thing I'm learning while building a product is that getting it built is only half the work. Finding the right people who actually need it is a completely different challenge.
I'm trying to understand how early-stage makers approach distribution without spending all their time posting everywhere or chasing vanity metrics.
I've been thinking about a few approaches, like sharing useful content, joining relevant communities, and talking directly to potential users.
What are some of the best GTM strategies for an open-source developer-facing efficiency tool?
I am working my open-source, local-first tool for developers that turns day-to-day engineering activity into useful project updates, without timers or manual busywork.
My current GTM plan is fairly founder-led:
Start with Product Hunt and developer communities where people already discuss productivity, worklogs, AI coding agents, Jira, Linear, GitHub Issues, and engineering visibility.
I created /services/ai-copilot-development on 5 July. Google crawled it for the first time on 31 August. Fifty seven days.
Nothing was wrong with it. It returns 200 with a title tag. It sits in sitemap-0.xml. robots.txt allows everything except /studio, /api and /preview-mode. It is linked from the site navbar, the footer and eight sibling service pages, so ten files point at it.
