Connect with the Product Hunt community

When you re building a startup, nothing is ever enough.

More users, a new feature, a bug. MRR, churn. It's hustling all the time. and pretty uncomfortable sometimes.

I tend to forget the day to day, and just think about tomorrow.

A student might finish a lesson and do well on practice questions, then struggle when asked to explain the same idea aloud.
Understanding something privately and presenting it to others seem like different skills.

For people who have built or used education tools: have you found a way to help with that step?
Would you use a short spoken explanation, audience questions, peer feedback, or something else to help a student practice?

I m especially curious how you would tell whether a student understands the topic better, rather than has simply memorised a polished answer.

Most of what I build is a better version of something that already exists. My company is 22 years old, and the pattern has barely changed:

Start from a tool that I or a client already use and aren't happy with

Make it better, and price it a little below the competition

Never raise the price. I haven't once

When we hit our first 1,000 signups, we popped champagne. Everyone was celebrating top-of-funnel growth. But weekly active usage was practically flat.

Digging into the analytics, we realized we were optimizing for the wrong metric. Vanity signups feel amazing on a dashboard, but zero active engagement means your core loop is broken.

Do you focus entirely on fixing retention before pouring fuel on acquisition or try to balance both at the same time?

Last year my clothing brand was bleeding money on returns. Almost twenty-five percent of our monthly orders were coming back with the exact same remark about the item not fitting as expected.

Instead of tweaking our ad copy or running new discounts I spent a full week reading every single return request note from the past six months.

What I realized shocked me. Our sizing chart was technically accurate but our fabric had zero stretch. Real customers with broad shoulders were constantly buying their usual size and getting disappointed.

I updated our size guide with a clear note telling broad-shouldered buyers to order one size up. We even added a quick ten-second video showing a model trying it on and moving around.

Two years ago, I hired a senior dev from a top-tier tech company. Great credentials, spotless GitHub, aced every technical interview step. Six weeks in, it was a nightmare he wouldn't push code without endless spec documents, refused to touch legacy code, and couldn't operate without direct management.

A few months later, I took a gamble on an applicant who had a 2-year gap on her CV (she took time off to care for a sick family member while running a tiny local freelance gig).

During the interview, instead of talking about frameworks, she talked about outcomes:

• How she handled clients when deadlines slipped.

• How she debugged broken sites at 2 AM without documentation.

• Why simple, maintainable code beats clever code every time.

We fell into the trap of blindly trusting our feature request board. Our top voted item was an advanced reporting dashboard so we dedicated weeks of dev time to make it perfect.

The usage numbers after launch were a reality check. Most people who asked for it barely touched it proving there's a huge gap between what users ask for and what they actually use daily.

My content team used to publish two articles each week. We spent a lot of time researching topics but search traffic barely moved.

Writing content takes weeks to rank and requires building fresh authority from scratch. Meanwhile dozens of posts sat on page two of search results and received zero clicks.

We stopped writing articles for a whole month to focus only on our existing library. We updated statistics added better images and expanded thin sections in past posts.

Search engines already trust URLs so giving them fresh content pushes them up the ranks much quicker. A post that moves from position eleven to position four brings hundreds of visitors overnight.

Tab came out of stealth this week, and TechCrunch reported a $300M valuation. It's a personal assistant you text on iMessage or WhatsApp. The founder said it has its own phone number, computer and wallet, so it does the task instead of telling you how.

I like that there's no app to install. What I'd worry about as a user is checking what it actually did. A chat log isn't a great receipt when money is involved. For anyone building on WhatsApp or SMS, how do you show people what happened after the fact?

Ok so i ve been trying to get into the claude startup credits program.
Filled the form, hit submit, it says application submitted . Then like 5 seconds later the same form is back, blank.

So i filled it again. and again. 16 times now lol.

No idea if my application is actually going through or if i m just feeding a loop. No email, no status page, nothing that tells me either way.

If you ve applied, did the same thing happen to you? and has anyone actually gotten credits, and how long did it take.

Over the past few months, I ve been testing how far a founder or tiny team can stretch AI capabilities across marketing, copy, and visual asset generation. While AI handles a massive portion of speed and execution, it hits a hard wall when it comes to brand strategy, contextual judgment, and authentic human connection.

Pushing output out faster doesn't mean much if it loses the nuance that makes people care. For those running solopreneur setups or lean startup teams: which specific workflows are you comfortable delegating completely to AI, and what non-negotiable tasks are you keeping strictly human?

Year our newsletter open rates dropped below 15% even though we had great content. I spent three weeks testing subject lines and send times but nothing seemed to help. The numbers stayed low.

The real issue was that Gmail and Apple Mail started marking our emails as spam. Why? Because many people were ignoring them. We had thousands of subscribers who hadn t opened a single email in over six months. These were accounts ghosts in our database.

