Validation · drive to a verdict
Validation to-do
The cheapest-first test to a confident go / park / kill on Capable-Kids OS — protocols + app + community for parents raising resilient, capable kids. Edge-native (content engine + your capable-kids taste), blue-ish ocean, high great-brand ceiling. Tick items; progress and verdict save in this browser.
◆ The one make-or-break
Will parents pay recurring for a raise-capable-kids protocol — and can the content engine acquire them cheaply, then keep them engaged past the parenting-app churn cliff?
Demand and acquisition are the edge (content-native, an audience you can build). The real risk is the same one that kills most parenting apps: engagement/retention — parents download, try once, drift. So we test demand cheap, then hit the retention question before building.
✕ Falsification — any one of these kills it
- The content engine can't acquire parents at a viable CAC → the edge doesn't apply here.
- Parents like the idea but won't pay recurring — it's a one-off book/course, not a subscription.
- Engagement falls off the parenting-app cliff (try once, drift) → no retention, no compounding brand.
- The promise reads preachy / childish and can't be made a brand adults are proud to belong to.
Verdict
After the gates: pursue seriously, park, or kill?
▲ GO — pursue
Demand + retention + economics green. A second mission brand.
⏸ PARK
Demand yes, retention weak. Revisit format later.
✕ KILL
A falsifier tripped. Stop.
~3–5 wks
to a confident verdict
< €700
content engine owned; a small paid test
0
app built before demand + retention prove out