claude-code-arcane 1.0.0

package/skills/copywriting/scripts/headline_scorer.py

@@ -0,0 +1,256 @@
+#!/usr/bin/env python3
+"""
+headline_scorer.py — Scores headlines 0-100
+Usage:
+  python3 headline_scorer.py "Your headline here"
+  python3 headline_scorer.py --file headlines.txt
+  python3 headline_scorer.py --json
+  python3 headline_scorer.py          # demo mode
+"""
+
+import argparse
+import json
+import re
+import sys
+
+
+# ---------------------------------------------------------------------------
+# Word lists
+# ---------------------------------------------------------------------------
+
+POWER_WORDS = {
+    # urgency / scarcity
+    "now", "today", "instantly", "immediately", "urgent", "limited",
+    "exclusive", "last", "hurry", "deadline", "expires", "fast",
+    # value / benefit
+    "free", "save", "proven", "guaranteed", "results", "boost",
+    "increase", "grow", "maximize", "unlock", "secret", "revealed",
+    "transform", "master", "ultimate", "best", "top", "powerful",
+    # curiosity / intrigue
+    "discover", "uncover", "surprising", "shocking", "hidden",
+    "unknown", "insider", "hack", "trick", "truth",
+    # social proof / authority
+    "experts", "researchers", "scientists", "officially", "certified",
+    "award-winning", "world-class",
+    # ease / simplicity
+    "easy", "simple", "effortless", "quick", "step-by-step",
+    "foolproof", "beginner", "without",
+    # negative triggers (fear/loss)
+    "avoid", "stop", "never", "mistake", "fail", "warning", "danger",
+    "worst", "deadly", "risky",
+}
+
+EMOTIONAL_TRIGGERS = {
+    "love", "hate", "fear", "hope", "joy", "pain", "anger", "envy",
+    "trust", "doubt", "regret", "pride", "shame", "relief", "success",
+    "failure", "happiness", "frustration", "excitement", "anxiety",
+    "lonely", "powerful", "confident", "inspired",
+}
+
+JARGON_WORDS = {
+    "synergy", "leverage", "disruptive", "paradigm", "scalable",
+    "bandwidth", "circle back", "ping", "holistic", "ecosystem",
+    "utilize", "facilitate", "ideate", "incentivize", "stakeholders",
+    "deliverables", "actionable", "bespoke", "granular", "boil the ocean",
+    "low-hanging fruit", "move the needle", "thought leader", "deep dive",
+}
+
+
+# ---------------------------------------------------------------------------
+# Scoring functions
+# ---------------------------------------------------------------------------
+
+def tokenize(headline: str) -> list:
+    return re.findall(r"\b\w+(?:[-']\w+)*\b", headline.lower())
+
+
+def score_power_words(tokens: list) -> tuple:
+    found = [t for t in tokens if t in POWER_WORDS]
+    # 1 power word = 60pts, 2 = 85, 3+ = 100
+    score = min(100, len(found) * 35 + (10 if found else 0))
+    return score, found
+
+
+def score_emotional_triggers(tokens: list) -> tuple:
+    found = [t for t in tokens if t in EMOTIONAL_TRIGGERS]
+    score = min(100, len(found) * 50)
+    return score, found
+
+
+def score_numbers(headline: str) -> tuple:
+    numbers = re.findall(r"\b\d+(?:[,\.]\d+)?%?\b", headline)
+    score = 100 if numbers else 0
+    return score, numbers
+
+
+def score_length(tokens: list) -> tuple:
+    n = len(tokens)
+    if 6 <= n <= 12:
+        score = 100
+        note = f"{n} words — optimal (6-12)"
+    elif n < 6:
+        score = max(0, 40 + (n - 1) * 12)
+        note = f"{n} words — too short (6-12 optimal)"
+    else:
+        score = max(0, 100 - (n - 12) * 10)
+        note = f"{n} words — too long (6-12 optimal)"
+    return score, note
+
+
+def score_specificity(headline: str, tokens: list) -> tuple:
+    signals = []
+    if re.search(r"\b\d+\b", headline):
+        signals.append("contains number")
+    if re.search(r"\b(in \d+|within \d+|\d+ days?|\d+ weeks?|\d+ months?|\d+ hours?|\d+ minutes?)\b", headline, re.I):
+        signals.append("timeframe")
+    if re.search(r"\b(how to|step|guide|checklist|strategy|system|framework|formula)\b", headline, re.I):
+        signals.append("concrete format")
+    if re.search(r"\b\d+%\b", headline):
+        signals.append("percentage")
+    score = min(100, len(signals) * 34)
+    return score, signals
+
+
+def score_clarity(tokens: list) -> tuple:
+    found_jargon = [t for t in tokens if t in JARGON_WORDS]
+    score = max(0, 100 - len(found_jargon) * 30)
+    note = "No jargon detected" if not found_jargon else f"Jargon: {', '.join(found_jargon)}"
+    return score, note
+
+
+# ---------------------------------------------------------------------------
+# Aggregate
+# ---------------------------------------------------------------------------
+
+WEIGHTS = {
+    "power_words":        0.25,
+    "emotional_triggers": 0.15,
+    "numbers":            0.15,
+    "length":             0.20,
+    "specificity":        0.15,
+    "clarity":            0.10,
+}
+
+
+def score_headline(headline: str) -> dict:
+    tokens = tokenize(headline)
+
+    pw_score, pw_found = score_power_words(tokens)
+    et_score, et_found = score_emotional_triggers(tokens)
+    num_score, nums = score_numbers(headline)
+    len_score, len_note = score_length(tokens)
+    spec_score, spec_signals = score_specificity(headline, tokens)
+    clar_score, clar_note = score_clarity(tokens)
+
+    breakdown = {
+        "power_words":        {"score": pw_score,   "found": pw_found,      "weight": "25%"},
+        "emotional_triggers": {"score": et_score,   "found": et_found,      "weight": "15%"},
+        "numbers":            {"score": num_score,  "found": nums,           "weight": "15%"},
+        "length":             {"score": len_score,  "note": len_note,        "weight": "20%"},
+        "specificity":        {"score": spec_score, "signals": spec_signals, "weight": "15%"},
+        "clarity":            {"score": clar_score, "note": clar_note,       "weight": "10%"},
+    }
+
+    overall = round(sum(
+        breakdown[k]["score"] * WEIGHTS[k]
+        for k in WEIGHTS
+    ))
+
+    grade = "A" if overall >= 85 else "B" if overall >= 70 else "C" if overall >= 55 else "D" if overall >= 40 else "F"
+
+    return {
+        "headline": headline,
+        "overall_score": overall,
+        "grade": grade,
+        "breakdown": breakdown,
+    }
+
+
+# ---------------------------------------------------------------------------
+# Demo headlines
+# ---------------------------------------------------------------------------
+
+DEMO_HEADLINES = [
+    "10 Proven Ways to Double Your Email Open Rates in 30 Days",
+    "Marketing Tips for Better Results",
+    "Unlock the Secret Formula That Top Experts Use to Grow Revenue Fast",
+    "How to Leverage Synergistic Paradigms for Scalable Growth",
+    "Our New Product Is Now Available",
+]
+
+
+# ---------------------------------------------------------------------------
+# Output helpers
+# ---------------------------------------------------------------------------
+
+def print_result(result: dict):
+    h = result["headline"]
+    score = result["overall_score"]
+    grade = result["grade"]
+    print(f"\n{'─' * 60}")
+    print(f"  Headline: {h}")
+    print(f"  Score:    {score}/100   Grade: {grade}")
+    print(f"{'─' * 60}")
+    bd = result["breakdown"]
+    rows = [
+        ("Power Words",       "power_words",        lambda r: f"found: {r['found'] or 'none'}"),
+        ("Emotional Trigger", "emotional_triggers", lambda r: f"found: {r['found'] or 'none'}"),
+        ("Numbers/Stats",     "numbers",            lambda r: f"found: {r['found'] or 'none'}"),
+        ("Length",            "length",             lambda r: r["note"]),
+        ("Specificity",       "specificity",        lambda r: f"signals: {r['signals'] or 'none'}"),
+        ("Clarity",           "clarity",            lambda r: r["note"]),
+    ]
+    for label, key, detail_fn in rows:
+        r = bd[key]
+        bar_len = round(r["score"] / 10)
+        bar = "█" * bar_len + "░" * (10 - bar_len)
+        detail = detail_fn(r)
+        print(f"  {label:<20} [{bar}] {r['score']:>3}/100  {detail}")
+
+
+# ---------------------------------------------------------------------------
+# Main
+# ---------------------------------------------------------------------------
+
+def main():
+    parser = argparse.ArgumentParser(
+        description="Headline scorer — rates headlines 0-100 across 6 dimensions."
+    )
+    parser.add_argument("headline", nargs="?", help="Single headline to score")
+    parser.add_argument("--file", help="Text file with one headline per line")
+    parser.add_argument("--json", action="store_true", help="Output as JSON")
+    args = parser.parse_args()
+
+    if args.headline:
+        headlines = [args.headline]
+    elif args.file:
+        with open(args.file, "r", encoding="utf-8") as f:
+            headlines = [line.strip() for line in f if line.strip()]
+    else:
+        headlines = DEMO_HEADLINES
+        if not args.json:
+            print("No input provided — running in demo mode.\n")
+            print("Demo headlines:")
+            for h in headlines:
+                print(f"  • {h}")
+
+    results = [score_headline(h) for h in headlines]
+
+    if args.json:
+        print(json.dumps(results, indent=2))
+        return
+
+    for result in results:
+        print_result(result)
+
+    if len(results) > 1:
+        avg = round(sum(r["overall_score"] for r in results) / len(results))
+        best = max(results, key=lambda r: r["overall_score"])
+        print(f"\n{'=' * 60}")
+        print(f"  {len(results)} headlines analyzed  |  Avg score: {avg}/100")
+        print(f"  Best: \"{best['headline'][:50]}\" ({best['overall_score']}/100)")
+        print("=" * 60)
+
+
+if __name__ == "__main__":
+    main()

