Anatomy of a launch post, line by line

About the examples
Both posts below are constructed for this piece, not lifted from anyone. They're composites of patterns we see constantly in the channels on this site — the point is the mechanism, not a real person's bad afternoon.

Version one: the one that dies

🚀 Introducing ShipNote — the all-in-one changelog tool for modern SaaS teams!

Hey everyone! Super excited to finally share what we've been working on. ShipNote makes it effortless to keep your users in the loop with beautiful, customisable changelogs. Features include: in-app widgets, email digests, Slack integration, custom domains, and more!

We'd love your feedback. Check it out at shipnote.example and let us know what you think! 🙏

What's wrong with it

Line	Problem
🚀 Introducing…	The word 'Introducing' tells a reader this is an announcement, which is the one genre nobody has ever chosen to read. The rocket confirms it before they get to the noun.
the all-in-one … for modern SaaS teams	'All-in-one' and 'modern' are both filler. Together they describe roughly nine hundred products, so they identify none.
Super excited to finally share	Your excitement is not a reason for anyone to keep reading. It's twelve words about you before a single word about them.
makes it effortless to…	A claim with no evidence. 'Effortless' is what the landing page says; a post has to show the effort it removes.
Features include: …	Five features listed flat means no feature is important, and it reads as a spec sheet rather than a solution to anything.
We'd love your feedback	The broadest possible ask. Nobody knows what to say, so nobody says anything.
🙏	Fine in isolation, but stacked on the rocket it completes the pattern a moderator's eye is trained to catch.

Notice that none of the problems are about the product. ShipNote might be excellent. The post gives nobody a way to find out.

Version two: same product, same day

We shipped 60 features last year and our users found out about four of them.

I checked, because someone emailed asking for a thing we'd built eight months earlier. It was in the changelog. The changelog was a Notion page linked in the footer, which is the same as not having one.

So I built the version I wanted: a widget that shows a small dot in your app when there's something new, and stops showing it once they've read it. That's the whole product. It doesn't do email digests, and it doesn't do a public roadmap, because both of those turned into their own products every time I sketched them.

It's for teams who ship often enough that it's a problem. If you ship monthly, you don't need this — a page is fine.

One thing I'm unsure about: the dot is deliberately easy to ignore, and I don't know yet whether that makes it useless. If you've solved this, I'd like to hear how.

shipnote.example

Every edit, and why

1. The first line is a number and a failure
   '60 features, users found four' is concrete, slightly embarrassing, and completes a thought. It's a post you can react to before you know what's being sold.
2. The second paragraph is a story, not a description
   One specific email, one specific realisation. This is the paragraph that makes the reader believe a person is typing, and it's the one most founders cut for length.
3. The product arrives as a consequence
   'So I built' — by the time the product shows up, the reader already agrees there's a problem. Announcing first inverts this and asks for agreement you haven't earned.
4. It says what the product doesn't do, twice
   Naming the missing email digests and roadmap does three things at once: it defuses the top comment, it makes the scope legible, and it's the strongest available signal that this isn't marketing copy.
5. It disqualifies people
   'If you ship monthly, you don't need this.' Turning readers away is the most credible thing a founder can do in a launch post, and it makes everyone who isn't turned away pay attention.
6. The ask is a specific open question
   'Is a deliberately ignorable dot useless?' is answerable. 'Feedback welcome' is not. Specific questions get threads; open ones get silence.
7. One link, at the bottom, bare
   No UTM soup, no pricing page, no 'check it out'. The link is a full stop, not a call to action.

The underlying rule
Version one asks the reader to care about a product. Version two gives them something to think about and mentions that a product exists. Every edit above is a different way of doing the same swap, and it's the entire difference between the two outcomes.

The checklist version

1. Does the first line work as a standalone sentence someone would repeat?
2. Is there a number in the first three lines?
3. Does a specific thing happen to a specific person before the product appears?
4. Have you named at least one thing it deliberately doesn't do?
5. Have you told some group of readers this isn't for them?
6. Is your ask answerable in one sentence by someone who hasn't used it?
7. Is there exactly one link, and is it at the end?
8. Have you deleted the words 'excited', 'introducing', 'seamless', 'effortless' and 'game-changer'?

Doesn't admitting weaknesses hurt conversions?

On a landing page, sometimes. In a post, no — a post has to get read before it can convert anything, and the honest limitation is usually the line that earns the read. They're different jobs.

What if my product doesn't have an origin story?

Then use the first real user's story, or the specific moment you realised the existing options were bad. The requirement isn't drama, it's specificity.

Can I reuse version two everywhere?

Reuse the structure, rewrite the opening for each place. The same first line rarely works in two different rooms, and identical text posted in several communities is the pattern spam filters look for.