The Product Launch Plan: 30 Days to Your First Users

Launch day is short. On most launch platforms you get a day or a week in front of a crowd, then the list moves on. What happens in that window is mostly decided in the month before it: whether the right people know it's coming, whether your page explains the product in a few seconds, and whether anyone has a reason to come back.

This product launch plan turns that month into a schedule. It runs from day 30 to launch day, about an hour or two a day, in four weekly blocks: set a goal, build your page and kit, line up people, then rehearse. It works for any launch platform. Where a step depends on a platform's rules, we quote the rules and link to the source, all checked on 19 October 2026. For the full task list by phase, filtered for SaaS, mobile apps, developer tools or AI products, use our free, interactive startup launch checklist.

Before you start: what this plan assumes

This plan is for founders launching a working product, not an idea. It assumes three things:

1. The product works end to end for one use case. A visitor can sign up, do the main thing, and see a result without your help.
2. You can give it an hour or two a day for the next month, alongside building.
3. You can clear the whole of launch day. Answering questions quickly matters more on launch day than anything you can schedule.

If the first one isn't true yet, start with a waitlist and come back to this list when it is. A launch sends people to whatever you have. If that's broken, most of them won't return for a second look.

The 30-day plan at a glance

Week 1: Set the foundations (days 30 to 24)

The first week is for decisions. Skip them and every later step gets harder, because you won't know who you're writing for or what counts as success.

Day 30: Write down one launch goal

Pick one number you can count that matters to your product. Good launch goals look like these:

• 100 sign-ups from people who match your target user
• 15 conversations booked with potential customers
• 5 paying customers in the first week

Upvotes, rank and page views make poor goals. They feel good, but they don't tell you whether the right people found you. Write the goal at the top of your launch document, so you can check every later decision against it.

Day 29: Describe the one person you're launching for

Write a few sentences about a specific person: their job, the problem they have, what they use today, and where they spend time online. "Developers" is too broad. "Solo developers who deploy side projects on a weekend and hate setting up auth" is useful.

Paul Graham describes the trade-off well: you can build something a large number of people want a small amount, or something a small number of people want a large amount. In his words, "You can either dig a hole that's broad but shallow, or one that's narrow and deep, like a well" (Paul Graham, How to Get Startup Ideas (opens in a new tab), November 2012). A launch works best when it's aimed at the narrow, deep group first.

Day 28: Pick your platform and your date

Choose the launch platform where that person already spends time. Our comparison of Product Hunt alternatives sorts ten platforms by how they share out attention, and our list of startup directories covers the places to list your product afterwards.

Then pick a date at least 30 days out, and check the platform's timing rules:

Product Hunt's guidance is honest about timing: "The best day to launch is the day on which you're most prepared" (Product Hunt launch guide (opens in a new tab)). It also reports that "products launched on the weekend get 15% more 'Visit' button clicks than those on weekdays", because fewer products compete. If your goal is visits rather than rank, a weekend is worth considering.

Day 27: Set up tracking you'll trust

You need to know where launch visitors came from and what they did. Set this up now, while there's time to test it.

1. Analytics on every page, including sign-up and checkout.
2. Campaign links for every place you share. Google's guidance is to always set utm_source, utm_medium and utm_campaign, to use lowercase, and to use "only one unique utm_source for each distinct platform", because "Parameter values are case sensitive" (Google Analytics help, URL builders (opens in a new tab), checked 19 October 2026). Decide the names now, for example utm_source=producthunt&utm_medium=launch&utm_campaign=launch_2026.
3. Google Search Console, with your sitemap submitted. Google notes that a sitemap is "merely a hint", not a promise that pages get crawled (Google Search Central, Build and submit a sitemap (opens in a new tab)). It's still worth doing before people start linking to you.
4. A simple sheet to log sign-ups, questions and feedback on launch day, with a column for where each one came from.

Days 26 to 24: Fix the first five minutes

Create a brand new account on your own product, on a phone, on a slow connection. Time how long it takes to reach the moment where the product proves its worth. Write down every point where you hesitated, then fix the three worst.

