Connect with the Product Hunt community

I still answer every support email personally. Every bug report, every billing question, every "how do I do this" and every "this is broken and I'm furious." It takes hours I don't have, and some days it's the only thing I actually get done.

I do it because the signal is irreplaceable. Support emails are the most honest feedback I'll ever get people tell me exactly where the product confuses them, exactly what broke, and exactly what they wish existed. If I hand that to someone else, I lose the pulse of my own product and start making decisions from dashboards instead of from real frustration.

We used to offer a standard 20% discount code whenever a demo prospect hesitated or asked for lower pricing. It felt like we were closing deals, but buyers kept stalling, waiting to see if they could haggle for more.

Two months ago, we instituted a strict Zero Discount Policy" across the board fixed prices for everyone. Surprisingly, our deal cycle shortened by two weeks. Buyers stopped playing negotiation games and made decisions much faster.

Have you ever stopped offering discounts and noticed that prospects actually respected your value more?

Every CRO guide told us to keep our hero section clean, concise, and minimal. We had a super short landing page with just a bold headline and a CTA button, but conversion stayed stuck at 2%.

We decided to do the exact opposite: we rebuilt the page into a 3,000-word long-form teardown showing the exact step by step workflow real screenshots and edge case limitations. Conversions jumped to 5.4%.

It turns out high-intent buyers wanted deep clarity, not slick marketing buzzwords.

A customer asked me last week for a full export of everything they've put into the product every record, every file, every note. And I froze.

My first instinct was trust. Of course they should be able to take their data. It's their data, not mine. Refusing would be exactly the kind of lock-in behavior I've always hated in other products. A product that holds your data hostage isn't a product it's a hostage situation with a login page.

We were getting plenty of signups with our 14day free trial, but 80% of users were ghosting us after day 3. They simply didn t have enough skin in the game to properly set up the product.

We decided to replace the free trial with a 30day no questions asked" money back guarantee. Signups dropped by 25%, but activation soared, and 30-day retention doubled because users were actually committed to testing it out.

Have you ever gated your product more strictly and seen better long term retention as a result?

Back when I was doing dropshipping, honestly the worst part was testing. You find a product, make the store, run ads... and a week later you find out nobody wants it. Money gone.

So how do you do it now?

• do you test before launch or just launch and pray lol

• what's the cheapest test that actually worked for you?