package/skills/cpo-advisor/SKILL.md

@@ -0,0 +1,102 @@
+---
+name: cpo-advisor
+description: "Product leadership for scaling companies. Product vision, portfolio strategy, product-market fit measurement, product org design, and north star metrics."
+argument-hint: ""
+category: "clevel-advisors"
+user-invocable: true
+allowed-tools: Read, Glob, Grep, Bash
+---
+
+# CPO Advisor
+
+Strategic product leadership. Vision, portfolio, PMF, org design. Not for feature-level work — for the decisions that determine what gets built, why, and by whom.
+
+## The CPO's Core Responsibilities
+
+| Responsibility | What It Means | Reference |
+|---------------|--------------|-----------|
+| **Portfolio** | Which products exist, which get investment, which get killed | `references/product_strategy.md` |
+| **Vision** | Where the product is going in 3-5 years and why customers care | `references/product_strategy.md` |
+| **Org** | The team structure that can actually execute the vision | `references/product_org_design.md` |
+| **PMF** | Measuring, achieving, and not losing product-market fit | `references/pmf_playbook.md` |
+| **Metrics** | North star → leading → lagging hierarchy, board reporting | This file |
+
+## Diagnostic Questions
+
+**Portfolio:**
+- Which product is the dog? Are you killing it or lying to yourself?
+- If you had to cut 30% of your portfolio tomorrow, what stays?
+
+**PMF:**
+- What's your retention curve for your best cohort?
+- What % of users would be "very disappointed" if your product disappeared?
+
+**Org:**
+- Can every PM articulate your north star and how their work connects to it?
+- What's blocking your slowest team — the people or the structure?
+
+## Product Metrics Hierarchy
+
+```
+North Star Metric (1, owned by CPO)
+  ↓ explains changes in
+Leading Indicators (3-5, owned by PMs)
+  ↓ eventually become
+Lagging Indicators (revenue, churn, NPS)
+```
+
+**Good North Stars by business model:**
+
+| Model | North Star Example |
+|-------|------------------|
+| B2B SaaS | Weekly active accounts using core feature |
+| Consumer | D30 retained users |
+| Marketplace | Successful transactions per week |
+| PLG | Accounts reaching "aha moment" within 14 days |
+
+## Investment Postures
+
+Every product gets one: **Invest / Maintain / Kill**. "Wait and see" is not a posture.
+
+| Posture | Signal | Action |
+|---------|--------|--------|
+| **Invest** | High growth, strong retention | Full team. Aggressive roadmap. |
+| **Maintain** | Stable revenue, slow growth | Bug fixes only. Milk it. |
+| **Kill** | Declining, no recovery path | Set a sunset date. Write a migration plan. |
+
+## Red Flags
+
+- Products that have been "question marks" for 2+ quarters without a decision
+- D30 retention below 20% (consumer) or 40% (B2B) and not improving
+- CPO has not talked to a real customer in 30+ days
+- North star going up while retention is going down (metric is wrong)
+
+## Integration with Other C-Suite Roles
+
+| When... | CPO works with... | To... |
+|---------|-------------------|-------|
+| Setting company direction | CEO | Translate vision into product bets |
+| Roadmap funding | CFO | Justify investment allocation per product |
+| Technical feasibility | CTO | Co-own features vs. platform trade-off |
+| Sales-requested features | CRO | Distinguish revenue-critical from noise |
+
+## Proactive Triggers
+
+- Retention curve not flattening → PMF at risk, raise before building more
+- No user research in 90+ days → product team is guessing
+- Portfolio has a "dog" everyone avoids discussing → force the kill/invest decision
+
+## Reasoning Technique: First Principles
+
+Decompose to fundamental user needs. Question every assumption about what customers want. Rebuild from validated evidence, not inherited roadmaps.
+
+## Communication
+
+All output passes the Internal Quality Loop before reaching the founder (see `agent-protocol/SKILL.md`).
+- Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision
+- Every finding tagged: verified, medium confidence, or assumed.
+
+## Resources
+- `references/product_strategy.md` — Vision, JTBD, moats, positioning, BCG, board reporting
+- `references/product_org_design.md` — Team topologies, PM ratios, hiring, product trio, remote
+- `references/pmf_playbook.md` — Finding PMF, retention analysis, Sean Ellis, post-PMF traps

