Skip to main content

The Pre-Launch Stage: What Must Be True Before You List

Growth stages · 10 min read ·

A stage-one-to-three checklist for the weeks before you list a product: problem, audience, page, first use, measurement and a plan for the days after.

Illustration: An isometric launch pad drawn in cyan lines with a short checklist hovering above it, ticks beside each of six items

A launch is not an event that you prepare for the night before. It is the end of a short, quiet stage of work in which a handful of things are made true so that, when strangers arrive, they find something that makes sense. Skipping that stage is the most common way to waste a launch: the attention comes, the page is unclear, the first use is confusing and nobody can tell afterwards what happened.

This guide is a checklist for that stage. It is organised as six things that should be true before you list your product, in the order that tends to matter. It is written for small teams and solo makers; a larger team will have more to add.

Where this sits

On the path from idea to scale, the pre-launch stage sits between a working prototype and the public moment. You have, or nearly have, a product that does its main thing. What you do not yet have is evidence that strangers can understand it, begin using it and tell you what happened. This stage closes that gap.

You do not need to finish the product. A minimum viable product is the version with just enough features to be used by early customers who can give feedback. The test is not completeness but honesty: does it do what you say it does?

One: the problem and the person

It must be true that you can say, in one sentence, whose problem you solve and what the problem is.

Write it down: "[Product] helps [specific person] to [do something] without [pain]." If you cannot fill the blanks, the page will be vague, and readers will move on.

Check it against evidence. Customer development, the practice of getting out and learning from potential customers rather than assuming, is the habit behind this. Have you spoken to at least a handful of people who have the problem? Can you quote one of them?

Test: show the sentence to three people in your target group. If they say "yes, that is me", continue. If they look puzzled, rewrite.

Two: the audience and where they are

It must be true that you know where those people already gather, and you have a plan to reach them there.

List three places: communities, directories, newsletters, forums or events where your audience looks. Be specific: not "social media" but a named group or a particular newsletter. Read their rules about posting products. Think about what you can contribute beyond an announcement.

You do not need a large following. A small number of people who know you are launching and who will look is plenty. Tell them a week ahead, with the date and a single link.

Test: name three places and what you will post in each.

Three: the page

It must be true that a stranger can understand the product from the page in under a minute.

The page needs:

  • a headline that names what it is and who it is for
  • a first image that shows the product in use
  • two or three short lines on what it does and why that matters
  • a plain statement of the stage, such as early version or beta
  • a clear next step, with one button
  • the basics: who you are, how to contact you and, where relevant, what it costs

Cut anything that competes with those. Check the page on a phone. Make sure it loads quickly and nothing jumps around as it loads.

Test: ask someone who has not seen it to look for thirty seconds and say what the product is. If they cannot, the page is not ready.

Four: the first use

It must be true that a new person can reach the first moment of value without your help.

Onboarding is the process of guiding new users toward getting value from a product. At launch, the first-use path is the single most important part. Walk it as a stranger would.

  • Open the product in a private window, with no saved logins.
  • Sign up, if required, with a new address.
  • Follow the first steps. Where do you hesitate? Where would a stranger give up?
  • Note how long it takes to get to the first useful result, and shorten it.
  • Check that errors are written in plain language and that the empty states, what people see before they have added anything, are helpful.

Remove steps that are not essential. Where you must ask for information, say why.

Test: watch two people do it, silently, and write down every place they pause.

Five: measurement

It must be true that you will be able to tell what happened.

You need only a handful of numbers, but you need them recorded from the first visitor.

  • Source: where did visitors come from?
  • Arrival: how many reached the page?
  • Action: how many tried the product or took the main step?
  • Return: how many came back, and when?
  • Words: what did people say, and where?

Use simple, privacy-respecting analytics, and tell visitors what you collect. Set up a shared place, even a spreadsheet, where you will log the numbers each day. Decide in advance what you would count as a good result, so that you are not rationalising afterwards.

