How to fix a SaaS launch that got zero signups

Find out why your SaaS launch got zero signups from three numbers, fix a broken signup or unclear headline the same day, and replace the launch with a daily routine of messages and answers.

ByDinesh BypillaReviewed byMurali SidLast checked 17 min read

You launched your SaaS on Product Hunt, Show HN or Reddit, and got zero signups. To fix a SaaS launch that got zero signups, first find where people stopped, from three numbers you already have, and fix that one thing today. Then replace the launch with a daily routine, because a launch is one day and your first users come from the weeks after it.

Do these three things

About 4 to 5 hours a day, every day. Fix the signup today. Judge the rest after 2,800 messages and 560 answers, about 4 weeks.

Show the three actions in full
  1. Today: find where your launch lost people from three numbers: visits, clicks on your signup button and finished signups. Then sign up yourself on a phone and a laptop, and fix the first thing that breaks.
  2. Every day: send 100 personal messagessoon, starting with everyone the launch reached, and answer 20 questions in places where people ask about the problemsoon now. AI drafts; you add one true line.
  3. Every Sunday: count signups by where they came from. Relaunch only once you have 20 users and a real change to show.

Get help doing these

ChatGPT or Claude reads this guide and works through it with you.

1. Find where your launch lost people, using three numbers

A launch with zero signups broke in one of three places: too few of the right people saw it, people came but the page did not tell them why to sign up, or people tried to sign up and could not. Three numbers from launch day tell you which one.

Pull these for the launch day and the 3 days after it:

  1. Visits from the launch. In Google Analytics 4 (free), go to Reports, then Acquisition, then Traffic acquisition. Add the "Session source" dimension and read the row for producthunt.com, news.ycombinator.com, reddit.com or wherever you posted.
  2. Clicks on your signup button. If you track conversionssoon, read the event. If not, count visits to your signup page.
  3. Finished signups. Count new accounts in your database for those days, not in your analytics.

Then read them with this rule:

  • Under 100 visits from the launch: a reach problem. Too few people saw it. Do steps 2 and 3 first, about 2 hours 30 minutes in all, then put your time into steps 4 and 5.
  • 100 or more visits, but fewer than 3 clicks on signup: a page problem, a low conversion rate. People came and did not see why to try it. Go to step 3 next.
  • Clicks on signup, but 0 finished signups: a signup problem. People wanted in and something stopped them. Go to step 2 now.

If you had no analytics on launch day, install Google Analytics 4 and Microsoft Clarity today. Clarity is free with no traffic limit, and records visits so you can watch where people stop. Since 31 October 2025, it needs a consent signal from your cookie banner before it records visitors from the EU, UK and Switzerland. Without the numbers, do steps 2 and 3 anyway. They take about 2 hours 30 minutes and check the page and the signup.

In July 2026, a founder reached the top 50 on Product Hunt and got zero signups. His own words: "People browsing PH are in discovery mode. They're not in pain right now." He also said his headline was "too vague". That was a reach problem and a page problem at once.

  • Tool: Google Analytics 4, Microsoft Clarity and your database. All free.
  • Time: 30 minutes.
  • You will have: three numbers in a sheet, and one line: "My launch broke at ___."
  • It worked if: you can fill in that line with a number beside it.
  • Common mistake: judging the launch by upvotes, rank or comments. None of them is a visit or a signup. A high bounce rate on its own does not tell you which of the three problems you have either. The other mistake is fixing the product first. Check the numbers, then fix where they point.

See it done: Bugmoth's launch-day numbers

Bugmoth is a made-up bug-reporting tool for small web teams. It costs $19 a month per team, with a 14-day trial.

Product Hunt launch, day 1 to day 4

NumberCountWhere it came from
Visits from producthunt.com212Google Analytics 4, Traffic acquisition
Clicks on "Try it free"9Visits to the signup page
Finished signups0New rows in the accounts table

Why it works: Most visitors did not click, but 9 who did click still made no account, so the signup form is the first thing to fix.

