YC OS · Chapter 05

10-100 Customers Who Love You

It's better to have a small number of people who would be devastated to lose you than a large number who are lukewarm.

After this lesson

  • Prefer intensity of love over breadth of interest at this stage
  • Know the difference between polite usage and real dependence
  • Decide when to fire a customer who is quietly steering you wrong
Better to make a few users love you than a lot ambivalent.
Paul Graham, Startups in 13 Sentences

Depth before breadth

At this stage the goal is not maximum users — it's finding 10 to 100 people who would be genuinely upset if your product disappeared tomorrow. That intensity is the real signal of product-market fit forming. A thousand indifferent signups tell you less than ten people emailing you the moment the product goes down.

How to tell love from politeness

  1. They come back without being reminded or re-marketed to
  2. They'd be genuinely disappointed, not just mildly annoyed, if it went away
  3. They tell other people about it unprompted
  4. They tolerate rough edges because the core job matters that much to them
  5. They ask for more of the thing instead of asking you to fix everything else

Offer surprisingly good service

  1. Respond to early users faster than any 'normal' company would
  2. Fix their specific bug before fixing the general case
  3. Treat support tickets from your best users as product research, not overhead
  4. Thank people by name for using something that barely works yet

Find out who actually loves you this week

  1. Pull usage data and rank users by depth and frequency of use, not signup date
  2. Personally reach out to your top 5 most active users and ask what they'd miss if the product vanished tomorrow
  3. Do one clearly unscalable, generous thing for your single best user today — something they'd notice was just for them
  4. Name the one loud or off-persona customer steering your roadmap, and decide by Friday whether to keep serving them as-is

Case

Case: sometimes you need to fire a customer

A loud, demanding, off-persona customer can consume a disproportionate share of a small team's time — while quietly pulling the roadmap toward a market you don't actually want.

Takeaway: YC's own advice is blunt about this: sometimes you need to fire your customers, because they might be killing you. Saying no to the wrong customer protects the right ones.

Lukewarm growth or a loyal core?

Where should the next month of effort actually go?

Read the original

Startups in 13 Sentences

See point 5 on making a few users love you, and point 6 on surprisingly good customer service.

This chapter is a working summary. When the idea matters, read the source once — then come back and do the practice.

Read next

  1. Interview your 5 most active users using the practice below before adding a single new feature
  2. Write down, verbatim, what they say they'd miss — that sentence is closer to your positioning than anything you'd write yourself

Next