Interpret a cohort retention table and surface key insights
Cohort retention tables are easy to generate but hard to read quickly. This prompt extracts the most important signals and frames them as actionable observations for a product or growth team.
You are a product analytics expert. I will paste a cohort retention table and I need you to extract the most important insights from it.
Retention table (paste raw data or describe it): {{RETENTION_TABLE}}
Context:
- Product type: {{PRODUCT_TYPE}}
- Cohort definition (e.g., users who signed up in a given week/month): {{COHORT_DEFINITION}}
- Retention metric being tracked (e.g., DAU, feature usage, purchase): {{RETENTION_METRIC}}
Follow these steps:
1. Identify the overall retention curve shape (e.g., steep early drop, flattens at a floor, gradual decline) and what it typically signals for this product type.
2. Compare the three best-performing cohorts to the three worst-performing cohorts. List the specific percentage-point differences at Day 7 and Day 30 (or the closest intervals available).
3. Flag any cohort that shows an unusual pattern — either a sudden improvement or a sudden drop — and name a plausible cause.
4. State the approximate long-run retention floor if the data shows one, or note if the data does not extend far enough to determine it.
5. Suggest two specific hypotheses worth testing to improve retention at the biggest drop-off point.
Note: This prompt works best when you have at least 6 cohorts and retention data through Day 30. Shorter windows will produce less reliable trend analysis. {{RETENTION_TABLE}}{{PRODUCT_TYPE}}{{COHORT_DEFINITION}}{{RETENTION_METRIC}}
How to use this prompt
- Copy the prompt above (Copy button on the top-right).
- Replace each
{{VAR}}with your own value. Variables:{{RETENTION_TABLE}}{{PRODUCT_TYPE}}{{COHORT_DEFINITION}}{{RETENTION_METRIC}}. - Paste it into one of the recommended tools below.
- Iterate: tighten constraints in the prompt if the output is generic.
Why this prompt is structured this way
The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.
Pair this prompt with a tool
Notion AI
$8/user/mo add-onAI baked into the docs/wiki/projects tool you already use.
Notion AI is unremarkable as a standalone writer but indispensable if Notion is your team's source of truth — it works on the docs and databases you already have.
Claude (Anthropic)
$0/mo (Pro at $20)Frontier model with long context and strong reasoning.
Claude (Opus / Sonnet / Haiku tiers) is the assistant favored by writers and engineers who care about reasoning quality and tone. 1M token context on Opus.
ChatGPT (OpenAI)
$0/mo (Plus at $20)The category-defining general-purpose AI assistant.
ChatGPT has the broadest feature surface: image gen, voice, custom GPTs, web browsing, code execution. Often the right default; sometimes beaten on specific tasks by Claude or Perplexity.
Perplexity
$0/mo (Pro at $20)AI search engine with citations.
Perplexity is the answer engine Google would build if it weren't protecting search ad revenue. Cited answers, follow-up questions, focused source modes.
The PlaybookPrompts weekly
One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.
Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.