Connect with the Product Hunt community

I have seen people with various different approaches of launching their saas. Some do their distribution via paid channels, some via launch directories and some others via their network etc. I always wonder whether any of those launch methods have consistently bring results for everyone even if small.

I understand the paid channel strategy. You just have to be visible to a wider audience and people would pick you accordingly. But, I have tried these directories and they are almost meaningless or I had a bad launch there. I don't currently have any network of people who would be my first users, so I am clueless about this.

I still design in Adobe first. It's in my fingers, like being used to writing notes with a pen and then having to do everything on a computer.

After that I bring it to life with AI, which opens up a lot I couldn't do on my own before. But I don't want to skip the first part. That's where I actually think.

Before launching a SaaS project, I spent a lot of time researching competitors. A few weeks later, product work took over and my notes were already outdated.

I m now trying to understand which changes are genuinely worth tracking. Daily alerts could become noise, while a weekly review might miss something urgent.

For founders who monitor competitors:

• Which changes have affected your pricing, positioning, or roadmap?

• How often do you review them?

• What did you stop tracking because it never helped you make a decision?

Whenever I use coding assistants to flesh out app features the generated screens end up looking mismatched. One page uses a custom table, while the next invents a totally different card wrapper or color shade.

Even when referencing component libraries, the assistant eventually ignores existing UI patterns and builds placeholder elements instead. Going through every route to manually clean up design inconsistencies takes up way too much dev time.

I'm trying to get better at competitor research for SaaS products, but there's one thing I keep struggling with: knowing which updates are actually worth paying attention to.

A competitor might change their pricing, launch a new feature, redesign their website, or announce an integration. It's interesting to see all these changes, but I don't think every update should influence what you build.

My current thinking is that a change matters when it affects how a product is positioned or what customers can do with it. I'm still figuring out how to separate those signals from the noise.

We're getting ready to launch on Product Hunt for the first time. The marketing team is one person, just me ;p

Scrolling through launches from bigger brands is a bit intimidating. They have launch videos, whole marketing teams answering comments all day, and hunters with big followings. We have limited time, resources and a to-do list that doesn't get shorter.

As a solo developer I feel like I am constantly caught between building new stuff and fixing my past mistakes.

When you are trying to launch fast you write quick dirty code just to see if an idea works. But a few months later that same code turns into a headache. Changing a tiny button now breaks two completely unrelated things.

The issue is users always want new features but my codebase is crying for a complete rewrite. If I spend two weeks refactoring I ship zero updates to users. If I keep building new features the whole app will eventually break.

For those running solo projects long term how do you balance refactoring with building new features. Do you set aside specific days for tech debt or just fix things as you go?

I used to look at other founders doing cheap growth hacks and think I'd never run my project like that. Fast forward to today, and I ve cut prices and built messy features I vowed I d never touch, mostly out of fear of slow growth.

Some changes genuinely helped the business, but others just feel like I took the easy way out.

Where do you draw the line between adapting to the market and completely selling out on your core beliefs?

I keep seeing posts about some secret growth hack that supposedly saved a product, but when you look at what they actually did, it's usually pretty basic stuff.

Answering support messages talking to early users writing useful posts instead of pushing generic promos.

sometimes it feels like calling it a "hack" just makes people look for shortcuts instead of doing the boring work consistently.

has anyone actually found a real growth shortcut, or does it usually just come down to doing the basics really well?

Last week I gave Claude Code the task of fixing a broken checkout test in my little Next.js store project. Within 20 minutes, it came back telling me all tests were passing. I was thrilled until I saw the diff. The test file had become 40 lines shorter, and the one test that failed was no longer there.

To be fair, I had asked him to make the tests pass, and he did just that. It was my mistake, but it gave me some valuable insight into how I give instructions. An objective stated as an outcome makes it easy to take the shortest route to achieving it, even if that route is cheating.

I ve started paying more attention to the permissions apps ask for. Some tools want access to contacts location or payment details even when I m not sure they actually need them. I understand that some data helps improve the experience but sharing everything by default doesn t feel right. I d rather use a tool that explains why it needs certain information and lets me choose what to share. What makes you trust a company enough to share your personal data and what information do you never feel comfortable giving away?

I ve ended up with hundreds of saved links that I keep telling myself I ll come back to. Now it s getting harder to find anything useful and I don t really want another paid bookmarking tool just to organize them. Do you have a simple system or any built-in browser features that help you automatically clean up old bookmarks?

Always see people buying .com names and making logos before even building the actual tool.

I used to think you need the whole setup ready to look legit, but buying tech stuff early feels like a waste if the idea flops.

How long do you run on free subdomains or cheap placeholders before dropping money on official branding?

Users of a focused tool naturally ask for the next thing next door and often they already have the data in your product to do it. Saying yes feels like listening. Saying yes ten times is how a sharp tool becomes a bloated one that does everything adequately and nothing well.

