How much user feedback is enough before launching a new feature?
Hi everyone,
I'm curious how other founders decide when a feature is ready for release.
Do you rely on feedback from a small group of beta users, or do you wait until you have a larger sample size before making the feature public?
I've seen cases where launching early helps gather valuable insights, but I've also seen users become frustrated when a feature still has rough edges.
I spend too much time switching between apps, tabs, folders and windows... does anyone else?
I've been thinking about a productivity app and I'm curious if it's something other people would actually find useful.
One thing that slows me down every day is context switching. I work on multiple projects, and I'm constantly jumping between Finder, browsers, terminal windows, documentation, Slack, emails, and a bunch of web apps. Individually, none of these actions take long, but after doing them hundreds of times a day, it adds up.
Have events been part of your early-stage marketing plan?
Curious how other founders have approached events in the early days. I know for some, hackathons, expos, and pitch competitions are game-changers: early validation, first users, even investors. But for others, they end up being more of a distraction than a getting-early-traction opportunity.
So, I'm curious to know:
Did you include events in your early marketing/growth strategy?
What s the most rewarding event you ve ever participated in with your startup?
Any lessons learned (good or bad) you d pass on?
Why is decision-making still so difficult in B2B companies?
As companies grow, they adopt more tools CRMs, marketing platforms, finance software, customer support systems, analytics, and more. Each one generates valuable data, but that data usually lives in isolation.
I've realized that many leaders struggle because they have too much of that, spread out across too many places. Before making a decision, they often have to gather reports, reconcile numbers, and understand how one department affects another.
In your experience, what's the biggest obstacle to making fast, confident decisions in a growing B2B company?
Anyone else find the launch itself is the easy part?
Shipped BuildLead this week my first real Product Hunt launch. Spent months on the actual building. Spent maybe two days on "the launch" and somehow those two days felt harder.
I'm building this solo out of Abuja, Nigeria, so there's no team standup to catch the dumb stuff. Found a bug the night before scheduling that would've quietly broken the product for literally every first-time visitor the kind of thing a second pair of eyes finds in five minutes and I almost shipped blind. Fixed it, then spent an embarrassing amount of time wondering what else I hadn't caught.
What's actually gotten me is how much of "launching" has nothing to do with the product. Writing the tagline. Figuring out if a promo code helps or just trains people to wait for discounts. Asking friends to upvote without it feeling like begging. None of that was in any tutorial I read.
Curious if this is universal or just a solo-founder thing for the people who've launched here before, was there a part of the process that surprised you more than it should have?
How my team turns a SaaS idea into an MVP in 14 days (Our exact process)
Building fast is easy, but building the right thing fast takes proper team alignment.
Over the past few projects, my team and I refined a 14-day execution framework:
Days 1-2 (The Cut): We brutally cut 70% of feature requests. If it s not core to the main value proposition, it doesn't get built.
Days 3-5 (Design & Architecture): UI/UX is kept dead simple using pre-built UI kits to save engineering bandwidth.
Days 6-12 (Sprint): Devs focus purely on functional workflows. No micro-optimizations or premature scaling.
Days 13-14 (QA & Launch Prep): Team testing, bug squashing, and landing page polish.
This approach helped us launch multiple products without developer burnout.
How does your team handle the balance between speed and quality during an MVP build?
You can check out what my team is building on my profile link!
How do you decide which fire gets your attention first?
I run into the same moment most weeks, a client goes quiet, an employee seems off, and a report shows a number that looks slightly wrong, all on the same morning. Nothing on paper says which one to handle first. Whatever I choose usually comes down to instinct built from watching the same three businesses long enough to recognize a pattern, not from anything a dashboard actually told me.
Curious how other founders running more than one business, or more than one location, decide what gets handled first when everything looks equally urgent on the surface. Is it always the loudest voice, or is there something quieter you have learned to notice first?
What in your business only a person watching would catch, not a report?
Reports tell me what already happened. They almost never tell me what is about to happen if nobody steps in today. A client going quiet, a hire pulling back weeks before handing in notice, a location quietly underperforming while the numbers still look fine on paper. None of it showed up as a flag on any dashboard, someone just had to be paying attention closely enough to notice the shift before it became a complaint or a resignation letter.
Curious what the equivalent has been for people running more than one location, or more than one business at once. What is the thing that only ever gets caught by a person watching, never by a report sitting in an inbox?
The single metric we tracked that changed how we build AI interfaces
Hey Product Hunt community!
While building multi-model software over the past few months, our team fell into a common trap: focusing almost entirely on response speed and model capability.
However, after looking closely at user session recordings, we noticed something unexpected:
Users weren't abandoning chats because an AI model gave a bad answer. They were quitting because they spent over 40% of their total session time just setting up context, pasting background data, and switching tabs.
Is "Distribution Fatigue" real, or are we just solving a problem people don't care enough about?
Hey PH community!
As makers, we often spend months building solutions for problems we personally feel every single day.
For us, it was "AI Context Fragmentation" wasting hours re-explaining project rules and pasting docs every time we switched between Claude, GPT, and Gemini. We were convinced that millions of builders faced this exact same pain point.
Today, after hitting the launch button, the silence is humbling.