← Learn

Product launch checklist for a solo founder

A solo founder's product launch checklist has four stages. Four weeks out, finish the promise, landing page, waitlist, payments, legal pages, and email setup. The week before, test sign-up, payment, emails, and alerts on a phone. On launch day, post and reply within the hour. For 30 days after, track who stays and fix what they ask.

A founder in glasses sits on a rocky cliff path above a dark ocean, typing on a laptop with an orange screen, a backpack beside them and a coffee thermos in front, drawn in black ink with orange accents

A product launch checklist for a solo founder fits on one page: what to finish four weeks out, what to test the week before, what to do on launch day, and what to watch for 30 days after. ZeroCrew built this checklist for founders who launch alone, so every step names AI tools from the ZeroCrew directory that can carry the work.

Most product launch checklists online are written for a team, with rows for marketing, sales, and support. ZeroCrew's version assumes one founder with a crew of AI agents, so it keeps the items that protect your first users and drops the meetings.

ZeroCrew's guide on how to launch a product alone explains the strategy behind each stage. This ZeroCrew checklist is the short version to copy into your notes and tick off, item by item, in the order a solo founder needs it.

What is a product launch checklist?

A product launch checklist is an ordered list of everything that must be true before, during, and after a product goes public, so nothing important depends on memory. ZeroCrew sorts its solo founder checklist by time, because one person works through the list in order, not in parallel across departments.

A useful solo checklist is short, and every item on it has a clear done state. ZeroCrew's rule for each line is a test you can run in a minute, like "a test payment went through" rather than "payments ready".

What should you finish four weeks before launch?

Four weeks before launch, a solo founder finishes the items that need time to settle: a one-sentence promise, a landing page, a waitlist, payments, legal pages, and email setup. ZeroCrew's job pages rank the tools for each of these jobs, and each step below offers two options from the ZeroCrew directory.

  1. Write the promise. One sentence on who the product is for and what changes for them. Draft versions with Claude or ChatGPT, then keep the one a stranger can repeat back.
  2. Build the landing page. Use Framer to design and publish a site with its AI design agent, or Canva to make the visuals and a simple page from templates. ZeroCrew's design and sites page compares them.
  3. Open a waitlist. Collect emails with Tally, which builds forms you write like a doc, or Typeform, which asks one question at a time. ZeroCrew's feedback and surveys page lists others.
  4. Set up payments. Use Stripe for payments and billing under your own account, or Paddle when you want a merchant of record to handle sales tax for you. ZeroCrew's payments page compares them.
  5. Publish your privacy policy, terms, and cookie banner. Generate them with Termly or iubenda, then read every line yourself. ZeroCrew's privacy and compliance page ranks the options.
  6. Authenticate your email domain. Send sign-in links and receipts from your code with Resend, or use Customer.io for messages triggered by what users do. Then add SPF, DKIM, and DMARC records for your domain at your DNS host, such as Cloudflare.

Privacy information is a legal duty in many markets, not an extra. The UK Information Commissioner's Office says you must give people privacy information at the time you collect their data, in clear and plain language, including why you process it, how long you keep it, and who you share it with. ZeroCrew suggests having that page live before the waitlist form, since the waitlist is your first data collection.

Cookie consent belongs on a launch checklist next to the privacy policy. The ICO's guidance on cookies says you must tell people if you set cookies and get their consent, with an exception for cookies essential to a service the user asked for. ZeroCrew's privacy and compliance page lists tools that write a cookie banner, so your analytics can run with consent from the first visit.

Launch emails reach inboxes more reliably from an authenticated domain. NIST's Trustworthy Email guide (SP 800-177 Rev. 1, 2019) recommends SPF, DKIM, and DMARC to authenticate the domain you send from. ZeroCrew suggests setting all three weeks before launch, so the sign-in links and receipts your first users wait for are more likely to land in the inbox.

What should you test the week before launch?

The week before launch, a solo founder tests every path a new user takes: sign-up, payment, emails, error alerts, and support, on a phone and a laptop. ZeroCrew's checklist for that week treats each path as a test with a pass or fail, because these are the places a first visitor leaves without telling you.

Phone testing comes first because nearly everyone carries a phone. Pew Research Center's mobile fact sheet reports that 91% of US adults own a smartphone and 16% are smartphone-only internet users, from its 2026 survey. ZeroCrew suggests running every test below on a phone before you run it on a laptop.

  1. Sign up as a stranger. Create a new account with a fresh email on a phone, then ask someone outside your circle to do the same while you watch.
  2. Pay yourself. Run a real payment and a refund through Stripe or Paddle, and check that the receipt arrives.
  3. Check every email. Confirm that sign-in links, receipts, and welcome emails land in the inbox, whether Resend or Customer.io sends them.
  4. Turn on error alerts. Catch crashes with Sentry, or use the error tracking built into PostHog, so you hear about a broken sign-up first.
  5. Track sources. Tag each launch link and confirm that PostHog or Mixpanel shows the visit and the sign-up. ZeroCrew's product analytics page compares them.
  6. Open a support channel. Add a chat widget and shared inbox with Crisp, or an AI agent that answers from your docs with Chatbase or Fin. ZeroCrew's chat and email agents page and help desks page rank more.
  7. Check readability. Test your text and buttons against the contrast rule below.

