Blog

I launched and nobody came: a 7-day recovery plan for student builders

· buildtolaunch

You posted your project, refreshed the page for a day and got almost nothing. This guide explains why that is common, how to find out which part failed, and what to do in the next seven days. It is part of the student launch playbook.

Short answer

Launching to silence is normal, especially with no audience. Do not rebuild the product yet. Check four things in order: did the right people see it, did they understand it, did they try it, did they come back. Message ten people who have the problem, ask what confused them, fix one thing and launch again within a week.

Why nobody came (it is usually not the product)

A single post reaches the people who happen to be online and already follow you. If you have 40 followers, a post reaches a handful of them. Silence tells you about reach, not about quality. Big public sites make this clearer: Product Hunt's own launch FAQ says upvotes from established, active members count for much more than upvotes from new accounts, so a launch with no network starts behind (as checked on 18 Nov 2026, Product Hunt launch FAQ).

That is why most student launches that stall have a distribution problem first. The fix is to go to people directly, not to post louder.

Diagnose it: four checkpoints

Work through these in order and stop at the first "no".

CheckpointQuestionHow to checkIf no
1. SeenDid the right people see it?Count who you actually messaged or who posted in a group where your users hang outGo to them directly (below)
2. UnderstoodCould they say what it does?Ask three people to explain it back after reading your titleRewrite your one-line pitch
3. TriedDid they click and do the main action?Free analytics, or watch one person use it on a callRemove steps before the first action
4. ReturnedDid anyone come back?Ask the people who tried itSee my users do not come back

Most people skip to checkpoint 4 and conclude "my idea is bad". At checkpoint 1 you usually have fewer than 20 real views. That is not enough data to judge the idea.

The seven-day recovery plan

Day 1: List ten people. Write the names of ten people who have the exact problem: classmates in the right major, club members, a cousin who runs a small shop. If you cannot name ten, your audience is too vague. Narrow it.

Day 2: Send ten personal messages. Use this shape:

Hi [name], I built [one-line pitch]. Could you try it for two minutes and tell me the first thing that confused you?

Personal messages get far more replies than a public post. Expect three or four replies from ten. That is normal.

Day 3: Watch, do not explain. Ask one person to share their screen or send a screenshot as they try it. The place where they pause is your biggest problem. Use five questions for user interviews after launch (Vietnamese) if you want a script.

Day 4: Fix one thing. Only the biggest blocker. A clearer title, a shorter signup, one button instead of three. Tell the people who helped that it is fixed. They are now your first supporters.

Day 5: Post in one specific community. Choose a place where your users already are, join in for a few days, then share with context. See how to post in student Facebook groups without looking like spam (Vietnamese).

Day 6: Share what you learned. A short post: "I launched, got 2 users, here is what I changed." People reply to honest stories more than to adverts. See build in public là gì (Vietnamese).

Day 7: Launch the fixed version. Post it again as an update. A weekly rhythm of small launches beats one big day, because each round gives you users to learn from.

What not to do

  • Do not pay for upvotes or fake traffic. Product Hunt tells makers never to pay for upvotes, and it adds noise without real users.
  • Do not spam groups. One account posting the same link ten times gets muted or banned.
  • Do not add features. Silence is almost never solved by feature number twelve.
  • Do not decide it failed after one post. One post is one data point.
  • Do not hide. Quiet launches are common. Telling people what you learned builds trust.

When to change the idea

Change the idea only when you have talked to at least ten target users and heard some version of "I do not have this problem" or "I would not use this". If people understand it, try it and shrug, the problem is not painful enough. Keep the code, change the problem or the audience. One honest question helps: "What would you miss if this disappeared tomorrow?" If the answer is "nothing", pivot.

Where buildtolaunch fits

A weekly practice board lowers the stakes. On buildtolaunch you can post your project on the Launch League, a public board that resets every Monday, and get feedback from other student builders without a big public launch. The free library at /courses and the AI tutor at /practice can help you improve what you built. Everything is free and open to any major.

FAQ

Is it normal to get zero users on launch day? Yes. Without an existing audience, one post rarely reaches enough of the right people. Direct messages to ten people with the problem will teach you more than a public post that nobody sees.

How many users do I need before I decide the idea is bad? Talk to at least ten people from your target group before judging. If most of them understand the product and still do not care, change the problem or audience. If most do not understand it, the message needs work, not the idea.

Should I relaunch the same project? Yes, if you changed something real: the audience, the message or the first-use experience. Post it as an update with what you learned. Product Hunt, for example, has a help page on relaunching a product. Do not repost the identical link.

Why did my friends say they liked it but never used it? Polite feedback is cheap. Ask them to do the main action while you watch, or ask what they would use it for this week. If they cannot name a moment, the problem may not be urgent for them.

Should I spend money on ads? Not yet. Ads send strangers to a product you have not tested with real people. Fix the first-use experience with ten users first. If it works with them, you will know what to say in an ad.

How long should I keep trying before I move on? Give it four to six weeks of small weekly launches and conversations. If you have learned something each week and users still do not care, it is fine to start a new project. You will carry the skills over.

Read the full guide for the whole launch plan.