2. Sign up yourself on a phone and a laptop, and fix what breaks

Sign up to your own product as a stranger would, four times, and fix everything that stops you. A broken signup is easy to miss, because people who hit an error close the tab and never tell you.

In June 2026, a founder asked Hacker News why his site had no users after a month. The first people to try it found the answer in minutes: registration showed "Something went wrong on our side", the code request failed, the form did not fit on a phone, and a sign-in screen came before anyone could try the product. One wrote: "get hit by a sign in screen, my enthusiasm has gone, close tab."

Do the test like this:

  1. 1

    Sign up four times

    Open a private window, so you are not logged in. Sign up once on your phone and once on a laptop, each with a new Gmail address and a new Outlook address. Four signups in all. Use every sign-in button you show, such as "Sign in with Google".

  2. 2

    Time the confirmation email

    Write down how long each confirmation email takes, and whether it lands in the inbox or in spam. It should arrive in the inbox within a minute.

  3. 3

    Check who sends your emails

    If you built on Supabase and never set up your own email sender, your emails may not reach anyone. Supabase's built-in sender is for testing: it sends about 2 emails an hour and only to your own team. Set up your own email sending service and turn on SPF or DKIM for the domain it sends from. Gmail requires one of them from every sender.

  4. 4

    Let people try before they sign up

    If the main thing needs an account, add a demo that works without one: sample data, or the first result before the signup form. Show HN's rules ask for the same: make it easy to try, "ideally without barriers such as signups or emails". It is how you get people to try your product at all.

Ask for a credit card at signup only if you already know people pay. If you ask now, you will have fewer signups to learn from. The free trial or freemiumsoon choice can wait until people use it. Also open the page on your phone's mobile data. If you are still waiting when you want to tap the button, fix the slow sitesoon next.

  • Tool: your phone, a laptop, two free email accounts and your email sending service.
  • Time: 1 hour for the test. Fixes vary: an email sender takes about an hour to set up.
  • You will have: four test signups in your sheet, and every break fixed.
  • It worked if: 4 of 4 test signups finish, and every confirmation email lands in the inbox within a minute.
  • Common mistake: testing only on your own laptop, where you are already logged in. The other mistake is sending more people to the site before this passes. Fix it first.

See it done: Bugmoth's four test signups

Test signups, before and after the fix

DeviceEmailBefore: confirmation emailAfter: confirmation email
PhoneGmailNever arrivedInbox, 12 seconds
PhoneOutlookNever arrivedInbox, 20 seconds
LaptopGmailNever arrivedInbox, 9 seconds
LaptopOutlookNever arrivedInbox, 15 seconds

Why it works: The test found the fault in 20 minutes: the confirmation email never arrived, so nobody could finish.

3. Test your homepage on 10 people for 5 seconds and fix the headline

Show your homepage to 10 people for 5 seconds, then ask what it does and who it is for. If fewer than 8 can say, rewrite the headlinesoon so it names the result the user gets, in their words.

This is the page problem from step 1. The full method is in step 2 of how to market a SaaS product. The short version: take the sentence that says who your SaaS is for, turn the problem into the result, leave out the technology, and put a "Try it free" button right under it. Your value proposition is the headline.

Before you rewrite, watch 20 visit recordings in Clarity. Note where people stop scrolling, what they click that is not a link, and whether anyone reaches the button. Write down the most common stopping point. That tells you if the headline is the problem or something lower on the page. For a longer fix, find where visitors drop offsoon.

The headline
[What the user gets, in their words]. [How fast, or which pain goes away].[One line under it: who it is for.][Button:] Try it free

Find the 10 people from outside your team: friends at companies like your buyer, or people in the communities from step 5. Ask them to answer in writing, so you do not help them.

  • Tool: Microsoft Clarity and your site editor.
  • Time: 1 hour 30 minutes.
  • You will have: a new headline live on the site, and a note of where visitors stop.
  • It worked if: at least 8 of 10 people can say what it does and who it is for. Then check the next 200 visits give more clicks on signup than launch day did. At this traffic, skip an A/B testsoon; it would take months.
  • Common mistake: redesigning the whole site. Change the headline, the line under it and the button first, then look at the numbers again.

