Post-Launch Vocabulary

A retention curve plots the percentage of users still active at increasing time intervals after signup (Day 1, Day 7, Day 30, Day 90...). Nearly all products see retention decline initially as casual or curious signups drop off — the meaningful signal isn't the initial decline, it's whether the curve flattens into a plateau rather than continuing toward zero.

Why the specific time window matters: a curve that's still declining at 90 days suggests users are gradually abandoning the product even after the initial "trying it out" phase — a weak PMF signal. A curve that has flattened by 90 days suggests a stable core group of habitual or dependent users has formed — a strong PMF signal, since these users have moved past the novelty phase and are still finding ongoing value.

Related term: "cohort retention" — analysing retention curves separately for different signup cohorts (e.g. users who signed up in January vs. March) to see whether retention is improving over time as the product improves, rather than looking at one blended average that can hide this trend.

DAU/MAU (stickiness ratio) is one of the most widely cited engagement metrics for consumer and habit-forming products, because it directly measures frequency of use in a single normalised number, rather than requiring separate DAU and MAU figures to be compared manually.

Rough interpretation guide (varies significantly by product category):
• Below ~0.10 — used occasionally, low habitual use (common for many B2B tools used a few times a week)
• ~0.15-0.25 — moderate stickiness
• 0.50+ — very sticky, near-daily habitual use (typical of the best consumer social/messaging apps)

The trend (0.08 → 0.15) usually matters more than the absolute number, since acceptable stickiness varies enormously by product category — a project management tool used 3 times a week can be perfectly healthy at a lower DAU/MAU than a messaging app used daily. Reporting the trend alongside context ("stickiness nearly doubled, which we attribute to the new notification feature shipped in March") turns a raw ratio into an actionable growth narrative.

The distinction between early adopters and the broader mainstream market is a foundational concept in product strategy (rooted in the "technology adoption lifecycle" / "crossing the chasm" framework), and recognising it explicitly is critical during a post-launch phase when teams are deciding what to build next based on the feedback they've received so far.

Why this divergence happens: early adopters are self-selected to be more forgiving of bugs, more excited about novel capabilities, and often more technical than the eventual mass-market user. A common post-launch trap is over-building for this vocal, engaged, but non-representative early group, while the features that would actually unlock broader adoption (simpler onboarding, more polish, fewer configuration options) go unaddressed.

Vocabulary for communicating this in a retrospective: "our early adopter feedback skewed heavily toward power-user features, but our churn data among newer, less technical signups suggests onboarding friction is the bigger opportunity — we should weight our roadmap accordingly." This shows the team is triangulating between qualitative feedback and quantitative behaviour data, not just following the loudest voices.

Net Revenue Retention (NRR) — sometimes called Net Dollar Retention (NDR) — is one of the most closely watched SaaS metrics because it isolates the health of the existing customer base, separate from new customer acquisition. It's calculated as: (starting revenue from a cohort of customers + expansion revenue − churned/contracted revenue) ÷ starting revenue.

Why NRR > 100% while churn is non-zero is not contradictory but normal and desirable: churn (customers leaving or downgrading) reduces revenue, but expansion revenue (existing customers adding seats, upgrading tiers, or buying more usage) can offset and exceed those losses. An NRR of 108% is generally considered a strong, healthy signal in SaaS/B2B businesses — it means the company would keep growing even with zero new customer acquisition, purely from its existing base expanding.

Related vocabulary: gross revenue retention (GRR) — the same calculation but excluding expansion revenue, showing pure retention without the "boost" from upsells; comparing NRR and GRR side by side reveals how much of retained growth comes from expansion versus simply not losing customers.

The signup → activation → retention funnel is a standard product-analytics framework, and precisely distinguishing these three stages is essential for diagnosing exactly where a growth problem lies, since each stage points to a different fix.

Definitions:
• Signup — the low-friction moment of creating an account; doesn't indicate the user has experienced any real value yet
• Activation — the "aha moment" — a specific, defined action that correlates strongly with a user going on to become a retained, engaged user (e.g. for a messaging app, "sent their first message to another person"; for a data tool, "connected their first data source and viewed a report")
• Retention — whether activated users continue returning over time

Diagnostic value of separating these: "strong signups, steep activation drop-off" specifically points to an onboarding problem — the product's value exists but users aren't reaching it — which calls for a different fix (simplifying onboarding, better empty-state guidance) than a retention problem (users reach the value but it doesn't stick), which would call for improving the core product loop instead. Naming the specific funnel stage precisely, rather than a vague "our numbers are down," directs the team's effort correctly.

This comment focuses on code clarity and maintainability – 'verbose' and 'readability' are key terms in software development. The suggestion for a helper function addresses potential complexity, which is a common concern when reviewing code. It's not about performance or architectural disagreements; it's directly about the quality of the code itself.

'Time savings' is a crucial element of the *value proposition*—it directly addresses a key user need. Startups frequently focus on demonstrable benefits, and reducing user effort is a common and effective approach to drive adoption. While data analysis and marketing are related, they aren't what 'time savings' represents in this scenario.

'Seamless integration' emphasizes a smooth and intuitive user experience. It suggests that the new payment functionality has been added without causing confusion or requiring users to navigate unfamiliar processes. The opposite of seamless would be complex or disruptive.

'Signups' represent the *number* of new users who registered. 'Conversion rates', on the other hand, measure the percentage of those signups that actually become paying customers – a crucial indicator of revenue potential. Understanding this distinction is vital for identifying areas needing improvement.

'Click-through rate' is a standard metric in digital marketing that measures the effectiveness of an interactive element. It specifically indicates how many users *clicked* on something – in this case, the banner ad – out of the total number who saw it. This provides insight into user interest and engagement.