The tempting version is when the adjacent feature uses the exact data the user already entered, to answer the very next question they were about to ask elsewhere. That feels less like creep and more like finishing the job. But that is also what every scope-creep decision feels like from the inside.

Vibe coding works because we stop reviewing every step. We describe what we want, the agent gets on with it, and we look at the result. That speed is the whole point, and I don't think anyone wants to go back to approving every command.

But it means the agent is running commands, reading files, installing packages and calling tools with our own permissions, mostly unwatched. When something goes wrong, the transcript doesn't help much: it's a conversation, not a record of what actually happened on the machine.

For a long time that felt fine to me. Then I started recording every action my own agents took, and looked at a few days of it.

What surprised me wasn't any single command. It was the combinations. Reading a file with credentials in it is normal. Calling a cloud API is normal. The same session doing one and then the other, without me asking for either, is the kind of thing I want to at least notice. Some of what got flagged I could explain right away. A few I'm still going through, which is exactly the point: without the record, I wouldn't even know there was something to look at.

First post here. Been browsing Product Hunt for a while without an account and finally made one.

Honest question about my own behavior. I upvote things way more than I try them. Something looks interesting, I hit the arrow, feel like I participated, and move on. I couldn't tell you the last thing I upvoted and then actually signed up for.

It's not that upvoting is bad. It's just that it's become this frictionless thing I do while scrolling, and it has almost nothing to do with whether I'd use the product. Which makes me wonder what the upvote even means to me at this point.

Do you upvote things you'd actually use, or do you upvote to signal "this looks cool" and move on? And has anyone here found a product because of the upvote count specifically, or do you ignore the numbers entirely?

I ve been using AI APIs to build my projects but the monthly bills are starting to add up. Running open-source models on a cloud server seems like a good alternative but GPU costs maintenance and idle time make me wonder if the savings are actually worth it. I don t want to spend hours managing servers just to save a few dollars. For developers who ve made the switch did hosting your own models really reduce costs or were API calls still the better deal?

Post-mortem from last week.

My site is translated into 10 languages. The language switcher and the internal links on every localised page were supposed to keep visitors in their language. For months they did not. Every locale page quietly linked back to the English homepage.

I was testing how LLMs rank products in our space by asking vague buyer questions like "what's the best tool for X." We showed up on Gemini, but ChatGPT kept listing older competitors that haven't updated in years.

It made me realize how inconsistent these AI recommendations are compared to traditional Google SEO.

If you added comparison pages, structured data, or an llms.txt file recently, did you notice any real difference in how models cite you?

First post here. Been browsing Product Hunt for a while without an account and finally made one.

I keep noticing apps adding an AI button to something that didn't need one. A calendar app with "AI scheduling." A to-do list with "AI prioritization." A notes app with "AI summaries." Most of the time I poke at it once, it does something vaguely fine, and then I go back to using the app exactly the way I did before. The button just sits there.

I'm not against AI features. Some of them are genuinely good and I use them. But there's a difference between a tool that was built around it and a tool that stuck a chat box on top because it was trendy. From the listing alone, those two look identical.

Curious if anyone else feels this. What's an AI feature you actually use regularly, versus one you tried once and forgot about? And does a listing mentioning AI make you more likely to try something, or less at this point?

Been doing client work for a while now and it pays the bills fine but my own product keeps getting pushed back.

Client requests always feel way more urgent because someone is waiting on them.

Tried blocking out morning hours and dedicated days but everything breaks when a heavy client work month hits.

I spent last month cranking out a couple of quick apps using AI tools and honestly the easy part was getting the features to work. The painful part was realizing that having a live product means nothing if you don't know how to reach your target audience.

Since the barrier to building is basically gone, distribution feels like the only thing that actually matters anymore.

For anyone who bridged that gap what did your first month of actual outreach look like?

I scrolled through a few pages of p/general sorted by new this week, and most posts seem to fall into a handful of recurring topics:

• marketing and growth,

• pricing and churn,

• building in public,

• solo-founder workflow.

Sometimes the same question comes up two or three times within an hour, just phrased a little differently.

My monthly api bills for proprietary models are getting pretty high as a solo dev. Thinking about switching to hosted llama or mistral on cloud servers but I'm worried about server upkeep and paying for idle GPU time. Not sure if the monthly server bill actually ends up saving anything. For anyone running self-hosted models are you actually saving money compared to normal api keys?

As my app traffic grows keeping up with open AI API costs is becoming a huge monthly expense. I've been eyeing self-hosted setups for Llama to cap my spending but I keep hearing mixed stories. Running cloud GPUs 24/7 means paying even when traffic is low and managing server maintenance takes away time I could spend building features. Plus if output quality drops users might notice right away. Have you swapped paid APIs for hosted open-source models and did it lower your monthly run rate or just add headache?