What to do if your SaaS has zero paying customers after launch

You launched. The chart is flat. The bank account did not move. The urge is to open the editor and “fix” the product. That urge is the trap.

In July 2026, Jack Builds wrote on Indie Hackers after four months of solo building. 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.

Zero after launch is not rare in 2026. Building got cheap. The feed filled with lookalike 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. Indiecity is for one person or a team under twenty. You do not need a relaunch campaign. You need people, a price, and a direct ask.

What zero actually means

A paying customer is someone who sent you money. A payment link, an invoice, a bank transfer, UPI, or cash. Signups who never pay do not count. Friends who will “try it later” do not count. “Interesting” does not count. Zero means money never moved. It does not mean the problem is fake. It does not mean you need a new product on day two.

It usually means one of three things. Name which one before you touch the code.

• Nobody who feels the pain saw you. First move: rooms where buyers already complain, not a new feature.
• The people who saw you were not buyers. First move: change who you write to, not the landing page palette.
• You never asked for money in plain words. First move: a price in the next note.

You find out which one by talking. You do not find out by shipping v2 in private. A second product waits until you can write, in plain words, which of those three you actually hit.

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

Paul Graham wrote that in 2013. It is even more true now. The big launch does not do the work for you. You go get users one by one.

Do not build v2

The editor feels safe. A new feature feels like progress. Jack did the common thing: months of building, almost no time finding buyers. After zero, he flipped it. 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 spent ten months building, then launched to silence. His first 30 users came from personal messages, not more code. If your first instinct after zero is “I need better onboarding,” pause. You need names.

• No 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 in front of a product you could already charge for.
• Fix only what blocks a demo or a payment you already have.

Building is easy to measure. Conversations are not. Count conversations until the board is not zero.

Talk to people who already have the pain

Start with anyone who already touched the launch: signups, waitlist emails, commenters, upvoters, “cool project” DMs, friends who said they would try it later. They already spent a click. That list is the only leftover the launch gave you. Treat it like inventory, not a trophy. Write them before you hunt strangers. The recovery week after silence is spelled out in what to do the week after your SaaS launch dies. Use that plan if you still have a warm visitor list.

If the visitor list is empty, 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.

When you get someone on a call, keep learning and selling apart. Rob Fitzpatrick’s Mom Test is simple: talk about their life, ask what they did last time the problem hit, and do not pitch. After you know they have the pain and you have a price, the next call is a sales call. Mix the two and people stay polite. They do not pay.

Write ten humans this week

LinkedIn and email are full of the same ChatGPT opener. Everyone sounds identical. A note written for one person still gets opened. Ten human messages beat two hundred automated ones.

Hey [name]. You checked out [product] when I launched. It does [outcome] for [who] at [price]. I am writing the people who actually opened it. 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]. Last time we spoke you were dealing with [the messy thing]. I built a small tool that does [outcome] for [who]. It is [price]. If that is still a pain, I can show you in 15 minutes this week. If it is not, who should I talk to instead?

Hey [name]. Saw your note about [pain in their words]. I charge [price] to [outcome] for people in that exact mess. Want a 15-minute walkthrough, or is this not your problem right now?

Charge a number you can say without wincing. Patrick McKenzie has been saying for years that most builders undercharge. Put the price in the note. Send it.

On the call, ask for the money

Fifteen minutes. Not a 40-minute demo. Have them say the problem in their own words. Show the one thing that removes it. Then say the price and stop talking. Do not end with “I will send a link later.” Get the payment while they still care.

If this takes [pain] off your week, it is [price]. I can start you today. Want to do that?

If they need to think, book the follow-up before you hang up. If they say it is too expensive, ask what they currently spend (time, tools, a person) on the same mess. Stay on the price unless you learn you priced the wrong buyer. After the first payment, ask for one intro. One paid customer plus a name beats a waitlist of fifty.

That full loop of price, list, notes, calls, and intros is how to get your first 10 paying customers without ads. Zero after launch is the reason you start that loop now, not after the next rewrite.

A two-week plan out of zero

1. Day 1. Write 0 / 10 on a line. Write the offer in one sentence with a price. Export every name that touched the launch. Close the feature branch.
2. Days 2 to 6. Send two personal messages a day. Track sent, replied, booked, paid.
3. Day 7. Rewrite only the headline and the line under it using words people said back to you. Do not add features.
4. Days 8 to 12. Send the next ten names from warm visitors, intros, or rooms where buyers already complain. Ask every paid customer for one intro.
5. Days 8 to 12. One useful reply in a room you already belong to, if a real question matches the offer.
6. Day 14. Count paying customers. If you have some, keep going. If you have zero after 20 real conversations, change the offer or the buyer. Do not buy ads. Do not book another launch day.

Keep four columns: sent, replied, booked, paid. Add a fifth only for the exact phrase they used for the problem. That phrase replaces your headline.

How you know it is working

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 prettier app does not count. A second launch post 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. Your offer or your buyer is wrong. It is not a reason to hide in the editor and build v2.

What to stop doing

• Building the next version before anyone paid for this one.
• Treating a quiet launch day as the end of the product.
• Adding a waitlist in front of a product you could charge for now.
• Buying ads so you can avoid writing ten names.
• Posting another launch thread instead of writing people who already came.
• Pitching on a learning call and calling that proof.
• Pasting the same ChatGPT opener to everyone who upvoted.

Then the board is not zero

Zero after launch is common. 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 you get paying customers and you will put your name on how you got them, send us the story. When the product is real, put it on the map. You can join Indiecity while you send the notes. That gives you people to talk to. It does not replace the list.

Until then, talk to people. Leave the editor closed.