Connect with the Product Hunt community

I started dictating my prompts recently because typing out long paragraphs of context during debugging gets exhausting. The upside is huge you naturally explain the why behind a bug instead of just throwing a short command like "fix error" at the LLM. But the friction comes when you have to say exact file names or variable paths out loud. I end up sounding ridiculous trying to spell out camelCase names or special symbols.

For those using voice tools regularly in tools like Cursor how do you split what you dictate versus what you still manually type?

Our early Discord and launch feedback was dominated by a tiny group of power users asking for deep customizations and niche integrations. We spent a full quarter building for them only realize our boarder subscriber base was struggling with basic onboarding and core navigation.

How do you filter out the noise from super-vocal power users when planning your core roadmap?

When we launched, we priced our entry tier at $9/month to make it an easy decision for anyone. But we noticed potential buyers kept asking hyper skeptical questions about security reliability and support . As an experiment we bumped the starting to $29/month with zero product changes, and closing conversations actually became smoother.

Have you ever found that raising your prices changed the quality or confidence of your buyers?

A few of my consulting clients have their teams using my products every day. So feedback shows up fast, and I usually get requests done the same day.

I've come to think the best thing you can do early on is get your heaviest user on your side. In my case the first heavy user was me, and the client teams came next.

How fast do you usually act on feedback from your users?

Everyone told us enterprise SaaS needs a Book a Demo / Contact Sales button instead of clear prices. But sales cycles were taking 60 days just to qualify budget fit.

We decided to publish clear baseline tiers right on the homepage. Inquiries dropped slightly, but sales cycle times cut in half because leads coming in were already pre qualified.

Do you keep high tier pricing transparent or do prefer forcing a demo call?

Noticed so many products get top spots and hundreds of upvotes on launch day but by the end of the week nobody is talking about them.

Feels like a lot of traffic comes just to see the launch event rather than actually use the app. Having a solid group of daily active users before you launch seems to be what keeps things alive.

What do you guys do right after launch week to keep new signups coming back?

We originally priced based on team size, but realized our product was heavily driven by individual daily usage instead. Watching users downgrade because the billing didn't match their work reality was a brutal wake-up call.

Transitioning tiers without alienating early adopter feels like performing surgery while blindfolded. For founders who have successfully restructured pricing: what indicators told you it was time to make the shift?

We track daily signups like a scoreboard, and a spike in traffic always feels amazing on a Tuesday morning. But then you log in on Monday and see a cancellation email from someone who paid on Friday and barely touched the dashboard. It makes you realize that an acquisition metric is just a vanity mirror if the product doesn't hook into their habits during that very first session.

How early in the onboarding flow do you actually know if a user is going to stick around long-term?

Hey everyone, Connor here. I've been spending a lot of time in the vibecoding space lately, and I want to talk about something that's been nagging at me.

The promise of vibecoding is real. You describe what you want, the model builds it, and suddenly an idea that would have taken a weekend is sitting on your screen in twenty minutes. That feeling is genuinely addictive. It's the closest thing to magic I've experienced as someone who loves building things.

It's a really weird feeling having a decent number of signups on paper but having zero clue what your actual ideal customer looks like. You look at your analytics and see one group living inside your app daily while another batch signed up months ago and never came back. When you're trying to design features for two completely different types of users at the same time you end up satisfying nobody.

Looking back do you wish you had niched down right from day one or is it better to cast a wide net early on just to see who sticks around?

Sometimes you spend weeks fixing backlogs clearing debt or narrowing focus without shipping a single new feature. Visible progress looks like zero on the dashboard but the underlying product gets way stronger.

It's easy to feel guilty when there's nothing new to announce or post in a changelog even though that cleanup work was totally necessary.

How do you measure progress during periods where you're fixing internal stuff instead of launching new features?

When I was selling things myself, the iPhone video with bad audio always beat the nice version. Just someone at a kitchen table showing the product, no lighting, no edit.

Now I'm doing marketing for a launch, and I keep catching myself making things prettier when I should be making them more real.

We spent three weeks building an advanced export feature because users kept asking for it in support tickets. Once we shipped it, adoption was almost zero. When we reached out we realizes people didn't actually want a new feature they just didn't understand how to use existing tools to get the same output.

