Build · Create · Analysis & Finance
Pre-launch PMF threshold register
The founder gets a structured PMF threshold register that fixes the metrics, their pass thresholds, and the false-positive traps in advance, so the later PMF call is measured against pre-committed bars instead of post-hoc rationalization.
You receive: A JSON object: { metrics: [{ metricId, name, metricType: enum(survey|retention|activation|revenue|referral), threshold: number, unit: enum(percent|count|days|ratio), measurementWindow }], falsePositives: [{ pattern, whyItMisleads }], sets BeforeLaunch: bool, seanEllisIncluded: bool }
Part of Choose Business Model
What you receive
The shape of your delivered file. Your result is generated for your inputs.
Your deliverable is a structured document carrying these fields:
- False Positives
- Measurement Window
- Metric Id
- Metric Type
- Metrics
- Name
- Pattern
- Set Before Launch
- Threshold
- Unit
- Why It Misleads
Some fields carry set values, drawn from:
percent, count, days, ratio
survey, retention, activation, revenue, referral
yes, true, 1
Opens soon
STUD opens runs for everyone soon, on every play at once.
Scope of the check
What's verified: STUD verifies the register is structurally complete and that the named guardrails exist: minimum metric count, a Sean-Ellis-style survey threshold at >=40%, Day-7/Day-30 retention metrics, and defined false-positive patterns. STUD does NOT measure the product's actual retention or run the survey; it does NOT decide whether the chosen thresholds are the correct PMF bar. It checks that pre-committed, structurally valid thresholds were authored, not that PMF was achieved.
Get early access to STUD the day it goes live.