How do you collect feedback after launching a niche product?
I recently launched a niche product for composers called ShevtoneAudio.
One thing I've realized is that building the product is actually easier than finding the right users and collecting meaningful feedback.
I'm trying to avoid spam or aggressive promotion and instead reach people who would genuinely benefit from the tool.
For those who have launched specialized products:
The best AI tools I've seen lately do one thing really well - not everything
There's a pattern I keep noticing: the AI tools that actually get traction on PH aren't the swiss-army-knife platforms. They're the ones that nail one specific workflow end-to-end.
Been working on a few launches recently and this keeps proving true. What's the most focused AI tool you've come across lately?
Pacing the Frontier-A statement from 1,224 employees of frontier AI companies calling government
Hey folks,
just saw that there is a petition going on by the big frontier model companies, asking the US government to develop technical and governance tools to pace the AI development.
What is software testing and why is testing necessary?
What was the biggest mistake you made before getting your first 100 users?
I'm a first-time founder and recently launched my first product. I keep finding myself switching between improving the product and trying to get users.
Looking back, what do you wish you had done differently before reaching your first 100 users? More product? More marketing? More conversations with users?
THE MISTAKE THAT COST ME A YEAR
last year i was randomly visiting a website and couldnt download a video in hd quality. then as a dev, when something doesnt work, you think "let's build it." so i got the same thought. i started researching idea validation and found like 0.2% of websites actually worked fine, but they were full of shitty ads. i thought this is the perfect market , we should go all in. and when i checked their traffic i got shocked , cause they werent getting one or two million, they were getting tens of millions.
after some weeks of confusing "thinking" with actual progress, and a lot of procrastinating, i finally started. chose a regular tech stack, MEAN stack, to build it. at that time i wasnt even an experienced dev, just a kid at 17 with some exposure to stuff, knew how to code, but those traffic numbers pushed me to build as fast as possible.
i came to know we needed a scraper, and one of the best is yt-dlp. there were other options too, like youtube-dl, gallery-dl, unofficial tiktok apis. by all means i was overengineering, trying to build a robust system with multiple fallbacks that could download video and audio in every format avaliable. built that in two months, even using ai to figure stuff out. and by the end i had added so much complexity into one codebase that changing a single line meant updating 15 or 20 files, controllers, services, everything. that's when i realized this is what people call bad code.
so i rewrote it. this time removed external dependencies and just used yt-dlp efficiently in node js. after building that i felt it was pretty slow, taking about 10 to 15 sec just to fetch info, then another 10 to 15 sec to start the download. felt way too slow. tried optimizing with yt-dlp arguments and prewarmed pools, still around 9 to 10 sec. i was obsessed with speed at this point. almost 3 months gone.
How long will you wait for an AI agent before you give up on it?
Genuinely collecting numbers on this, because everyone I ask gives a different one and I suspect the honest answer is much lower than people admit.
I build real-time voice and face models, so waiting is the problem I stare at all day. The thing that surprised me is that the tolerance is not one number, it moves enormously depending on what the agent appears to be doing.
If it is silent, people bail in about two seconds. If it shows a spinner, maybe five. If it streams tokens so you can see it working, people will sit there for thirty and not complain. Same wait, wildly different patience, purely from feedback. And in a live voice conversation the budget collapses to a couple of hundred milliseconds, because silence in a conversation does not read as thinking, it reads as the thing being broken.
So what is yours? A rough number and what the agent was doing at the time.
Four dictation apps launched yesterday. Most are competing on the wrong axis.
Yesterday's board had SKI, Yap and Phantom Voice all launching, with Wispr Flow promoted alongside them. Four takes on getting speech into a machine, one day.
They are mostly racing on the same three things: accuracy, latency, and whether it runs locally. All real, all table stakes within a year.
Getting early users has been harder than building the first version.
We initially assumed that once the product was usable, finding a small group of early adopters would be straightforward. In reality, most people were interested in the problem but hesitant to try a new solution without proof, reviews, or an established user base.
A few lessons so far:
Specific outreach works better than broad promotion.
Conversations about the problem generate more useful feedback than product demos.
Early users need a clear reason to switch now, not just a list of features.
A small number of engaged users is more valuable than a large list of passive signups.
We are now focusing less on getting users and more on finding people who experience the problem frequently enough to help shape the product.
What's the PROBLEM your product solves?
In the month that I've been here, I've been noticing a pattern in a lot of launches - strong demos, polished UI, clear outputs of "what it does."
But when I ask myself "What problem does this solve?" I sometimes have to dig for the answer. (I come by that thinking honestly - I've spent 33 years building and fixing businesses, so this is the lens I can't turn off.)