Common problems at this stage:

• A sign-up form that asks for more than it needs
• An empty screen after sign-up, with no example or next step
• Confirmation emails that land in spam or take minutes to arrive
• A pricing page that doesn't answer "can I try it for free?"

Week 2: Build your page and launch kit (days 23 to 17)

Most launch visitors give your page a few seconds before deciding whether to stay. This week makes those seconds count.

Your landing page checklist

Read the headline to someone who matches your target user and ask them to explain it back to you. If they can't, rewrite it before you touch the design.

Your launch kit

Write every launch asset once, in one document, then adapt it for each platform. Product Hunt's limits are a good default because they're the strictest most founders will meet:

Spend the most time on the gallery. Your first image is often the only one people see, so make it show the product doing its main job, with a short caption, not your logo on a gradient.

Write your first comment now

Product Hunt reports that "70% of products that achieved Product of the Day, Week, or Month included a first comment by the maker", and recommends a humble, helpful tone (Product Hunt, Preparing for launch (opens in a new tab)). The same comment works as the opening of a Show HN post or a community thread. A simple structure:

1. One line on who you are.
2. The problem, in a sentence or two, and how you met it.
3. What the product does, and what makes it different.
4. A specific question you'd like answered, such as "Would you use this for X or for Y?"

Week 3: Line up the people (days 16 to 10)

A launch is only as good as the first few hours of attention it gets, and that attention comes from people, not algorithms. This week, you find them and give them a reason to show up.

Build a list of people who care about the problem

Open a spreadsheet and fill it with real names. Aim for people who have the problem, not people who like you.

Paul Graham's advice on this stage still holds: "The most common unscalable thing founders have to do at the start is to recruit users manually" (Paul Graham, Do Things That Don't Scale (opens in a new tab), July 2013). A list of 50 well-chosen names beats a broadcast to thousands who don't have the problem.

Talk to five people before you launch

Book five short calls with people from your list who match your target user. Don't pitch. Ask about the last time they had the problem, what they did about it, and what that cost them. Rob Fitzpatrick's book The Mom Test (opens in a new tab) is built around this idea: ask about real past behaviour, not opinions about a future product, because people are kind about ideas and honest about their own lives.

These calls give you three things for launch day: the words your users use (steal them for your page), the objections you'll hear in the comments, and a handful of people who now care how the launch goes.

Ask for the right thing

Every major launch platform has rules about asking for votes, and breaking them can sink a launch.

• Product Hunt: "Ask for feedback, comments, opinions, help spreading the word, not for upvotes" (Product Hunt, Sharing your launch (opens in a new tab)).
• Hacker News: users should vote for a story "because they personally find it intellectually interesting", not because they were asked (Hacker News FAQ (opens in a new tab)).

That's also better strategy. A thoughtful comment from a real user helps your launch and your page far more than a silent vote.

Write your messages now

Write the launch-day messages this week, while you have time to make them personal. Keep them short. For people who know you:

Hi Sam, we're launching [product] on Product Hunt tomorrow. You told me last month that [problem] cost you hours every week; this is our answer. I'd love your honest take in the comments, even if it's "this isn't for me". Here's the link: [link]

For communities, lead with what you learned, not what you're launching. A post titled "What 20 user calls taught me about [problem]" with a link at the end will be read. A post titled "We launched!" usually won't.

Week 4: Rehearse and schedule (days 9 to 1)

The last week is for removing surprises. Nothing new gets built unless something is broken.

Days 9 to 7: Run a full rehearsal

Ask two people who haven't used the product to go through the journey while you watch, without helping:

1. Find the launch post and read it.
2. Click through to your site.
3. Sign up, on a phone.
4. Reach the moment where the product proves its worth.
5. Pay, if you charge, using a real card and a refund.
6. Get every email the product sends.

Fix anything that made them stop or ask a question. Check that your campaign links show up correctly in your analytics.

Days 6 to 4: Schedule and prepare

