Answering every support ticket directly as a founder gave us incredible insights into real user bugs and UX confusions early on. but now that active accounts are growing, spending three to four hours a day answering repetitive onboarding questions is completely pulling focus away from core development.
for small teams, how did you transition from answering every query manually to building scalable self-serve help centers without losing that personal human touch?
I used to describe a feature and let the agent build immediately. It felt fast. It wasn't. The architecture got decided implicitly by whatever the agent tried first.
When that first approach was wrong, everything built on top of it was wrong too.
sharing weekly progress and feature roadmaps on public forums creates incredible community excitement and gives us early validation before writing complex code. however, last month a larger competitor built a toned down version of a feature we teased publicly weeks before our own release was ready for beta testing.
how do you balance the momentum of building in public with protecting unique feature concepts until they are fully polished?
We spent months trying to build groundbreaking, AI-powered workflows that would blow our users' minds. But when we looked at our power users versus our churned users, the difference was tiny and mundane.
Power users had positioned our app right in the middle of their existing morning browser tabs. Churned users treated it like a utility tool something they opened once a week, forgot about and eventually cancelled.
I ve been thinking about this with agent harnesses. A lot of the work between LLM calls is just deciding what happens next: retry, switch tools, pick another model, or stop. Some of these decisions seem simple enough for a small model or even normal code. But getting one wrong can mess up the entire run. Would it make sense to use a small, fast model for these Type 1 decisions and save the bigger reasoning model for the hard stuff? Where would you draw the line? I d be interested in how people are handling this in their own setups.
Every project felt like an opportunity small ones underpriced ones ones outside my expertise. My calendar was full and I felt important. Then the numbers came in. I started declining anything below a rate I set in advance. Income went up hours went down.
The opportunities weren't bad. I was using busyness to avoid the scary work of pricing myself properly.
For those who've started saying no: was it the requests' fault or your inability to prioritize? And what are you doing right now that you'd drop immediately if you were honest about its value?
I tell everyone to ship earlier. I say it in comments, I say it to friends, I believe it. And I've been sitting on a landing page rewrite for three weeks because it's not "ready."
The advice is good. The problem is that giving advice and taking it are two completely different activities, and the first one is much cheaper. I suspect this is universal and nobody admits it.
So: what's advice you genuinely believe, that you give freely, and that you routinely ignore in your own work? And the harder follow-up: is it actually good advice that you're failing to follow, or is it advice that sounds good but doesn't survive contact with your actual situation?
I'm asking because I want to know if "ship earlier" is advice I should keep giving, or advice I should stop giving because I can't even follow it myself.
I have launched on PH twice but before launching, I always prefer to share the product with at least 20 potential users over DM. The goal is to get early feedback and testimonials. This helps me understand what s working (or not) in the copy, design, offer, value proposition, etc. Based on those early insights, I iterate quickly and it could be small tweaks or full rewrites, depending on what people are saying.
To make it easy for them to say yes and share feedback, I create a no-brainer offer (like 70 90% discount) and DM potential users on X asking for feedback. What s your pre launch strategy for collecting feedback and improving your product before launching on PH? P.S. Here s a sample DM I use to get early feedback for Boringlaunch: Hey [User Name]
We ve just launched (product name) for [Industry/Category/Domain/Target Audience]
Your launches are pure gold. So are you. That s why we re introducing Maker Minutes. We re doing our best to shine on a light on the talented and interesting makers that make up the Product Hunt community. One small way you can participate is sharing self-recorded videos of yourself answering some casual questions about yourself that we will selectively share on our socials so the broader community can get to know you and what you re working on better.
Community Hours got a permanent residence
We ve been loving our Community Hours sessions where we get to meet some fresh faces and consult with makers about their upcoming launches, so we decided to give the sign up links a permanent home. No more scratching your head to remember where you stored that link that s floating around on various parts of the internet. Find the sign up link on our Launch Guide or in the launch submission flow. If you haven t joined us yet, please do!
