# The launch thread should teach the product before the homepage does > Why Loom used Product Hunt as the real launch room: concentrated comments, a sharper first page, use-case-rich maker notes, personal video replies, repeat launches, and a tiny tagline people could retell. - Canonical HTML: https://growth.iangoh.com/blog/the-launch-thread-should-teach-the-product-before-the-homepage-does/ - Published: 2026-06-07 - Updated: 2026-06-07T04:11:58.000Z - Categories: launches, community-led growth, brand trust - Niches: SaaS, Collaboration software, Creator tools, AI products, Developer tools ## On this page - Put the first wave where the conversation can compound - The thread has to win the skeptic click first - Use the first comment to teach the job, not flatter the release - Replies can become product demos - Launch again when the story gets better ## Start with these related tactics - [Loom Product Hunt post before homepage spike](/growth-ideas/loom-product-hunt-post-before-homepage-spike/): Send the first launch-day wave into the Product Hunt post instead of the homepage when the goal is feedback density, visible trust, and public conversation around a new workflow. - [Loom first launch page gets the skeptic click](/growth-ideas/loom-first-launch-page-gets-the-skeptic-click/): Build the Product Hunt page so a skeptic can decide to click through from the post itself, with a sharp page, tight screenshots, and just enough detail to invite the next action. - [Loom first comment links use cases not release notes](/growth-ideas/loom-first-comment-links-use-cases-not-release-notes/): Use the first maker comment to show concrete use cases and what changed, not to dump a changelog that only the team understands. A lot of launch teams still treat the community thread like a traffic ramp. That is backwards when the product is new, easy to misunderstand, and still missing borrowed trust. The thread is often the first real product page people believe, because it shows the room reacting in public. The launch thread should teach the product before the homepage does. ## Put the first wave where the conversation can compound [Loom Product Hunt post before homepage spike](/growth-ideas/loom-product-hunt-post-before-homepage-spike/) is the core move. Shahed Khan said they chose to launch on Product Hunt, not on their own site, because they wanted the engagement on the post itself. That gave Loom 3,000 signups in the first 24 hours, but the bigger point is what the next visitor saw: comments, rankings, maker presence, and social proof in one place. I would read that beside [Product Hunt no waitlist on launch day](/growth-ideas/product-hunt-no-waitlist-on-launch-day/) and [the first customers should leave fingerprints on the product](/blog/the-first-customers-should-leave-fingerprints-on-the-product/). The pattern is the same. Do not make the highest-intent room do unnecessary translation work. ## The thread has to win the skeptic click first [Loom first launch page gets the skeptic click](/growth-ideas/loom-first-launch-page-gets-the-skeptic-click/) and [Loom one-click tagline before the demo loads](/growth-ideas/loom-one-click-tagline-before-the-demo-loads/) belong together. Loom understood that a Product Hunt post is a sorting surface, not a storage bin for every detail. The clear page, the screenshots, and the tiny one-click promise all helped the reader picture the workflow before a homepage or full demo had to rescue the explanation. That is close to [Product Hunt first comment as positioning asset](/growth-ideas/product-hunt-first-comment-as-positioning-asset/). If the first public surface needs a paragraph to explain why the product exists, the product story is probably still loose. ## Use the first comment to teach the job, not flatter the release [Loom first comment links use cases not release notes](/growth-ideas/loom-first-comment-links-use-cases-not-release-notes/) is my favorite move in the batch because it is so easy to miss. Loom used later first comments to explain what changed and to link people to use cases. That turns the comment into a second product layer. People who are still unsure can keep learning without leaving the thread. This works especially well for collaboration tools, AI products, and anything that feels obvious only after one concrete workflow. I would pair it with [Miro Marketplace visuals teach the workflow not the logo](/growth-ideas/miro-marketplace-visuals-teach-the-workflow-not-the-logo/). Different surface, same discipline: explain the work, not the category. ## Replies can become product demos [Loom video replies turn commenters into allies](/growth-ideas/loom-video-replies-turn-commenters-into-allies/) shows the nicer version of launch hustle. Instead of only replying in text, Loom sometimes answered people with Loom videos. The reply became proof that the product worked, proof that the team was paying attention, and a little bit of theater that commenters were happy to remember. That is stronger than generic community management. It is closer to [GitHub Discussions pin start-here and release threads](/growth-ideas/github-discussions-pin-start-here-and-release-threads/) or [Substack Chat invite post with permission explainer](/growth-ideas/substack-chat-invite-post-with-permission-explainer/). The room becomes useful when people can tell the maker is actually inside it. ## Launch again when the story gets better [Loom repeat launches for pivots and new angles](/growth-ideas/loom-repeat-launches-for-pivots-and-new-angles/) is the reminder most founders need. The first launch is not sacred. Loom kept coming back as the positioning sharpened and the product changed. Product Hunt's own coverage later described Loom as a community favorite with two Golden Kitty Awards and 19 total badges. That is what happens when the room remembers you for more than one day. This cluster is strongest for SaaS launches, collaboration tools, creator tools, AI products with a public workflow demo, and any startup that still needs to borrow trust from a room full of early adopters before the homepage can carry the story alone. If you want help tightening launch rooms, trust surfaces, and product stories that people can actually repeat, the advisory CTA is here: [work with Ian Goh](https://iangoh.com/advisory). ## Related GrowthDex tactics - [Loom Product Hunt post before homepage spike](/growth-ideas/loom-product-hunt-post-before-homepage-spike/) - Product Hunt, Community, Launches - [Loom first launch page gets the skeptic click](/growth-ideas/loom-first-launch-page-gets-the-skeptic-click/) - Product Hunt, Landing pages, Conversion - [Loom first comment links use cases not release notes](/growth-ideas/loom-first-comment-links-use-cases-not-release-notes/) - Product Hunt, Content, Community - [Loom video replies turn commenters into allies](/growth-ideas/loom-video-replies-turn-commenters-into-allies/) - Product Hunt, Community, Video - [Loom repeat launches for pivots and new angles](/growth-ideas/loom-repeat-launches-for-pivots-and-new-angles/) - Product Hunt, Launches, Brand - [Loom one-click tagline before the demo loads](/growth-ideas/loom-one-click-tagline-before-the-demo-loads/) - Product Hunt, Messaging, Conversion ## Essay chronology - [Newer essay: The platform wins when creators can build the next shelf](/blog/the-platform-wins-when-creators-can-build-the-next-shelf/) - creator economy, community-led growth, marketplaces - [Older essay: The unfinished game should give players something to show](/blog/the-unfinished-game-should-give-players-something-to-show/) - gaming, community-led growth, product-led growth ## Keep reading - [The Show HN thread should finish the first technical conversation](/blog/the-show-hn-thread-should-finish-the-first-technical-conversation/) - community-led growth, brand trust, launches - [The launch thread should look alive before it looks popular](/blog/the-launch-thread-should-look-alive-before-it-looks-popular/) - launches, community-led growth, brand trust - [The product should keep a visible pulse](/blog/the-product-should-keep-a-visible-pulse/) - developer marketing, launches, brand trust ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path ## Sources - [Product Hunt: How Loom’s bet on Product Hunt paid off](https://www.producthunt.com/stories/how-loom-stood-out-from-the-rest-and-thrived-on-product-hunt) · [GrowthDex source hub](/sources/product-hunt-how-loom-s-bet-on-product-hunt-paid-off-producthunt-com/) - [Product Hunt: How Loom grew its user base after its Product Hunt launch](https://www.producthunt.com/stories/how-loom-grew-its-user-base-after-its-product-hunt-launch) · [GrowthDex source hub](/sources/product-hunt-how-loom-grew-its-user-base-after-its-product-hunt-launch-p/) - [Forbes: Nearly-Broke To $1.5 Billion: How They Built Loom And Grew It To 14 Million Users](https://www.forbes.com/sites/stevenli1/2022/03/14/nearly-broke-to-15-billion-how-he-built-loom-and-grew-it-to-14-million-users/) · [GrowthDex source hub](/sources/forbes-nearly-broke-to-1-5-billion-how-they-built-loom-and-grew-it-to-14/) - [Product Hunt: Loom product page](https://www.producthunt.com/products/loom) · [GrowthDex source hub](/sources/product-hunt-loom-product-page-producthunt-com/) ## Editing notes - Kept the essay on one plain claim: the launch thread is a teaching surface, not a traffic ramp. - Used Loom-specific details like 3,000 first-day signups, first-comment use cases, personal video replies, and repeated Product Hunt launches instead of generic launch advice. - Linked the argument to existing Product Hunt, Miro, GitHub Discussions, and Substack tactics so the piece reads like one operating system for public rooms. - Cut startup-theater language and ended on the kinds of products where community launch threads can genuinely change trust. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.