Disclosure: I work on LaunchReach, which publishes the directory discussed below. This is a draft for human review, and the product is mentioned where it is relevant.
If you have ever built a spreadsheet of places to launch your SaaS, you know how it goes. You list the sites, then fill in the columns: does it accept free listings, is there an API, how long does review take, what is the character limit on the description. Halfway down, you start filling cells with what seems likely. Then a month later you trust the spreadsheet as if you had checked it.
This article is about that habit, and about why we think a directory should leave a cell empty when nobody has confirmed the answer.
The problem with plausible guesses
A guess in a directory looks identical to a fact. There is no visual difference between "accepts submissions via form" that someone verified and one that someone assumed because similar sites do. The reader cannot tell, so the reader plans around both equally.
For a founder, the cost shows up in specific places:
- You prepare copy for a field that does not exist, or miss one that does.
- You assume a listing is free and find a fee at the last step.
- You assume a site has an official submission route and build around it, when it is actually a manual form.
- You schedule your week around a review time that was never stated.
None of these is catastrophic alone. Together they eat the few days you set aside for launch, and they erode trust in the whole list. After the first wrong cell, you recheck everything, which defeats the point of having a directory.
What the public platforms page says
LaunchReach has a public page listing the launch platforms it works with: 45 destinations in total. The rule the page follows is simple: items that have not been confirmed are left blank rather than guessed.
I want to be careful about what that does and does not mean. It does not mean every field for every platform is filled in. It means that when you see a value, someone has confirmed it, and when you see nothing, the honest reading is "unknown", not "probably yes" and not "probably no".
I will not list per-platform details here, because this article should not claim more than the page itself supports. Go and read the page; the blanks are part of the content.
How to read a blank
A blank is a prompt to do a small amount of work before you commit. Here is how I would treat one:
- Check the destination's own page. The platform's submission page or terms are the primary source. If you find the answer, you have more than the directory had.
- Treat the blank as a risk, not a no. An unknown fee or rule is something to verify before you prepare assets, not a reason to drop the platform.
- Write down what you found and when. Rules on third-party sites change. A dated note beats a memory.
- Order your list by what is known. Do the destinations where you can verify the requirements first. Leave the uncertain ones for when you have time to check.
This is slower than trusting a full table. It is also the only way I know to avoid the failure where a confident-looking cell turns out to be wrong at submission time.
Why this matters more for a portfolio
If you run one product, a wrong assumption costs you an afternoon. If you run a studio with several products, the same wrong assumption gets copied across every product, because you reuse the checklist. A single unverified cell becomes several wasted submissions.
That is an argument for keeping a clear record of the difference between confirmed and assumed, whatever tool you use. Even a plain spreadsheet can do it with a "confirmed on" column that stays empty until you have actually looked.
The same principle applies to outcomes
The blank-over-guess rule is not only about directory fields. It is about outcomes as well. On LaunchReach's side, the terms state that third-party destinations decide whether to accept, publish or remove a listing, and that LaunchReach does not guarantee outcomes. The product also states that it does not claim attribution the data cannot support, and that AI recommendations are labelled as interpretations.
That is the same idea in a different place: say what is known, mark what is interpretation, and leave out what cannot be supported. If a tool tells you which directory drove your signups, you want to know whether that came from a tagged link or from a hunch.
Where the directory fits in the product
For context, here is what LaunchReach does with the directory, based on what the product site states. You add a product once and it reaches 45 destinations, ranked by fit, with copy written per destination's rules. Where a destination has an official API, submission goes through a dedicated adapter. Where it does not, browser automation fills web forms using your authorised session, only where platform terms allow. For communities such as Show HN, you post yourself and LaunchReach prepares the copy and records the outcome. It never bypasses CAPTCHA, 2FA or platform rules, and it pauses when a human is needed.
Each submission also gets its own UTM link, so traffic and signups roll up to the right destination.
That is the practical reason the blanks matter to us. If the product is going to prepare copy per destination's rules, it needs to know which rules are confirmed. Guessing would produce confident, wrong copy.
A practical checklist you can use without any tool
If you maintain your own list, try this:
- Add a "source" column: link to the page where you confirmed each fact.
- Add a "confirmed on" date.
- Leave a cell empty rather than writing "probably".
- Mark fees separately, and check them before you write any copy.
- Re-verify anything older than your launch window.
It takes more discipline than filling in a table from memory, but you end up with a list you can rely on at 11pm the night before launch.
What I would take from this
A directory is a tool for saving time, and it only saves time if you can trust it. The way to earn that trust is to be explicit about the edges of what you know. A blank cell tells you where to look. A guess tells you nothing and hides the gap.
If you want to see how this looks in practice, the platforms page is public. LaunchReach also has a 7-day Growth trial for $1, paid by card or mobile money, and nothing renews automatically. Growth includes 60 submissions per month and attribution by destination. Directory listing fees are shown before approval and passed through at cost.
Whatever you use, keep the habit: confirmed means confirmed, and unknown stays unknown.
Try LaunchReach: 7-day Growth trial for $1 at mambatxhub.com
