HTSaS · Chapter 04

Building Products People Love

'Make something people want' is the whole company. Love is measurable — go find the number and design toward it.

After this lesson

  • Understand why love, not feature count, drives durable growth
  • Measure love with a real survey and a real retention curve
  • Design tight iteration loops instead of big-bang releases

Where Lecture 7 fits

You've launched small (Chapter 2) and you're talking to users (Chapter 3). Now the course turns to Kevin Hale's Lecture 7, the single most quoted talk in CS183B — he built Wufoo, sold it to SurveyMonkey, and became a YC partner specifically because he's obsessive about the mechanics of product love. Everything in this chapter is downstream of his framework.

Make something people want.
Y Combinator's founding motto

Read the original

Lecture 7 — How to Build Products Users Love — Kevin Hale

Extract Hale's exact Sean Ellis survey wording and his 40% threshold — then note how he ties survey results to specific product changes, not just a scoreboard.

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

Love is measurable, not vibes

You don't have to guess whether people love your product. Ask directly: 'How would you feel if you could no longer use this product?' If 40%+ of active users say 'very disappointed,' you likely have something people love — below that, you're probably optimizing the wrong thing.

What drives the love number

  1. Solving one job completely, rather than many jobs partially
  2. A fast, clear 'aha moment' early in first use
  3. Craft in the details that users notice even if they can't articulate why
  4. Being reliably there when the pain recurs, not just impressive once

Retention is the real love metric

Surveys tell you what people say; a retention curve tells you what they do. Plot the percentage of users still active at week 1, 4, 8, 12. A curve that keeps falling toward zero means no love yet. A curve that flattens above zero — even a low number — means you have a core who won't leave. That's the seed to build from.

Tight iteration loop

  1. Ship a small, complete change — not a half-finished big one
  2. Watch how real users respond within days
  3. Talk to a handful of the users most affected
  4. Decide: keep, cut, or double down
  5. Repeat weekly — speed of loop beats size of loop

Case

Kevin Hale and Wufoo's support as a product strategy

Wufoo, Kevin Hale's form-building startup, became known for founders personally writing detailed, funny, fast replies to every support email in the first years.

Takeaway: Users didn't just tolerate a small product — they evangelized it, because every interaction reinforced that someone cared. Support quality is part of the product experience, not a cost center to minimize. Hale later turned this exact experience into the Lecture 7 framework above.

More features or fix retention?

Growth has stalled and the team wants to ship more surface area.

Practice