Connect with the Product Hunt community

I have a bad habit and I am pretty sure a lot of you can relate to this. I am absolutely terrible at launching stuff.

Every time I get close to shipping an MVP my brain starts making excuses. I tell myself it needs push notifications first or the onboarding flow feels a bit clunky or maybe I should just add dark mode before sharing it with anyone.

Before I even realize it two weeks turn into two months. The initial excitement for the project dies down and the code just sits on my hard drive untouched.

Logically I know an MVP is supposed to be basic and simple. But the developer side of me panics at the thought of putting out something that is not completely polished.

I've been putting off a price increase because I keep telling myself I need more data first. "I should wait until I know my churn rate." "I should wait until I have a cohort that's been on the product for six months."

But the waiting has now lasted longer than I'd like to admit. I'm worried I'm using "need more data" as a cover for just being scared to ask for more money.
For those who've navigated this: did you raise prices early and adjust later, or wait until you felt you had solid retention numbers? And if you raised early, what actually happened?

The common thread in all of these is that they're specific, grounded in a real experience, and end with a question that gives people something concrete to react to. A stated frustration or gap works better than a broad "what do you think?" because it gives people a clear edge to grab onto

Our interactive 10-step product tour had high completion rates, but 30-day retention remained weak. Once we stripped the tour down to just one core setup action, retention jumped.
Showing off everything upfront just overwhelmed users before they got actual value.

Did simplifying your onboarding boost retention or increase confusion?

We offered full access for 14 days, thinking it was the best way to prove value. But conversions stayed flat until we swapped the time limit for feature gates. The open trial gave users too much time to wander without hitting their
Aha! moment. Restricting the scope created immediate momentum.

Did limiting trial access help or hurt your paid conversions?

I decided to do an experiment. For 90 days, I logged every hour of work in a spreadsheet. Not just "worked on product" but exactly what I did. Every task, every meeting, every rabbit hole.

Here's the breakdown:

• Product development: 31% (I thought it was way more)

• Admin/email/ops: 24% (this one hurt to see)

• "Research" (reading Twitter, watching YouTube, "staying informed"): 18%

• Actual customer conversations: 9%

• Marketing/distribution: 7%

• Fixing things I broke: 6%

• Staring at the screen feeling overwhelmed: 5%

The number that gutted me was the 18% I spent on "research." I was consuming content about building instead of actually building. I was reading threads like this one instead of talking to users.

I run a small online laptop store in the UK and pretty much do everything myself, from SEO and product pages to fixing random site issues. Over the last year my tool stack has got out of hand, and I'm sure I'm paying for a few things I open once a month.

Trying to cut it down to stuff that genuinely saves me time. What are you paying for that you'd be annoyed to lose? And is there anything you cancelled and never missed?

I keep wondering whether every company is eventually going to need a company-wide AI memory.

Right now, most businesses have knowledge scattered across docs, Slack, calls, CRM notes, shared drives, and (probably most importantly) the heads of a few people who have been there forever.

That was already a problem for onboarding and operations.

I realized recently my bookmark bar is basically a graveyard of articles and tools I thought I d read later. It s reached the point where searching through them takes longer than just Googling the page again.

Really want to avoid adding another subscription service just to organize web links.

What simple habits or native browser tricks are you using to clear out links you don't need anymore?

I'm a solo founder and needed a launch video this month. I couldn't afford a motion designer, so I tried to make it using AI tools.

What worked: it was fast and cheap, and the AI video clips looked better than I expected.

What didn't: the first attempt looked generic. Getting the timing, pacing, and story right took many rounds of feedback. That's the part a good motion designer does naturally.

So I'm wondering how other builders are handling this. Do you still hire a motion designer for launch videos, or has AI become good enough for your team? And if you still hire humans, what's the one thing AI couldn't do for you?

I ve been comparing the workflow of using React Server Components with a more traditional client rendered React setup. Server Components can reduce the amount of JavaScript sent to the browser, but they also change how I think about data fetching and component boundaries. For people building production apps, which approach has fit your workflow better and what tradeoffs have you noticed?

When churn spikes, our instinct is to build the "one missing feature" a customer asked for before leaving. But after shipping three major updates, our 30-day retention rate barely moved.

When we watched user session replays, we realized people weren't leaving because the product lacked power. They were leaving because they got overwhelmed within the first 5 minutes and never reached the "aha" moment.

Is retention almost always an onboarding problem in disguise, or do products genuinely die from lack of features?

