The pre-sale threshold tells you whether to build. The founding cohort tells you what to build after that.

This is the part that gets underused. Most builders treat the founding cohort as customers to satisfy rather than as an instrument to learn from. The distinction matters because these are different orientations — satisfying customers means delivering what you promised, learning from them means understanding what they actually needed, what they used, what they skipped, and what they asked for that wasn’t in the spec. The first is a delivery task. The second is a research task. You need to do both, but the research task has a time limit: it’s only available while the cohort is new enough to articulate their early experience.

What the founding cohort can tell you that no one else can:

They can tell you which use case was actually primary. Your pre-sale page described one thing; the people who paid might be using it for a slightly different version of that thing. Not wrong, but adjacent. The first cohort will show you the gap between the problem you thought you were solving and the problem they’re actually bringing to the tool. That gap is your roadmap — it tells you where to sharpen, where to extend, and where the second use case is hiding inside the first.

They can tell you what provenance is actually worth. For tools that return data from documents, buyers often say they care about citations and sourcing — but the founding cohort will show you how they actually behave. Do they follow citations back to the source, or do they trust the output and move on? Do they use the citations in their own work products, or are citations just confidence builders? That behavioral data shapes the depth of citation you invest in for v2.

They can tell you where the friction is. Every product has friction that the builder can’t see because the builder knows too much. The founding cohort encounters the tool fresh. Where they get stuck, what they ask about, what they try and give up on — that’s the friction map. A support interaction from a founding member is worth more than ten user interviews from strangers, because the founding member has already paid and is already trying to use the thing. Their problem is real.

They can tell you who else has this problem. Founding cohort members talk about tools they’re using. They talk to colleagues. If the problem is real and the solution works, you’ll hear about adjacent buyers through the founding cohort before you find them through any other channel. That’s the organic referral signal — it shows up in support questions from people who weren’t on your list, in “my colleague asked me about this,” in communities where founding members are already active.

The founding cohort is a research instrument with a natural expiry. The window for learning from first-time experience closes as users become habituated. Learn while the experience is still fresh.