Show HN Soft-Killed: Restore Post, Convert Demo

A soft kill hides your launch

You just posted to Show HN, and the post is missing from a private window or a phone. That is a soft kill, and it can hide the real launch test. DDL to Data offers a way to create realistic test data from SQL schemas. Its Show HN post went up on a Tuesday morning. Within an hour, the submitter saw that the post showed only to logged-in users and was absent from private browsing and mobile.

The submitter emailed the moderation inbox, hn@ycombinator.com, with a plain account of what they saw and a request for review, and the post was visible again within a few hours. After restoration, it reached a front-page rank of 8. That rank is proof the post can be fixed, not a guarantee of signups.

A first launch with no signups is usually a reach problem or an offer problem. A hidden post hides the reach problem; a weak offer hides the conversion problem. Check the post from outside your own session before you judge the product. A missing post in a private window does not prove removal, but it does show the launch is not reaching the people you need.

When you write to that address, keep it short. Include the post URL, the time you noticed the problem, the views you checked, and a plain request for review. Arguing, threatening, and asking for a favor will not help. You are reporting a visibility issue, not requesting a promotion.

Recover the post, then inspect the offer

Keep this checklist next to your launch tab. Each item is a quick check, not a growth experiment. The early items fix visibility; the later items inspect the offer before you spend more time on distribution. You need both checks before you decide whether the problem is reach or offer.

• Open the post in a private window and on a phone, and if it is missing, treat it as a visibility problem.
• Email hn@ycombinator.com with the post URL, what you saw, and a plain request for review.
• Recheck the same private and mobile views after a few hours.
• Compare demo interest with signups, and if interest is high but signups are low, stop chasing traffic and inspect the offer.
• Check whether the price is too high for a first-time user.
• Ask whether the free tier gives real value without payment.
• Read the landing page and ask if it is too long to explain the product.

If the post is restored, spend the next pass on the offer, not on more promotion.

Demo interest is a lead, not a sale

In the first 24 hours, the DDL to Data post drew demo interest but produced very few conversions. The submitter traced the gap to three blockers: a price that felt too high, a free tier that did not give enough value, and landing-page copy that was too long. Those blockers explain why a curious visitor leaves without entering an email address.

Look at the path between the demo and the signup button. People who finish the demo understand the product; people who do not sign up do not see a reason to commit. The gap usually sits in the offer, not the explanation. The landing page should stop selling once the demo has made the case, and the offer should match that moment before the visitor gets distracted.

Lowering the price means making the first action small enough for a stranger to take, not giving the product away. A useful free tier should let a user create something real, not just see a screenshot. Short copy should say what the tool does, who it is for, and what the user gets next.

For the first users, manual outreach is the work. Paid ads, referral loops, and content calendars can wait. Reply when someone tries the demo, answer questions in public, and fix the wall before you ask a user to come back.