Readable pages take minutes to check on launch week: W3C's Web Content Accessibility Guidelines (WCAG 2.2) set a minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text. ZeroCrew suggests checking your landing page and sign-up form against those two numbers, since a button people struggle to read is a button fewer people press.

What goes on the launch day checklist?

On launch day, a solo founder's checklist is about presence: post where your users gather, email the waitlist, stay online, and answer every comment within the hour. ZeroCrew suggests writing every launch post the week before, so launch day goes to replies and fixes instead of writing.

  1. Post on your first launch site. Choose it with ZeroCrew's guide to Product Hunt alternatives, which compares 12 places to launch.
  2. Email your waitlist. Send one short note with Kit or beehiiv, with your postal address and an unsubscribe link.
  3. Share on social. Schedule posts with Buffer for many networks at once, or Typefully for writing posts for X and LinkedIn.
  4. Reply within the hour. Keep the launch post, your support inbox, and your Sentry or PostHog alerts open side by side.
  5. Fix in public. Ship small fixes the same day and say so in the thread. Note every question for a help article later.

Launch emails follow the law as well as good manners. The FTC's CAN-SPAM compliance guide says commercial email must include a valid physical postal address and a clear way to opt out, opt-outs must be honored within 10 business days, and there is no exception for business-to-business email. ZeroCrew suggests confirming your newsletter tool adds both before you press send.

Honest attention lasts longer than bought attention. The FTC's final rule on fake reviews (August 2024) bans fake reviews, including AI-generated ones, undisclosed insider reviews, and buying fake followers or views for a commercial purpose when the buyer knew or should have known they were fake. ZeroCrew suggests asking people to try the product and say what they think.

What should you do in the 30 days after launch?

In the 30 days after launch, a solo founder finds out who stays, asks why, fixes what users ask for, and picks the next place to launch. ZeroCrew suggests one short review each week, with analytics and feedback tools from the ZeroCrew directory doing the counting while you talk to users.

  1. Watch who comes back. Check in PostHog or Mixpanel which launch source brought users who returned in week two.
  2. Collect requests in one place. Use Canny for a public voting board, or Tally for a short survey sent to new users.
  3. Talk to five users. Book short calls yourself, or let an AI interviewer like Listen Labs or Outset run them and sum up the answers. ZeroCrew's customer interviews page lists more.
  4. Automate the repeats. Hand recurring jobs like welcome follow-ups to Zapier for no-code workflows, or n8n for workflows you can inspect step by step.
  5. Plan the next launch. Pick the next site from your list and put a date on it.

What does the whole checklist look like on one page?

The whole solo founder launch checklist fits in one table: twelve items across four stages, each with a test that tells you it's done. ZeroCrew suggests copying the table into your notes and ticking each row only when its test passes, not when the work feels finished.

WhenItemDone when
4 weeks outPromiseA stranger repeats it back correctly
4 weeks outLanding page and waitlistThe form saves a test email
4 weeks outPaymentsA test payment and refund went through
4 weeks outPrivacy policy, terms, cookiesThe pages are live and linked in the footer
4 weeks outEmail domainSPF, DKIM, and DMARC records pass a check
Week beforeSign-up on a phoneA stranger signs up without help
Week beforeErrors and analyticsA test error and a test sign-up both show up
Week beforeSupportA test question gets an answer
Launch dayPosts and waitlist emailSent, with an unsubscribe link
Launch dayRepliesEvery comment answered within the hour
30 days afterWho staysYou know which source brought users who returned
30 days afterNext launchA site and a date are picked

How does ZeroCrew help you finish the checklist?

ZeroCrew helps a solo founder finish a launch checklist by showing which AI tools do each job and how they compare. The ZeroCrew directory sorts tools by role and job, and each job page ranks its tools by how many people search for each one by name and by what founders say about them, so you start from the tools founders already look for.

ZeroCrew's directory is independent of the tools it lists. ZeroCrew's page on how it chooses tools says nobody pays to be listed or ranked, and it judges every tool on eight questions, including whether agents can use it through an MCP server or API, what it really costs at your size, and whether you can export your data.

Your own AI agent can work through the checklist with ZeroCrew too. ZeroCrew's MCP servers page gives the address of its public MCP server, which lets an agent in Claude, Cursor, or ChatGPT search the directory by job, so you can ask it for two payment tools or two error trackers while you write launch posts.

ZeroCrew can also set up the agents behind your launch for you. ZeroCrew's done-for-you AI agent setup starts with a free 25-minute discovery call, and as of November 2026 projects start at $1,000, with agents for jobs like calls, follow-ups, and support connected to the tools you already use.

When your product is itself an AI agent or tool, ZeroCrew gives it a place to be found after launch day. The ZeroCrew Launchpad lists every tool that went live in the directory, grouped by the week it launched, and ZeroCrew's page on how it chooses tools explains what earns a place.

Sources (7)
  1. The right to be informed (ICO)
  2. Cookies and similar technologies (ICO)
  3. Trustworthy Email, NIST SP 800-177 Rev. 1 (2019)
  4. Mobile Fact Sheet (Pew Research Center)
  5. Web Content Accessibility Guidelines (WCAG) 2.2 (W3C)
  6. CAN-SPAM Act: A Compliance Guide for Business (FTC)
  7. FTC announces final rule banning fake reviews and testimonials (August 2024)

Zero employees. Never build alone.

Find the agent for every job