The three levels of validation most founders skip, the five signals that mean yes, the five that lie, and a four-week sprint to find out whether anyone will actually pay for what you want to build.
Methodology. This guide synthesizes The Mom Test by Rob Fitzpatrick, customer-development frameworks from Steve Blank, public solo-founder build logs, and our own analysis of 50+ solo SaaS launches from 2023–2025.
The thing that kills most solo SaaS isn’t a bad product or insufficient marketing. It’s the six months spent building something nobody was ever going to pay for. The founder shipped a polished MVP, watched signups trickle in, watched paid conversion hover near zero, and concluded the marketing was broken. The marketing wasn’t broken. The idea was. The validation work that would have surfaced this in two weeks was never done.
This guide covers what validation actually is, the signals that predict willingness-to-pay, the signals that lie, interview discipline that surfaces real pain, willingness-to-pay tests that produce action rather than opinion, and a four-week sprint that delivers a clear go/no-go at the end. The goal is a validated answer — yes, no, or pivot — reached cheaply enough that you can run the loop several times until something sticks.
The word “validation” gets used loosely enough that it has lost most of its meaning. Founders say they have validated an idea when what they actually mean is “I told three friends and they said it sounded cool.” That is not validation. That is flattery. People will tell you almost any idea sounds good, particularly if they like you and have no skin in the game.
The cleanest definition: validation is evidence that people will act on the problem in a way that costs them something. Time, money, reputation — any friction. Action through friction is the only reliable signal because action is expensive and opinion is free. Only people with real pain will spend twenty minutes filling out a form, fifty dollars on a pre-order, or three hundred dollars on a competitor’s broken tool to get partial relief.
The bar is higher than founders typically set it. “People said they liked the idea” clears no bar. “People signed up for a free waitlist” clears a low bar (it cost them nothing). “People pre-ordered for $49” clears a real bar. “People are already paying $99/month for a worse alternative” clears the highest bar.
Validation is not a single binary. It is three distinct levels, each requiring different evidence. Most founders run one of them (usually the middle) and skip the other two.
Level 1: Problem validation. Does the problem actually exist? Is it painful enough that real people spend time, money, or attention trying to solve it today? Evidence: customer-discovery interviews about past behavior, search-volume data, active forum threads, observable manual workarounds.
Level 2: Solution validation. Does your specific approach resonate? Evidence: prototype walkthroughs, smoke-test landing pages, click-through tests, concierge MVPs.
Level 3: Willingness-to-pay validation. Will people actually pay at the price you need to charge? Evidence: pre-orders, paid waitlists, manual concierge service charged at price.
The trap: most founders run level 2 alone, get positive feedback, and assume the whole thing is validated. They skipped level 1 (which would have told them the problem is too small) and level 3 (which would have told them people like the idea but won’t pay). All three are necessary.
Some signals are real. They are unambiguous, hard to fake, and predict willingness-to-pay reliably. When you see one of these, you have evidence worth acting on.
The strongest pre-launch signal. Not friends. Not people you asked. Strangers who saw a tweet, a Reddit post, or a landing page and reached out unprompted. The signal is strong because it costs the stranger reputation — they are inserting themselves with a real expectation the product will exist. If three or four unrelated strangers reach out about a single idea, you have a real demand signal.
Pre-orders are not the same as free waitlist signups. Free waitlists signal curiosity; paid waitlists — even at $9 or $19 — signal commitment. Money creates friction; friction filters the curious from the intent. Five paid pre-orders carries more signal than five hundred free signups. The hard rule: if you cannot get five strangers to pay anything to be first in line, you do not have evidence of willingness to pay.
Counterintuitively, competitors are a positive signal. If three other tools serve the niche and one is doing $20K MRR, the market exists, the audience is reachable, and people pay. The work shifts from “is there a market” to “can I serve an underserved segment better.” A niche with zero competitors is more often a sign no one wants the product than an untapped opportunity.
A subreddit, Discord, Indie Hackers thread, or Slack community where people ask about the problem unprompted, on a recurring basis, in their own words. The forum activity tells you the vocabulary, the workarounds, and the previous failed attempts. Free research.
The cleanest path is a market already paying for a solution that’s genuinely worse than what you can build. Customers have validated the problem (they pay), the price point is established (you can see what they pay), and the dissatisfaction is documented (G2 reviews, tweets, Reddit). Building a better version of something people already pay for is one of the highest-success solo SaaS patterns.
Some signals look like validation but are not. They feel good. They produce screenshots that look impressive on Twitter. They predict almost nothing about whether the product will sell. Founders who chase these signals end up shipping products that nobody buys.
The most common false signal. Friends, family, Twitter followers, and people at meetups will tell you almost any idea sounds great because they are being polite. The cost of saying “I’d totally use that” is zero, so the information content is also close to zero. Past behavior is a signal; future intent in casual conversation is not.
Free waitlists filter no one. Founders routinely report 5,000 free signups and then watch fifty convert when the product launches at $19/month. The waitlist measured curiosity, not buying intent. The same audience asked to pay $5 to reserve a spot would have signed up at perhaps 2% the rate — and that 2% would have converted at 20% to paid. The smaller, higher-friction signal is the actual signal.
Your sister, your old roommate, three friends from your last job — they are not your customer. They are using the product because they love you or want to support you. The data they produce is corrupted by the relationship. A founder with twenty “active users” who are all personal contacts has zero actual users in the sense that matters.
A tweet with 500 likes is not validation. Likes are the cheapest action on the internet. The audience that liked is mostly other founders, not target customers, and a like means “this concept resonates at a vibes level,” not “I will pay for it.” The correlation between viral engagement and conversion to paid is shockingly weak.
The price is rarely the actual problem. The prospect is giving you a polite reason that avoids articulating the real one — usually that the product doesn’t solve a painful enough problem to be worth any price, or that the value isn’t landing, or that a free alternative is good enough. Founders who cut prices in response typically discover the same customers don’t convert at the lower price either, and now the unit economics are broken too.
Problem-validation interviews are the foundation of everything else. Done well, they produce a clear picture of whether the problem is real, who has it, how painful it is, and what workarounds people currently use. Done badly, they produce a series of polite conversations that tell you nothing and feel productive.
Rob Fitzpatrick’s short book The Mom Test is the best resource on this. The core insight: do not pitch your idea. Do not ask whether people would use a hypothetical product. Ask about actual past behavior with the actual problem. Past behavior is observable and verifiable; hypothetical future behavior is opinion.
“Would you use a tool that organizes your inbox?” gets almost everyone to say yes, because it costs nothing and sounds nice. “Walk me through the last time you spent more than fifteen minutes managing your inbox — what frustrated you, and what did you do about it?” gets you actual evidence.
The audience you need is the one with the problem, not the convenient one. Solo founders interviewing other solo founders about productivity tools end up with biased samples and obvious products built ten times already.
Notice none of these are about your idea. They are about the customer’s reality. The interview is research, not sales.
Five to ten interviews is enough. By interview five or six you start hearing the same answers and workarounds. When new interviews stop producing new information, you have saturation. Aim for seven to ten well-conducted conversations. The customer interview playbook covers the mechanics in depth.
Problem validation says the problem is real. Willingness-to-pay validation says people will open their wallet. The gap between the two is where most ideas die. Plenty of real problems do not produce viable businesses because nobody pays enough to solve them.
The most reliable test. Landing page describing the product, clear price, take pre-orders with a refund guarantee if you don’t ship in ninety days. The friction of authorizing a charge filters everyone who is merely curious. If you cannot get five strangers to pre-order at the price you need to charge, the product is not validated at that price. How to validate a SaaS idea in 48 hours walks the setup.
Landing page with a pricing table and an email-capture signup flow that announces “in beta — we’ll reach out when access opens.” Measure visitors-to-email-conversion from a specific attributable channel. Above 5% on cold traffic, or 15% on warm/targeted traffic, is real signal. Below 1% is signal in the other direction.
Skip the software entirely for the first five customers. Do what the software would do, manually, for actual paying customers. Want to build automated bookkeeping for solo accountants? Do the bookkeeping yourself for five of them for a month, charge what the software would cost. The information you learn is enormous — what they want, where the value is, what they’ll pay for — and you get paid during validation.
The hypothetical version, and it lies. Roughly 30–50% of people who say yes to a hypothetical price do not pay when actually asked. The hypothetical is a screening tool at best; pre-order, smoke test, and concierge MVP are the real tests.
If you read no other book on customer development, read The Mom Test by Rob Fitzpatrick. The whole thing fits in an afternoon. The principles, distilled:
Don’t pitch. Ask about the problem. The moment you pitch, the conversation becomes about whether the listener wants to be polite. Pitch later, when you’re selling. During validation, listen.
Past behavior beats future opinions. “What did you do last week?” is truth. “What would you do if I built X?” is what they think you want to hear. Pull the conversation back to specific past instances with specific details.
Specifics beat generalities. “I sometimes have trouble with [X]” is useless. “Last Tuesday I spent three hours on [X] and gave up” is data. Drill into the specifics.
Listen for what they already do. Customers with real pain are already running a workaround — a spreadsheet, a Notion doc, a freelancer they pay, a competitor product they tolerate. The workaround is the validation.
A founder who asks “would you use this?” is selling. Selling is the opposite of validating. If you catch yourself, redirect.
Looking across fifty solo SaaS launches from 2023–2025, four validation patterns recur. Each represents a different founder personality and path into the market.
Builds an audience first — newsletter, Twitter following, YouTube, niche podcast — then asks the audience what to build. Pieter Levels is the archetype. Validation is built in because the audience signals demand directly. The downside: audience-building takes 12–24 months. The upside: every subsequent product launches with distribution and validation baked in.
Solves a personal problem, then asks if others share it. Marc Lou’s ShipFast started as frustration with repeated SaaS boilerplate. The risk is the “market of one” trap, where the founder’s frustration is unusual and nobody else cares. Validation interviews surface this quickly. Should you build SaaS in 2026 covers the broader view.
Finds a problem from data — Ahrefs search volume, forum activity, Trends — before having a personal connection. Validation is partially pre-baked because search volume implies demand. The risk: entering a market the founder doesn’t understand and getting out-built by native operators. Mitigated by embedding in the niche first.
Finds a successful incumbent and builds a better version for an underserved slice. The incumbent has done the validation work. Tony Dinh’s tools often fit this pattern. The risk is being a feature, not a company — the incumbent ships your feature and ends you. Mitigated by picking niches the incumbent has structurally written off.
Most ideas die at validation. That is the point. Killing after two weeks costs two weeks. Killing after six months of building costs six months.
You cannot get five strangers to pre-order. Smoke-test conversion under 1%. Interviews produce shrugged shoulders rather than specific frustrations. Nobody runs a workaround. Forums don’t surface the problem. These are signals to stop.
Three questions when validation comes back ambiguous:
If all three point to “not painful enough,” kill and move on. The next idea is cheaper than pushing through this one.
Six months of solo-founder time is worth $50K–$150K in opportunity cost depending on your day-job alternative. That is the cost of pushing through a negative signal. A clean validation cycle takes two to four weeks. The math is not close.
The whole framework collapses into a four-week sprint. The output is a clear go/no-go decision at the end of week four.
Write down the problem, the specific audience, and the five critical assumptions underneath the idea. Critical assumptions are things that must be true for the business to work — “veterinarians spend at least two hours a week on appointment scheduling,” “they would pay $49/month to get that time back,” “they will switch from their legacy software.” Output: a one-page document.
Find ten people in the target audience. Twenty-to-thirty-minute Mom Test interviews. Do not pitch. Ask about past behavior. By interview ten you will have a clear sense of whether the problem is real, painful, and being solved badly today. Output: a written summary of patterns and direct quotes.
One-page landing page with pricing and an email-capture “Get early access” flow. Drive 200 targeted visitors from Reddit, Twitter, a subreddit AMA, a niche newsletter, or cold outreach. Above 5–10% conversion on cold targeted traffic is strong signal; below 2% is weak. Output: a documented conversion rate.
Add a real payment option. Take pre-orders with a refund guarantee. Reach out to the week-three email list. Output: a count of paid pre-orders. Five is the threshold. Below five, the idea is not validated at that price.
End of week four: five paid pre-orders or not. If yes, build — the solo-founder week-1 plan covers next steps. If no, kill the idea or pivot one dimension (framing, audience, or product approach) and run the sprint again. Do not skip the kill step.
Validation is evidence that people will do something costly to get the problem solved. Run all three levels — problem, solution, willingness-to-pay — not just the middle one. Trust the five signals that mean yes (stranger DMs, pre-orders, competitor traction, active forums, bad incumbents). Distrust the five that lie (“I’d use that,” free waitlists, friends, social engagement, price objections). Run the four-week sprint with discipline. If five strangers won’t pre-order at the price you need to charge, you do not have a business yet. Kill, pivot, or run the sprint again on a sharper idea.
Validation is upstream of every other discipline. Once an idea is validated, the next layer of work is the solo-founder week-1 plan, launching the SaaS, and positioning the product. The customer interview playbook goes deeper on the Mom Test mechanics. How to validate a SaaS idea in 48 hours is a faster, lower-fidelity version of the sprint above. Should you build SaaS in 2026 sits one step before validation — the market view. The complete guide to SaaS customer acquisition picks up where validation ends. Micro-SaaS ideas surveys the kinds of ideas that consistently survive validation.
The stack, prompts, pricing, and mistakes to avoid — for solo founders building with AI.