docs: ratify product-health metrics (2026-08-29)
Activation 20/35 from access-key date; campaign contributor waitlist 50/100; post-key submissions 10/25 in 90 days; renewal 40/60 excluding lifetime; curation SLA demoted from launch bar.
This commit is contained in:
+16
-9
@@ -4,7 +4,7 @@ type: prd
|
||||
status: draft
|
||||
owner: Patrick (Product)
|
||||
launch-target: 2026-09-26
|
||||
last-updated: 2026-08-26
|
||||
last-updated: 2026-08-29
|
||||
---
|
||||
|
||||
# 📚 AIBook.fun — Product Requirements Document
|
||||
@@ -249,12 +249,18 @@ metrics; those measure the *campaign*, not the *product.* A funded campaign can
|
||||
dead product if nobody activates, renews, or contributes.
|
||||
|
||||
### Product health (report these first)
|
||||
| Metric | Floor | Target | Why it matters |
|
||||
|:--|:--|:--|:--|
|
||||
| **Activation** — read 1 workflow + do 1 Try-it in 14 days | 20% | 35% | The North-Star. Is the core loop actually useful? |
|
||||
| **Workflow submissions** during campaign window | 10 | 25 | Early signal that Layer 2 (contribution) is real |
|
||||
| **Renewal rate** — year-1 cohort | — | 60% | Is a *subscription* the right model at all? |
|
||||
| **Curation turnaround** ≤ 10 working days | 80% | 95% | Can we keep quality without becoming the bottleneck? |
|
||||
|
||||
**Ratified 2026-08-29 (Product).** These are the numbers we run. Do not quote the 60% renewal target on Kickstarter or any public surface.
|
||||
|
||||
| Metric | Floor | Target | Clock / notes | Why it matters |
|
||||
|:--|:--|:--|:--|:--|
|
||||
| **Activation** — read 1 workflow + finish 1 Try-it | 20% | 35% | **14 days from access-key date, not pledge date.** North-Star. | Is the core loop actually useful? |
|
||||
| **Contributor waitlist** during the campaign | 50 | 100 | People who *say* they will contribute a workflow. Not written recipes. | Early Layer-2 signal without betting launch on cold-start writing |
|
||||
| **Workflow submissions** | 10 | 25 | First **90 days after keys go out** | Is paid/open contribution real once the library exists? |
|
||||
| **Renewal rate** — year-1 **paid** cohort | 40% | 60% | **Exclude lifetime SKUs** from the denominator. 60% is internal. | Is a *subscription* the right model at all? |
|
||||
| **Curation turnaround** ≤ 10 working days | 80% | 95% | **Ops SLA after Layer 2 is on** — not a launch health bar | Can we keep quality without becoming the bottleneck? |
|
||||
|
||||
Leading indicator before fulfillment: % of the pre-launch list who run the *sample* Try-it.
|
||||
|
||||
### Campaign performance (the fundraise)
|
||||
| Metric | Min | Target | Stretch |
|
||||
@@ -284,8 +290,9 @@ dead product if nobody activates, renews, or contributes.
|
||||
registrar login.)*
|
||||
2. **Resolve the pricing spine together — lifetime ([D-1](#10-open-decisions)) *and* royalties
|
||||
([D-2](#10-open-decisions)).** They're linked, and both block copy freeze.
|
||||
3. **Ratify the North-Star + the product-health floors** (§8) so we're measuring the right
|
||||
thing from Day 1.
|
||||
3. **~~Ratify the North-Star + the product-health floors~~ Done 2026-08-29.** Locked in §8:
|
||||
activation 20/35 from access date; campaign waitlist 50/100; post-key submissions 10/25 in
|
||||
90 days; renewal 40/60 excluding lifetime; curation SLA not a launch bar.
|
||||
4. **Ratify the Minimum Lovable Library number and assign every workflow an author** (§5.2).
|
||||
5. **Confirm the two unconfirmed co-authors** (Higher Ed, Communities) or re-scope those
|
||||
verticals out of v1.
|
||||
|
||||
Reference in New Issue
Block a user