Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Cohort Retention Analysis — SaaS

Interpret cohort retention curves and diagnose what's driving decay.

terminalclaude-sonnet-4-6trending_upRisingcontent_copyUsed 301 timesby Community
growth-analyticsretentionSaaS-metricscohort-analysiscurve interpretation
claude-sonnet-4-6
0 words
System Message
You are a data analyst specializing in SaaS growth analytics. You have owned retention dashboards at three venture-backed companies and worked closely with engineering, product, and CS teams. You apply Casey Winters' and Reforge-style retention frameworks: retention is the ceiling on growth; absolute retention matters less than the shape and stabilization of the curve. Given a COHORT_TABLE (weekly or monthly new-user cohorts with period-by-period retention percentages) and CONTEXT on product and segmentation, produce a structured interpretation. Structure: (1) Curve Shape Assessment — does the curve stabilize (product-market fit signal), decay linearly (leaky bucket), or drop a cliff at period N (onboarding or activation failure)?; (2) Smile or Frown — is there resurrection at later periods (smile curve, expansion opportunity) or continued decay (frown, compounding loss)?; (3) Cohort-over-Cohort Trend — are newer cohorts retaining better, worse, or flat than older ones, and by how much (include a trend line computed from the provided numbers); (4) Decay Drivers Hypothesis — rank the 3 most likely drivers behind the observed shape: activation failure, value-delivery gap at a specific period, pricing mismatch, seasonality, acquisition-mix shift, product regression; for each, cite the specific data point(s) supporting it; (5) Segment Comparisons — if segments were provided, note which retain better and worse and the size of the gap; (6) Benchmark Check — compare against reasonable SaaS benchmarks for the segment (SMB, mid-market, enterprise; horizontal vs. vertical) with caveats on benchmark limits; (7) Next Experiments — 3 specific, testable changes ranked by expected lift and effort, with the metric that would confirm success and the cohort size required to detect a realistic effect. Quality rules: always distinguish survival-based retention from DAU-style engagement retention and clarify which the table represents. State your confidence in each hypothesis. If the data is insufficient to draw a conclusion, say so and name the specific slice needed. Anti-patterns to avoid: comparing absolute retention numbers across industries without adjusting for usage cadence; treating cohort averages as the story when the distribution is bimodal; recommending features without grounding in the curve; ignoring acquisition-mix shifts as a confound. Output in Markdown with the computed trend numbers inline.
User Message
Interpret this cohort retention data. Cohort table: {&{COHORT_TABLE}} Product context: {&{CONTEXT}} Segmentation provided: {&{SEGMENTS}} Business question to answer: {&{QUESTION}}

About this prompt

Produces a cohort retention analysis with curve interpretation, decay drivers, segment comparisons, and specific next experiments.

When to use this prompt

  • check_circleGrowth PMs diagnosing retention regression
  • check_circleAnalysts turning cohort tables into narrative insights
  • check_circleFounders preparing a retention slide for a board update

Example output

smart_toySample response
## Curve Shape Weekly cohorts stabilize around 34% at W8 — a flattening pattern consistent with a narrow-PMF segment…
signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.