Our brain run on autopilot more often than we realise. One such behaviour is hearding, where we have the tendency to follow group or try to in a group. Imagine a few people suddenly started running. You don't know what's happening, but you might start running too, assuming they know something you don't?
Now, lets apply this into Cusomer behaviour, a D2C product goes viral and suddenly everyone wants to try it. A resturants has a queue outside it, we assume food must be good. A SaaS product gets #1 on product hunt and everyone wants to know what it does.
This i find really intriguing, becuase popularity can become a shortcut for credibility. (PS not shade to people who gets #1 on this platform a very big deal and hardwork) I'm just naturally curious on cusomer behaviour, read this paper recently in harvard business review about how fast consumer behaviour is changing in this decade.
Curious to hear what other makers think.

AI tools can now analyze years of employee performance reviews, retention metrics, and project outputs to generate hiring profiles and team structures: "hire for X trait," "keep teams under Y size."

I ve spent over a decade leading cross-functional teams, and I m skeptical. Not because the AI can t spot correlation, but because I ve seen how easily corporate data misrepresents human dynamics. A team can look high-performing on paper while burning out its best people behind closed doors. If the AI learns from that HR record, it standardizes burnout with total confidence.

Here s where I ve landed so far. I d need three things before acting on an AI-generated organizational lesson:

1. The qualitative feedback, visible. Skip-level notes, team sentiment, and anonymous feedback loops. Not just productivity charts.

2. The market context at the time. A hyper-aggressive growth playbook from a bull market will backfire in a retention-focused downturn. The lesson should state when it applies.

3. A leadership sign-off. A manager who navigated the human side confirms the nuance before it becomes an algorithmic hiring filter.

We learned the hard way that free users and paying customers want totally different things. Free users usually ask for dozens of features to avoid buying other tools while paid customers just want speed and simplicity.

After wasting months on a feature that non-paying users demanded we tagged support feedback by payment history. Focusing mostly on paid requests cut our user drop-off in half and saved us tons of dev time.

I tested 10 prompts like "best tool for X" in ChatGPT, Perplexity and Gemini. Our product came up in 2 of 30 answers, and a competitor with less traffic showed up in 14.

Curious how others approach this:

• Do you track AI mentions at all, or is it too early to matter?

• Has anything you changed (docs, reviews, comparison pages) actually moved the needle?

• Is "AI search visibility" a real channel yet, or mostly hype?

Genuine question for freelancers and small agencies.

For big projects, a contract is a no-brainer. But for a $300 logo tweak or a two-day dev fix, it can feel like overkill. Sending one can even make the client hesitate.

I ve gone both ways:

• No contract: fast start, but twice the scope crept and once the payment took 60 days.

• Contract every time: slower start, but no awkward that wasn t included conversations.

Been here 2 months now and something finally clicked. Half the upvotes and half the comments on any launch are people returning a favour.
You upvote mine, i comment on yours, everyone goes home happy.

Nobody says it out loud because we all benefit from it. It s like a group chat where everyone agreed not to talk about the group chat.

Doesn t make PH useless tbh. It just means rank and comment count show who has the bigger circle, not whose product is actually better.

Maybe i m wrong and i m just new here.
Would love to hear from people who ve been around longer, does this match what you ve seen or have i been reading it all wrong.

I shipped a small tool built with Claude Code thinking it was ready to go. The moment a second person opened the app and made a live update, it wiped out my recent edits because there was no conflict handling built in.

Since AI agents only build what you specifically tell them to I now ask one question in every prompt: what happens if two users do this exact action at the same time?

We ve been working with a developer in Germany for a while and would now like to bring them onto the team full-time.

The problem is that we don t have a German entity, and keeping them as a contractor doesn t really feel right once they re basically working as a regular employee.

Our accountant suggested looking at an employer of record, and G-P is one of the options we re considering so we wouldn t need to set up a company in Germany just for one person.

Has anyone here actually hired someone this way?

I m building a small clothing brand from USA and I m trying to grow without paid ads. So far I ve been testing Pinterest boards and SEO for traffic, but it s slow and I can t tell what s actually working.

For those of you who ve launched a physical product store:

1. What was your first channel that brought real customers, not just visitors?

2. How long did SEO or Pinterest take before you saw results?

3. Is there a metric you wish you d tracked from day one?

I d love to hear what worked and what was a waste of time. I ll share what I learn from this thread in a follow-up.

I'm considering the possibility of small development teams spending less time on repetitive tasks and more time on solving actual problems.

For instance, a team could end up spending hours each week on manual testing, carrying out deployment checks, preparing bug reports, or keeping the project updates in order. However, it isn't always the case that everything should be automated since the costs involved in setting it up and in maintaining it can end up exceeding the time that is saved.

I would like to get some feedback from developers and startup teams who have dealt with this issue.

What is the basis on which you choose the first repetitive task to automate and was the outcome worth the trouble?

When I launched my design agency, I gave a 20% "early adopter" discount to almost every client who asked for one. I told myself it was necessary to build a portfolio. In reality, I was afraid of hearing the word "no."

Eventually, I was overbooked, underpaid, and burning out. I decided to enforce a strict no-discount policy across all services. I was expecting angry pushbacks and lost deals. Instead, most clients simply accepted the quote, and those who asked for discounts respected my polite refusal and signed anyway.

The lesson I learned: Clients negotiate discounts not because you are overpriced, but simply because they want to see if you'll yield. Discounting your core rate erodes trust and signals insecurity in your work. If a client truly has a lower budget, reduce the scope of work rather than cutting your price.

How do you handle clients who constantly ask for discounts? Do you hold your ground or offer scope adjustments?

Last month we connected an autonomous agent to our support inbox to speed up reply times. The AI agent worked well at first cutting our backlog to zero within the first 48 hours. I was thrilled by the results.

The trouble started when a regular client asked a billing question that had a small edge case. The AI agent hallucinated a policy refund that we never offered and answered with politeness. We only caught the AI agent because our human quality audit flagged the outbound volume before sending. I felt uneasy when we discovered the mistake.

The issue was not the model capability. Our lack of guardrails around irreversible actions. We quickly updated the workflow so the AI agent drafts all responses but any account changes require approval. I think this new guardrail is essential.

Our current setup is simple. The AI agent handles the synthesis and drafting while humans own the click. I feel this balance keeps speed and safety aligned.

Offering monthly plans makes it way easier to get that initial yes from users but chasing churn every month is exhausting.

Annual upfront gives you cash right away but it definitely scares off people who aren't fully convinced yet.

Giving a huge discount to force annual signups feels like it cuts too far into profit.

Do you guys push annual pricing upfront or start everyone on monthly and upgrade them later?

On 16 Sep I rewrote the title of one of my blog posts, a case study guide on AI in manufacturing. Google recrawled it on 18 Sep at 07:06, and the same day Search Console moved it from indexed to crawled, currently not indexed.

I posted about it that day as if the edit had cost me the page. In my next daily report, on 19 Sep, it was listed as newly indexed again. I had not touched it.

We ran our B2B SaaS software at $19/month for almost two years without touching the price, despite adding dozens of new features. We were afraid that an increase would trigger a mass churn event, especially among our early supporters.

When we finally decided to raise the rate to $39/month for new signups and gave existing users a 6-month price lock guarantee, the retention rate blew us away. Churn didn't spike, and our MRR (Monthly Recurring Revenue) almost doubled over the next quarter.

The lesson I learned: Your most loyal users stay for the value your product provides, not just because it's cheap. Grandfathering existing customers into their old rate for a set period builds immense goodwill and gives them time to adjust. Communicating transparently why the price is changing (e.g., product improvements, support expansion) makes all the difference.

How do you handle price changes for SaaS or recurring subscription products without upsetting your core user base?

A user signs up on a Monday, forgets to cancel their sandbox project, and gets hit with a $49 charge on Sunday morning. They immediately dispute the charge with their bank instead of emailing support, costing us a processing fee and a potential advocate.

Nothing about our conversion funnel makes that cliff feel manageable. The fourteen-day trial label sets an expectation of breathing room, but the friction of entering payment info upfront turns the trial into a ticking clock rather than an exploration.

Card-required trials exist because they filter out low-intent signups and improve conversion rates to paid tiers, and that metric drives our growth charts. But optimizing for upfront conversion while ignoring day-one hostility creates a toxic cycle of chargebacks and angry churn.

What I would do differently: let users build and test fully in the free tier with strict functional limits, then prompt for payment only when they hit a hard wall that requires production scale. Harder to build separate feature gates, much healthier for long-term retention.

Hi everyone!

I've noticed a problem with the way I discover and use digital tools. Whenever I find a useful website or app, I try it out, but after some time, I often forget its name or where I found it.

I've tried saving links in bookmarks, but eventually, they become difficult to organize, and I rarely go back to check them.

I'm wondering if this is something other people experience too. It feels like discovering a useful tool is only half the challenge; remembering it and actually using it later is another.