What to do the week after your SaaS launch dies

Launch day is over. The chart flatlined. You refresh analytics like the number might change if you stare hard enough. It will not. The week after a dead launch is where most builders open the editor and start “v2.” That is the wrong move.

In July 2026, Jack Builds wrote on Indie Hackers after four months of solo work. He coded the features. He polished the landing page. He set up onboarding. Launch day: zero paying customers, not one signup. He had never talked to a potential customer before he shipped. His first ten customers came later, when he looked for people already searching, not from feature 47 on the roadmap.

A quiet launch is not a funeral. It is a list. People who visited, upvoted, commented, or said “interesting” already showed up once. This week you write them. You do not hide in the editor. Indiecity is for one person or a team under twenty. You do not need a relaunch campaign. You need ten human follow-ups and a clear ask. If you launched with zero paying customers, this is the week that decides whether that stays true.

What a dead launch actually means

A dead launch means strangers did not turn into buyers on day one. It does not mean the problem is fake. It does not mean you need a new product. It means the launch was traffic, or it was nothing, and either way you still have not done the unscalable work.

Paul Graham wrote in 2013 that the big launch usually does not work, and that you have to go out and get users. That line still holds in 2026. Building got cheaper. The feed filled with lookalike SaaS pages. Pieter Levels said it in June 2026: everyone can build apps with AI, and almost nobody has an audience, ad money, or a free way to get attention. A dead launch is the default. Recovery is manual.

You can't wait for users to come to you. You have to go out and get them.

Treat the silence as your cue to start the list, not as a verdict. Open the names of people who already saw the thing.

Do not build v2 this week

The editor feels safe. A new feature feels like progress. Jack spent most of his time building and almost none finding buyers. After zero, he flipped it. That flip is the whole week. You ship code only when a conversation or a paid user forces a fix. You do not invent a roadmap to avoid the inbox.

On that same thread, wealtii wrote about ten months on Wealtii: hundreds of thousands of lines of code, a product he was proud of, launch day silence. His first 30 users came from personal messages, not a growth hack. He had been hiding in the editor. If your first instinct after a dead launch is “I need better onboarding,” pause. You need names.

• No new major features until someone paid or booked a real call.
• No second Product Hunt date as a substitute for follow-up.
• No full redesign from your own taste.
• No “waitlist while I rebuild” if you could already deliver the outcome.
• Fix only what blocks a demo or a payment you already have.

Building is easy to measure. Conversations are not. Measure conversations this week.

Pull everyone who already showed up

Before you invent strangers, write the people who already touched the launch. They are warmer than a cold list. They already spent a click.

• Signups, waitlist emails, “notify me” forms
• People who started checkout and stopped
• Product Hunt, Indie Hackers, or HN commenters and upvoters you can message
• Friends who said they would try it later
• Analytics: emails from forms, chat widgets, calendar links, support pings
• Anyone who DMed “cool project” and got a thumbs-up from you

Write 20 names if you can. Ten is the floor. If you cannot find ten humans who ever saw the page, the launch never left your bubble. Expand to people who already complain about the problem in public, not to another feature branch.

Write the people who visited

This is the work of the week. Short notes. One person at a time. No ChatGPT opener. No “hope this finds you well.” Say what they saw, what the product does in one line, and ask for 15 minutes or a yes on price.

Hey [name]. You checked out [product] last week when I launched. It does [outcome] for [who] at [price]. I am writing the people who actually opened it, not blasting strangers. Got 15 minutes this week so I can see if it matches how you work? If not, a one-line “not for me” helps.

Hey [name]. You saw [product] around launch. Curious whether [pain in their world] is still a mess for you. If yes, I can show the one path that fixes it in 15 minutes and tell you the price. If no, who should I talk to instead?

Hey [name]. Thanks for the [upvote / comment] on [post]. I am following up with people who actually looked. [Product] is [price] for [outcome]. Want a quick walkthrough, or is this not your problem?

Send two or three a day. Track sent, replied, booked, paid. When someone books, show the one thing that removes their pain, say the price, and stop talking. Do not end with “I will send a link later.” Get the payment while they still care. That full loop is the same job as getting your first 10 paying customers without ads. The dead launch just handed you a warmer list. If you launched with no followers, the same list work is in how to launch a SaaS with no audience.

If the visitor list is empty, go where people already complain

Some launches truly hit zero. No emails. No comments. Then you still do not build v2. You go where the pain is already written down. On Jack’s thread, OmnionAi put the method in plain terms: search for people asking for a tool that does X, read one-star reviews, show up the same day someone vents. You answer a need they already feel.

Do not confuse founder rooms with customer rooms. If your buyer is not a founder, another Indie Hackers post is still the wrong room. Other builders will clap. They will not pay. Sit in the forum, Slack, or Discord where buyers already talk about their work. Reply with help first. When someone describes the problem your page already charges for, send them the page.

• Threads asking for a tool that does X
• One-star reviews on competitors
• Niche Slack and Discord channels where people vent about the workflow
• Job posts and public threads that describe the broken process in their own words
• Your own network: past clients, coworkers, people who complained in a chat

Copy their words. Those words replace your headline. That is the only “rebuild” allowed this week.

A seven-day plan after the silence

1. Day 1. Export every name and email that touched the launch. Write the offer in one sentence with a price. Close the feature branch.
2. Days 2 to 4. Send two or three personal notes a day to visitors, signups, and warm comments. Log sent, replied, booked, paid.
3. Day 3 or 4. Take every booked call. Show one path. Ask for the money on the call.
4. Day 5. Rewrite only the headline and the one sentence under it using words people said back to you. No new screens.
5. Days 5 to 7. Write the next ten names from those rooms or from intros. Ask every paid user for one intro.
6. Day 7. Count replies, calls, and payments. If people are replying, keep going. If you have zero after 20 real asks, change the buyer or the offer. Do not schedule another launch party.

Keep four columns: sent, replied, booked, paid. Add a fifth for the exact phrase they used for the problem. That phrase is your next page, not your next feature list.

How you know the week worked

People reply. People take 15 minutes. Someone asks the price before you do. Someone pays. Those are the only signals that matter. “Cool idea” does not count. A second spike of launch traffic does not count.

If 20 people who should care will not give you 15 minutes, you are talking to the wrong people or they do not spend enough on this problem. That is useful. It is not a reason to hide and build v2. Change the offer or the buyer. Then run the same week again.

What to stop doing

• Opening a v2 roadmap the morning after silence
• Blaming the landing page before you talk to ten visitors
• Posting another launch thread instead of writing people who already came
• Buying ads to avoid the list
• Pitching on a learning call and calling that proof
• Pasting the same ChatGPT opener to everyone who upvoted
• Waiting for the “right” week to follow up

Then keep going

A dead launch is common in 2026. Recovery is boring: names, notes, a price, and a direct ask. Jack’s first ten did not come from polishing. wealtii’s first thirty did not come from more code. Yours will not come from v2 either.

If this week produces paying customers and you will put your name on how you got them, send us the story. Keep the days in Launch week. You can join Indiecity while you send the notes. That gives you people to talk to. It does not replace the list.

Until then, write the people who visited. Leave the editor closed.