Introducing Cohort15: The original product thesis

Watch on YouTube ↗

Cohort15 began with a personal experience: learning something difficult became possible after finding a small group of people willing to take the same journey seriously.

The problem Cohort15 set out to solve

The original idea was an application where people could form cohorts of 15 members or fewer around a specific intention. Learning TypeScript was one example, but the format could also support building, gaming, accountability, or any other journey that benefits from committed peers.

The important quality was not the subject. It was signal: people who genuinely cared about the same outcome and were willing to contribute time, effort, and consistency.

The founder story

Without a formal computer-science background, programming initially felt too difficult to begin. Seeing other developers build useful things was inspiring, but also intimidating. The turning point was finding a small group of people attempting the same journey.

That group did not remove the difficulty. It made taking the first step—and continuing through a long learning process—possible. Cohort15 grew from the belief that more people should have an easier way to find that kind of small, committed group.

Cohort15 should help people publish an intent, gather the right people, and then get out of their way.

An assembly point, not another community platform

One of the earliest product boundaries remains important: Cohort15 is for assembling the group, not keeping it captive. Once enough people come together, they can move to Discord, Google Meet, Slack, or whatever tool suits them.

The product’s job is to make an intention visible, let interested people commit, and create a clear moment when the group is ready to begin.

The original mechanics

The first concept used a small credit payment as a filter. Creating a cohort would cost two credits, showing interest would cost one, and credits would be returned if the group failed to reach its target. A successful cohort would unlock a creator-provided meeting link.

The video also proposed publishing cohort requests across social networks so people could discover relevant groups where they already spent time instead of repeatedly checking another application.

What stayed true

• Groups should form around a concrete goal rather than generic networking.
• Participants should understand the commitment before joining.
• A quorum should turn scattered interest into a group that can begin.
• Cohort15 should assemble people, then let them use their preferred tools.
• The product should be treated as an experiment and public good, not as a claim that every assumption is already correct.

What changed in the validation MVP

The current version tests the underlying demand before testing monetization or heavier filtering:

• No credits, authentication, or payments. Creating a cohort and showing interest require only a private email address.
• Quorum instead of maximum membership. A creator chooses how many interested people are needed, from 1 through 15; interest closes when that threshold is reached.
• The meeting link is supplied at creation. It remains private until quorum is reached.
• No automated social publishing yet. Distribution is a separate assumption to test after the core formation flow.
• A seven-day interest window. Each request has a defined period in which to become viable.

This smaller product asks a narrower question: will people publish focused group intentions, and will others commit when the goal, schedule, and quorum are visible?

Why document the earlier version?

Product ideas become more useful when their assumptions remain visible. The video records where Cohort15 started; the validation MVP records what was removed to obtain a clearer test. Future results may support bringing some mechanics back, changing them again, or discarding them permanently.