How do you figure out whether a product issue is a missing feature or just a clarity problem?

There s a weird mental shift that happens when you switch from typing prompts to speaking them. When I write I naturally trim everything down to save effort, which usually gives the AI too little context and leads to messy code output.

When I talk I ramble through the logic, and the results are honestly way more accurate. The only awkward part is doing it in a shared office space without feeling like a lunatic.

Has anyone else made voice dictation a core part of their daily build cycle or does it still feel more like a novelty?

Before launching, most founders study competitors carefully. After launch, product work takes over and that research quickly becomes outdated.

I am exploring a workflow that watches a small, fixed set of competitors and reports meaningful changes in pricing, features, positioning, and integrations every couple of days without creating constant notification noise.

We kept adding advanced dashboards, custom filters, and multi-step automations because we wanted to appeal to power users. Instead, we accidentally bloated the interface for everyday teams who just wanted a quick, frictionless way to get a single task done. When churn spiked the exist interviews didn't say it was too simple they said it felt like too much work to figure out.

How do you balance building advanced features for enterprise buyers without alienating everyday users?

We spent three straight weeks shipping a heavily demanded integration because five loud users swore it was a dealbreaker. It felt like a massive win when we pushed it live. But looking at the retention data a month later it didn't move the needle on churn at all. The real issue wasn't a missing button or connector; it was that users had to remember to open our app instead of having it embedded where they already lived.

Have you found that building requested features actually saves customers, or does it just distract from core workflow fit?

When a major account threatens to leave unless you build a custom export tool, the temptation to drop everything is massive. But every time we caved, our core product got a little more bloated and harder to navigate.

Balancing immediate revenue with product vision is easily the hardest psychological trap in early SaaS.

For teams managing enterprise demands: how do you filter out noise while keeping your biggest accounts happy?

For months, every negative review sent our engineering team into a panic to rewrite code. Looking back, half of those complaints came from people who simply weren't a good fit for what we were building.

Learning to ignore the wrong users is painful, but trying to please everyone completely diluted our product's original edge.

For founders navigating user feedback: how do you set a clear filter for what deserves a spot on your roadmap?

Every time we moved upmarket, enterprise prospects asked for more integrations, more roles, and more settings. Before we knew it, our clean and simmple tool started feeling heavy and intimidating to solo founders and small teams.

The hardest part is accepting that you cannot build a product that serves both solo creators and Fourtune 500 companies equally well.

For teams that faced this fork in the road: how did you decide which market segment to finally double down on?

Someone messages me on WhatsApp: What did we agree on last time?

I open my email to find the conversation. Or they ask about meeting next week, and I need to check my calendar.

We deliberately avoided adding forced product tours or initial setup calls because we wanted a totally seamless, self-serve sign-up flow. But tracking analytics showed that users who didn't complete setup within their first 15 minutes almost never came back. Adding just one required setup screen cut our drop off rate significantly.

Do you prefer keeping onboarding completely frictionless, or is adding a bit of friction worth it if it guides users to value faster?

We thought giving users a 30-day free trial would give them plenty of time to explore everything and fall in love with the app. Instead, most signed up, poked around on day one, forgot we existed, and then churned when the automated reminder email went out. When we shortened the trail to 7 days activation actually shot up because it created a sense of focus.

What length of free trial or sandbox experience has worked best for getting users to their "aha" moment?

I used to make the mistake of trying to write things that sounded super safe so nobody would get upset, but those posts literally got zero traction.

The moment I started sharing stuff that I actually learned the hard way even if some people might think differently things actually started moving. It feels like platforms are flooded with generic lists that everyone already agrees with.

Do you actively try to share opinions that might spark a debate or do you prefer keeping your thoughts neutral?

It is so easy to fall into the trap of redesigning your landing page hero section four times before the actual app logic even functions. tweaking gradients, adjusting border radii and swapping fonts feels like real work, but it is just a clever way to procrastinate on writing difficult backend code. I now build the ugliest functional UI possible first and ban myself from touching CSS until the core workflow is tested.

How do you keep yourself focused on building functionality instead of tweaking pixels too early?