• Schedule the launch post, or write it as a draft if the platform doesn't allow scheduling.
• Write a list of likely questions and short answers: pricing, privacy, how it compares with the obvious alternative, what's next. You'll paste and adapt these on launch day.
• Prepare a launch-day offer if it suits your product, such as an extended trial for people who come from the launch.
• Add a small notice to your site so returning visitors know you're launching.

Days 3 to 2: Line up launch-day support

If you have a co-founder or a helper, split the day: one person answers comments, the other handles support and sends messages. If you're alone, block your calendar and turn off everything that isn't the launch.

Day 1: Rest

Send nothing new. Check that the post is scheduled, that the site is up, and that your messages are ready to send. Then stop and sleep. Launch day is long.

Launch day: hour by hour

Two rules for the whole day. First, answer quickly and in a human voice, including the critical comments; they're often the most useful ones. Second, never post anything that reads like a request for votes. Ask for opinions and comments instead.

The week after launch

The launch-day spike fades quickly. The work that turns visitors into users happens over the next few days:

• Reply to everyone who left a comment or signed up, and ask one follow-up question.
• Ship one visible fix that came from launch feedback, and tell the people who asked for it.
• Move from the launch page to the product page. Product Hunt calls your product page "your permanent and comprehensive source of truth" (Product Hunt, Days after launch (opens in a new tab)), and the same idea applies on any platform.
• List the product in the right directories, now that you have screenshots and a story.
• Check your goal. Did you hit the number? Write down why or why not.

Our 30-day plan for after a Product Hunt launch covers this period in detail, and our guide to getting your first 100 users without ads covers what to do once the launch traffic is gone.

The plan on one page

Copy this into your launch document and work through it.

Days 30 to 24: Foundations

• One countable launch goal, written down
• A few sentences describing the person you're launching for
• A platform and a date at least 30 days out
• Analytics, campaign links and Search Console set up and tested
• The three worst problems in your first five minutes fixed

Days 23 to 17: Page and kit

• A landing page with a clear headline, one action, a demo and an email sign-up
• Name, tagline (60 characters or fewer) and a short description (260 characters or fewer)
• A square logo, two or more gallery images and a short demo video
• Your first comment, drafted

Days 16 to 10: People

• A list of real people who have the problem
• Five calls about their past experience with the problem
• Launch-day messages written, asking for feedback and comments, not votes

Days 9 to 1: Rehearsal

• A full rehearsal with two fresh users, and the fixes it showed
• The launch post scheduled, and answers to likely questions written
• Launch day cleared, and a good night's sleep

Launch day and after

• First comment posted and every comment answered
• Every question and piece of feedback logged
• Follow-ups sent within a week, and one fix shipped from feedback

Where Zutto Launch fits

Zutto Launch is our product, so weigh this section with that in mind. It's a launch platform built so your launch doesn't depend on a single day: products stay on a monthly leaderboard, and the work in this plan keeps paying off for weeks.

• A free launch with a product page that stays up after launch day.
• A monthly leaderboard decided by community votes, so the people you contact in week 3 have a month to find you, not a few hours.
• The Weekly Top 3 get a promo kit: a short AI launch video, reels on our YouTube Shorts, Instagram and X accounts, and a section in our newsletter. Votes decide the Top 3; paid placement never buys a spot.
• Monthly winners can earn partner-sponsored rewards.
• Spotlight ($19, one time) adds a 2,500-word story on our blog, a featured listing in your category and a permanent do-follow link with no badge required.
• Premium Launch ($50, one time) adds an AI-generated 30-second launch video, 3 more do-follow backlinks and two posts on our blog comparing you with your alternatives.

Optional paid placement (Spotlight and Premium Launch) is clearly labelled and never changes leaderboard ranking or prize eligibility. See pricing for what each option includes. Zutto opens to waitlist members first.

Your next step

Open a document today and write your launch goal and the description of your target person at the top. Those two lines are day 30, and they decide everything else on this list. If you're planning a Product Hunt launch without a following, our guide to launching on Product Hunt without an existing audience adds the community work that starts months before launch day.