The reading room · Digna Legi
Why retention is so hard for new tech products
/100
80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.
Evidence-reviewed score based on available publisher text. Evidence is sampled with gaps, so completeness, full structure, and omitted arguments cannot be judged.
Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.
How scoring works →This brief · about 3 min with detail
Original article ↗ · about 15 min (text estimate)
Why read this
Chen argues weak retention usually reflects product-category mismatch and early cohort behavior, not missing notifications or onboarding tweaks.
AI brief · Checked against source text
The main idea
The central claim is that weak retention in new tech products is rarely fixable through notifications, onboarding tweaks, or A/B tests. Retention usually decays predictably from early usage, so poor day-one or month-one behavior signals a deeper mismatch between product, category, and user need. The exception is not clever growth hacking but a major product reframing, a category with natural frequency, or revenue expansion among the users who remain.
Some background helpful. Some startup metrics: D1 means day-one retention; D30 means day-30 retention; LTV means lifetime customer value.
Go a little deeper
Small fixes do not move a bad curve
Chen distinguishes marginal improvement from structural failure. Moving day-one retention from weak-but-real to somewhat better may be workable; trying to rescue near-total early abandonment usually means the product is not compelling enough. The implied remedy is not optimization but a large pivot: change the home screen, core flow, creation-versus-sharing emphasis, positioning, or comparison set.
Early usage is a leading signal
The essay treats retention as a decay curve rather than a morale curve. If early retention is mediocre, later retention will normally be worse, because cohorts tend to fall away rather than revive. Chen notes rare exceptions, especially products where network effects can reactivate users, but the practical consequence is blunt: late retention is usually already visible in the early curve.
Usage and revenue can diverge
A product can lose users while earning more from the customers who stay. Chen presents this as a major advantage of business software: a company may adopt a tool more deeply over time, expanding seats or usage even as some individual users disappear. Consumer products can show a related pattern only when the product’s scope naturally broadens into more purchases or use cases.
Growth changes the denominator
The best-looking early cohort is often not representative. Early organic users are usually higher intent, easier to monetize, more digitally fluent, and better matched to the initial product. As acquisition expands into paid channels, other platforms, and international markets, retention and monetization usually degrade. The real question becomes whether later users remain profitable while the early valuable base stays intact.
A case from the article
Slack’s revenue curve
Chen uses Slack to show why business software can behave differently from consumer apps. Individual user cohorts may still decay, but when a company adopts the tool, usage can spread internally and the customer account can generate more revenue over time. The case illustrates the distinction between retaining every user and expanding value from the remaining organization.
How the case is made
The case is made from investor and operator observation of thousands of retention curves, supported by product-category examples.
Where the idea has limits
The argument is explicitly about patterns Chen sees in startups and internet products; it allows rare exceptions for hardcore products, network effects, revenue-expanding business software, and true new-category creation.
A question to take away · from Digna Legi
Is your product fighting users’ natural frequency, or replacing something they already do often with a clearly better core interaction?
What the original adds
The source adds a broader catalog of retention patterns, including measurement problems from seasonality, bugs, market launches, and long time horizons, plus founder-facing comments on timing and category selection.
About this brief
AI-written, then separately checked for source support, useful detail and clarity. The author’s claims and our editorial question are kept separate. The original remains the author’s work. How we select and summarise →
How was this brief?
Rate this summary, separately from the author’s article.
Optional. Saved in this browser; shared only if you allow analytics.
How was the original article?
Rate the author’s original after reading it.
Optional. Saved in this browser; shared only if you allow analytics.
Digna legi. Worth reading.