LaunchBert is a free product launch checklist tool. Its official page title is "The product launch checklist," and it is aimed mainly at indie developers and small teams, helping them move software products from "it works" to the first month after launch. Applicable product types include SaaS, mobile apps, AI tools, browser extensions, open source projects, and developer tools.
Purpose The checklist organizes the launch process chronologically, from pre-launch preparation, to launch-day actions, to follow-up in the first week after launch. Each item explains why it matters and states under what circumstances it can be skipped. Users can choose their launch type, and the checklist becomes correspondingly shorter, with inapplicable items removed.
Main capabilities The checklist content covers multiple dimensions. The pre-launch section includes: write one sentence explaining what the product does and who it is for; define the target user in one sentence; set pricing, and if you charge, have a paid plan from day one; collect early interest (waitlist or notification list); choose a launch date and work backward from it; test signup and onboarding with a fresh account; install analytics and focus on one metric; set up error tracking; send transactional emails (verification, password reset) from your own domain; add a privacy policy and terms of service; use HTTPS site-wide and redirect from the non-www or www version; have a title and description on every page; make social share images (Open Graph) display correctly in chats; a favicon; a sitemap and robots.txt; a useful 404 page; make the site load quickly on mobile; verify in Google Search Console and Bing Webmaster Tools; make sure AI assistants can read and recommend the product; provide a working contact address; both square and wide versions of the logo; three to five screenshots showing the product actually working; a short demo video or GIF (can be skipped for libraries or command-line tools); one short and one long description, reused; a first comment explaining why it was built; answers to the five questions people will ask (price, privacy, obvious competitors, missing features, why not use a big-company product).
The launch channels section includes: find directories and launch platforms that accept your product; leave space for badges in the footer; expect to need to register an account on most platforms; schedule launches in advance; do not expect every listing to bring backlinks; decide whether Product Hunt is right for you (can be skipped if you only target business buyers).
The launch day section includes: email everyone who said they wanted to know; where users alreadypost on social accounts; reply to every comment on the day of launch.
The first-week-after-launch section includes: emailing everyone who signed up but never started using the product; talking to five people who have used the product; asking the most satisfied users for testimonials; fixing the three most-reported issues; writing a short launch retrospective with real numbers (skip numbers when they are commercially sensitive or the buyers are enterprise customers); finding out which list or post brought visitors; getting onto "best X tool" roundup pages and alternatives pages; and submitting steadily rather than all at once in a single day.
How to use Users do not need to create an account or provide an email address. Reading, checking off items, sharing, and exporting all require no account or email. Checked progress, skipped items, and launch type are stored only in the current browser, with no account, email, or progress upload involved. Page view statistics do not use cookies and do not store anything on the user's device. To migrate progress, you can use the Share link; the link carries the checked items and launch type, and opening it anywhere will show the same state.
Use cases Suitable for indie developers and small teams preparing to launch SaaS, mobile apps, AI tools, browser extensions, open-source projects, or developer tools. The checklist can be used to check pre-launch preparation, day-of-launch execution, and post-launch follow-up, and can also be used to understand which steps can be skipped.
Limitations User data is stored only in the local browser, with no cloud account sync, and migration requires manually using a share link. Whether the checklist covers all platforms or all product types is not currently provided in the material. Whether it is paid: the material clearly states it is free.
