PreValidation: Early Demand & Distribution Scoping Tool for Solo SaaS Founders

Distribution over everything else, especially early. Credibility and product speed tend to sort themselves out once you have a channel that keeps working without you pushing it every day. Runway just buys time to find that channel, it doesn't replace it. The failure mode I see the most: six months building a polished product, then realizing nobody showed up and there's no repeatable way to get them there.

4, 8, 3, 5. the failure mode i'm avoiding is the one i actually hit: building a lot of something before knowing who was already looking for it. 4, the 500 interview notes, goes first because every other slot gets spent badly without it. the notes are the words. the landing page, the ads, the emails, the onboarding, all of it is copied out of that database instead of written. i spent a summer shipping 4,500 pages and then measured which ones anyone opened, and the ones that worked were the ones that answered a question in the words people had typed. i could have read that in the notes for free. 8, the proprietary dataset, because it's the only slot competitors can't buy back. after google's august update demoted my site, the thing that started recovering wasn't the design or the copy, it was the pages built on measurements only i had run. a dataset is also the marketing: people don't share "it's improved", they share "20 of 51 didn't boot". 3, the 20k email list, and this is the regret pick. i have zero owned audience after a year of publishing, and it means every visitor is a stranger again tomorrow. a list at 45% open is a second launch every week that costs nothing. 5, the enterprise design partner, over the waitlist, because 5,000 people who said "sure" teach you less than one who pays and complains. i'd rather have the complaints. what i'd leave: the creator intro is one day of attention with no next step, the app store rank is rented, the ui kit solves a constraint i never had (frontend was never the slow part, knowing what to build was), and the 90 day no-meeting pass is the failure mode itself with a nicer name. i took that one by default for months. it's how you end up with 4,500 pages and no list.

4, 8, 3, 5. the failure mode i'm avoiding is the one i actually hit: building a lot of something before knowing who was already looking for it. 4, the 500 interview notes, goes first because every other slot gets spent badly without it. the notes are the words. the landing page, the ads, the emails, the onboarding, all of it is copied out of that database instead of written. i spent a summer shipping 4,500 pages and then measured which ones anyone opened, and the ones that worked were the ones that answered a question in the words people had typed. i could have read that in the notes for free. 8, the proprietary dataset, because it's the only slot competitors can't buy back. after google's august update demoted my site, the thing that started recovering wasn't the design or the copy, it was the pages built on measurements only i had run. a dataset is also the marketing: people don't share "it's improved", they share "20 of 51 didn't boot". 3, the 20k email list, and this is the regret pick. i have zero owned audience after a year of publishing, and it means every visitor is a stranger again tomorrow. a list at 45% open is a second launch every week that costs nothing. 5, the enterprise design partner, over the waitlist, because 5,000 people who said "sure" teach you less than one who pays and complains. i'd rather have the complaints. what i'd leave: the creator intro is one day of attention with no next step, the app store rank is rented, the ui kit solves a constraint i never had (frontend was never the slow part, knowing what to build was), and the 90 day no-meeting pass is the failure mode itself with a nicer name. i took that one by default for months. it's how you end up with 4,500 pages and no list.