I launched and nobody's buying. What to do on Monday
Find out which of three things is broken, the people, the problem or the offer, and fix that one before you build anything else.
3 min read · Updated 1 Nov 2026
The short answer
If you've launched and nobody's buying, stop building for a week. Something is broken in one of three places: the people seeing it, how much the problem matters to them, or the offer you're asking them to accept. Talk to ten people who match your customer about the last time they hit the problem, then fix the first thing that's broken.
In June 2026 Pieter Levels passed on a friend’s report from a meetup of indie hackers building AI products. They’d built impressive automated pipelines, he wrote, “but the most interesting part is that almost none of them have money or traffic” (levels.io).
Building has got cheap. Finding the people who’ll pay hasn’t, and that’s the gap most quiet launches fall into. The good news is that a launch with no buyers is information. This piece is about reading it.
First, check whether anyone has actually seen it
Before you decide the product is wrong, check the numbers. Unbounce’s 2024 benchmarks, drawn from more than 41,000 landing pages, put the median conversion rate for SaaS pages at 3.8% (MarketingProfs). At that rate, 100 visitors gets you three or four sign-ups.
So if your launch brought 80 visitors, most of them friends, other founders and people browsing a directory, zero sales doesn’t prove much yet. You have a reach problem before you have a product problem. If you’ve had several hundred visitors who look like your customer and still nothing, the page or the offer is telling you something.
The three places it breaks
Almost every quiet launch is broken in one of three places. Work out which one before you change anything.
| Where it breaks | What it looks like | What to test this week |
|---|---|---|
| The people | Visitors are other founders, friends or tyre-kickers. Nobody who looks like your customer has seen it | Name ten real people who match your customer and get it in front of them directly |
| The problem | The right people see it and shrug. They agree the problem exists but they’re managing fine | Ask about the last time it happened and what it cost them. If nobody can remember, it isn’t painful enough |
| The offer | People are interested but don’t act. They ask questions, then go quiet | Rewrite the page in their words, show the price, and ask for one clear decision |
What to do on Monday
- Stop building for a week. No new features, no redesign. Every hour goes to finding out which of the three is broken.
- Write down ten names. Real people who match your customer, with how you’ll reach each one. If you can’t name ten, the people part is your problem and you’ve already found it.
- Ask for fifteen minutes, about the problem. Skip the demo. Ask about the last time the problem happened: when, what it cost, what they did about it.
- Write the problem in their words. Use the exact phrases they used. The Problem Receipt below is built for this.
- Rewrite the offer from what you heard, then ask each person for a decision: buy, start a paid pilot, or tell you why not.
What to stop doing
Adding features is the most common response to a quiet launch, and it’s usually the wrong one. If the people seeing it aren’t the people who need it, a better product meets the same silence. The same goes for a redesign, a second directory launch, or paid ads before you know who buys.
Each of those feels productive because it’s building. The work that fixes a quiet launch is mostly conversations, and it feels slower than it is.
Almost none of them have money or traffic. And nobody knows where to get either one.
When it’s time to stop
Decide the line before you start the week, and write it down. For example: “If twenty conversations with people who match my customer produce no one who calls the problem costly, I’ll pause this and write up what I learned.”
Then you have four honest options when the week ends: carry on with a clearer customer, narrow to the people who did respond, change the offer, or pause. Each one beats another month of polishing something nobody has asked for.
Questions
How many visitors do I need before I can judge my launch?
More than most founders have when they start worrying. Unbounce's 2024 benchmarks put the median SaaS landing page at 3.8% conversion, so 100 visitors would bring three or four sign-ups at the median. Below a few hundred visitors from the right people, treat zero as a reach problem first.
Should I relaunch on Product Hunt or another directory?
Not yet. A second launch sends more of the same people to the same page. Fix whoever it's for and what you're offering first, then launch again with something that has changed.
Should I run ads to get traffic?
Only once you know which people buy and what they respond to. Ads before that buy you expensive proof of the same silence.
What if the people I talk to say they like it?
Ask what they did about the problem last time and whether they'd pay for this now. Liking it is polite. Paying, or arranging a second call with the person who pays, is evidence.
When should I give up on it?
Decide before you start this week. For example: if after twenty conversations nobody describes the problem as costly, pause and write down what you learned. Pausing on evidence is a good outcome.
Next step
Is your idea worth 30 days? Find out free.
Five questions about your idea and a straight answer. It's week zero of Humble's 30 days, and it costs nothing.