4. Message everyone the launch reached, then 100 people a day

Send a personal message to every person your launch reached: everyone who commented, replied, emailed you or joined a waitlistsoon. Then send 100 personal messages a day to people who fit your buyer.

The people who commented already know your product. That makes them warm outreach, and it is the fastest place to start. Reply to every comment on the launch page first. Then, where a person's profile links to a website, X or LinkedIn, message them there, and quote what they said.

After that, run the daily routine from how to get your first 100 SaaS users, step 4:

  • Add 100 new names a day to your lead listsoon: people who have the problem, found on Google and LinkedIn. 100 a day needs about 3,000 names a month.
  • Let AI draft, and you add the truth. Paste 10 names at a time into ChatGPT or Claudesoon, each with one thing you found about them. Read each draft and make the first line true and about them. About a minute a message.
  • Offer a 15-minute set-up call, not a demosoon. They do the main thing while you help. It turns a "maybe later" into a user today, and you hear feedback from your first userssoon first-hand.
  • Follow upsoon twice, 3 days apart, with one new line each time. Stop the moment someone says no.

Keep every message one-to-one, even if you are a technical founder who hates selling: you are asking about their problem. If you email more than about 50 strangers a day, set up a second domainsoon and warm it up first, so your signup emails from step 2 stay safe. LinkedIn restricts invitations when you send too many, and the block usually lasts a week, so on LinkedIn message people you are already connected tosoon and send the rest by email. In the US, the CAN-SPAM Act covers business email too: every message needs your postal address and a way to say no, and you must honour a "no" within 10 business days. In the UK and EU, the rules are stricter, so check them first.

The message to someone the launch reached
Hi [first name],Thanks for your comment on [launch site]: "[their words]".[One line that answers it, or says what you changed because of it.]Would you let me set it up with you on a 15-minute call? You'd have [the result] by the end. Pick a time: [booking link][Your name]
[Your company, postal address]
Not for you? Reply "no" and I won't write again.
  • Tool: the launch page, Gmail or LinkedIn, ChatGPT or Claude, and your sheet.
  • Time: about 2 hours a day for messages and follow-ups, 45 minutes to find 100 new names, and the calls they book.
  • You will have: everyone the launch reached messaged in the first 2 days, then 700 messages sent and logged each week.
  • It worked if: you get at least 3 chats or set-up calls from every 100 messages. Below 2, rewrite the first linesoon so it is more about them, then send the next 100.
  • Common mistake: a mass "We just launched!" email to a bought list. That is spam, and it can put your signup emails in spam too. The other mistake is stopping after 50 messages because nobody replied yet.

See it done: Bugmoth's message to a launch commenter

To: Dan, who runs a 3-person web studio and commented on the Product Hunt launch

Subject: your comment on our launch

Hi Dan,

Thanks for your comment on our launch: "Does it work on client staging sites with a password?"

It does now. We added it the day after, because of you.

Would you let me set it up on one of your client sites with you on a 15-minute call? By the end, your client can click a bug and you get the screenshot, their browser and the steps. Pick a time: [booking link]

Sam Bugmoth, [postal address] Not for you? Reply "no" and I won't write again.

Why it works: It quotes his comment, shows the founders listened, and offers to get it working on a call.

5. Answer 20 questions a day where people have the problem now

Pick 5 online places where people ask for help with the problem your SaaS fixes, and answer 20 questions a day across them. A launch reaches people who are browsing. These places reach people who have the problem today.

In August 2026, a founder 15 days after a launch counted 3 Product Hunt upvotes and 1 new follower on X. His note: "I have been publishing, not distributing." One useful 40-minute argument in someone else's thread did more than the whole launch. So he stopped posting announcements and went to answer questions.

A place can be a subredditsoon, a Slack or Discord group, or a forum. Read each place's rules on self-promotion first. Reddit's own rule is to "participate authentically in communities where you have a personal interest, and do not spam". Spread 20 answers over 5 places; 20 in one place in a day looks like spam.

