Most launches that disappoint were not short of effort on the day. They were short of preparation: a one-line pitch nobody could repeat, a landing page that says something else, no way to tell which channel worked, and nobody told the date in advance. This checklist puts every step in the order it needs to happen, so the work that takes longest starts first.
It is written for a first launch by one founder or a small team, with a software product (SaaS, an app, a developer tool or an AI product). If you prefer to tick things off as you go, the same stages are in the free interactive launch checklist, which saves your progress in your browser.
Before anything: decide what the launch is for
A launch is a short burst of attention. Decide what you want that attention to turn into before you plan anything else, because it changes which platforms you pick and what your page asks people to do.
- Sign-ups or users. The page leads with a free plan or a trial, and you measure activated accounts, not visits.
- Paying customers. The page leads with pricing and a launch offer, and you measure trials that convert.
- Feedback. You pick communities that give frank answers (Show HN, niche subreddits, Indie Hackers) and you measure the number of real conversations.
- Search visibility. You pick platforms that give a permanent page and a followed link, and you measure referring domains and indexed pages over the next months.
Write the goal down as one number with a date: "100 activated accounts by the end of launch week". Every later choice gets checked against it.
Four weeks out: positioning and the page
These items take the longest, and everything else depends on them.
- Write the one-line pitch. Say what it is and who it is for in under 60 characters, because that is the Product Hunt tagline limit and a good test for every other platform. Check it with the Product Hunt tagline checker, and if you are stuck, start from the tagline generator.
- Write the two-sentence description. The problem, then what the product does about it. Keep a 260 character version (the Product Hunt description limit) and a longer one for directories.
- Make the landing page say the same thing. The headline on your site should match your tagline closely. A visitor who clicks "the fastest way to send invoices" and lands on "Welcome to Acme" leaves.
- Pick one call to action. One primary button, worded as the result ("Start sending invoices"), not the mechanism ("Submit"). Our launch copy guide covers taglines, CTAs and listing copy in detail.
- Get the basics of search right. A unique title and meta description, one H1, a canonical URL and a sitemap. Run the homepage through the on-page SEO checker once and fix what it flags.
- Make link previews work. Every launch post you write will be shared as a link. Check the Open Graph title, description and image with the social preview checker; a link with no image is a thin line of text in a feed full of pictures.
Three weeks out: pick the platforms and the dates
Do not launch everywhere on the same day. Spread launches over one to two weeks so you can answer every comment, and so each launch teaches you something before the next one.
- Shortlist five to eight platforms. The launch platform finder matches platforms to your product type, stage and budget. The launch platform database lists what each one is, who it suits and whether its link is dofollow or nofollow (we only mark a link type after checking it on a real listing).
- Match platforms to the product. Developer tools belong on Show HN and the developer tool launch sites. AI products have their own AI tool directories. B2B software fits the software review directories. Pre-launch products fit beta lists.
- Check review times. Many directories review submissions by hand. Submit to those first so they go live during your launch window, not a month later.
- Set the dates. Put the big launch (Product Hunt, or your main community) on its own day. Use the launch time planner to see what a launch time means in San Francisco, London and Bangalore at once. Our guide to the best time to launch goes through each platform.
Two weeks out: assets
- Logo as a square PNG with a transparent background, at least 240 by 240 pixels.
- Three to five screenshots showing the product doing its main job, each with one short caption. Real screens beat mockups.
- A short demo video or GIF, under a minute, starting with the result rather than the login screen.
- A press kit page with the pitch, the description, the logo, screenshots and the founder's name. The press kit generator builds one.
- Platform copy written ahead and checked against each platform's limits: the launch post generator drafts X, LinkedIn, Reddit, Hacker News, Product Hunt and email posts from one set of details, and the character limit checkers cover every field from the App Store subtitle to a Bluesky post.
The week before: tell people and set up tracking
- Tell the people who already care. Your waitlist, newsletter, beta users and friends who would genuinely use the product. Give them the date and ask them to try it and leave honest feedback. Do not ask anyone for upvotes: platforms penalize vote rings, and a comment from a real user is worth more than a vote.
- Tag every link. Build one UTM link per platform with the UTM builder, so your analytics shows which launch brought users who stayed, not just visits.
- Test sign-up end to end on a phone, on a slow connection, with a fresh email address. Then test the password reset and the welcome email.
- Prepare the first comment for each platform: who you are, why you built it, what is different and one question for readers. The maker comment generator gives you a draft.
- Check page speed. Launch traffic arrives all at once. Run the page speed checker and fix anything slow on mobile.
Launch day
- Go live at the planned time and check the listing yourself, logged out, on a phone.
- Post the first comment immediately.
- Share the launch with the people you told last week, with one personal line each rather than a mass message.
- Reply to every comment within the hour for the first part of the day. Thank critics specifically; they are telling you what the next visitor thinks but will not say.
- Keep a running note of every question, complaint and feature request. It becomes your roadmap and your FAQ.
- Do not refresh the ranking all day. It changes nothing; replies do.
The two weeks after
The days after launch decide what the launch was worth. Most founders stop here, which is why most launches are a spike that disappears.
- Email every new user personally in the first days and ask one question: what did you expect it to do?
- Fix the top three issues people raised, then tell them it is fixed. Nothing earns a loyal early user faster.
- Read the numbers by source. Activation and retention by UTM source, not total visits. Our guide to onboarding, feedback and metrics after launch lists which numbers matter.
- Run the next launch. Use what you learned: a clearer tagline, a better first screenshot, a different community.
- Collect your links. Check which listings went live and whether each link is followed with the nofollow checker.
If you are launching alone
A solo founder cannot be on six platforms, answer support and fix bugs on the same day. Cut the plan to fit:
- One main launch per week. Pick the platform that fits your audience best and give it a full day of attention. Directory submissions can run in the background because they need no attention on the day.
- Write everything the week before. Launch day is for replying, not writing.
- Block the day. No feature work, no meetings.
- Use your story. "I built this alone because I needed it" is a real advantage on Indie Hackers, Show HN and X. Say it plainly.
If you are a small team
With two to five people, give each launch task one owner, so nothing falls between people:
- The maker posts and answers product questions on the main platform.
- Someone on support watches sign-ups, the inbox and error logs, and fixes what breaks.
- Someone on distribution handles social posts, the email to your list and the directory submissions.
Agree in advance what counts as a reason to roll back a release on launch day, and who decides.
If you are launching a SaaS product
- Show the price. Visitors from launch platforms compare quickly. A hidden price reads as expensive.
- Make the free path short. A free plan or trial with no card, and an empty state that shows what to do first.
- Plan the email sequence. Welcome, a first-value nudge on day two, a check-in at the end of week one. The after-launch guide has templates.
- List it where buyers compare. The SaaS directories keep sending visitors long after launch week because buyers search them when they are ready to pay.
The mistakes that sink most launches
- Launching to nobody. No list, no community, no one told. The first hour sets the tone on every ranked platform.
- A vague pitch. "The future of productivity" tells a visitor nothing. Name the job the product does.
- Everything on one day. You cannot reply well in six places at once, and you learn nothing between launches.
- Asking for upvotes. It breaks the rules of most platforms and is easy for them to detect. Ask for feedback instead.
- A sign-up wall before any value. Especially on Hacker News, where people want to try the thing now.
- No tracking. Without UTM links you will not know which channel to do again.
- Stopping after the day. The follow-up emails, fixes and second launches are where users come from.
Where Aback Launch fits
Aback Launch is a weekly launch platform. New products go live every Friday at 00:00 UTC and collect upvotes through the week, and the top three are recorded on the winners page. Every product gets a permanent page that search engines can read, and the link to your site becomes dofollow once you add our badge. A free submission is reviewed by a person, so add it to your list early: it needs no attention on the day and keeps working after the launch week ends.
FAQ
How long does it take to prepare a startup launch?
Two to four weeks for most small launches. The positioning and landing page take the longest; assets and directory submissions take a week; telling people and setting up tracking take the last week.
What is the most important item on a launch checklist?
A clear one-line pitch that matches your landing page. Every platform shows the pitch first, and every visitor decides in a few seconds whether to click.
Should I launch on several platforms on the same day?
No. Spread them over one to two weeks so you can reply to everyone and improve your copy between launches. Directory submissions are the exception, since they need no attention on the day.
What should I do after launch day?
Email new users personally, fix the top issues they raise, read activation by source, and plan the next launch on a different platform with what you learned.
Topics
Written by
Devvrat Hans
Founder
By subscribing, you agree to get our newsletter by email. Unsubscribe any time in one click. See our Privacy policy and Terms.
Related Articles
How Long Does SEO Take for a New Website? An Honest Timeline
How long SEO takes for a new website, month by month: indexing, the first impressions, the long stretch on page five, and when clicks arrive. With a real example and the signs that it is working.
How to Get Backlinks for a New Startup Website
How to get backlinks for a new startup website: the links a new domain can earn first, how to check a source before you spend time on it, the tactics that keep working, and what to avoid.
How to Get Cited by ChatGPT and Perplexity: a Guide for Startups
How to get your startup cited by ChatGPT, Perplexity and other AI assistants: how they pick sources, which crawlers to allow, how to write pages they can quote, where to get mentioned, and how to measure it.