The post everybody writes
Open any launch week and the posts are interchangeable. We are excited to announce.
We have been heads-down for eighteen months. We think this changes how teams do the thing. We would love for you to try it.
Ben Horowitz described the same template from the investor side, where it takes the form of a partner explaining that they met a great founder, went on a walk, called him eight times and eventually convinced him to take the money.
His verdict on both versions was that they are the lamest story in the world, and his list of what is wrong with them is worth keeping: fake bragging, boring, egocentric, passive aggressive, and to no purpose.
The one that matters most is the last one he added. It is indistinguishable. Everybody can gaze at their own navel, there is nobody who cannot do that, so it is not a differentiated story.
Why self-description carries no information
A post about your company asks the reader to already care about your company. On launch day most of them do not, which is the entire problem a launch exists to solve. You have opened by requesting something the reader has not yet agreed to give.
There is a mechanical version of the same point. Ranking systems on X read the first stretch after posting, and a reader deciding whether to keep going gives you about a second.
A claim about the world can be evaluated in that second by somebody who has never heard of you. A claim about your company cannot, because its significance depends on context the reader does not have.
So the generic launch post fails twice over: it is filtered before quality is assessed, and it would have been interchangeable even if it had been read.
The move
Marc Andreessen put the alternative in one sentence, and it is the most useful thing in the whole conversation. The story of you and your startup is not inherently interesting, but there is almost certainly an interesting story that involves your startup.
That story is something else happening in the world that is genuinely interesting, which your company relates to.
The shift is small to describe and hard to execute. You are no longer announcing a product. You are explaining a change that a reader can use whether or not they ever buy from you, and your product appears as the part of that change you happen to have built.
The clearest working example
a16z named Alex Karp as the practitioner who does this best, and the observation is easy to verify. Watch his interviews and he barely mentions Palantir.
He talks about the world: institutions, the West, what software does to state capacity, which side of an argument he is on. The company arrives as the consequence of a worldview rather than as the subject.
The result is that people who have no interest in buying enterprise software still watch, still form a view, and still know exactly what the company is for.
That is what a story built outside-in buys you. The audience is everyone interested in the subject, which is always larger than the audience interested in a vendor.
The objection, and why it inverts
Founders resist this, and the resistance is consistent enough to be predictable. It feels presumptuous.
Who are we to go and explain some bigger thing? Are the people who tell a bigger story not just making themselves look important?
The truth runs the other way, and it is worth sitting with. Writing about yourself is the egocentric option, and readers experience it exactly that way.
Explaining a change you can see clearly, in a way that leaves the reader better informed, gives them something before you ask for anything. That is the generous version, and it happens to be the one that works.
Company size has no bearing on it. Nobody has to earn the right to explain something they understand. A twelve-person company that has been living inside a problem for two years usually understands that problem better than anyone writing about it from the outside.
Details are the whole proof
Horowitz added a constraint that stops all of this collapsing into vagueness. Good storytellers have great details, and details matter a lot. The reason the generic post is so weak is that it contains none: no numbers, no names, no observed behaviour, just an assertion of significance.
A bigger story told without details becomes a worse problem than the self-description it replaced, because now you are making sweeping claims about the world and offering nothing to check them against. The detail is what converts a thesis into something a reader can believe.
The reliable test for both halves is the same. Ask whether a competitor could have published your sentence. Anything true of every vendor in your category is filler that happens to be about you.
How to find yours
Start from the outcome
a16z's own framing is to work backwards. Decide who has to believe something different by the end, whether that is an enterprise buyer, an engineer you want to hire, or an investor tracking the category. Everything true about your company is still true, and only some of it is relevant to the person you named.
Name the change, not the feature
The story sits one level above your release notes. Something is now possible that was not, or something everyone assumed is turning out to be wrong, or a cost that used to be fixed has collapsed. Your product is the proof, and the proof goes second.
Pick a position you would defend at 9pm
A story about the world implies a view, and a view attracts disagreement. Planting a claim and retreating the moment somebody takes it up is worse than never planting it, because the retreat becomes the story.
Then narrow it to one sentence
The frame is what this page is about. The claim inside the frame is a separate discipline, and it has its own failure modes, covered in launch narrative design.
Once both are settled, how to write an X post covers the shape the thing takes on the page, and launch conversation design covers how to leave people something to reply to.
Questions we get asked
Why does our launch post get ignored when the product is good?
Because a post that describes the company asks the reader to already care about the company, and most of them do not yet. Every company on earth can describe itself, so self-description carries no information and reads as interchangeable. The version that travels puts a change in the world first and lands the company inside it as the evidence.
Is telling a bigger story arrogant for a small company?
It runs the other way. Writing about yourself is the egocentric option, and readers experience it that way.
Explaining something happening in the world that a reader can use, and showing where your company sits within it, gives the reader something before it asks for attention. Size has no bearing on whether you are allowed to explain a change you can see clearly.
How do we know if our launch narrative is specific enough?
Ask whether a competitor could have published the same sentence. Anything true of every vendor in your category is filler.
The reliable test is detail: a real number, a named constraint, a specific behaviour you observed. Generic posts fail because they contain nothing that could only have come from you.