The waitlist was an operating control. Karri Saarinen reviewed survey responses, chose people who matched the intended user, and sent invites from his personal email. The team added about ten users a week, then indexed on why daily users loved the product instead of averaging feedback from everyone who tried it.
THE LINEAR SYSTEM
Linear
10K-person waitlist, admitted roughly 10 users a week
Use scarcity to improve the learning loop, not to manufacture hype.
Linear entered an old category with a deliberately narrow point of view. The team used a private beta to control who reached an unfinished product, learn from the people who returned every day, and preserve the quality bar while removing blockers one cohort at a time.
2 plays worth stealing.
Open a play for the mechanism, the exact receipt, the failure mode, and a deployment brief Elena can put into your backlog.
28 Admit the users your product is ready to teach you from
Linear collected roughly 10,000 waitlist emails, but invited only about ten people a week. Saarinen handpicked them from survey responses and sent each invitation himself.
A narrow cohort prevents the same known defect from flooding the team with duplicate feedback. It also makes every new user legible, so behavior can be connected to role, expectations, and prior workflow.
About 10% of the waitlist became users during the first year of private beta. The team maintained weekly contact with the people who used Linear every day.
Ask two qualification questions at signup. Admit one coherent cohort at a time. Resolve the blockers that cohort shares before widening the aperture.
Artificial scarcity is not the play. If the cohort is not tied to a learning question and a release decision, the waitlist is theater.
Operator-reported. Karri Saarinen reports waitlist size, invite rate, selection method, and beta conversion.
Open the exact source ↗Turn this observation into a real experiment.
- Run it when
- The product is useful for a narrow segment but known blockers would overwhelm broad access.
- Owner
- Founder or product lead
- First sprint
- Add two qualification questions, admit ten matched users, contact each personally, and clear shared blockers before the next cohort.
- Leading signal
- Cohort activation, daily use, feedback duplication, and time from issue to fix.
- Stop rule
- Open access or change the segment if controlled cohorts stop producing new learning for three rounds.
29 Study concentrated love before broad objection
The founders built a weekly feedback relationship with daily users and weighted the reasons those users returned more heavily than the reasons occasional testers disliked the product.
In a replacement category, broad feedback pulls the product toward the incumbent. Concentrated love identifies the wedge worth protecting while the team gradually removes adoption blockers around it.
Strong private-beta usage helped Linear raise its seed round before public launch. The company opened signups only after a year of cohort-by-cohort refinement.
Segment feedback by observed frequency, not enthusiasm in an interview. Preserve the behavior that creates daily use, then fix one adjacent blocker per cohort.
Love is not an excuse to ignore churn. The method works only when the loved behavior belongs to the customer segment you intend to serve.
Operator-reported. Saarinen describes weighting daily-user love and maintaining a weekly feedback relationship.
Open the exact source ↗Turn this observation into a real experiment.
- Run it when
- Feedback is broad and contradictory, but a small set of users returns frequently.
- Owner
- Founder and product analyst
- First sprint
- Identify the top daily users, reconstruct their repeated behavior, and interview them weekly about why they would resist losing it.
- Leading signal
- Frequency and depth in the loved behavior, retention of the target segment, and adjacent blocker removal.
- Stop rule
- Abandon the wedge if concentrated use does not belong to a commercially viable target segment.
Do not copy Linear. Adapt the system to your constraint.
Elena learns your product, customer, funnel, and current bets. Then she chooses the relevant pattern, scopes the first sprint, and watches the leading signal.