Launching with no audience: a realistic first week

Nobody can give you an honest visitor forecast. The platforms don’t publish averages, and the figures in launch write-ups come from the makers who had something to show. What the platforms do document is how visibility is decided, and that tells you where a maker with no following stands.

• Product Hunt. Its team reviews every launch and picks by hand which ones appear on the homepage leaderboard, and meeting the criteria doesn’t guarantee a place. Rank depends on points, comments, time since launch and other signals, and the formula isn’t public (Product Hunt’s launch guide, read in November 2026).
• Hacker News. The basic ranking divides points by a power of the time since submission, with flags, anti-abuse software and moderators also affecting rank (HN FAQ). A post that gets no early points sinks quickly, whoever wrote it.
• Search. Google says some changes take effect in a few hours and others take several months (SEO starter guide). Expect nothing from search in week one.

Paul Graham’s 2013 essay on early startups lists the “Big Launch” as a tactic that usually doesn’t work, and says all you need from a launch is some initial core of users (source). That is the right size of ambition for a first week with no audience: a small group of people who tried the product and told you what they thought.

Product Hunt’s own guide tells makers to decide what a win looks like, pick one or two goals and make them measurable, and notes that plenty of launches that don’t finish first still get what they came for (source). The same applies everywhere. Write your goals down before the week starts, in terms you can count:

• A number of people who finished sign-up and did the product’s main action once.
• A number of conversations with people who tried it: replies, emails or calls.
• A list of the objections and confusions you heard more than once.

Pick numbers you could reach through your own effort. “Ten people used it and five told me why they would or wouldn’t keep using it” is a goal you can work towards on a slow day. “Top five of the day” is not.

The launch checklist covers the site, analytics, share previews and indexing. With no audience, add these:

• A list of people, by name. Former colleagues, people who complained about the problem in public, members of communities you already belong to, anyone who replied when you described the idea. Each one gets a personal message, so the list can be short.
• Accounts with some history. Product Hunt says the makers who do best usually started weeks earlier, by commenting on other launches and answering questions in its forums (source). The same is true of any community with rules about self-promotion: take part before you post.
• A way to try the product without friction. Show HN asks for something people can play with, ideally without a sign-up or an email address, and doesn’t accept landing pages or sign-up pages (Show HN guidelines). A demo account or a sandbox helps on every platform.
• Your listing text and images. Write the tagline and description and prepare the screenshots and share image once, then reuse them.
• A short list of places. Three or four where your users actually are. The guide on where to launch helps you choose.

One post per day is easier to look after than five posts on one morning. With no audience to send, your replies are the main thing you add, and you can only reply well in one place at a time.

1. Day 1: people you know. Send the personal messages. Ask each person to try one specific thing and tell you where they got stuck. Fix what they find the same day.
2. Day 2: your main platform. Post where you prepared most. Product Hunt launches go live at 12:01 AM Pacific Time and its guide says the best day is the one you’re most prepared for (source). See Product Hunt without an audience. Stay for the whole day and answer everything.
3. Day 3: one community. A Show HN if the product can be tried, or a subreddit whose rules allow it. Write the post for that community; don’t paste the previous day’s text.
4. Day 4: weekly boards and directories. Submit to the few you chose. Boards that run by the week, such as IndieTide, don’t need you present hour by hour, so they fit a day when you’re also fixing things.
5. Day 5: one-to-one outreach. Find people who have described the problem in public and write to them individually, with a reason you chose them.
6. Day 6: follow up. Reply to everyone who signed up or commented. Tell people who reported a problem that it’s fixed.
7. Day 7: review. Go through the numbers below and write down what you learned while you remember it.

Graham’s essay says the most common unscalable thing founders have to do at the start is recruit users manually: you can’t wait for users to come to you. His arithmetic is the argument for doing it even when the numbers feel small. With 100 users, you need 10 more next week to grow 10% a week, and that rate compounds (source).

A message that gets answered is short and specific. Compare:

• Weak: “Hey! I just launched my new app and would love your support. Check it out and upvote if you like it!”
• Better: “You wrote last month that exporting invoices to your accountant takes you an afternoon. I built a small tool that does that export in one step. Would you try it on last month’s invoices and tell me where it falls short?”

The second one shows you read what they wrote, names the job, and asks for feedback. The guide on getting your first 100 users goes further into this.

• Visits by source. Referrers and the UTM tags from your own links show which post sent people.
• Sign-ups by source. A place that sent 30 visitors and 6 sign-ups was a better fit than one that sent 300 and 2.
• Activation. How many of those who signed up did the main action once. This is the number that says most about the product.
• Replies. Count the conversations and keep the exact words people used to describe the problem. They improve your tagline.
• Search, later. Search Console reports impressions, meaning how many times your site appeared in results, and clicks (Search Console help). Look after a few weeks, not on day three.

If the week was quiet, the guide on what to do after a launch with no traction shows how to read these numbers.

A maker without an audience is the one most tempted by these, and the platforms name them directly:

• Asking for upvotes. Product Hunt says never to ask for them, and forbids buying upvotes or comments, giveaways tied to an upvote, mass DMs and copy-pasted messages to strangers. A launch can be removed, and bought engagement can get the account banned (source). Ask people to try the product and comment.
• Asking friends to vote or comment on Hacker News. The guidelines say “Don’t solicit upvotes, comments, or submissions” (source), and the FAQ says submissions, accounts and sites that break the voting rule are penalised or banned (source).
• Posting in communities you’ve never taken part in. Product Hunt’s guide advises against it (source). Read each community’s rules on self-promotion before you post.
• Chasing a famous hunter. Product Hunt lists thinking you need one among the common mistakes (source). Post it yourself.