Anyone else keep working on something just because you started it?
When I started I thought consistency meant never giving up. If something wasn t working my first instinct was always to try harder and give it more time. But sometimes more effort doesn t really change the outcome. It just makes it harder to admit that the idea direction or approach might need to change. How do you know when to keep pushing and when to let something go?
Should you ship a buggy MVP early, or wait until the product feels completely polished?
hen we built our first app, we followed the classic startup advice to ship fast and fix things later. We launched a very raw version, but initial users were turned off by minor bugs and UI glitches, and most of them never gave us a second chance.
For our second tool, we spent two extra months polishing the core UX and fixing edge cases before letting anyone in. The launch was smaller, but first-time user activation and positive reviews were night and day compared to the first attempt.
Is the ship an embarrassing MVP advice outdated now that users expect high-quality software from day one?
How do you know when an AI agent is ready for production?
One question I've been thinking about is when an AI agent is actually "ready" for production.
Traditional software often has clear testing processes, but AI agents introduce a different level of uncertainty. They rely on reasoning, external tools, changing context, and non-deterministic outputs, making it difficult to define a clear launch criterion.
Launching multiple products on the same day: Is it a smart strategy or launch suicide on PH?
Hey Product Hunt community!
As a serial maker managing a pipeline of micro-SaaS products, I ve been analyzing launch strategies closely.
Building a good product takes immense effort from validation and architecture to design and copy. But like many builders here, I've noticed a frustrating pattern on PH sometimes:
>>Highly polished, solve-a-real-problem products end up stuck at the bottom of the daily page, while seemingly simpler tools push to the Top 3.
We tracked every refund reason for 6 months.
We processed 214 refunds between January and June. Instead of just approving them, we tagged each one with a reason from a fixed list of 12 categories. Here is what came back:
"Too expensive for what it does" 61 (28.5%)
"Didn't work as expected" 44 (20.6%)
"Forgot I subscribed" 33 (15.4%)
"Found a free alternative" 27 (12.6%)
"Team member left / role changed" 18 (8.4%)
"Billing error / double charge" 14 (6.5%)
Everything else 17 (7.9%)
The "forgot I subscribed" number was the one that changed how we operate. 33 people paid us and didn't remember. We added a pre-renewal email 7 days out with a one-click cancel link. Refunds in that category dropped to 4 in the following 6 months. The others stayed roughly flat.
The "too expensive" category was almost entirely users who had been on the plan for less than 14 days. That told us the problem was expectation-setting on the pricing page, not the price itself.
Anyone else change what matters most after a few years?
When I started I thought growth would be the main thing to focus on. More users more revenue more momentum.
But over time other things started feeling just as important. Keeping good customers protecting my time avoiding unnecessary complexit and not chasing every opportunity. How do you know when your priorities are evolving for the better?
How do you dig past price complaints to find the real cause of churn?
We were getting ready to lower our monthly plans because too expensive was our top churn reason on paper. But once we jumped on calls with churned users, we realized they were paying double for alternative tools that saved them time every single day.
Our app wasn't too costly we just failed to make it an essential part of their workflow.
If you ve dealt with this what specific questions do you ask during churn interviews to uncover true value issues?
How do you balance team collaboration when core hours drain your remote devs?
I thought establishing a strict two-hour daily overlap was the fair way to keep our global team aligned.
But I recently realized one of our team members was silently burning out just to make those mandatory sync calls fit their local time.
Spreadsheet schedules look great until you factor in real life sleep cycles.
We started testing rotating core windows to share the burden but it still feels like a compromise.
Does everything that annoys you eventually turn into "there should be an app for this"?
There s the cheesy line "with great power comes great responsibility," and I can t quite shake when I think about how many products I mentally sketch in a week. How how i can use AI to build product around it given enough time.
A running list of those I've actually sat with:
- A shared calendar that doesn't force everyone to already be on the same app
- A cab-booking flow that doesn t mean checking three apps to find the cheap one that s actually nearby
- Something that makes AI actually useful for how my kids learn, not just another screen they're on
- A means to divide group expenses and track personal finances better
- Something that tracks all the warranties and receipts so I don t lose them a year later
I know most of these exist in some form already. That knowledge has never once stopped the itch I still design my own version in my head, anyway. What really prevents these from going anywhere is bandwidth. I can only build one thing at a time, and the rest just sit in a notes app, quietly piling up.
Are you always creating new problems and thinking about building products for them too?
And when you do, is it the does this already exist question that kills the idea?
Or running out of hands stops you from building it?
Where did your first few paying users actually come from?
Everyone always says to build a massive audience before launching but most of that launch traffic just turns into free advice and zero sales.
My first paid signups came from digging through reddit comments and jumping into slack groups where people were already complaining about the issue.
Did your first actual customers come from your launch day push or was it just unscalable 1-on-1 outreach?