Connect with the Product Hunt community

In our early days, we spent almost three weeks building a custom internal dashboard to manage customer data and subscriptions. While it gave us complete control over our workflow, maintaining that custom code eventually took time away from improving our main product. For our recent launch, we integrated third-party platforms from day one. Although we pay monthly subscription fees, our engineering team spends 100% of their time delivering value to our end users.

At what point does building custom internal software make financial sense, or should growing teams always leverage existing solutions?

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.

We launched on a deal platform offering a $99 lifetime access plan to build early traction and cash flow. We brought in $40,000 in two weeks, but ended up flooded with demanding, feature-heavy requests from users who would never pay us another dollar. Out of frustration, we closed the deal, refunded the top 10% most abusive users, and switched strictly to a $29/month subscription model. Sales slowed down drastically at first, but our user retention and product quality improved dramatically within three months.

Are lifetime deals a dangerous trap for early startups, or is the upfront cash flow worth the support overhead?

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.

Built a quick working prototype over the weekend using mostly AI prompts and people actually loved the idea.

But the second i tried adding a new feature everything broke down.

The state management was all over the place and styles were messy. Ended up spending weeks rewriting the core data layer just to make it usable again.

We spent months perfecting a fully automated, self-serve signup flow, assuming developers would hate talking to sales. Our conversion rate stayed stubbornly low because users got lost inside the app and gave up without asking for help. Out of frustration, we removed the instant signup button and replaced it with a simple "Book a 15-min Demo" calendar link. Signups dropped, but our deal close rate jumped significantly because we could explain the value proposition face-to-face.

Are self-serve models overhyped for complex tools, or is direct human onboarding still the fastest way to hit initial revenue?

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?

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?

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?

Japanese founder, 22 years selling software in Japan. Ask me anything about the Japanese market

I've been running my company in Japan for 22 years, mostly on my own. I keep seeing people here who are curious about Japan but never really try it, so I thought I'd just open it up.

So ask away. Pricing for Japanese customers, getting a Japanese team to use an English-only tool, how buying decisions get made here, whatever. I'll be answering in the comments.

Also curious, have you ever thought about selling in Japan? What stopped you?

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?

We spent months building custom requests to lower our cancellation rate, but it backfired. The product became so bloated that users started leaving us for basic single-purpose alternatives that were just easier to navigate.

It s scary to pause feature work, but simplifying our UI did way more for retention than adding another setting.

Have you ever dedicated a full dev cycle strictly to removing old features, and how did your active users react?

I m still fairly new to Product Hunt, and one thing that surprised me is how quickly a product launch becomes messy.

You start with Product Hunt, then directories (+100s of them), SEO, GEO, outreach, ads, content, meetings, follow-ups and suddenly you re tracking everything across Notion, spreadsheets, notes, task managers, and random browser tabs.

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?

I've imported my browser links into almost every popular bookmarking app out there hoping for better organization.

But maintaining all those boards and custom categories quickly feels like taking on a second job.

Does anyone know a cheap/free tool for estimated DAU/MAU of mobile apps?

I'm looking for DAU and MAU only, ideally separately for Android (Google Play) and iOS (App Store) and by country.

Maybe it s just me, but I feel like every random extension I look at now wants permission to read and change all your data on all websites.
Like why
I get that some extensions probably need it, especially if they re doing something directly on webpages. But a basic dark mode extension or screenshot tool asking for access to literally everything feels kinda crazy.
I usually end up not installing them because I don t really want some random third-party extension having access to my banking, email, etc. I d rather just do whatever I was trying to do manually than give an extension that much access.
Do you guys actually check the permissions before installing extensions? And how do you tell if a smaller/unknown extension is actually trustworthy?
Or do most people just click allow and hope for the best lol..

