Product-market fit is not a binary milestone — it is a measurable state where your product solves a problem so well that users return organically and tell others. This guide presents a quantifiable framework for measuring PMF, including the Supergraphic metric, cohort retention analysis, the Sean Ellis test, and specific action plans for when you have not yet found fit. The techniques described here were used in the development of tanstackship.com.
What Product-Market Fit Actually Means
The most practical definition comes from Andrew Chen (a16z): PMF is when your retention curve flattens. Users do not churn because your product has become a habit.
Before PMF, your retention curve looks like this:
100% │
75% │ ↘
50% │ ↘
25% │ ↘
0% │__________↘____
│ D1 D7 D30 D90
After PMF:
100% │
75% │ ↘
50% │ ↘───
25% │ ────
0% │__________────
│ D1 D7 D30 D90
The difference is the plateau — users who reach day 30 tend to stay. This is the single metric that matters more than any other.
The Supergraphic Metric
Coined by David Sacks (Yammer/Craft Ventures), the Supergraphic is a simple cohort retention chart that visually shows PMF:
// Calculate cohort retention from your analytics database
// src/server/analytics.ts
export const getCohortRetention = createServerFn({ method: "GET" }).handler(
async ({}, { context }) => {
const rows = await context.env.DB.prepare(`
SELECT
strftime('%Y-%m', created_at) as cohort_month,
COUNT(DISTINCT id) as total_users,
COUNT(DISTINCT CASE WHEN last_active_at >= datetime('now', '-7 days')
THEN id END) as active_last_week,
COUNT(DISTINCT CASE WHEN last_active_at >= datetime('now', '-30 days')
THEN id END) as active_last_month
FROM users
GROUP BY cohort_month
ORDER BY cohort_month DESC
LIMIT 12
`).all()
return rows.results.map((row) => ({
cohort: row.cohort_month,
retention: (row.active_last_month / row.total_users) * 100,
weeklyActive: (row.active_last_week / row.total_users) * 100,
}))
}
)
Reading the Supergraphic:
- If earlier cohorts show higher retention than recent ones → product is improving
- If all cohorts converge at ~30-40% → you have weak PMF
- If any cohort stably plateaus > 40% → you have strong PMF
- If the most recent cohort drops below 20% → you have a problem with onboarding or activation
The Sean Ellis Survey
The most famous PMF metric: "How would you feel if you could no longer use the product?"
// Prompt this survey in-app after 2 weeks of usage
const pmfSurvey = {
question: "How would you feel if you could no longer use [Product Name]?",
options: [
"Very disappointed",
"Somewhat disappointed",
"Not disappointed",
"N/A — I no longer use it",
],
}
| Survey Result | Interpretation |
|---|---|
| 40%+ "Very disappointed" | Strong PMF — focus on growth |
| 25-40% "Very disappointed" | Promising — improve core features |
| < 25% "Very disappointed" | Need to find the right problem or audience |
Implementation
// Track survey responses against user behavior
export const submitPmfSurvey = createServerFn({ method: "POST" }).handler(
async ({ data, context }: { data: { response: string } }) => {
await context.env.DB.prepare(
`INSERT INTO pmf_surveys (user_id, response, created_at) VALUES (?, ?, ?)`
).bind(context.user.id, data.response, Date.now()).run()
// Also check: do "very disappointed" users have higher usage?
return { recorded: true }
}
)
Cohort Retention Analysis
Set up automatic cohort analysis using TanStack Start server functions and Cloudflare D1:
export const getCohortAnalysis = createServerFn({ method: "GET" }).handler(
async ({ data, context }: { data: { months: number } }) => {
const cohorts = []
for (let i = 0; i < data.months; i++) {
const cohortStart = new Date()
cohortStart.setMonth(cohortStart.getMonth() - i)
cohortStart.setDate(1)
const cohortEnd = new Date(cohortStart)
cohortEnd.setMonth(cohortEnd.getMonth() + 1)
const rows = await context.env.DB.prepare(`
WITH cohort_users AS (
SELECT id, created_at FROM users
WHERE created_at >= ? AND created_at < ?
),
weekly_retention AS (
SELECT
u.id,
CAST(julianday(e.created_at) - julianday(u.created_at) AS INTEGER) / 7 as week
FROM cohort_users u
JOIN events e ON e.user_id = u.id AND e.name = 'session'
)
SELECT
week,
COUNT(DISTINCT id) as retained_users
FROM weekly_retention
GROUP BY week
ORDER BY week
`).bind(cohortStart.getTime(), cohortEnd.getTime()).all()
cohorts.push({
cohort: cohortStart.toISOString().slice(0, 7),
retention: rows.results,
})
}
return cohorts
}
)
Retention Benchmarks by Industry
| SaaS Type | D1 Retention | D7 Retention | D30 Retention | PMF Threshold |
|---|---|---|---|---|
| Consumer social | 60% | 40% | 25% | 30% |
| B2B productivity | 80% | 60% | 40% | 50% |
| B2B SaaS (SMB) | 85% | 65% | 45% | 55% |
| B2B SaaS (Enterprise) | 90% | 75% | 60% | 70% |
| E-commerce | 50% | 30% | 15% | 20% |
| Developer tools | 70% | 50% | 35% | 45% |
The PMF Action Framework
Scenario A: Retention Plateau > 40%
Action: Scale acquisition
You have found PMF. Stop optimizing the product for retention and focus on:
- Increasing paid acquisition spend
- SEO and content marketing
- Referral program optimization
- Expanding to adjacent markets
Scenario B: Retention Plateau 20-40%
Action: Deepen engagement
You have partial PMF — some user segments love you, others do not:
- Segment power users and identify what they do differently
- Build features specific to the high-retention segment
- Consider repositioning for a narrower audience
- Improve onboarding for the second user archetype
Scenario C: Retention Plateau < 20%
Action: Pivot or narrow
Something is fundamentally wrong:
- Re-interview the 5-10 users who tried and churned
- Run the Sean Ellis survey and analyze "Not disappointed" responses
- Consider a narrower target market or different problem
- If you are building a developer tool, check: is the first-run experience under 5 minutes?
Leading Indicators of PMF
Before you have enough data for cohort analysis, watch for these signals:
| Signal | How to Measure | Good Signal |
|---|---|---|
| Organic signups | UTM source = direct/referral | > 30% of total signups |
| Self-serve conversions | Paid without touching sales | > 20% conversion rate |
| Feature adoption | % of users using core feature | > 60% weekly use |
| NPS score | Post-onboarding survey | > 30 |
| Time to value | From signup to first "aha" | < 5 minutes |
| Support ticket nature | Feature requests vs bug reports | More feature requests |
| Customer requests | Word-of-mouth referrals | > 1 referral per user |
Case Study: PMF Journey at TanStack Ship
When we started building at tanstackship.com, the initial assumption was that the product would appeal to all React developers building SaaS. Cohort analysis told a different story:
Cohort Analysis (Early Stage):
┌────────────┬──────────┬──────────┬──────────┐
│ Cohort │ D1 │ D7 │ D30 │
├────────────┼──────────┼──────────┼──────────┤
│ 2025-Q3 │ 82% │ 52% │ 18% │
│ 2025-Q4 │ 85% │ 58% │ 22% │
│ 2026-Q1 │ 88% │ 62% │ 35% │
│ 2026-Q2 │ 91% │ 71% │ 48% │
└────────────┴──────────┴──────────┴──────────┘
The key insight from user interviews: users who were solo founders or small teams building their first SaaS had significantly higher retention than users evaluating it as part of an enterprise stack. We narrowed messaging, documentation, and feature development to serve the solo founder segment first.
Measuring PMF With Your Analytics Infrastructure
If you have built UTM and event tracking into your SaaS (as TanStack Ship provides), you can automate PMF measurement:
// Automate PMF dashboard with worker cron
export const generatePmfReport = createServerFn({ method: "GET" }).handler(
async ({}, { context }) => {
const [retention, survey, usage] = await Promise.all([
getCohortRetention(),
getPmfSurveyResults(),
getCoreFeatureAdoption(),
])
return {
supergraphic: retention,
seanEllisScore: survey.veryDisappointedPercent,
dailyActiveUsers: usage.dau,
weeklyActiveUsers: usage.wau,
recommendation: survey.veryDisappointedPercent > 40
? "Scale acquisition"
: survey.veryDisappointedPercent > 25
? "Deepen engagement"
: "Investigate pivot",
}
}
)
Conclusion
Product-market fit is not magic — it is measurable. The Supergraphic shows you at a glance whether your retention curve is flattening. The Sean Ellis survey tells you whether users would miss your product. Cohort analysis reveals which segments love you and which do not.
The framework is simple but not easy:
- Measure cohort retention weekly
- Survey users at the 2-week mark
- Segment power users and analyze their behavior
- Act on the data — narrow, deepen, or pivot
Most startups fail not because they never find PMF, but because they give up too early or pivot too late. A systematic, data-driven approach removes the guesswork.
For a SaaS starter with built-in analytics and cohort tracking infrastructure, see tanstackship.com.
Top comments (1)
This is an excellent, practical framework for measuring product-market fit (PMF) in SaaS. I really appreciate how you combine quantitative metrics—cohort retention, Supergraphic, Sean Ellis survey—with actionable insights for founders. The breakdown of retention plateaus and the targeted actions—scale, deepen engagement, or pivot—makes PMF tangible rather than abstract.
I’d love to collaborate and explore how we could automate PMF dashboards, track usage patterns, and segment users across different SaaS workflows. Sharing strategies for real-time PMF monitoring and early detection of churn risk could be extremely valuable for startup teams.
Would you be open to discussing a collaboration to prototype a data-driven PMF evaluation toolkit for early-stage SaaS products?