I decided to run a re- campaign. It was simple: a text-based email asking if they still wanted to hear from us. I gave them a choice click "yes" if they wanted to stay or let us know if they were done.

Only a handful responded with a yes. So I deleted over 4,000 contacts the next morning. It was genuinely terrifying to see our subscriber count drop so much overnight.. I didn t look back.

I ve been using AI pretty heavily while building my latest project, and one thing surprised me: the code can look completely fine while the architecture is already going in the wrong direction.

The worst example was multi user data. Everything worked perfectly during testing because I was basically the only user. It was only when thinking through multiple users that I realized how easily AI can make assumptions like there s only one current user or forget ownership checks.

Since then, I ve started giving AI more context before asking it to code:

• who can access the data

• where the data comes from

• what must never be changed

• how errors should be handled

• what happens when multiple users do the same thing

AI is becoming a major part of software development, but there's a challenge I don't hear discussed enough: how do independent founders get access to AI if they don't yet have the resources to integrate it into their products?

I'm an independent founder from Pakistan. I've already built and launched a SaaS platform, and my next goal is to introduce AI tools and agents that help creators, freelancers, and small businesses save time and grow.

I've explored startup programs from major AI companies, but I haven't secured support yet. Building independently means making difficult choices about what I can afford to develop next.

I am not really big on promoting myself or what i do, but in this day and age you can have the best app/idea on earth and if no one will get to it then it's nothing. So what do you do? How do you promote? on a budget.

built a simple app with an AI builder and it worked great when it was just me using it.

as soon as a second person signed in and started making changes, they kept overwriting everything. turns out the AI saved all list data into one giant record because I never told it to handle multiple people editing at once.

what basic rules or prompts do you always give AI tools to avoid silly setup bugs like this?

Building a quick demo with AI is one thing, but adding authentication, handling edge cases, and maintaining the code over time is a different challenge.

For anyone who has shipped something with Lovable, Bolt, or a similar tool, when did you first feel the need to move beyond vibe coding?

I've noticed that coming up with ideas is the easy part. Starting a new project is exciting, picking the tech stack is fun, and the first few days fly by.

Then you hit the boring parts, start doubting the idea, and suddenly you're already thinking about the next project.

I've definitely been guilty of this. Lately, I've been trying to focus more on finishing things than coming up with new ideas.

Curious how other indie makers deal with this. Do you have a system for staying focused, or do you just force yourself to ship?

People always say that Tuesday or Wednesday is the day to release something to get the most attention. We chose to go against that advice and launched on a Sunday when there was less competition. We got way total upvotes than, during our last launch but the number of people who became paid users went up by two times. The number of visitors was smaller. The people who came had a much clearer interest. Has anyone else chosen to use a day with traffic in favor of a day with more interested people?

It s kind of frustrating to set up cookie banners, especially when you re just trying to get people to sign up. Having visitors constantly see cookie popups adds a lot of friction.

How do you guys handle this? I still want to track where most of my visitors are coming from, but with GDPR, it feels like I have no choice but to add these annoying cookie banners.

I searched this forum for vertical drama and found almost nothing. It is the series format shot upright for a phone, about 90 seconds an episode, each one breaking off right where you need the next.

I make a few myself, with AI, so I would enjoy talking shop with whoever else does.

Who else is doing this? What do you generate your shots with, and how do you keep a character or a prop the same from one shot to the next?

Four measurements from each of three events give 12 rows and 3 distinct events. Those counts describe different things, and neither alone proves independence.

For an analytics interface, would you show both counts beside the headline metric, or use a short explanation with a methodology link? What wording makes the unit clear to a first-time reader?

How do you handle marketing when you're a developer?

I've noticed that for me, building the product is actually the easy part. I can spend hours working on features, fixing bugs, improving the UX, etc. But once I have something I'm happy with, I have to switch gears and start thinking about marketing, content, social media, getting users, etc. And honestly, that's the part I struggle with the most.

I'm curious how other developers/solo makers handle this.

Do you start thinking about marketing while you're building, or only once you have something ready?

I spent 3 weeks over-engineering a dashboard feature because I was terrified of launching a "clunky" product. I wanted every pixel to look clean, every transition to feel smooth, and every detail to represent my best work before letting real users see it.

When I finally shipped it, 0 people used that specific feature I spent days polishing. Instead, 5 users immediately emailed me complaining about a basic login bug I had completely ignored while focusing on aesthetics.

Felt like a complete waste of time to polish things nobody asked for. That s when I realized that perfectionism isn t high standards; it's often just fear of judgment. Pride doesn't validate your startup, traction does. Shipping fast gives you real feedback, while shipping late only protects your ego.

How do you mentally detach yourself from perfectionism when shipping your first version? Do you push raw code out early, or do you delay until it feels right?