The product lifecycle
Exploration, growth, maturity, decline — the priorities are completely different.
Before deciding whether something is worth doing, ask which stage the product is in. The same feature is noise during exploration and essential during maturity. A product moves through roughly four stages — exploration, growth, maturity, decline — and each has its own single question and its own metric to watch.lean
What you'll run into:
- The product has almost no users, and you're building referral programs and points systems
- Users are growing fast, but the team is still polishing a detail nobody complained about
- You're staring at a pile of metrics without knowing which one matters right now
What each stage focuses on
| Stage | The one question to answer | Metric to watch | Don't do this now |
|---|---|---|---|
| Exploration | Is there a small group that must have it? | Retention, especially week-1 retention | Paid acquisition, referrals, big redesigns |
| Growth | How do similar people find you faster? | Acquisition cost, activation rate | Custom features for niche requests |
| Maturity | How do you keep users and make money? | Paid conversion, renewal, average order value | Rebuilding the core flow |
| Decline | Milk it as-is, or pivot? | Churn reasons, maintenance cost | Big investments to rescue old features |
Retention-only during exploration is the most counterintuitive row. If users grow fast but don't stick, the product isn't established yet — spending money on acquisition then is pouring water into a leaking bucket. The four-stage shape comes from the classic marketing concept of the product lifecycle; applied to software, the point is that each stage has a different question to answer.plc
How to tell which stage you are in
Ignore how long you've been at it and the raw user count. Read these three signals:
- Is the retention curve flattening? Still sliding = exploration. Flattened = you can talk about growth. This is the dividing line: if retention never flattens, no growth work will save you; once it does — even at a low level — some people genuinely need you.
- Do users come on their own, or were they bought? Organic growth and word of mouth mean you've entered growth. Users pulled in purely by paid campaigns don't count.
- Is new-user retention getting worse? That usually means you've already eaten the core audience and are reaching into the outer ring. The move is not to push more acquisition but to check whether the product still holds for the core group.
Read the three signals together. Any single one can mislead: a flattened retention curve may just mean the product is so niche that only the core group remains; organic growth may just be a news wave. Conclude only when all three point to the same stage.
There's a subtler version of misalignment: the same people push you in different ways at different stages. What users ask for is always valid — but whether to do it now, and how far to go, depends on which stage the product is in. So don't just record "users want X"; record "users want X, raised during this stage."
The cost of doing the wrong stage's work
- Chasing growth during exploration. You burn through the budget, and the users who stick around are still the same few. This is the most common mistake among solo developers.
- Polishing during growth. The window is only a few months wide. While you're adjusting spacing, competitors take the whole market.
- Rebuilding during maturity. Touch the core flow once and every existing user's habit breaks — the revenue curve reacts immediately.
- Rescuing during decline. Big investments rarely bring back a product that's already retreating. That money earns far more pointed at a new direction.
If you are building solo, you spend most of your time in exploration. That means your default move should be: cut scope, find the small group that cannot live without it, and watch whether they come back next week.