If somebody sent you this, they were probably being helpful rather than critical. Most launches that underperform were fine as products and unready as claims, and the difference shows up in questions like these weeks before anyone writes a post.
Nothing here needs an agency, a budget or a tool. Answer honestly, in your own words, and count the blanks.
The claim
1. Can you say what changed in one sentence?
A strong answer is a single sentence a technical stranger could disagree with, containing no adjectives doing load-bearing work. A weak answer needs a paragraph, or arrives as a list of features.
If you cannot compress it, the launch has more than one story in it and both will land at half strength. The compression method is in launch narrative design.
2. Could a competitor publish that same sentence?
A strong answer is no, and you can name why. A weak answer is any sentence that would be true of every vendor in your category.
Faster, smarter, more accurate and enterprise-ready are all true of everybody, so they carry no information. This is the single most common failure and it is fixable in an afternoon.
3. What specific detail proves it?
A strong answer is a number, a named constraint, or a behaviour you observed and nobody else has published. A weak answer is a claim of significance with nothing underneath it.
Detail is what converts an assertion into something a reader can check, and its absence is why generic posts feel like advertising even when the underlying work is real.
The audience
4. Who specifically has to see this?
A strong answer is a named, countable group: platform engineers evaluating orchestration tooling, heads of AI at insurers, technical founders who have hit the same wall. A weak answer is developers, or founders, or the market. If the group cannot be counted, the creator set cannot be chosen and reach cannot be modelled in advance.
5. Where do those people already spend attention?
A strong answer names the accounts, communities or publications they read now, and you can list several without looking. A weak answer is a channel name.
Knowing it is X does not tell you whose feed, and the whose is the entire question. The reasoning behind that is in our thesis.
The mechanics
6. Is the date set for a distribution reason?
A strong answer ties the date to when your audience is reachable and what else is happening that week. A weak answer is that it is when engineering finishes, or when the board meets.
Ship when it is done and launch when it will land, and treat those as two decisions. Choosing the date covers the day and the hour.
7. Who is posting, and is it a person?
A strong answer names an individual with a real account and a reason to be believed. A weak answer is the company account alone.
Personal accounts outperform brand accounts on reach and on trust, and a launch carried only by the logo starts from the weakest position available. The mechanics are in founder-led marketing.
8. What can a reader do in the first minute?
A strong answer is a link that leads somewhere usable without a call, a demo they can run, or a repository they can clone.
A weak answer is a waitlist with no indication of when. Attention on launch day is perishable, and a reader who wants to act and cannot will not return when you are ready.
After the day
9. What happens on day two?
A strong answer is a plan for the following fortnight: the replies you will answer, the follow-up posts already drafted, the questions you expect and who handles them. A weak answer is that the launch is the plan.
Most of the value of a launch arrives after the day itself, and it arrives only for teams who are still there. The checklist covers T+1 to T+14 in order.
10. What is your baseline, recorded before you launch?
A strong answer is a written record of current weekly signups, traffic, follower count and inbound, captured before anything goes out. A weak answer is that you will look at analytics afterwards.
Without a baseline you cannot say what the launch moved, and every number you report later will be arguable. Attributing signups to a launch covers what to record.
How to read your answers
| Clear answers | What it means | What to do |
|---|---|---|
| 8 to 10 | Ready. The claim holds and the mechanics are in place. | Book the date and build the calendar backwards from it. |
| 5 to 7 | The plan is fine and the story is not. Usually questions 1 to 3. | Keep the date. Spend a week on the claim before anything else. |
| Under 5 | The launch would consume an audience you cannot get back. | Move the date. Two weeks now is cheaper than a relaunch. |
Question 3 fails more often than any other, and question 10 is the one teams regret. The detail is what makes the claim believable, and the baseline is what lets you prove anything afterwards. Both take under an hour and both are almost always skipped.
On moving a date: the cost is lower than it feels. A launch that lands flat spends the audience you would have reached with the corrected version, because the same people rarely give full attention to the same company twice in a quarter. Two weeks of narrative work is the cheaper trade nearly every time.
Questions we get asked
How do we know if our product launch is ready?
Readiness is a property of the claim rather than the code. If you can state in one sentence what changed, name the specific detail that proves it, name the group who has to see it, and say what a reader can do in the first minute, you are ready. If three or more of the ten questions on this page have no clear answer, the date is the problem rather than the plan.
Should we move the launch date if we are not ready?
Usually yes, and it costs far less than people assume. A launch that lands flat consumes the audience you would have reached with the corrected version, because the same people rarely pay full attention to the same company twice in a quarter. Two weeks spent fixing the claim is cheaper than a wasted launch and a warmed-over relaunch.
What is the most common reason a launch underperforms?
A claim that any competitor could have published. Announcements that are true of every vendor in a category carry no information, so a reader who has seen forty of them recognises the pattern in seconds and moves on. The post is filtered before its quality is ever assessed, which is why the specific detail matters more than the wording.