I feel like I ve tried every bookmarking/read-it-later app that gets mentioned on here.
And somehow I always end up back where I started: Chrome bookmarks and sending links to myself on Telegram.
The funny part is that I want to like these apps. I ll import a ton of stuff, spend an hour setting up folders, tags, boards, etc., and convince myself I m finally going to have my life organized.
Then I never open the app again.
Maybe I m missing something, but a lot of these tools seem to turn save this link into a whole productivity project. I don t need another dashboard to maintain. I just want to save something in two seconds and actually find it three months later.
So genuinely curious: what s your actual system for this?
Do you have a bookmarking/read-it-later app that you ve stuck with for years, or is the whole category kind of overcomplicated and browser bookmarks are still good enough?
And if you do use one regularly, what made you stick with it instead of abandoning it after a month?

Tracking signups feels great, but churn is the silent killer when real money enters the picture.

Most cancellations aren't caused by missing features they happen because the product fails to become a daily habit. Changing a user's existing workflow is far harder than building a shiny new feature.

Do seasoned founders ever stop stressing over churn or do they just get better at diagnosing and fixing drop off points early?

I work on a B2B AI product, and one UX problem I find interesting is how to design for AI failure.

With traditional software, an error can often be fairly clear. Something failed, and we can usually tell the user what happened or what to do next.

AI is different.

The system can technically work and still produce a result that isn t useful. Sometimes we know why. Sometimes we only know that the output didn t meet expectations.

Our loudest power users were driving our product roadmap, and it almost destroyed our conversion funnel for new signups.

We spent weeks building advanced custom options for 5% of our user base. Meanwhile, standard churn kept rising because initial setup was becoming overwhelmingly complicated for everyday users.

For founders balancing different user tiers: how do you filter out loud feature requests to protect the core experience for regular users?

1. Google showed the previous owner of my domain
I bought my domain second-hand, and searching it on Google still showed the old owner's business.
Fix: In Google Search Console, go to URL Inspection Test live URL Request indexing, and submit your sitemap.

2. My sitemap sent Google to my login page
My pricing and legal pages were in the sitemap, but my login check treated them as private, so Google got sent to /login.
Fix: Open every sitemap URL in an incognito window. If any of them redirect, make that page public or remove it from the sitemap.

3. "Upgrade" sent buyers to a sales page, not checkout
That's one extra click where people drop off.
Fix (Gumroad): add ?wanted=true to your product link to open checkout directly.

4. Paid, but didn't get Pro
My payment webhook matches buyers by email. If someone pays with a different email, they pay, but nothing gets unlocked.
Fix: Pre-fill the user's email in the checkout link, and add one line: "Use the same email you signed up with."

My Product Hunt launch is in two days. The gallery is ready, but it's all screenshots: a hero image and a few shots of the product in use. I don't have a video. I could spend the next two days recording one. I'd rather spend that time on the first comment and on replying to people on launch day, though, and I'm not sure a rushed video helps more than it hurts. If you've launched before, did your video actually change anything? Or did most people just look at the first image and read the tagline?

When I first launched I swore I d keep things super minimal and never do heavy discounts or bloated features. A couple years in I catch myself making compromise after compromise just to keep numbers up. Partly because I was naive back then but partly because taking shortcuts was just easier. How do you tell if you re actually maturing as a founder or just losing your original vision?

When we launched on AppSumo, we were desperate for early traction and validation. We created a $99 Lifetime Deal (LTD) hoping it would give us that initial boost, and on paper, it looked like a massive win we made $40,000 in just two weeks! But the honeymoon phase ended fast, and the real nightmare started right after.

Suddenly, our inbox and support queue were flooded with demanding requests from LTD buyers who wanted custom enterprise features, priority support, and endless updates all without ever intending to pay us another dime. They were completely hijacking our roadmap, and our dev team spent months chasing feature requests for users who generated $0 recurring revenue, while completely neglecting our core paying subscribers.

Out of sheer frustration and burnout, we made the painful decision to pull the plug on lifetime deals entirely. We refunded the top 10% most toxic users, drew a hard line on feature requests, and switched strictly to a $29/month subscription model. Sales hit a brick wall initially, but within three months, our retention stabilized, our product quality improved drastically, and we finally regained control of our vision.

Are lifetime deals a dangerous trap that hijacks your startup s future, or is that initial cash flow worth the massive support burden and roadmap chaos?