It has happened to me with my previous saas. There were visitors coming from different channels and through SEO also. At the beginning, I was very confident that people would be signing soon. But, after sometimes, I was actually confused as to what is the problem. 2 people signed up. That's it. They used the application just once and never came back. I concluded that it wasn't solving any big or real problem and moved to my new project. What do you actually do in these situation? Would you continue with your journey, pivot or move to your next project?
I launched my product 10 days ago on Product Hunt. Built it to solve a problem I personally had with AI voice tools constant credit limits and monthly bills.
YouTube sent 600 visitors to my landing page. Not a single sale.
I'm not posting this for sympathy I genuinely want to understand what's going through someone's head when they land on a new product page.
Do you look for reviews first? Does a one-time payment feel risky compared to a subscription? Is it the landing page? The trust factor?
I am Nikolas and with my 30+ team we like giving back to the community. So, while I cant support every project that launches every day (I can barely keep up so somedays I dont even log on PH), I do want to make an effort for dev tool projects, especially those helping with AI code assistants (and platforms that could help me evaluate their effectiveness), IDEs, productivity tools and more. I am also interested in SaaS products with an API or simply APIs, especially APIs that leverage AI and can help developers build better (and faster).
I m looking for tools that can take a single image of a person or cartoon character and make them dance in sync with an audio track, so the movement follows the rhythm and beats of the sound.
I ve already tried open-source models, Wan2.2 and LTX. The results weren t good enough. The motion was off-beat or barely there, and the character s identity drifted over time.
Been thinking about this as I evaluate tools for my own workflow: a lot of products look reasonably priced on the surface, but the actual cost/value only becomes clear after you're locked in auto-renewing annual plans marketed as "discounts," usage-based pricing that spikes unexpectedly, or feature-gating that pushes you into a much pricier tier than you expected.
Curious to hear from other makers and users here:
What's a pricing structure that seemed reasonable at signup but turned out to be a bad deal in practice?
In hindsight, what pricing-page signal should you have caught before paying?
As a maker, how do you think about pricing transparency for your own product to avoid this exact reaction from users?
Lately I ve been thinking about how different design challenges look depending on the product you re building.
In theory, design processes often look clean and structured. But in reality, every product comes with its own constraints unclear requirements, edge cases, technical limitations, or simply trying to balance user needs with business goals.
After launching, my project received only three upvotes, and two were from family. The anxiety of refreshing the browser every few minutes hoping for validation is something I won't forget.
The silence was humiliating for days. But then, an active user reached out to let me know my tool solved a massive headache in their daily workflow. That message proved to be worth way more than a hundred upvotes on a leaderboard.
I constantly remind myself that a launch day doesn't define the life of a product. Still, self-motivation is a constant struggle, and often I sit down to build purely out of persistence rather than passion.
How do you push through when the launch response is far below your expectations?
My first launch sitting at three upvotes two of which were family members was a painful reality check. I spent hours refreshing the dashboard, hoping for a sudden bump that never came.
It left me feeling discouraged for days, until I received an unexpected email. A user wrote to say that my small utility saved them an entire evening of tedious work. That simple note was infinitely more valuable than any vanity metric.
It made me realize that product launches are fleeting moments, while real building takes patience and steady effort. Yet, maintaining momentum remains tough, and some weeks I only code because I refuse to give up.
How do you reactivate your drive when the public reception falls flat?
Just finished my product and quickly learned that building it was the easy part. Starting with zero followers or email list makes getting those initial sales feel almost impossible. There are so many channels to try but most feel like shouting into the void. If you started from scratch did cold messages posting in online groups or something else actually get people to pay?
It's so easy to mistake a loud minority for market demand. People will request integrations or dashboards but analytics almost always show they stick to just a couple of core tools anyway.
When we stopped building requested features and started focusing purely on fixing drop offs in our main workflow, our metrics improved a lot.
How do you measure whether a requested feature is genuinely going to help everyone or just satisfy one user?
