How to Validate a SaaS Idea With a Founding Cohort Instead of a Waitlist

A waitlist feels like validation. It isn't. It's a list of people who were willing to type their email address into a box - which is one of the lowest-commitment actions a person can take on the internet, right up there with clicking "maybe interested" on an event. A thousand waitlist signups tells you a headline was compelling. It tells you almost nothing about whether anyone will actually use, pay for, or stick with what you build.

A founding cohort is a different instrument, measuring a different thing, and it's worth understanding exactly how before you pick one. (What a founding cohort is, in full.)

What a waitlist actually measures

Interest. That's it. Someone saw a landing page, liked the idea, and gave you an email address that costs them nothing and commits them to nothing. Waitlists are genuinely useful for one thing: gauging whether a concept resonates before you've built anything. They are not evidence that the concept is a business. The gap between "1,200 people joined the waitlist" and "12 people will actually pay for this" is where most first products quietly die, usually a few months after a founder mistook the first number for validation of the second.

What a founding cohort measures instead

A founding cohort asks for something real up front - usage, in most cases, sometimes payment, always a defined activation event you chose and committed to before anyone joined. (What an activation event is, precisely.) "Fill 25 spots" sounds similar to "get 25 waitlist signups" right up until you look at what each person actually did to count. A waitlist member typed an email. A cohort member did the thing you defined as proof - ran their first budget, shipped their first build, completed their first workout, whatever "real use" means for your specific product. That's the entire difference, and it's not a small one.

Declare the activation event before you recruit anyone

The order matters more than people expect. If you decide what counts as "real use" after you've started recruiting, you'll unconsciously pick a definition that flatters whatever numbers you already have - which defeats the point of measuring anything at all. Decide first: what does a real user of this product actually do? Not "sign up." Not "log in once." The specific action that means someone got value, before you have any data telling you what that number should be.

This is worth writing down somewhere permanent, not just deciding privately, because the temptation to quietly loosen the definition once the going gets slow is strong and mostly invisible in the moment. It's why the indie board makes founders publish the activation event before the cohort opens, frozen (R-20) - the rule exists specifically to close the exact loophole where "proof" slowly becomes whatever's easiest to hit.

Evidence isn't binary - but it should be labeled

Not every proof point is equally solid, and pretending otherwise is its own kind of self-deception. There's a real difference between:

• What you say happened - your own account of usage or interest, useful as a signal but easy to be generous with, even unintentionally
• What's independently confirmed - a real payment, a signed agreement, something with a paper trail that doesn't depend on your own reporting
• What the actual users confirm themselves - someone else verifying, in their own words, that it happened

The instinct is to collapse all three into one number on a slide. Don't. Keeping them separate - even just privately, in your own tracking - keeps you honest about how solid your "traction" actually is, and it's a habit worth building before anyone else is checking your math. (The full tier breakdown.)

Why 25 verified joiners beats 1,000 interested ones

Twenty-five people who did the real thing tell you more than a thousand who clicked "notify me." They tell you whether the activation event you defined is achievable, whether people who try it stick with it, and - most importantly - whether the 26th person would join on the same terms without you personally convincing them one by one. A waitlist can't tell you any of that. It can only tell you the pitch worked once, on a page, for five seconds, before anyone actually touched the product.

If you're deciding between building a waitlist and running a founding cohort for whatever you're validating next: the waitlist is faster and feels better in the short term. The cohort is the one that actually tells you if you have something. (Selling to companies rather than consumers? The pilot-vs-waitlist version of this argument.)

The indie board runs founding cohorts as its core mechanic - declared bars, frozen terms, every number tiered. The open chairs →