Startup launch checklist
Use this to get the basics in place before you build. You do not need to finish every item today. Mark what is decided, what needs a decision and what can wait.
1. Customer and problem
- [ ] I can describe one type of customer in plain language.
- [ ] I know what problem they have and when it occurs.
- [ ] I have spoken to at least five people who resemble this customer.
- [ ] I can explain what they use today and why it falls short.
- [ ] I have separated evidence from assumptions.
2. Offer and first test
- [ ] I can describe the result I want to help the customer achieve.
- [ ] The first version solves one clear problem.
- [ ] I know what is out of scope for the first release.
- [ ] I have chosen a small test: interviews, a landing page, a waitlist or a paid pilot.
- [ ] I know what result would make me continue, change direction or stop.
3. Accounts and ownership
- [ ] Business email and domain are under business control.
- [ ] The code repository belongs to an account I control.
- [ ] A password manager and two-factor authentication are set up.
- [ ] Billing, hosting and third-party accounts have named owners.
- [ ] Recovery methods are stored safely and are not shared in code.
4. Product and data
- [ ] I have chosen the smallest useful technology stack.
- [ ] Development and live environments are kept separate.
- [ ] Secrets and API keys are not committed to the repository.
- [ ] I know what personal data the product collects and why.
- [ ] I have a backup and a way to restore the service.
- [ ] I have tested the main task on a phone and desktop.
5. Sales and marketing
- [ ] I can explain the offer in one short paragraph.
- [ ] The website has one main action for a new visitor.
- [ ] My first useful content answers a real customer question.
- [ ] I have chosen a manageable posting rhythm.
- [ ] I have a place to record enquiries and agreed follow-ups.
- [ ] Any outreach has a clear audience, honest reason and opt-out process.
6. Before launch
- [ ] The main user journey works from start to finish.
- [ ] Contact details, links and calls to action are correct.
- [ ] Privacy information describes the data actually collected.
- [ ] I know how to handle support requests and service problems.
- [ ] I have a simple way to learn what users do and where they get stuck.
- [ ] I have picked a review date and one metric to watch.
First five actions
- Write down the customer and problem in one sentence.
- List the five assumptions most likely to make the idea fail.
- Book conversations with people who match the customer.
- Choose one small test before building a full product.
- Set up ownership, access and recovery for the accounts you need.