LaunchRepo.

Free tool

SaaS launch checklist

Thirty launch tasks in six phases, from 30 days before launch day to 30 days after. Tick them off as you go: your progress stays in this browser, and you can export the whole list as Markdown whenever you like.

By Updated How we research and update

Your launch checklist

Progress is saved only in this browser (localStorage). Nothing you tick is sent to LaunchRepo.

0 of 30 tasks done
T−30 30 days before0/6

Decide what you launch, when, and how you will know it worked.

  • Why: Every tagline, listing form and launch post reuses this sentence, so writing it once saves hours later. Source: Glossary: product context file →

  • Why: Free directory queues can take weeks, so an early submission can go live before your page is ready. Source: When should listings go live? →

  • Why: Sign-ups or trials per channel tell you more than visits; Search Console shows clicks, impressions, CTR and position for organic search. Source: Google: Search Console performance report ↗

  • Why: Commercial digital services in Germany must keep name, address and a fast contact such as email permanently available (§ 5 DDG). Source: § 5 DDG (German law) ↗

  • Why: Under GDPR Article 13 people must be told at the time you collect their data; checkout providers and many directories also ask for this link. Source: GDPR (EUR-Lex) ↗

  • Why: Product Hunt requires personal accounts and prohibits company accounts; setting them up early leaves time to learn each community. Source: Product Hunt launch guide ↗

T−14 14 days before0/7

Make the product, the page and the payment path ready for strangers.

  • Why: Google recommends descriptive, concise and distinct titles for each page, without repeating keywords. Source: Google: title links ↗

  • Why: og:title, og:type, og:image and og:url are the four required properties; they decide how your link looks when people share it. Source: The Open Graph protocol ↗

  • Why: Product Hunt recommends a square 240×240 thumbnail under 3 MB and 1270×760 gallery images; the same set serves most other listings. Source: Product Hunt: preparing for launch ↗

  • Why: Stripe provides test cards such as 4242 4242 4242 4242 for success and 4000 0000 0000 0002 for a decline; never test with real card data. Source: Stripe: testing ↗

  • Why: Gmail requires SPF or DKIM for all senders, and SPF, DKIM and DMARC for bulk senders; otherwise welcome emails can land in spam. Source: Google: email sender guidelines ↗

  • Why: Good Core Web Vitals mean LCP within 2.5 s, INP of 200 ms or less and CLS of 0.1 or less, measured at the 75th percentile. Source: web.dev: Web Vitals ↗

  • Why: WCAG 2.2 asks for a 4.5:1 text contrast, text alternatives for images and full keyboard operation; launch visitors use every kind of device. Source: W3C: WCAG 2.2 ↗

T−7 7 days before0/5

Write the copy once, in every length, and line up the channels.

T0 Launch day0/5

Publish in order, be present, and write down what happened.

  • Why: A fresh account on a real phone finds the broken step before your first visitors do.

  • Why: Product Hunt calls 12:01 am Pacific Time the best time for makers who plan ahead, because it gives the launch the full day. Source: Product Hunt launch guide ↗

  • Why: Product Hunt says you cannot ask people directly to upvote, and Hacker News asks you not to ask friends to upvote or comment. Source: Hacker News: Show HN rules ↗

  • Why: Launch day is the one day many people read the thread; quick, specific answers turn visitors into users.

  • Why: Submitted, pending, scheduled and live are different states; writing them down stops duplicate submissions later. Source: Submission states explained →

T+7 First week after0/4

Turn attention into conversations and fixes.

  • Why: A recorded next action and date turns a waiting list into work you can finish. Source: Recording outcomes →

  • Why: Five short conversations show where people got stuck and what they expected, which no dashboard tells you.

  • Why: Fixes shipped in the first week reach the people who arrived with the launch and are still deciding.

  • Why: An update gives everyone who signed up a reason to come back and shows the product is moving. Source: Example: the LaunchRepo changelog →

T+30 First month after0/3

Measure by channel and choose your next launch moment.

How to use the checklist

  1. Start at the phase that matches today. If your launch is in two weeks, begin with “14 days before” and skim the earlier phase for anything you skipped.
  2. Tick a task once it is really done, not when it is planned. The progress bar then shows what is left, phase by phase.
  3. Export the list as Markdown and paste it into your issue tracker, a README or a note. Ticked tasks export as [x], open tasks as [ ], with the reason and source for each.
  4. When you know what to do, move the tasks onto dates and owners with the launch plan template.

What this checklist does not cover

  • It is not legal advice and not a legal review. The imprint and privacy items point to the official texts; whether and how they apply to your business is a question for a lawyer.
  • It is not tied to one platform. For the details of a Product Hunt listing, use the Product Hunt checklist for solo developers.
  • It is not the LaunchRepo runbook. The paid kit contains the platform playbooks and the workflow your agent follows; this list is the general launch frame around it.

Product Hunt launch checklist →

Where the list comes from

Each reason is checked against the official page linked next to it on September 30, 2026: Product Hunt’s launch guide, Hacker News’ Show HN rules, Google Search Central, Gmail’s sender guidelines, Stripe’s testing docs, web.dev, WCAG 2.2, the Open Graph protocol, § 5 DDG and the GDPR.

Two tasks come straight from launching our own products: an earliest public date (in the LaunchRepo kit since September 15, 2026) and recording each listing’s state with evidence.

Checklist or launch plan?

This checklist answers what to do. The launch plan template answers when and who: it puts the same kind of work on calendar dates, assigns it to roles and shows each person’s hours, with CSV and Markdown export.

Open the launch plan template

Frequently asked questions

Is the SaaS launch checklist free?
Yes. It runs in your browser without an account or email address, and the Markdown export is free as well.
Where is my progress saved?
Only in this browser’s localStorage. Nothing is sent to LaunchRepo. Another browser or device starts with an empty list; clearing your browser data or pressing “Reset progress” removes it.
Can I launch in less than 30 days?
Yes. Start with the phase that matches today and move anything that does not fit to after launch. The slow items are the ones with queues, like free directories, so start those first.
Is this a Product Hunt checklist?
No. It covers the whole SaaS launch across channels. Product Hunt appears where its rules matter, and the separate Product Hunt checklist goes into the listing in detail.
Does the checklist replace legal advice?
No. The imprint and privacy tasks link to the official texts so you know they exist; a lawyer tells you what applies to your business.

Let your agent do the directory part

LaunchRepo gives your coding agent the platform playbooks, the local dashboard and the tracker for the directory launch, so the submissions in this checklist get done and recorded.

See pricing