Search each place for the words your buyers use for the problem, and sort by New. Answer as if your product did not exist. Say it is yours only if someone asks, or the thread allows it. AI can find the questions and list the points to cover. Write the answer in your own words: communities remove replies that read as pasted from AI. The reply template is in step 5 of how to get your first 100 SaaS users.

  • Tool: the search box on each site.
  • Time: about 1 hour a day, 3 minutes an answer. Steps 4 and 5 together are about 4 to 5 hours a day; fit them into your week before anything else.
  • You will have: 140 useful answers a week, under your own name.
  • It worked if: after 560 answers (4 weeks), at least 5 signups say they came from one of these places.
  • Common mistake: pasting your launch link into every thread. Moderators remove it, and accounts that keep doing it get banned.

6. Relaunch only after 20 users and a real change

Do not relaunch next week. Relaunch once you have about 20 users and something real to show, because the launch sites have rules on when you may post again, and a second quiet launch teaches you nothing new.

The rules today:

  • Product Hunt: wait at least 6 months between launches of the same product, and there must be a significant update, such as a new mobile app or a redesign with new features. Product Hunt says new designs and pricing changes do not count. You can ask to relaunch sooner, and its team reviews the request. Its help page was updated on 7 July 2026. Use the wait to prepare a better Product Hunt launch.
  • Show HN: if your post got little attention, Hacker News allows "a small number of reposts". Do not delete a post and post it again. Show HN is only for things people can try, not landing pages. When the change is ready, post a new Show HNsoon.
  • Never ask anyone for upvotes. Hacker News says "Please don't ask friends to upvote or comment", and Product Hunt can ban you for paying anyone to hunt your product or send it traffic.

Until then, do not count directory submissionssoon as a launch. They mostly bring links, not users. If you want people to test it before you relaunch, find beta users the same way as step 4.

  • Tool: Hacker News and Product Hunt. Both free.
  • Time: 15 minutes now to write down the date and the change. Half a day to prepare when the time comes.
  • You will have: a relaunch date, the change you will show, and the user count you must reach first.
  • It worked if: on relaunch day you have at least 20 users, a signup that passed step 2, and a demo people can try without an account.
  • Common mistake: relaunching with a new design and calling it an update. The other mistake is spending the next month planning the relaunch instead of doing steps 4 and 5.

7. Count signups every Sunday and decide after 2,800 messages

Every Sunday, fill in one row: messages sent, answers posted, signups, users, and where each signup came from. After 2,800 messages and 560 answers, use the rules below to decide what to do next.

Add one question to your signup form: "Where did you hear about us?" This is self-reported attribution. Tag every link you share with UTM parameterssoon too, so your analytics show the source. The Sunday sheet is the one in step 7 of how to market a SaaS product.

After 2,800 messages and 560 answers (4 weeks), use these rules:

Leave paid adssoon until at least 10 people have paid you and you know which message brought them. Once a month, step back for a marketing reviewsoon.

  • Tool: Google Sheets and your signup form.
  • Time: 20 minutes each Sunday.
  • You will have: one row a week, and a clear answer on where your signups come from.
  • It worked if: every signup in the sheet has a source.
  • Common mistake: changing everything after one quiet week. Judge after 2,800 messages, not after 7 days.

Where Scout7 helps

Scout7 speeds up step 5. Join Conversations searches social platforms for live discussions about the problem your SaaS fixes, groups them by the kind of reply that fits, and drafts a reply in your voice. You read each thread yourself and approve or rewrite every reply. Nothing is posted without your approval.

Your zero-signups launch fix checklist

0 of 17 done

Work through this list with an AI assistant

It drafts the work and keeps track of what is done.

Step 1 · Find where your launch lost people

Step 2 · Sign up yourself and fix what breaks

Step 3 · Test your homepage and fix the headline

Step 4 · Message everyone the launch reached, then 100 a day

Step 5 · Answer 20 questions a day