package/skills/cpo-advisor/references/pmf_playbook.md

@@ -0,0 +1,307 @@
+# PMF Playbook
+
+How to find product-market fit, measure it, and not lose it. Steps, not theory.
+
+---
+
+## What PMF Actually Is
+
+PMF is when a product pulls users in rather than pushing them. Signals:
+- Users find the product without you telling them about it
+- They're upset when it doesn't work
+- They bring their colleagues, their friends, their boss
+- They build workarounds when a feature is missing
+
+PMF is not:
+- Users saying they like it
+- A good NPS score with flat growth
+- Enterprise customers who are locked in but churning at contract end
+
+---
+
+## Step 1: Find Your Best Customers First
+
+Before measuring PMF across everyone, find the segment where PMF is strongest.
+
+**How:**
+1. Export a list of all churned users and all retained users (D90+)
+2. Identify 5-10 attributes to compare: company size, industry, job title, signup source, first action taken, time to first value
+3. Find the attributes that are over-represented in retained vs. churned
+4. That's your highest-PMF segment
+
+**This is not an analytics project.** Call 10 retained power users. Ask:
+- "What were you doing before you found us?"
+- "What would you use if we shut down tomorrow?"
+- "Who else in your life has this problem?"
+
+The segment where this conversation is easy and the answers are specific — that's where your PMF is.
+
+---
+
+## Step 2: Measure the Three PMF Signals
+
+Run all three. They measure different things. One signal without the others is misleading.
+
+### Signal 1: Retention Curves
+
+**Method:**
+1. Cohort users by week or month of first use
+2. Calculate % still active at D1, D7, D14, D30, D60, D90
+3. Plot the curve for each cohort
+
+**Interpretation:**
+
+| Curve Shape | What It Means |
+|-------------|--------------|
+| Drops to zero | No PMF. Product doesn't solve a recurring problem. |
+| Drops and keeps dropping | Weak PMF. Some people find value, but not enough to keep coming back. |
+| Drops then flattens above 0 | PMF signal. A core group finds ongoing value. |
+| Flattens higher with each newer cohort | PMF improving. You're learning. |
+
+**Benchmarks:**
+
+| Segment | D30 Retention (PMF threshold) | D90 Retention (strong PMF) |
+|---------|-------------------------------|---------------------------|
+| Consumer | > 20% | > 10% |
+| SMB SaaS | > 40% | > 25% |
+| Enterprise SaaS | > 60% | > 45% |
+| Marketplace (buyers) | > 30% | > 20% |
+| PLG (free-to-paid) | > 25% free D30, > 50% paid D30 | > 15% free D90 |
+
+**If retention is below threshold:**
+- Don't run more acquisition. You'll just churn faster.
+- Find the users who ARE retained. Understand why. Build for them.
+
+---
+
+### Signal 2: Sean Ellis Test
+
+Survey users with one question: "How would you feel if you could no longer use [Product]?"
+
+**Answers:**
+- Very disappointed
+- Somewhat disappointed
+- Not disappointed (it really isn't that useful)
+- N/A — I no longer use [Product]
+
+**Scoring:**
+- Count only "very disappointed" responses
+- Divide by total non-churned respondents
+- PMF threshold: **> 40% "very disappointed"**
+
+**Sample size requirement:** Minimum 40 responses. Under 40, the signal is noisy.
+
+**When to run it:**
+- When you have 100-500 active users
+- Quarterly for ongoing tracking
+- After major product changes
+
+**What to do with "somewhat disappointed":**
+Don't lump them with "very disappointed." The delta between "somewhat" and "very" is where your retention problem lives. Interview people in the "somewhat" group. What's missing? Why only somewhat?
+
+**When score is 20-35%:** You have a segment with PMF. Find them. Ask what they love. Run a separate survey for just that segment.
+
+**When score is < 20%:** Your core value proposition isn't working. This is not a retention tactics problem. Revisit the fundamental problem you're solving.
+
+---
+
+### Signal 3: Organic Growth and Referral
+
+**Metric:** % of new signups that came from existing user referral, word of mouth, or organic search — without a paid incentive.
+
+**Threshold:** > 20% of new users are coming organically without incentive programs.
+
+**How to measure:**
+1. Tag signup source: paid, organic search, referral (with referral code), direct/dark social
+2. Track monthly. Is the organic % trending up or stable?
+3. Interview organic signups: "How did you hear about us?" (don't trust the dropdown)
+
+**Why this matters:** Paid growth can mask the absence of PMF. You can buy users who churn. You can't buy users who tell their friends.
+
+---
+
+## Step 3: Run PMF Experiments (Pre-PMF)
+
+If you're below thresholds, don't optimize — experiment. The goal is to find the version of the product where at least a small segment has PMF.
+
+### The PMF Experiment Loop
+
+```
+1. Pick one customer segment + one hypothesis about their job to be done
+2. Remove everything from the product that doesn't serve that job
+3. Run a 4-week cohort with only that segment
+4. Measure retention + Sean Ellis for that cohort
+5. If PMF signal: this is your beachhead. Double down.
+   If no signal: new hypothesis. Repeat.
+```
+
+**Time box:** Each experiment 4-8 weeks. If you're running experiments for 18+ months with no signal, revisit the problem space, not just the solution.
+
+### What to Change
+
+| Lever | Change | Expected Impact |
+|-------|--------|-----------------|
+| Target segment | Narrow ICP from "all companies" to "Series A SaaS" | Faster learning, higher retention |
+| Core job | Reframe from feature-benefit to outcome-benefit | Better product decisions |
+| Onboarding | Remove steps to time-to-value | D1 retention up |
+| Pricing | Move from per-seat to per-outcome | Align incentives with value |
+| Channel | Switch from outbound to PLG | Different segment discovers product |
+
+---
+
+## Step 4: Validate PMF (Post-Signal, Pre-Scale)
+
+Congratulations, you have a retention curve that flattens. Before you scale:
+
+**Validate that it's real:**
+- Can you acquire more of the same customers? (Test CAC at 2x current volume)
+- Do the retained users expand? (Are they buying more seats, upgrading?)
+- Is the NPS from retained users > 40?
+- Are they forgiving of bugs and slowness? (Love, not tolerance)
+
+**Validate the unit economics:**
+- LTV / CAC > 3x (for SaaS)
+- Payback period < 18 months
+- Gross margin > 60% (SaaS), > 40% (marketplace)
+
+**The danger zone:** Convincing yourself you have PMF before economics are viable. High retention with terrible unit economics is not a business — it's a hobby that grows.
+
+---
+
+## PMF by Business Model
+
+### B2B SaaS
+
+**Primary signal:** D90 retention > 45% in target segment.
+
+**Secondary signals:**
+- NPS from retained users > 50
+- Expansion revenue from retained accounts (NRR > 110%)
+- Sales cycle shortening as word-of-mouth increases
+
+**PMF finding strategy:**
+- Start with one vertical, not the whole market
+- Get 3-5 reference customers who use it daily and refer others
+- Don't expand segment until you can replicate the reference case
+
+**Common false signals:**
+- Retained users who are locked in by contract, not value
+- Expansion revenue from upselling, not from organic growth
+- High satisfaction survey scores with flat usage data
+
+---
+
+### B2C / Consumer
+
+**Primary signal:** D30 retention > 20%, with a flat or rising tail at D90.
+
+**Secondary signals:**
+- DAU/MAU ratio > 20% (daily habit product: > 40%)
+- Session depth (users exploring multiple features, not one-and-done)
+- Organic referral rate > 20% of new installs
+
+**PMF finding strategy:**
+- Consumer PMF is about habit formation — which behavior do you own in a user's day?
+- Find the "aha moment" (the action that predicts retention). Build everything to get users there faster.
+- Segment ruthlessly — consumer PMF is often strong in one demographic, weak in others.
+
+**Common false signals:**
+- High D1 retention from email campaigns that re-engage dormant users
+- Good NPS from vocal users who are power users, not typical users
+- Media buzz driving installs from wrong audience
+
+---
+
+### Marketplace
+
+**Primary signal:** Successful transaction rate and repeat buyer rate.
+
+**Secondary signals:**
+- Supply-side retention (sellers/providers coming back)
+- Liquidity score: % of demand requests matched within acceptable time
+- Referral: both sides sending others
+
+**PMF challenge:** You have two customers (supply and demand). PMF can exist on one side and not the other.
+
+**PMF finding strategy:**
+- Start with constrained geography or category — don't try to be national before local works
+- Measure GMV per cohort, not just transaction count
+- Find the "magic moment" for both buyer and seller. Optimize for both.
+
+---
+
+### PLG (Product-Led Growth)
+
+**Primary signal:** Free-to-paid conversion rate + paid retention.
+
+**Secondary signals:**
+- Time to activation (reaching the "aha moment" in free tier)
+- PQL (product-qualified lead) conversion to paid
+- Team invites from individual users (virality coefficient)
+
+**PMF finding strategy:**
+- The free tier must have genuine value — not a crippled trial
+- Track activation milestone (the action that predicts conversion)
+- Optimize activation before conversion — conversion optimizations don't work if nobody activates
+
+---
+
+## After PMF: The Scaling Trap
+
+Most companies that fail after PMF weren't ready to scale. They scaled the wrong thing.
+
+### The Scaling Trap
+
+You have PMF with segment A. You hire sales and start selling to segment B. Segment B doesn't retain. NPS drops. Engineers chase segment B feature requests. Segment A users feel abandoned.
+
+**This is the most common way early-stage companies die after PMF.**
+
+### What to Do After PMF
+
+**First 90 days after confirming PMF:**
+1. Document your best customer profile in extreme detail
+2. Build the playbook to replicate the reference customer, not to expand the ICP
+3. Hire sales to replicate, not to expand
+4. Instrument everything — you need to know what's driving retention for every new cohort
+5. Don't launch new features. Remove friction from the path that's already working.
+
+**The expansion question:** Only expand ICP when:
+- You can replicate the reference customer at 3x volume with same retention
+- CAC is declining (word of mouth in the reference segment)
+- You've exhausted density in the reference segment
+
+**Don't expand ICP to save the business.** Expanding ICP when retention is declining is panic, not strategy.
+
+---
+
+## How to Know When PMF Is Slipping
+
+PMF is not a binary state. It can degrade. Watch for:
+
+| Signal | What's Happening | Response |
+|--------|-----------------|----------|
+| D30 retention declining across cohorts | Product changes or market change are eroding value | Run Sean Ellis test immediately. Interview churned users. |
+| Sean Ellis score dropping | Users less passionate about the product | Feature gap opening. Competitive pressure. |
+| NPS dropping for retained users | Power users seeing degraded experience | Product quality or performance issues. |
+| Organic referral rate declining | Satisfied users less enthusiastic | Product becoming commoditized. Moat eroding. |
+| Support tickets shifting from feature requests to bug reports | Technical debt catching up | Engineering quality investment needed. |
+| Sales cycles lengthening | ICP no longer self-evident. Positioning drift. | Re-run positioning exercise. Sharpen ICP. |
+
+**The PMF quarterly check:**
+Run Sean Ellis test every quarter. Track D30 retention by cohort every month. Put both on the CPO dashboard. These are your vital signs.
+
+---
+
+## Quick Reference
+
+| Test | Threshold | Frequency |
+|------|-----------|-----------|
+| Sean Ellis | > 40% very disappointed | Quarterly |
+| D30 retention (B2B SaaS) | > 40% | Monthly (by cohort) |
+| D30 retention (consumer) | > 20% | Monthly (by cohort) |
+| D90 retention (B2B SaaS) | > 45% | Monthly (by cohort) |
+| Organic signup % | > 20% | Monthly |
+| NPS (retained users) | > 40 | Quarterly |
+| DAU/MAU (if daily product) | > 20% | Weekly |
+
+Use `scripts/pmf_scorer.py` to run all dimensions together with weighted scoring.