A launch post is the short piece of writing that sits above your product on a directory or community feed and has to convince a stranger, scrolling fast and comparing you to a dozen other posts on the same page, to stop, click, and leave a comment before they move on. Most launch posts fail not because the product is weak but because the post reads like a press release nobody asked for: adjectives instead of proof, a screenshot instead of a demo, and a founder who disappears after hitting publish. This is the anatomy of a launch post that gets upvotes and comments, the exact first two lines that work, what to show instead of tell, how to talk about pricing without hiding it, how to ask for feedback without begging for it, how to reply in the first few hours, what gets ignored no matter how good the product is, a copy paste template you can adapt in ten minutes, and how the same launch needs a different post on every surface it appears on.
Key takeaways
- ▸The first two lines do all the work. If they do not state who the product is for and what changes for them, nothing below matters.
- ▸Proof beats adjectives every time it can be measured. A number, a before and after, or a real screenshot outperforms any claim of being powerful or seamless.
- ▸Your demo has to work with the sound off and the video not clicked, because that is how most people will actually see it.
- ▸Hiding your price in a launch post reads as a warning sign, not a strategy. State it plainly and let the value case do the persuading.
- ▸The founder comment is not optional. A launch post with no reply from the founder in the first hour looks abandoned, and abandoned posts do not get upvoted.
- ▸Asking for feedback works when it is specific and costs the reader ten seconds. Asking for feedback in general costs them nothing to ignore.
What a launch post actually has to do
A launch post is a piece of persuasive writing with one job: turn a stranger's two seconds of attention into a click, and turn that click into an upvote or a comment before they leave the page for good.
It is not a press release, an about page, or a pitch deck slide. Those documents are written to be complete and neutral, covering every feature and every audience so nobody can accuse you of leaving something out. A launch post has the opposite job. It has to be incomplete on purpose, cutting everything except the one thing that makes a specific reader care, because the reader is scrolling a feed full of other posts making the same bid for their attention.
Every launch surface, whether it is a directory listing, a community thread, or a social post linking to your product, compresses your entire pitch into a headline, one or two lines of body copy, and a piece of media. If any one of those three pieces fails to earn the next second of attention, the reader never reaches your actual product page, and no amount of quality inside the product will save the launch.
The mistake most founders make is writing the launch post last, as an afterthought after weeks of building the product, and it shows. The post reads like a summary of features instead of an argument for why a specific person should care today. Treat the launch post itself as a piece of product you are shipping, worth the same iteration and testing as your onboarding flow.
The first two lines decide everything
The first two lines of a launch post are read by everyone who sees it and the rest of the post is read by almost no one, which means those two lines carry more weight than the remaining three paragraphs combined.
The winning shape is consistent across almost every launch post that gets real engagement: line one names who the product is for and the specific problem, line two states the concrete change that happens once they use it. "For freelance designers who bill hourly, timesheets are the least favorite part of the job. This turns your Slack messages into an invoice in ten seconds" does more work than three paragraphs of feature description, because it lets the right reader recognize themselves immediately.
Compare that to the far more common opener: "Excited to finally launch something I've been working on for months." This line is true for the founder and irrelevant to the reader. It tells the reader nothing about whether the product solves their problem, and it uses up the only two lines guaranteed to be read on a sentence about the founder's feelings instead of the reader's problem.
A useful test before you publish: cover everything after your second line and ask a person unfamiliar with the product to describe who it is for and what it does. If they cannot answer both from the first two lines alone, rewrite until they can, because everything after that point is optional reading, not required reading.
Rule of thumbRead your first two lines out loud with nothing else visible. If they do not name a specific reader and a specific change, nothing else in the post gets read.
Proof over adjectives, every single time
Proof is a fact a reader can check or picture, and an adjective is a claim a reader has to take on faith, which is why a launch post built on adjectives gets scrolled past while one built on proof gets clicked.
Words like powerful, seamless, revolutionary, and game-changing describe how the founder feels about the product, not what actually happens when someone uses it. A reader cannot picture "powerful," but they can picture "exports a filed tax return in one afternoon" or "cuts your first response time from four hours to four minutes." The second kind of sentence is checkable, and checkable claims are the ones that make a skeptical reader lean in rather than scroll past.
The fix is mechanical: go through your draft and circle every adjective that is not attached to a number, a name, or a concrete outcome. For each one, ask what specific thing you actually meant, and replace the adjective with that thing. "Blazing fast onboarding" becomes "live in under five minutes, no credit card." "Incredibly accurate" becomes "matched a human reviewer on 940 of 1,000 test tickets."
This also matters for who reads your post later. A community full of comments quoting a specific number back to you, like "wait, four hours to four minutes, really," is a launch post working exactly as intended: it gave people something concrete enough to repeat.
Demo media that survives muted autoplay
Muted autoplay is the default way most people will encounter your demo, scrolling a feed where video plays automatically without sound and without the viewer ever tapping play, which means a demo that depends on narration or sound effects to make sense is invisible to most of your audience.
Design the first three seconds of your demo to communicate the core value with zero audio and zero prior context. Show the before state, show the action, show the after state, in that order, with on-screen text if needed to label what is happening. If someone watches only three seconds with the sound off, they should still understand roughly what the product does and for whom.
A common failure is opening a demo video with a logo animation, a founder's face saying hello, or a slow fade into a dashboard. Every one of those seconds is a chance for the viewer to scroll past before they have seen anything that matters. Cut straight to the moment the product does the thing it exists to do, and put the logo and framing at the end, where it costs you nothing if the viewer has already left.
A short looping GIF or a fifteen to twenty second clip that shows one complete before-and-after cycle usually outperforms a polished two-minute walkthrough, because it fits the attention span of someone scrolling rather than someone who has already decided to evaluate you. Save the longer walkthrough for the product page itself, where the reader has already clicked and is looking for more depth.
Screenshots that show real data, not a polished mockup
A screenshot in a launch post is doing the job of proof, and a screenshot filled with obviously fake placeholder data, generic lorem ipsum, or an unnaturally clean dashboard undercuts that job the moment an experienced reader notices it.
Real, slightly messy data reads as more trustworthy than a pristine mockup, because most readers on launch communities have shipped products themselves and can tell the difference between a real interface and a polished rendering built for the post. Use your actual product, with realistic names, realistic numbers, and the kind of visual imperfection that comes from a tool that is actually being used rather than staged.
If your product's core value is invisible in a static image, for example a background automation or an API, show the result of the automation instead of the automation itself. A before and after pair of screenshots, an inbox with forty unread support tickets next to the same inbox at zero, communicates more in one glance than any description of the underlying technology.
Pricing transparency instead of pricing hide and seek
Pricing transparency in a launch post means stating what the product costs plainly in the post or the first reply, and pricing hide and seek means making a reader click through two or three pages to find a number, which almost always reads as a signal that the price is worse than expected.
Launch audiences are unusually price-sensitive and unusually willing to say so in a comment, which means an evasive pricing answer gets called out publicly far more often than it would on a normal marketing channel. If your pricing page is a maze, or your post avoids the topic entirely, the first comment is often someone asking "how much," and a slow or vague answer to that question costs you more credibility than an honest number would have.
State the price, or the starting price and what it includes, directly in the post or pin it as the founder's first comment. If you are free during launch, or offering a launch-specific discount, say so explicitly with the actual number rather than "special launch pricing," because a vague promise of a deal reads as a marketing trick while a specific number reads as a real offer.
If your pricing genuinely is complex, for example usage-based billing that depends on volume, give a concrete example instead of a formula: "a team sending 5,000 emails a month typically pays about $80." A worked example does more to build trust than a technically accurate but unreadable pricing table.
The founder comment: why it is not optional
The founder comment is the reply a founder posts underneath their own launch, usually within minutes of it going live, and skipping it is one of the most common reasons an otherwise good launch post gets almost no engagement.
A launch post with no visible founder presence reads as abandoned, and people are far less willing to be the first comment on something that looks abandoned than the fifth comment on something that already has a conversation going. The founder comment breaks that silence immediately and gives the post its first sign of life.
A good founder comment does three things in a short space: it adds one piece of context that did not fit in the post itself, usually the why behind building the product or a specific customer story, it says something honest about what is not finished yet, and it asks one specific question the founder genuinely wants answered. Honesty about limitations is counterintuitively persuasive here, because a founder who admits what does not work yet reads as more credible than one who claims everything is perfect.
Post the founder comment the moment the launch goes live, not an hour later. The earliest comments set the tone for every comment that follows, and an empty comment section for the first hour is the single easiest engagement problem to avoid.
Rule of thumbDraft your founder comment before launch day, the same way you draft the post itself. Do not write it live under time pressure.
Asking for feedback without begging for it
Asking for feedback without begging for it means posing one specific, answerable question instead of a generic plea, because a generic plea like "would love your feedback" gives a reader nothing to respond to and costs them nothing to skip.
"Let me know what you think" is easy to ignore because answering it requires the reader to do all the work of deciding what is worth mentioning. "Does the three-step setup make sense, or would you expect a fourth step for connecting your calendar" is easy to answer because it hands the reader a specific decision to react to, and reacting to a specific decision takes ten seconds instead of five minutes of unprompted thinking.
The best feedback questions come from a genuine open decision inside the product, something the team is actually unsure about, rather than a manufactured question designed to look humble. Readers can tell the difference between a founder who is actually curious and a founder performing openness for engagement, and only the first version reliably gets real answers.
Avoid stacking more than one question in a launch post. A single specific question gets answered. Three questions at the end of a post read as a survey, and most readers respond to a survey by answering none of it.
The replying strategy for the first few hours
The first few hours after a launch post goes live are when the algorithm on most launch platforms decides how much further reach the post gets, which means how you reply in that window matters as much as what you wrote in the post itself.
Reply to every comment individually rather than posting one general thank-you at the end of the day. A specific reply, even a short one, signals to both the commenter and anyone reading later that the founder is actually present and actually listening, which encourages the next person to comment too.
Answer the actual question asked before adding anything else. If someone asks how the product handles a specific edge case, answer that edge case directly in the first sentence of your reply, then add context if there is room. Burying the direct answer under three sentences of enthusiasm reads as evasive even when it is not.
When a comment is critical or skeptical, resist the urge to be defensive. A calm, specific response to a tough question, especially one that concedes a fair point, tends to get more upvotes on the comment thread than a purely positive comment does, because it shows the founder can handle friction in public without deflecting.
Set aside a real block of time, not a few minutes between meetings, for the first three to four hours after launch. This is the highest leverage window of the entire launch, and treating it as a background task rather than the main event of the day is one of the most common regrets founders report afterward.
What gets ignored no matter how good the product is
Certain launch post patterns get ignored consistently regardless of the quality of the underlying product, because the pattern itself, not the product, is what a scrolling reader reacts to first.
A wall of features with no clear who or why gets ignored, because a reader cannot tell in two seconds whether any of the ten bullet points apply to them. A post that opens with the founder's personal journey before mentioning what the product does gets ignored, because the reader arrived looking for a solution to a problem, not a biography. A post with no media at all, just text, gets ignored on any platform where scrolling is visual, because there is nothing for the eye to stop on.
Asking people to upvote directly, with language like "please support us" or "every upvote helps," tends to backfire on communities that value organic reaction, because it reframes the interaction as a favor to the founder rather than a genuine response to something interesting, and experienced community members notice the difference and sometimes call it out.
A launch post that copies the structure and even some of the phrasing from a wildly successful unrelated launch also tends to underperform, because readers who frequent these communities see many launches and recognize a templated pitch even when the product behind it is genuinely different and interesting.
A copy paste template you can adapt in ten minutes
This template gives you a working structure to fill in rather than a blank page, which is usually the fastest way to get from zero to a publishable launch post.
Line 1 (who and problem): "For [specific role or group], [specific painful task] is [specific cost, in time or money or frustration]."
Line 2 (the change): "[Product name] turns [that task] into [concrete outcome], in [specific timeframe]."
Paragraph 3 (proof): One or two sentences with a number, a before-and-after, or a real customer result. No adjectives without a fact attached.
Media: One demo clip or before-and-after screenshot pair that communicates the core value in the first three seconds with no sound needed.
Pricing line: "[Plan name] starts at [price] and includes [what matters most]. [Launch offer if any, with a real number]."
Closing question: One specific, answerable question about a real open decision in the product.
Founder comment (post immediately after publishing): One sentence of context on why you built it, one honest limitation, and the same specific question restated in your own voice.
Rule of thumbFill in every bracket with your own specifics before publishing. A template with unfilled generic language is worse than no template at all.
Adapting the same launch for a directory listing
A directory listing, the kind of card that appears in a scrollable grid alongside dozens of other products, compresses your entire launch post into a title, one line of description, and a thumbnail, which means most of your longer post has to be cut down to its single sharpest sentence.
For a directory card, lead with the outcome and the who in the shortest possible sentence, because there is no room for a second line to build context. "Turns Slack messages into invoices in ten seconds, for freelance designers" fits a card in a way a two-sentence pitch does not. Save the proof point and the pricing detail for the product page the card links to.
The thumbnail matters more on a directory than almost anywhere else, because it is the only piece of media most viewers will ever see before deciding to click. A cropped, illegible screenshot or a generic logo on a plain background wastes that space. Use the same before-and-after framing from your demo, resized and simplified until it reads clearly even at thumbnail size.
Adapting the same launch for a community thread or forum
A community thread, whether on Reddit, a Slack group, or a niche forum, rewards a longer, more conversational version of the launch post than a directory does, because the audience expects context and is more suspicious of anything that reads like an ad.
On a forum, open with the problem and your own experience of it before mentioning the product by name, since most communities have explicit or unspoken rules against posts that feel like they exist purely to sell. A version that reads "I kept losing an hour a week doing X manually, so I built a small tool to fix it for myself and figured others here might have the same problem" performs better in these spaces than the sharper, more commercial two-line opener that works on a directory.
Community threads also reward transparency about limitations even more than a launch directory does, because the audience is often technical and will ask pointed questions regardless of how the post is framed. Mentioning a known limitation up front, before someone else points it out in the comments, tends to earn more goodwill than waiting to be asked.
Ready to put this into practice?
Submit your product to LaunchLoop, get reviewed by founders in your category, and relaunch whenever you ship something new.
Submit a launch →