Back to the journal

Indie software

The launch URL that still works on the Wednesday after Product Hunt

Product Hunt is a holiday. The product is a weekday. Keep one hub — waitlist, app, changelog, status, price — and paste that slug in the listing, the README, and the App Store field.

October 30, 20264 minLinkForge Editorial

Product Hunt is a holiday: a ranking, a comment thread, a spike. Your product is a weekday. If the only public URL in your bio, your README, and your App Store marketing field is the Product Hunt listing, you disappear on Wednesday when that page is an archive. People who bookmark “the launch” land on a graveyard and assume you did too.

The launch hub outlives the holiday. Waitlist, then the app, then a changelog, a status sentence, and a price. The same slug goes in the PH description, the launch tweet, the README, and the store listing. You change which button is first. You do not change the address every time a directory wants a link.

Buttons that match the phase

Pre-launch. Button one: waitlist, with what they are waiting for and that you will not spam a weekly newsletter unless they asked. Button two: a proof that the thing exists (a screenshot page, a short demo video, a founder note). The waitlist mechanics are a form that survives old posts.

Launch day. Button one can be the Product Hunt listing for that day, button two the app, if you truly want the ranking click. Say so in the label (“Upvote on Product Hunt — launch day”). Do not leave that order up in December.

The week after. Button one: open the app or start the trial. Button two: changelog. The PH link moves to a quiet “as seen on launch day” or disappears. Nostalgia is not a call to action.

The rest of the year. Button one: the product. Beside it: pricing, changelog, status. If you are down, the status sentence is the hero until you are not. A cheerful “get started” during an outage is how you collect one-star reviews from your own fans.

Ship the hub before you press publish on PH. Put it in the listing’s website field so the PH page itself points at something you will still update. Free is five links, which matches the set above. Pro at 7€/month is get.yourapp.com with SSL — the hostname you can say out loud.

Changelog as a trust object

Indie buyers are often other builders. They can smell a “coming soon” that has been coming since last spring. A dated changelog, even five lines a week (“Tuesday: fixed CSV export for EU dates”), beats a roadmap illustration. Link the full log if it lives in the repo or in a docs host. On the hub, show the latest entry in text so a person who will never open GitHub can see that a human shipped recently.

Write what you will not build, once, if the comments keep asking. “No mobile app this year” saves you a support macro.

Price, currency, and the surprise at checkout

State the currency. If you sell globally, “$12” and “€12” are different promises. Say whether tax is extra. A surprise VAT line is a refund. The same plainness coaches need is stating the currency on the page. Software does not get an exemption because the buyer is technical.

If there is a free tier, say what it cannot do. If there is a trial, say how many days and whether the card is required today. The hub’s sentence and the billing page’s sentence must match. PH commenters will quote whichever is more generous and then demand it.

Status without a status-page company

Until you are large enough to need a hosted status product, a sentence is enough: “API up. EU region. Last incident: 2 March, 40 minutes, exports delayed.” Update it when it is false. Delete the incident line after it is ancient, or move it to the changelog. Fake “all systems go” widgets are worse than a sentence, because they imply a monitoring desk you do not have.

Security reports do not go in the PH comments and do not go on the public hub’s form as a bug report mixed with feature ideas. Put an email on the page: security@ or the address you actually read. The stricter version of this split is a maintainer hub. Even a closed-source tool owes a private door for vulnerabilities.

README, landing page, and hub

The marketing site can be a full landing page on another host. The README is for people who clone. The hub is the object you paste when a bio, a badge, or a directory gives you one field and your fancy site is mid-redesign. Duplicate the one-line description everywhere. Do not duplicate the entire architecture diagram onto the hub. Link the docs.

If the landing page and the hub disagree on price, you will be judged by the cheaper one. Pick a source of truth — usually the billing page — and make the hub quote it.

The day after the ranking

Read the comments, fix the one bug they all hit, write it in the changelog, and point the hero at the app. Mail the waitlist with the hub URL and the button name. Do not mail them a PH link three days late. Look at taps: if everyone still hits Product Hunt and nobody hits the app, your order is stuck in launch day. Change it.

Leave the hub URL in the store listing and the README even when you are bored of it. The holiday ends. The slug is how Wednesday’s user finds the weekday product.

Create my page — Pro is 7€/month (~$7)

Free to start. Pro is 7€/month (~$7 depending on exchange) for a custom domain and full SEO controls.