Do Things that Don't Scale

Startups should focus on a deliberately narrow initial market to achieve critical mass before expanding, instead of launching broadly from the outset.

The article explicitly endorses starting in a narrow market to get critical mass, citing the "contained fire" strategy and examples like Facebook and Airbnb to argue for focused initial launches.

Founders should prioritize laborious, unscalable early tactics—manual user recruitment and delightful service—to jumpstart growth rather than waiting for organic scale.

The article repeatedly and explicitly advocates doing unscalable manual recruitment and obsessively delighting early users as the primary way to jumpstart startups, using many prescriptive examples and directives.

Individual vs Systemic

Strongly favors individual explanation: the article repeatedly says founders must take specific actions (manual recruiting, delighting users) and treats systemic factors as context, not primary drivers.

Moral vs Pragmatic

Strongly pragmatic: the piece prioritizes effectiveness, tactics, metrics, and tradeoffs over moralizing language or judgments about virtue.

Evidential vs Speculative

Leans toward evidential: recommendations are grounded in multiple concrete examples and data (case studies, growth math) rather than speculation about hidden motives or abstract possibilities.

Procedural vs Emotional

More procedural than emotional: the article prescribes concrete steps and processes to follow, using emotional language mainly to motivate those procedures rather than to replace them.

Mentions early fragility and the danger of founders dismissing their own startups, but overall frames these as solvable problems rather than threats.

Virtually no moralized anger or scandal language; criticisms are practical and constructive rather than indignant.

Repeated imperatives ('you have to', 'go out and get them', 'do things that don't scale') and examples of time-sensitive tactics convey pressure for immediate founder action.

Author empathetically addresses founder doubts and fragility (baby metaphor, encouragement to founders who under-estimate potential) and offers concrete support-oriented advice.

Skepticism toward big launches, partnerships, and conventional 'professional' behaviors (imitating big-company indifference) is a recurring theme, though presented as practical caution rather than conspiracy.

Mild reproach for laziness, perfectionism, or naiveté (founders who wait, imitate big-company flaws), framed as poor choices rather than moral evil.

Advice is delivered in a decisive tone ('you have to', 'you should'), treating the main claims (do unscalable things early) as established lessons from YC experience.

Text repeatedly notes exceptions and caveats (some startups grow organically, domain constraints, cases where an idea may be for one user) and includes conditional language and footnoted asides.

Author proposes a 'vector' model and suggests multiple valid unscalable tactics, allowing alternatives, but still tends toward recommending a primary playbook.

Occasional psychological inferences about founders (shyness, laziness, calibrated ambition) and causal interpretations (why launches fail) are offered without formal proof, relying on plausible reasoning.

Arguments are supported by concrete, named examples (Stripe, Airbnb, Pebble, Microsoft, etc.), personal YC experience, and numbered notes that document practical instances and exceptions.

Position of the Article

The article explicitly endorses starting in a narrow market to get critical mass, citing the "contained fire" strategy and examples like Facebook and Airbnb to argue for focused initial launches.

Framing Bias

The piece frames the narrow-market approach as a broadly applicable, recommended tactic by presenting it as a common and necessary 'unscalable' step for startups to succeed.

Selection Bias

The article predominantly cites success stories (Facebook, Airbnb, Stripe, Meraki, Pebble) that followed targeted early markets while offering little attention to counterexamples of successful broad launches.

Confirmation Bias

The author emphasizes anecdotes and examples that support the 'do things that don't scale' thesis, reinforcing the conclusion that starting narrow drives growth and product fit.

Emotional Appeal

The article employs vivid metaphors and anecdotes (e.g., 'contained fire,' 'insanely great,' 'juggernaut') to make the narrow-market strategy feel compelling and motivational in addition to practical.

Position of the Article

The article repeatedly and explicitly advocates doing unscalable manual recruitment and obsessively delighting early users as the primary way to jumpstart startups, using many prescriptive examples and directives.

Framing Bias

It frames unscalable tactics as near-universal necessities and contrasts them favorably against ineffective alternatives like big launches or partnerships, steering interpretation toward the recommended approach.

Selection Bias

The piece predominantly cites successful YC-backed examples (Stripe, Airbnb, Pebble, Facebook) and positive anecdotes while offering few counterexamples or systematic failures of the approach.

Confirmation Bias

The author emphasizes evidence and stories that confirm the thesis and characterizes opposing strategies as mistakes, with limited engagement of disconfirming data or contexts where the tactics fail.

Emotional Appeal

The article uses vivid metaphors, founder anecdotes, and charged phrases like 'insanely great' and 'juggernaut' to generate enthusiasm and urgency for the recommended tactics.