A launch platform can give you feedback, a backlink and a short burst of attention. It cannot choose your audience or build a repeatable way to reach them. Recent Hacker News discussion makes the distinction well: Show HN can work for products that are instantly usable and fit its technical audience; the same mechanics can be irrelevant for a very different buyer.
A launch has three jobs
- Feedback: learn what people misunderstand or want next.
- Proof: collect a real example, testimonial or insight.
- Distribution: build a path that keeps working after the post falls off the front page.
Most teams complete the first two and assume they completed the third. They did not.
Match the room to the product
Before you launch, describe the community in one sentence. What does it reward? What kind of evidence does it trust? What can a person try without creating an account? A developer community may reward a live demo, technical detail and a direct story. A buyer community may need an outcome, a peer example and a lower-risk first step.
The two-week launch companion plan
| Before | During | After |
|---|---|---|
| Talk to 10 potential users and write down their language. | Ask one specific question and reply honestly to every useful response. | Turn objections into product changes, documentation and follow-up content. |
| Prepare a way to capture interest. | Give people a small thing they can try immediately. | Return to the communities where the conversation started. |
What a launch should leave behind
- A clearer positioning sentence
- Three objections you can address on the page
- One small customer segment worth serving first
- A follow-up asset: guide, demo, template or case note
- A reason for the next person to find you without the launch post
Launch platforms are worth using when their audience overlaps your earliest users. Treat them as a research event. Build ongoing distribution somewhere your customers already return to.
