5 exercises — retention curves and PMF signals, DAU/MAU stickiness, early adopter feedback vs. mainstream users, net revenue retention, and activation vs. signup vs. retention.
0 / 5 completed
1 / 5
A product team says: "We think we've found product-market fit — retention is finally holding steady after 90 days." What does "retention holding steady" specifically indicate, and why does the 90-day window matter?
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.
2 / 5
A growth report states: "DAU/MAU is currently at 0.15, up from 0.08 last quarter." How would you explain what this ratio measures and why the increase matters?
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.
3 / 5
A founder is preparing a post-launch retrospective and needs to describe "early adopter feedback diverging from mainstream user feedback." How would this concept be explained to a new team member?
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.
4 / 5
A monthly metrics review states: "Churn is at 4% monthly, but net revenue retention is 108%." How can churn be non-zero while overall revenue is still growing from existing customers?
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.
5 / 5
A post-launch report notes: "We're seeing strong top-of-funnel signups but a steep drop-off at activation." How would a product manager explain "activation" to distinguish it from "signup" and "retention"?
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.
What will I learn from the "Post-Launch Vocabulary — Startup English | Exercises" exercise?
Practice post-launch product vocabulary: retention curves and product-market fit signals, DAU/MAU stickiness, early adopter vs. mainstream feedback, net revenue retention, and the signup-activation-retention funnel. 5 exercises for product-minded engineers.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall required.
How many questions are in this exercise?
This set contains 5 multiple-choice questions, each with a detailed explanation shown after you answer.
Do I need to create an account to track my progress?
No account is required. Your progress bar and score reset each time you reload the page, but you can retry the exercise as many times as you like.
Who is this Startup & Product Language exercise for?
This exercise is built for IT professionals and non-native English speakers who need to read, write, and discuss startup & product language topics confidently at work.
What happens if I answer a question incorrectly?
You will see the correct answer highlighted along with a detailed explanation of why it is correct -- so every wrong answer becomes a learning moment, not just a lost point.
Can I retry this exercise?
Yes -- click "Try again" on the results screen at any time to reset your score and go through all the questions again.
How long does this exercise take to complete?
Most learners finish all 5 questions in under 10 minutes, since each question is answered by clicking a single option.
Where can I find more Startup & Product Language exercises?
See the full Startup & Product Language exercises hub for more vocabulary drills on this topic.
Is this exercise mobile-friendly?
Yes -- the exercise works on any device with a modern browser, including phones and tablets, with no app download required.