Product Teardowns

Learn from real product decisions.

A curated teardown library across leading PM platforms covering onboarding, retention, monetization, acquisition, and strategy.

This is a reading list with opinions attached. Each teardown below is worth an hour of a working PM's time — but a list of links teaches you nothing until you know what to look for. So before the library, here is what it adds up to: the patterns that repeat across categories, and a short method for running a teardown of your own.

What the library reveals

Acquisition: the product is the channel

The strongest acquisition stories here barely spend on acquisition. Notion, Figma, and Substack all grow through the artifact the product creates — a shared doc, a design file, a writer's audience — so the person doing the sharing does the marketing. The pattern worth stealing: find the thing your users already send to other people, and make receiving it the first step of someone else's onboarding. Zepto is the instructive exception. When your entire USP is speed, acquisition is a legibility problem — you have to make the ten-minute promise believable in the first ten seconds, before any habit exists to lean on.

Retention: habit and identity are different engines

Retention here splits cleanly into two mechanisms. Duolingo's streaks, gems, and leaderboards manufacture a daily reason to open the app; the social layers in Strava and Duolingo make quitting feel like letting other people down. What's easy to miss is that the retention mechanic is usually separate from the core value — you learn a language or log a run for yourself, but you come back for the streak or the kudos. The teardowns worth reading twice are the ones that expose the seam between the two, because bolting a streak onto a product with no underlying value just trains users to resent you.

Monetization: the paywall is a design surface, not a switch

Almost every monetization teardown in this set is really a behavioral-science teardown. Calm sells motivation rather than features; Shopify's $1 trial removes the excuse instead of the price; Tinder segments willingness-to-pay by age and intent. The recurring lesson is that where you place the paywall, what you reveal behind it, and what the user is feeling at that exact moment move conversion far more than the number on it. Start with the Kristen Berman pricing roundups — they compress the most reusable patterns into a single read before you go deep on any one company.

Onboarding: delay the ask, front-load the payoff

The best onboarding flows here postpone the commitment and rush the reward. Duolingo lets you start a lesson before you ever create an account; Blinkist and Headspace spend the first session learning what you care about so the product feels tailored by the third screen. The friction to hunt for is the gap between "I understand the value" and "I have done the core action once" — the CultFit and Swiggy teardowns are useful precisely because they show where that gap widens. And the Zoom AI Companion teardown makes a point that generalizes to every AI feature shipping right now: adoption is an onboarding problem, not a capability problem.

Strategy: positioning, pricing, and product read as one system

The strategy teardowns are where the separate decisions get read together. Netflix and WhatsApp reward study for how a single, ruthlessly-protected core experience survives enormous scale. The quick-commerce comparison — Swiggy, Zomato, Blinkit, Zepto — shows the opposite lesson: four companies converging on nearly identical interfaces because the real strategy is operational, not visual. If teardowns are new to you, begin with the primers and the "100 teardowns" roundup; they hand you the framework before you try to reverse-engineer a specific product on your own.

How to run your own teardown

1
Name the job, not the app
Before you open the product, write one sentence: what is the user hiring this for? Every later observation is judged against that job.
2
Walk the first session cold
Go through sign-up and first value as a brand-new user. Screenshot every screen. The friction you feel in the first five minutes is the friction that costs the most.
3
Find the core action and its loop
Isolate the one action that delivers value, then trace what pulls the user back to do it again. Separate the value from the retention hook — they are almost never the same thing.
4
Propose one change with a metric
End with a single concrete change and the number it should move. A teardown that ends in admiration teaches you less than one that ends in a testable bet.