Retention is the only moat left
When anyone can rebuild your feature set in a weekend, the durable question is not what you built. It is why anyone opens it again on day thirty.
The short version
- When features are copied in weeks, the durable question is why anyone opens your product again on day thirty.
- Read cohort curves, not totals: a curve that flattens is a business, a curve that decays to zero is a leaky bucket with a marketing budget.
- Define "active" as the action that delivers value, and watch the second session above all — most products lose users before any feature matters.
- Retention is an onboarding problem in disguise: if the first session ends without a shareable result, everything after is re-earning attention you already had.
Feature moats have a short shelf life now. Design can be copied by looking. Pricing can be undercut by anyone with lower costs or more patience. What survives is unglamorous and hard to fake: whether people come back without being reminded.
Read the curve, not the total
Total users only ever goes up, which is why founders like it and why it explains nothing. The cohort curve is the honest instrument: of the people who arrived in a given week, how many are still active four weeks later, and does that curve flatten or reach zero? A curve that flattens — even at a modest level — is a business. A curve that decays to nothing is a leaky bucket with a marketing budget.
- Define "active" as the action that delivers your value, not as a login. Logins measure habit; the action measures worth.
- Compare cohorts against each other, not against your best week. Improvement means later cohorts flattening higher.
- Watch the second session above all. Most products lose the majority of users between the first and second visit, before any feature has had a chance to matter.
Retention is built at the beginning
It is tempting to treat retention as a late-stage problem to fix with notifications. It is really an onboarding problem wearing a disguise. If a user leaves the first session without a result they would show someone else, everything afterwards is an attempt to re-earn attention you already had for free.
Acquisition is a cost you pay repeatedly. Retention is an asset you build once and maintain. Only one of them compounds.
Ask the people who left
Churned users are the most informative audience you will ever have and the one founders most avoid. Ten short messages to people who stopped using it — no pitch, no discount, one question about what they expected — will out-perform a quarter of analytics dashboards. They have no reason to be polite, which is precisely their value.
Put this article to work
Ask it a question, or turn it into a to-do list for your own project. Both answer strictly from this article — nothing invented.
Answers are generated from this article only and are a working draft, not advice.
Questions this answers
What is a good retention rate for an early-stage product?
The shape matters more than the number. Of the users who arrived in a given week, the question is whether the share still active four weeks later flattens or decays to zero. A curve that flattens — even at a modest level — is a business; one that reaches zero means acquisition is filling a leaky bucket.
How do you measure retention properly?
By cohort, against the action that delivers your value rather than a login. Compare later cohorts to earlier ones instead of to your best week, and watch the first-to-second-session drop above all, because that is where most products lose the majority of their users.
How do you improve retention?
Fix onboarding before adding notifications. If a user leaves the first session without a result worth showing someone, later re-engagement is an attempt to buy back attention you already had for free. Then talk to ten people who churned — no pitch, one question about what they expected. They have no reason to be polite, which is exactly their value.
Building something?
Put it in front of founders who read this — free listing, community-voted, reviewed before it goes live.
Keep reading
Build for one job title: the vertical wedge that beats a generic tool
Generic AI tools are commoditizing weekly. The products holding their ground solve one job, for one role, in one industry — and charge accordingly.
Read the article →
Nine red flags your users see before you do
Most early products do not fail from one dramatic mistake. They fail from a handful of small signals that quietly tell visitors this is not for them.
Read the article →
Meter your AI feature: the cost ledger that decides your price
Most founders shipping an AI feature have never measured what a single user costs them in a month. Ninety minutes of instrumentation produces that number, and three levers already in the API move it.
Read the article →