I've been active on PH for a few weeks now, mostly commenting on launches and joining discussions.

One thing I didn't expect: the feedback here is more honest than almost anywhere else.

Not because people are harsh. But because makers here have actually shipped things. They know what a real problem looks like vs a solution looking for one.

I've found that reading comments on other people's launches teaches you more about product positioning than most courses do. You see exactly what confuses people, what excites them, and what makes them scroll past.

Early on I confused the two constantly.

I'd present roadmaps and projections like they were facts. Pricing decisions like they were calculated. Hiring timelines like they were guaranteed.

They weren't. They were structured guesses with good formatting.

The shift happened when I started saying "this is our best bet right now, here's why" instead of presenting everything as certain. Decisions got faster. The team trusted the reasoning more because it was honest.

I m curious how developers are handling review now that AI can generate fairly large pull requests. I tend to focus first on the overall architecture, changed files, tests, and possible edge cases rather than reading every line immediately. What does your review process look like before you merge AI generated code?

Generating a new project feels relatively straightforward, but modifying an older codebase with existing conventions is a different challenge. I m curious how well coding agents handle unfamiliar folder structures, shared components, and legacy code. What has your experience been with this?

I used to rely on personal messages on LinkedIn to get early feedback for new features, but over the last few months the reply rate plummeted.

It feels like automated AI sequences ruined cold messaging for everyone who s actually trying to have a real conversation.

I'm trying to figure out where people actually engage without filtering you out as spam.

I ve noticed that I understand things better when I first collect the useful links notes and sources myself before putting them into an AI tool. If I skip that part I sometimes get a quick answer but don t really understand where it came from. How are you handling this? Do you organize the information first and use AI afterward or let AI handle the research and sorting from the beginning?

Transparent updates work really well if your target customer is another founder or creator who hangs out on tech social networks all day. But if you're building software for traditional industries public updates rarely reach the actual decision makers.

At a certain point manual outreach and targeted marketing seem to produce far better results than posting general product updates.

Where do you draw the line between useful public marketing and wasted founder effort?

I gave the open building strategy a honest try for my last project. I posted progress milestones almost every day but while the engagement was decent the conversion to real users was basically zero.

It makes me wonder if people just like watching the journey without ever needing the actual software.

For those who actually got traction this way what specific type of post or update actually made people click through and try the product?

We built a product that solved a real problem but we made one mistake : we expected users to change their daily routines just to use our app. The churn feedback was crystal clear users loved the idea, but opening our app felt like an extra chore rather than a natural part of their workflow.

If your software requires people to break established work habits, even the best paid plans won't save you from cancellation.

Is it easier to reshape a user's daily habits or redesign your product to fit seamlessly into their existing workflow?

Agent drift is so annoying. you approve a clear outline and halfway through it rewrites a file it shouldn't even be looking at or claims a task is finished when it missed half the steps.

I started locking down access and only letting it handle small task pieces one by one instead of broad plans.

Does keeping tasks super small stop the code jumping, or do you still have to babysit every edit?

I keep telling myself i need a few more months of retention stats before changing my plans, but honestly i think i'm just nervous to charge more

.

Every time i look at the numbers i find another excuse to push it back.

I've done this rodeo a few times now, and the pattern is almost comically predictable.

You spend weeks prepping. The day comes. You get a bump in traffic, a handful of signups, maybe a few hundred upvotes if you're lucky. You reply to every comment, you feel like you're finally "seen." Then day 3 hits and the graph flatlines. The notifications stop. The silence is deafening.

I've started to think the launch itself is almost a distraction from the actual problem: what do you do on day 4, 5, 6 when nobody is watching anymore? The launch is a performance. The post-launch is the business.

I've watched people chase the dopamine of another launch, another spike, another "we're live!" thread, instead of sitting in the boring, uncomfortable work of retention. And I've done it myself. It's an addiction. The spike feels like validation. The flatline feels like failure.

I used to think spamming more discussions was the fastest way to get noticed here, but turns out new accounts just get auto flagged or rejected constantly.

Looks like actually commenting on other people's stuff and building some history first makes a huge difference in whether your thread gets approved or not.

Did your post approval rate get better once your account was a few weeks old or are there other factors at play?

Since i built every part of my app myself, i know every tiny flaw in it which makes asking for real money super uncomfortable.

I keep setting cheap $3/mo plans or huge free tiers just because i'm worried people will complain it's not worth it.

For solo devs who started out underpricing everything how did you finally build up the confidence to raise your rates?