Test: make a test visit yourself, and check that it appears in your records.

Six: the days after

It must be true that you have planned the week after the launch, not only the day.

Launch attention fades quickly. What matters is what you do with it.

  • Replying: decide who answers questions and how fast.
  • Fixing: reserve time to fix the problems that appear. They will.
  • Thanking: plan a short thank-you to those who helped.
  • Following up: prepare a message for the people who signed up, with one useful tip and a way to give feedback.
  • Reviewing: set a date, about a week later, to look at the numbers and decide what to change.
  • Resting: put a day off in the calendar. A tired maker replies badly.

The related guide on the weeks after launch covers this in more detail.

Test: write the plan for days one to seven, one line each.

The honest-wording check

Before you list, read every claim on the page and ask: can I show this?

  • Numbers: where do they come from, and when?
  • Comparisons: can I back them up?
  • Promises: can I keep them?
  • Stage: does the page say what stage the product is really at?

Early products can be modest and still appealing. Readers respond well to honest wording such as "early version, built by two people, feedback welcome". They respond badly to a claim that falls apart on the first click.

Common gaps

Teams often discover the same missing pieces in the last week.

  • No way to contact you, so early feedback has nowhere to go.
  • Broken or placeholder links, especially in the footer.
  • A sign-up form that does not send a confirmation.
  • A page that only works well on the maker's own machine.
  • A description written for insiders, full of internal terms.
  • No privacy notice, though data is collected.
  • A product that has never been used by a stranger.

Each of these is quick to fix and slow to forgive.

How much is enough

Perfectionism is its own risk. At some point the checklist is done well enough, and further preparation is delay. A practical rule: if all six tests pass, you are ready. If one fails, fix it. If you are still fiddling after they all pass, you are avoiding the moment, and the best cure is to set the date and tell someone.

A worked example

A solo maker is about to list a small tool that turns meeting notes into action lists. She works down the checklist over two weeks.

Problem: she writes "helps project managers turn messy notes into a list of who does what by when". Three project managers say yes. Audience: she names two communities, a newsletter and a forum for project managers, and reads their posting rules. Page: her first headline is "Supercharge your meetings"; two testers cannot say what it does, so she changes it to the sentence above and adds a screenshot.

First use: a tester takes four minutes to find the paste box because it is below a banner. She moves it up and cuts the sign-up to an email address. Measurement: she adds a simple analytics tool and a source tag on each link, and sets up a spreadsheet. The days after: she plans one reply session each evening, a thank-you note, a follow-up email on day three and a review on day eight.

On launch day, sixty people try it, twenty-two paste notes and eleven return within a week. The numbers are modest, and she knows exactly what they mean, because she prepared to read them.

Questions makers ask

Is it better to launch early or wait until it is polished? Launch when the main thing works and the wording is honest. Polish follows feedback.

What if nobody comes? That is information. Check the page, the audience and the message, and try again with one change.

Do I need a mailing list? Not required. A few people who know you are launching is enough.

Can I list while still in beta? Yes, if you say so.

Summary

Before you list, make six things true: you can name the person and problem, you know where that person gathers, the page makes sense in under a minute, a stranger can reach first value without you, you can measure what happens and you have planned the days after. Test each one with real people, check every claim honestly and stop when all six pass. The pre-launch stage is quiet work, and it decides whether the launch teaches you anything.

Questions and answers

How early should I prepare for a launch?
A few weeks is enough for a small product: time to test the page, the first use and the measurement, and to prepare for the days after.
Do I need a finished product to list it?
No. You need something that works for its main purpose and honest wording about its stage.
What is the most common pre-launch mistake?
Describing the product vaguely, so that visitors cannot tell what it does or who it is for.
Should I build an audience before launching?
Having a few people who know you are launching helps, but a large audience is not required.
What should I measure at launch?
Where visitors come from, how many try the product and how many return, at a minimum.

Sources

Related guides

Support