You Launched. So Why Is Nobody Finding Your Product?

I did the second half of this post already. Directories, listings, a launch thread, articles, replies. People can find the site if they look. Almost nobody arrives with a document in their hand and pays.
Discovery after launch day is a real gap. “Put it where people browse new tools” only fixes the people who are already shopping for a tool. Most of my category is not shopping. They are mid-checkbox, mid-renewal, mid-bill. They were never going to open a SaaS gallery that afternoon.
So I would split the problem:
• Launch visibility — listings and launch posts help a little. I would still do them.

• Use at the moment of pain — that is the part that did not move. A better directory does not put TermsGuard on the page where someone is about to click I Agree.
If your product is something founders hunt for (an API, a scraper, a component), a discovery site can matter. If your product is a 10-minute decision on someone else’s PDF, the missing place is that PDF, not another index of AI tools.
I am not saying don’t list it. I am saying listing is how you stop disappearing from searchers. It is not how you get the first stranger to change behavior.

The empty-checkout problem is real. I would not treat “build a physical product instead” as the fix.
Software is crowded because the cost to ship a thin AI wrapper is near zero. That is why a lot of us have a working app and a quiet Stripe account. Hardware does not remove that. It adds inventory, shipping, returns, certifications, and a longer loop before you learn whether anyone wanted the thing. You can still miss the market — you just miss it with boxes in a garage.
What feels oversaturated is undifferentiated software: another dashboard, another “AI reads X.” What is not oversaturated is a product that shows up at the moment someone already has a problem and will pay to make it smaller. That can be an app or a device. The scarce part is the moment and the willingness to pay, not the atoms.
I am in the first camp: document tools, free users, $0 so far. My lesson has not been “I should have made a gadget.” It has been “useful is not the same as someone changing what they do in the next two minutes.” A smart gadget that sits in a drawer has the same failure mode.
If you have a hardware idea with a clear job and a buyer who already shops for that object, build that. If the only reason to go physical is that SaaS feels crowded, you will meet the same discovery wall with freight on top.

link does not work

"total=1, items=0 for its own name" is a great specific way to describe that failure — the system technically acknowledges you exist while making sure nobody ever sees it. That's a nastier trap than a normal cold-start problem, because you'd check "is it live" and get a yes, and never think to check "does the API actually return it in a real search."

Your launch-order fix makes sense for the marketplace's incentives, but it's a little uncomfortable too — it means the platform is structurally biased against anything launched cold, since day-one usage can only come from outside traffic you had to build without its help. Did you ever find out what the actual threshold is, or is it still a guess you're reverse-engineering from behavior?

Ran into almost the exact same thing, the hard way. We'd shipped 9 SEO guide pages, all live, all in the sitemap, all individually indexable by URL. An external audit still came back with "no guides exist," because the homepage had literally zero links pointing at any of them. Google/Bing don't reward a page for existing, they reward it for being reachable by following links from somewhere they already trust. Sitemap submission got them crawled once, it didn't make them part of the site. Fixed it with a Guides nav link and a homepage section, and that's when it actually started working as a discovery surface. Worth checking: can someone reach your best content by clicking, not just by guessing the URL?

The post-launch gap is real. A useful test is to write the “where people discover this” sentence before launch, then make the first outreach repeat the same problem and outcome. If the message only says what the product does, discovery turns into a feature tour instead of a reason to try it.

Exactly. Launch day gets all the attention, but discovery needs to continue long after the launch.

A great product that nobody can find is basically a hidden product. Ongoing distribution and discoverability should be treated as part of the launch, not an afterthought.

I think that’s an important part of the post-launch phase. Getting attention on launch day is one thing, but having places where people can discover the product afterwards is a different challenge. I’m starting to see that myself with my first SaaS launch.

Discovery works better when treated as a channel experiment, not one launch blast. I’d pick one narrowly defined audience, spend two weeks answering their actual questions where they already hang out, and track activated users rather than clicks. That helps separate a distribution problem from a positioning problem.

A concrete version of this that bit me three days after launch: the marketplace I published on ranks listings by an internal quality score, and below a threshold the listing is counted in search totals but never returned in results. So my product was "live", the URL worked, and it was literally unfindable — the API returned total=1, items=0 for its own name. The fix isn't more marketing copy; the score is driven partly by usage and reviews, which you can only get from traffic that comes from outside the search. So the launch order I'd now recommend for any marketplace product: external write-up and community posts first, marketplace listing second, and don't assume "published" means "discoverable".