What must be ready before real people use it, for the launch you plan.
In Founder mode, open BUILD in the founder sidebar and choose Launch Preparation. It answers what needs to be ready before you put the product in front of real users. It comes after Product & MVP and Technology, and before First Users and Product Analytics. It is not the Launch page, which holds the launch day itself.
Press Prepare a launch and pick the launch type: prototype test, private beta, first users, first customers, MVP launch, public launch, major product launch, or other (then say which it is closest to). A prototype test needs far less than a public launch, and the checks adapt to it. You can prepare several launches; a bigger one can start from an earlier one and carry what still holds (who it is for, onboarding, support, the message, what to measure and the risks), but never what you checked.
On This launch, pick one or two purposes (get first users, test the core workflow, get first customers, test pricing, collect feedback and more), write what you want to learn, name who it is for (the target market from your Startup Profile is one tap away), choose who can get in (invite-only, your target group, or anyone), and add a date or a window if you have one.
Product, Users, Business, Support & feedback and Measurement list practical checks, grouped into needed for this launch, can wait, and not needed yet. Mark each Ready, Needs attention, Blocked or Not applicable, and move any check to Must work or Can wait for this launch. The technical check on Product shows what your Technology plan says about deployment, signing in, saving data, security, monitoring and payments; you mark whether each is ready enough for this launch. You can add your own checks too.
On Product, list what must work before launch (sign in, the core workflow, saving data) and what can wait, like advanced settings or extra integrations. The items in Now on Product & MVP are offered as suggestions. Mark each must-work item Works, Needs attention or Blocked.
On Users, describe a new user’s first session from the first visit to the core value, plus onboarding and how people get in. On Support & feedback, write who answers and how quickly, how people report a bug, where feedback is recorded (for example the feedback inbox in Product & MVP), what you would do if the product breaks, and who watches what.
On Measurement, choose what to measure from launch (visitors, signups, activation, the core action, conversion, usage, retention, revenue, feedback) and define the core event: the action that shows someone got the value, such as a user completing their first project. Product Analytics is where it then gets measured.
On Plan & risks, write what people will see, choose the channels you will actually use, and make a light plan for before, launch day and after. Track it turns a step into a commitment in your Command Center, so it comes back when it is due. For each risk, write what would happen, how to make it less likely and what you would do if it happens.
Readiness shows, from your own marks, which launches your preparation is enough for (for example a private beta, but not yet a public launch), where each area stands in words, the blockers apart from what can wait, and the whole checklist. When you are ready, review and decide; Not yet is an equal answer. Afterwards, mark it launched and write down what it taught you. Your next step then points to First Users, the Launch page or Product Analytics.
Open Prepare a launch in the app (sign-in required).