No list, no followers, no community to poll. Where to find ten strangers with the problem, and what to ask them.
To validate a SaaS idea with no audience you have to start somewhere other than where every guide begins. Post to your list, poll your followers, ask your community — none of that is available to you, so here is the version that starts from zero.
Validating without an audience is slower, not impossible. Budget three weeks.
Having no audience is also an advantage worth naming: nobody is watching, so you can change direction without explaining yourself.
People with expensive problems talk about them publicly. Four places, ordered by signal quality.
| Source | What you get | Effort |
|---|---|---|
| Review sites for competing tools | Complaints from people already paying | Low |
| Niche forums and subreddits | Problem described in their own words | Low |
| Support and feature-request threads | Unmet needs in existing products | Medium |
| Job listings mentioning the task | Companies paying salary to solve it | Medium |
Review sites are the strongest starting point and the most underused. A one-star review of a competitor is a person with budget, an active problem, and a documented reason for being unhappy. That is a better prospect than anyone on a mailing list you do not have.
Spend the first few days reading fifty complaints without contacting anyone. It costs nothing and it changes every message you send afterwards.
You are collecting two things. The exact words people use for the problem, which become your outreach language and later your headline. And the frequency — whether the same complaint recurs across many people or one person said it loudly.
Founders who skip this write outreach in their own vocabulary, get low response rates, and conclude that cold outreach does not work.
Ten conversations is the target. Expect roughly forty messages to get there, which is a week of work rather than a month.
What makes cold outreach convert at this stage is specificity. Reference the exact thing they wrote. Ask about their process, not your idea. Request twenty minutes, not a call.
Do not mention that you are building something. The moment you do, you get politeness instead of information — people soften criticism when they think you have already invested.
Four questions, in this order. All about the past, none about the future.
Never ask whether they would use your product. People are agreeable about hypotheticals and precise about history. The customer interview guide covers the technique in more depth.
Conversations establish that a problem exists. They do not establish that anyone will pay. That needs a separate test, and it is where validation without an audience usually stops too early.
Ask for something small and real: a pre-order, a paid pilot, a scheduled date to trial it, or an introduction to whoever holds the budget. Any of the four costs the person something.
Three commitments out of ten conversations is a strong signal. Zero commitments alongside ten enthusiastic conversations is the clearest warning available — and it is the pattern that kills more ideas than outright rejection does.
Enthusiasm is free and worthless. Ten people saying "I would definitely use that" and none of them putting a date in the diary is a negative result, not a neutral one. Treat it that way.
The conversations themselves are the start of your distribution. Ten people who spoke to you about their problem are ten people who will hear about the launch.
Ask each one whether they want to know when it exists. Most say yes, and that becomes the launch list you did not have three weeks earlier. That list of ten to thirty people outperforms a large following of strangers.
Being useful in the same places you found them compounds this. Answering questions properly in one forum for two months builds the channel that carries you to your first customers — the first customers guide covers the manual work.
Once the problem and the willingness to pay are both established, run the structured version before building — the validation checklist covers the nine specific tests.
Then decide who this is for and what it replaces, because that decision sets your pricing ceiling. The positioning framework works through it in five components, starting with the alternative you named in your interviews.
For the wider process and the full sequence, see how to validate a SaaS idea.
Go where people already complain publicly — review sites for competing tools, niche forums, support threads and job listings. Read fifty complaints before contacting anyone, then send around forty specific outreach messages to get ten conversations. Budget three weeks.
Review sites for competing tools are the strongest and most underused source. A one-star review is a person with budget, an active problem and a documented reason for being unhappy — a better prospect than a mailing list you do not have.
Ten conversations with people who have the problem, which typically takes around forty outreach messages. Patterns repeat quickly at that scale, and the tenth conversation rarely tells you something the first eight did not.
No. Once people know you have invested, they soften criticism and give politeness instead of information. Ask about their process and their past behaviour rather than your idea, and keep the product out of the conversation.
A commitment that costs the person something: a pre-order, a paid pilot, a scheduled trial date, or an introduction to the budget holder. Three commitments out of ten conversations is strong. Ten enthusiastic conversations with zero commitments is a negative result.
Tell Marcus your idea and who has the problem. You get named places to look and the exact questions to ask.
Try GhostCoach free →14-day free trial · cancel anytime · 30-day money-back on Lifetime