I saw a great discussion recently about building a personal brand before the product is even ready vs building the product first and revealing yourself later.
For those of you targeting specific, legacy enterprise problems, which route did you take? It's tempting to build in stealth to protect the core idea and architecture. On the other hand, building a brand (in the sense of building trust) seems critical for those first few partners willing to hand over their messy internal data for you to structure.
If you had to start your current project over, how would you go about it? What have been some of the most unignorable observations centering on this aspect?
Something I keep seeing on launches here: People say "we validated this with users" but when you dig in, it usually means 5 friendly people from their own network said "yeah I'd use that."
That's not the same as finding someone who was already complaining about the problem before you showed up. I feel one is politeness and the other is demand.
Feels like the real validation isn't in interviews at all - it's in the comment sections, reviews, and forum posts where people vent about a problem with zero idea a solution could exist.
Genuine question: Has anyone here actually found a real customer complaint "in the wild" (Reddit, G2, Twitter, wherever) that changed how you built something? What did it say?
Minh dang chuan bi launch san pham SaaS tren Product Hunt nhung quy trinh duyet app co ve cang ngay cang gat gao. Nhieu startup phai mat hang tuan moi duoc len trang chu, trong khi cac san pham duoc feature lai thuong den tu cac agency co doi ngu marketing lon hoac co san luong user lon. Viec nay gay kho khan cho cac nha phat trien doc lap hoac startup quy mo nho muon tiep can user thuc thu. Co ai co kinh nghiem lam sao de toi uu h a thong tin launch hoac xay dung momentum truoc khi ra mat de duoc chon feature tren trang chu nhanh nhat khong.
I ve noticed a growing trend: more and more early-stage startups are skipping the classic "waitlist" launch and going straight to open access. Some argue it's more authentic and helps get traction faster. Others say waitlists build FOMO, gather valuable user data, and give time to polish the product.
Sorry, I'm a PH launch rookie. Launched yesterday but my metrics and dashboard have not updated since then, and I know I'm getting upvotes and comments, per notifications.
Ever been so annoyed by a problem you thought someone needs to fix this ? That s where a ton of great products start. However how do you really know whether this frustration is worth building a product around, or if it's just a personal annoyance?
This was the first question @mwamedacen and I asked ourselves when we considered launching 1Stroke - an AI tool that generates and rephrases smart replies anywhere on the web with just a right-click.
Our pain point? We used to spend hours writing and rewriting professional emails and social media content, only for them to be read in mere seconds.
A few days ago, an old client I once helped set up backups for messaged me in an absolute panic: Emergency! Help, our server has been hacked!
Their project happened to be a typical WordPress build, but the root cause highlights a much broader issue that applies to almost any tech stack. They were relying on popular "security" modules that simply changed the admin login URL to a custom path a classic case of security by obscurity.
I'm thinking about building a website where users earn points simply by staying active. They would need to check in at least once a day to keep their points valid.
As users collect points, they could enter prize draws or redeem them for vouchers, discounts, or even free products.
The main goal is to build an active user base. Later, if the platform grows, I'd like to partner with companies that are
