Generic validation advice assumes you have time, money, and an audience. As a solopreneur, you have none of those. The validation method has to fit those constraints, or it costs you the one thing you cannot replace: the year you spent building the wrong thing.
The standard validation playbook was written for funded startups. Run forty customer interviews. Build a landing page and split-test the copy. Spend $500 on ads to measure intent. Test five different price points. Each of these assumes resources a solopreneur does not have.
You do not have time for forty interviews. You do not have $500 to spend on ads to validate one assumption. You cannot afford to test five price points sequentially over six months. You have weeks, not quarters, and the cost of being wrong is the only thing that matters: a year of your life building something nobody will pay for.
The solopreneur validation problem is fundamentally different. You are not optimizing across a hundred possible ideas to pick the best one. You are answering one question: should I build this specific thing, or kill it now? The method has to give you a clear answer fast, with the resources you actually have.
The frameworks that get cited most often — Lean Startup, the Mom Test, customer development — are useful inputs. But applying them as written will burn the year you are trying to protect. You need a tighter version calibrated for one founder, no budget, and a deadline measured in weeks.
Validation reduces to three diagnostic questions. If the answer to any one is no, the idea is dead. If the answer to all three is yes, you have something worth building.
Not "would someone use this if you built it" — that is the wrong question, because people will say yes to anything hypothetical to be polite. The real question is whether someone is currently doing something painful, expensive, or annoying that your product would replace.
The test: can you find five specific people who can describe, in their own words, the problem you are trying to solve, without you prompting them? If you have to lead them to the problem, they do not have it.
This is the question most validation work skips. Existence of a problem is not the same as willingness to pay. People have problems they would not pay to fix. People also have problems they will pay to fix but only at prices that do not support a business.
The test: can you get five people to commit to paying a specific monthly price before you have built the product? Commitment means signed up for a waitlist with a credit card, prepaid for early access, or written explicit confirmation. Verbal "I would totally pay for that" is not commitment. It is politeness.
This is the question that kills more solopreneur ideas than the other two combined. The problem exists. People will pay. But the cost of acquiring each customer is higher than they will ever pay you. That is a business that does not work, no matter how good the product is.
The test: name three specific places where your ideal customer hangs out and is reachable for free. A subreddit they read. A Discord they are in. A newsletter they subscribe to. If you cannot name them, you cannot afford to acquire them. The SaaS acquisition system guide covers what a sustainable acquisition channel actually looks like.
If you have not started building, run this sequence before writing a line of code. Total time: two to four weeks. Total cost: under $100.
Write down, in two sentences, the exact problem your product solves and the exact person who has it. Be specific. Not "small business owners" but "agency owners with three to ten employees who manage client projects in spreadsheets." If you cannot write this in two sentences, you are not ready to validate. Go think more.
Then find ten of these specific people. Not "people who might have this problem." Ten actual humans with names, jobs, and contact details. Find them in the channels you named in question 3 above. If you cannot find ten in a week, your audience is too narrow or you do not know where they are.
Talk to five of those ten people. Not all ten — five is enough to spot patterns. The conversations are not pitches. They are diagnostic. Ask about their current workflow, what is painful about it, what they have tried before, what they spend on tools or workarounds today. The SaaS customer interviews guide covers the specific questions that produce useful signal.
What you are listening for: do they describe the problem you assumed they had, in their own words, without you leading them? If yes, proceed. If they only confirm the problem when you describe it, kill the idea or rewrite the problem statement.
Now you find out if they will actually pay. Build a one-page landing page that describes the product, the price, and the launch date. Send it to the five people who confirmed the problem. Ask them to pre-order or commit a credit card to a waitlist. The price has to be real — same price you would charge at launch. The SaaS pricing guide covers how to set that number defensibly.
If three or more of the five commit, you have demand. If fewer than three commit, the problem exists but the willingness to pay does not. Kill or pivot. Do not build hoping it will convert better with strangers — it will not.
By the end of week 4, you have data on all three questions. Either build, or kill. Both are good outcomes. The bad outcome is building anyway because you are emotionally attached and cannot face the loss of the idea you have been carrying around. That is how you spend a year on the wrong thing.
If you already built the product before reading this guide — which is most solopreneurs — the validation sequence is different. You are now answering a slightly different question: given that the product exists, is the problem and willingness to pay strong enough to invest more time, or do you cut losses?
The fastest test: put the product behind a real signup with a real price and run a two-week experiment. Drive traffic from the channels you named in question 3, at the volume you can sustain without paid ads. Measure two things: signup-to-paid conversion, and post-signup activation (do they use it more than once).
If conversion is below 1 percent or activation is below 20 percent after two weeks of real traffic, the product is failing one of the three questions. The most common pattern: problem exists, willingness to pay exists, but the product is not solving the problem the way the target customer needs. The fix is usually scope, not promotion.
For vibe coders who already shipped, the post-build validation question is especially common. The after vibe coding guide covers the specific moves to make in the first ninety days post-launch.
The hardest part of validation is being honest about what the data is telling you. Founders are good at finding reasons to keep going. Below is the threshold I use, separated by stage.
| Stage | Kill if | Continue if |
|---|---|---|
| Problem discovery | Fewer than 3 of 5 describe the problem unprompted | 4 of 5 or more describe it in their own words |
| Willingness to pay | Fewer than 3 of 5 commit money at real price | 3 of 5 commit with a credit card or pre-order |
| Reachable channel | Cannot name 3 specific channels you can use today | Named 3 channels and seen organic traction in at least one |
| Post-launch conversion | Below 1% signup-to-paid after 2 weeks real traffic | Above 2% signup-to-paid sustained over 30 days |
| Post-launch activation | Below 20% of signups use the product more than once | Above 40% return within first week |
The middle of the table — kill at 3 out of 5, continue at 4 out of 5 — leaves a grey zone. In the grey zone, the right move is almost always to gather more data before committing more time. Run one more week. Find five more people. Do not build because you cannot bear to wait.
Two to four weeks of focused work, before any code is written. That is the target. If validation is taking longer than four weeks, one of three things is true: the audience is too narrow to reach, the founder is avoiding the kill signal, or the problem is not the one they thought it was.
Founders extend validation timelines because the decision is uncomfortable. Killing an idea feels like losing. Building the wrong thing for a year is the actual loss. The four-week budget is a forcing function: it forces you to make a decision before you have spent enough time to feel sunk into it.
The other failure mode is the opposite — shortcutting validation entirely and building the moment you have an idea. This is the more common pattern, and it is the more expensive one. Four weeks of validation costs you a month. Twelve months of building costs you a year. The math is not close.
If you want a second opinion on your specific idea before committing the four weeks, the AI business coach for solopreneurs page covers what kind of diagnostic Marcus can run on a pre-validation idea, including the specific kill signals for your situation.
Tell Marcus the idea, the audience, and the three channels you would use to reach them. Get a diagnostic before you spend the four weeks.
Talk to Marcus free →