Step 6 · Relaunch only after 20 users and a real change

Step 7 · Count signups every Sunday and decide

Frequently asked questions

Is it normal to get zero signups from a launch?

It is common. A launch reaches people who are browsing, and many have no need for your product that day. In July 2026, a SaaS in Product Hunt's top 50 got zero signups. Zero from 100 or more visits still tells you something: the page or the signup needs fixing. Zero from 30 visits tells you only that too few people saw it.

How do I know if it's my product or my marketing?

You cannot tell from one launch. Send 2,800 personal messages and 560 answers first. If nobody will even take a chat, you are talking to the wrong people. If people chat but will not sign up, the offer or the product misses. That is the job of why no one is buying your product.

Can I relaunch on Product Hunt next month?

Usually not. Product Hunt asks for at least 6 months between launches of the same product and a significant update, such as a new app or new features. A new design or new prices does not count. You can request an earlier relaunch, and its team decides. Use the months to reach 20 users, so the next Product Hunt launch has something to show.

Should I run ads to get signups after a failed launch?

Not yet. Ads send strangers to a page and signup you have not proved. Fix the signup (step 2) and the headline (step 3), then get signups by hand. Wait until at least 10 people have paid you and you know which message brought them. A small ad budgetsoon spent before that usually runs out before you learn anything.

Should I build a waitlist before my next launch?

Yes, if you can do it while you work on steps 4 and 5. Everyone who replies, chats or signs up in the next weeks is someone you can tell on relaunch day. A waitlistsoon is a list of people who asked to hear from you. Email each of them yourself on the day, not a mass announcement.

Sources

  1. 1.Ask HN: Spent thousands, got no customers. What's wrong with my site? — Hacker News, 4 June 2026
  2. 2.5 days post-launch: Top 50 on Product Hunt, zero signups, and why I think that's actually fine — Indie Hackers, 7 July 2026
  3. 3.15 days after launching to zero audience: $0, 1 follower, 0 stars. The full numbers. — Indie Hackers, 27 August 2026
  4. 4.[GA4] Traffic acquisition report — Google Analytics Help, checked 28 September 2026
  5. 5.Microsoft Clarity: free heatmaps and session recordings — Microsoft, checked 28 September 2026
  6. 6.Clarity cookie consent update: what site owners need to know — Microsoft Clarity Blog, 31 October 2025
  7. 7.Send emails with custom SMTP — Supabase Docs, checked 28 September 2026
  8. 8.Email sender guidelines — Google Workspace Admin Help, checked 28 September 2026
  9. 9.Show HN guidelines — Hacker News, checked 28 September 2026
  10. 10.Hacker News FAQ — Hacker News, checked 28 September 2026
  11. 11.Can I relaunch my product? — Product Hunt Help Center, updated 7 July 2026
  12. 12.How to schedule or draft a launch — Product Hunt Help Center, updated 24 February 2025, checked 28 September 2026
  13. 13.How Product Hunt works — Product Hunt, checked 28 September 2026
  14. 14.CAN-SPAM Act: A Compliance Guide for Business — Federal Trade Commission, checked 28 September 2026
  15. 15.Invitation limit reached — LinkedIn Help, checked 28 September 2026
  16. 16.Reddit Rules — Reddit, checked 28 September 2026

Next article to read

How to fix a SaaS website with traffic but no signupsSaaSComing soonOnce people visit again, this finds where they drop off before signing up.

Guides that link here

Cite this page

Dinesh Bypilla (2026). How to fix a SaaS launch that got zero signups. Scout7 Academy. https://scout7.ai/academy/first-customers/how-to-fix-a-saas-launch-that-got-zero-signups

Written by Dinesh Bypilla, Agentic systems engineer at Scout7. Reviewed by Murali Sid. Last checked 28 September 2026.

Quote any part of this guide with a link back to this page. © 2026 Scout7.

Markdown version of this page: https://scout7.ai/academy/first-customers/how-to-fix-a-saas-launch-that-got-zero-signups.md