Connect with the Product Hunt community

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?

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?

Our tiny team got completely flooded with support tickets during our last major update. Critical bug reports ended up buried under simple stuff like password resets and basic account questions.

Setting up basic auto replies for common issues and organizing tickets by tags made a huge difference. It cut our response times way down and saved us from hitting total burnout.

When someone raised money, especially from a prominent VC with a strong reputation, like Antler or Y Combinator, the company immediately sounded more trustworthy to me.

But the latest analysis shared by @4kulia showed that in the first half of the year, only 26 launches were VC-funded.

Three things went wrong on Arteza this year and not one was reported by a user.

A spend function wrote bad balance events, so the ledger drifted and the cap I thought I had wasn't the cap. Nothing threw, nothing alerted. Our sign-in gate promised a credit amount that didn't match what the account actually got, and I only found it by opening every modal in the product one at a time and reading what it promised. And before launch I said the failure I expected from 111 one click apps wasn't a crash, it was an app returning something plausible and slightly wrong that nobody would bother to report.

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?

Hey everyone. I use Claude for everything. I'm sure you too.

My biggest pain with it? Not knowing when I'll hit the 5-hour window limit.

Turns out, you can use Claude, to update Claude's UI and show you your current usage.

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?

Something I learned the hard way running outbound for my dev agency:

Everyone obsesses over the first message: the opener, the hook, the personalization. I did too.

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?

Giving away a product for free builds a nice illusion of fast growth, but transitioning to paid later is honestly brutal. Users get so used to getting everything for zero cost that asking them to pay later changes their entire mindset from curious explorers to strict critics overnight. Looking back I wonder if starting with a small paid tier right from the beginning filters out the wrong crowd and saves you from that sudden growth cliff.

Have you tried charging from day one or did you also struggle moving away from a free model?

Last night, two PHP security issues were revealed, CVE-2026-109618 and CVE-2026-109619. Both allowed remote code execution with no authentication needed, and they were very serious, with a vulnerability score of 9.2. Due to the extent of the impact, we found ourselves doing emergency work on client sites late that night.

What astonished people most: updating WordPress and its plugins doesn't fix it. The problem is in the PHP language itself, so the PHP on the server is what must be upgraded.

Also note that if a website is running a PHP version that's no longer supported by the PHP development team, there will be no official patch.

It's so easy to fall into the trap of over engineering a quick weekend project just to keep the styling under control. A massive design system feels like total overkill when you're just testing an idea but without some rules the third screen always looks like a completely different app. I've started keeping a basic note with just a few color and spacing constraints to feed the assistant.

What is your go to trick to keep your UI looking clean without slowing down your build speed?

On client sites I often hear the same sentence a few weeks later: it worked before, what changed? Without a record, nobody can answer, not even me.

I have seen a short changelog file, a note in the project tool, and a dated list sent to the client after each visit. All of them work only if someone keeps them up to date, which is the hard part.

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?

When I launched my first paid tool, I set the price at $5 a month because anything higher felt like I d scare people away. It took me almost a year to realize the people paying $5 were the ones emailing support the most, and the few who would have happily paid $30 never thought it was a serious product.

I raised prices earlier this year and lost a couple of users, but revenue went up and, oddly, the complaints went down. I still feel a little guilty every time I look at the pricing page, though.

I ve noticed two patterns with makers I talk to:

1. People who start cheap to get traction and then struggle for months to raise prices without upsetting early users.

2. People who charge more from day one, get fewer signups, but end up with customers who actually stick around.

There have been several articles about Apple in recent days from many angles.

For example:

There s a small difference in how you ask an AI to save something, and it changes what gets saved.
Save this for next time. The AI writes a message to the next AI, and it comes out as instructions:
Next session: confirm the hotel before booking trains. Do not change the Paris dates. Remind the user about the deposit.
Save what we settled. The AI writes down facts:
Paris is three nights. Trains between cities; a rental car was dropped because of city parking. The hotel deposit is due May 1.
The second note stays true after the conversation ends. A month later, it still says where things stand and why.
The first is a set of instructions from a moment that has already passed. A new conversation reads them and follows them, even after the plans have changed.
I saw this in my own records.
Notes written as instructions carried an earlier stage into new conversations. Notes written as facts read like a record: what was decided, and why.
Now when I save, I ask for what settled.
Have you noticed how your AI writes the notes it saves? I m curious what others have seen.

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?

With today s Vercel Day and its financial contribution, I thought of a topic we probably haven t talked about much here.

Money allocation once the funds are raised.

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?

I ve been testing a safety check for an AI app by running a script of test messages many times against the model. Every run was fine until it wasn t: after a day of repeated runs, calls started failing with 429 errors, and waiting 60 seconds between retries stopped helping.

I assumed the limit was per minute. It wasn t. On the free plan for the model I use, the limits are 30 requests a minute, 1,000 requests a day, 8,000 tokens a minute and 200,000 tokens a day. I believe I hit the daily cap, because the app itself also stopped generating responses at the same time. My tests and the app share one account, so they share one budget.

What I m changing: run tests in small batches, never repeat full runs, and plan a backup provider so a quota problem doesn t become an outage.

How do you keep testing from eating your production quota? Separate accounts, a cheaper model for tests, or something else?