
Features
How to plan a launch around attention that will not restock
Launch planning spends attention that does not restock: decide what the launch is for, spend renewable channels first, and write the prediction before the date.
A launch spends attention, and attention does not restock. The people on your list can be told once. The community you belong to will forgive one announcement. A partner will introduce you to their audience a single time and then it is gone. Whatever you show those people, they have now seen.
That is the whole reason launches need planning rather than just a date. Everything else you can rerun.
What to take away
- Sort every route to an audience into two piles.
- A launch is a test with a date attached, and it deserves the same discipline as any other test.
- If you have more than one audience, do not fire them all on the same morning.
- The most likely launch outcome is neither success nor rejection.
Decide what the launch is for
Three different goals, three different plans, and confusing them is how launches end up achieving none of them.
Three Launch Goals Compared
Revenue
- Primary aim
- Orders
- Offer readiness
- Finished, real price
- Success signal
- Payment works
Learning
- Primary aim
- Find if strangers act
- Offer readiness
- Controlled exposure
- Success signal
- Readable result
Credibility
- Primary aim
- Exist publicly
- Offer readiness
- Audience over conversion
- Success signal
- Modest response OK
Revenue. You want orders. Then the offer must be finished, the price must be real, and payment has to work before anyone arrives.
Learning. You want to find out whether strangers, unprompted, will act. Then a smaller and more controlled exposure is better, because you need to be able to read the result, in the way offer testing sets out.
Credibility. You want to exist publicly so that later conversations start differently. Then the audience matters more than the conversion, and a modest response is not a failure.
Write down which one this is. Most disappointed launches were quietly graded against a goal that was never the plan.
Spend renewable channels first
Sort every route to an audience into two piles.
Renewable vs One-Shot Channels
Renewable
- Examples
- Search, ads, content, referrals
- When to use
- Test and iterate first
- Risk if misused
- Costs money, not opportunity
One-Shot
- Examples
- Mailing list, community, press, network
- When to use
- Only when offer is stable
- Risk if misused
- Gone if fired at draft
Renewable: search, ads you can keep buying, ongoing content, referrals from customers, anything that will still be there next month in roughly the same shape. Choosing among them deliberately, rather than announcing once and hoping, is the whole of the SBA's marketing and sales guidance.
One-shot: your own mailing list, a community where you have standing, a partner's audience, a press moment, a launch platform, a personal network.
Test on the renewable ones. Iterate there, where a bad week costs money but not opportunity. Spend the one-shots only when the offer has stopped changing, because a one-shot channel fired at a draft is simply gone.
The mistake this prevents is common and expensive: burning the warmest audience on the earliest version, then having to reach strangers with the good version through channels you never learned how to work.
Back-plan from a truth list, not a task list
Work backwards from the moment of exposure. The output is not a to-do list. It is a list of things that must already be true, each of which somebody has personally verified.
Truth List Before Exposure
- Real payment verified with real card
- Outsider completed full path unaided
- Failure plan and owner known
- Support reply within a day
- Refund response decided
- Ten-times demand promise break plan
- Every claim has a source
Each of those has a name next to it. "We should be fine" is not a verification.
The readiness gate that matters
Not whether you can serve the first customer. Whether you can serve the tenth as well as the first.
Can You Serve the Tenth?
Can you serve the tenth as well as the first?
Launch without cap
Cap the first group and mean it
The first customer gets your full attention because there is nothing else happening. The tenth arrives while you are handling the seventh's problem. If your delivery only works at full attention, launch is when you find out, in public, in front of the audience you cannot re-invite.
If the honest answer is that you cannot serve ten, cap it. Say the first group is limited and mean it. A cap is not weakness, it is the difference between a queue and a set of bad reviews, and it is the same discipline as designing a minimum viable offer for ten rather than for one.
Write the prediction down
A launch is a test with a date attached, and it deserves the same discipline as any other test. Before it goes out, record what you expect: how many people will see it, how many will act, and what you will do at each of three outcomes.
Write Prediction and Stop Rule
- Record expected reach and actions
- Define three outcome responses
- Set a checkable stop rule
- State what changes if threshold missed
- State what happens if second attempt same
Then set the stop rule. Not "we will see how it goes". Something you can check against reality: if fewer than a stated number act, what specifically changes, and what happens if the second attempt lands the same way.
The value of writing it down is not accuracy. You will be wrong. The value is that a written prediction turns a vague disappointment into a specific surprise, and specific surprises are the only thing you can act on.
Sequence for two readings
If you have more than one audience, do not fire them all on the same morning.
Two Readings Sequence
- Week 0Smaller, forgiving audience first
- Week 0-2Fix what breaks
- Week 2Larger audience, same offer, fixed page
Go to the smaller and more forgiving one first. Fix what breaks. Then go to the larger one two weeks later with the same offer and a fixed page. You get two readings of the same offer under different conditions instead of one blurred number, and the second one is cleaner because the obvious defects are gone.
The instinct to concentrate everything into a single day comes from wanting the day to feel like an event. Events are for you. Readings are for the business.
When nothing happens
The most likely launch outcome is neither success nor rejection. It is silence. Very few people came, and of those, almost none did anything.
Diagnosing Silence in Order
- Did anyone actually see it?
- Were they the right people?
- Did they get past the first screen?
- Did anyone almost act?
Silence is usually a distribution result, not a product result, and it should be diagnosed in that order:
Did anyone actually see it?
Were they the right people?
Did they get past the first screen?
Did anyone almost act?
Only after all four should you conclude anything about whether people want the thing.
The debrief
Within a week, while the details are still recoverable, answer four questions in writing.
What did we predict and what happened. Which channel actually produced action, as opposed to which one produced traffic. What did people say without being asked, in their own words. And what is the single change we are making before the next exposure.
One change. After a flat launch, the temptation to alter everything guarantees the next result is as unreadable as the last. Then watch what the first arrivals do over the following weeks.
Post-launch behavior answers questions launch day cannot. The third question in market validation: was the audience reachable at a sane cost?
Common questions
How far in advance should planning start?
From the longest lead time you depend on, which is almost always somebody else's calendar rather than anything you build. Work back from that, not from a round number of weeks.
Should the launch date be public?
Only once every request with a long lead time has been answered. A public date turns your asks into obligations for other people, and they remember which way that went.
What if the launch slips?
Say so, with the new date and the reason, before anyone notices. A launch that slips and announces it costs a fraction of one that slips quietly.
Is a launch to a list of fifty worth planning?
Yes, and the plan is shorter rather than absent. The prediction and the record of what you will be able to observe are the two parts people skip at that size, and they are what decide whether the launch tells you anything.
Nobody came. Do I change the product?
Not yet. Silence is a distribution result until you have ruled out reach, audience match, and the first screen. Rebuilding the product answers a question nobody asked.
In this guide
- Launch planning guide: six documents, written in a fixed orderLaunch planning guide organized around the six short documents a launch actually needs, who reads each one, and the order in which they get written.
- Is a launch planning mistake about to cost you the channel itself?Launch planning mistakes sorted by what each one costs you: the reading, the channel, the goodwill, or your ability to ship the thing you just sold.
- Launch planning examples: five launches, what each tested and what teams misreadFive real launches, Google+ to Airbnb, each paired with an invented case: what the launch actually tested, how the result was misread, and how to run your own.
- Three calendars decide whether a launch plan holds togetherLaunch planning framework built on three calendars: what must be true, what you ask people for, and what you will be able to observe on the day.
- Launch planning tools: the five records that actually matterFive launch planning tools worth naming, each judged by the records it can hold: dated conditions, asks, claims, predictions and observations.
- Launch planning trends 2027: five claims to questionThis guide doesn't forecast launch planning trends 2027; it examines five familiar claims and what would need to be true before they change your plan.
- Scoring a launch against the prediction you wrote firstLaunch planning case study: how a dated prediction, a pre-launch truth list and a channel split turned two paying customers into a readable result.







