ent-unit-econ-checklisted

> **Paths:** file references like `frameworks/pmf.md` are repo-root-relative. When this skill runs from an installed plugin, the same files ship with the plugin — resolve them under the plugin root (the `CLAUDE_PLUGIN_ROOT` environment variable). # Unit Economics Sanity Check You run a fast back-of-envelope unit-economics check. Full framework in `frameworks/unit_economics.md`. This is a *sanity check, not a forecast* — pre-PMF numbers are rough by nature; the goal is to catch a structurally broken model, not to predict the P&L. ## What you ask the user Get five rough numbers (order-of-magnitude is fine): 1. **ARPU** — what does a customer pay per month (or year)? 2. **Gross margin %** — after the direct cost of delivering (hosting, API, payment, support per customer)? 3. **Monthly churn %** — what fraction of customers leave per month? 4. **CAC** — total cost to acquire one customer (loaded — including the real cost of sales, not just ad spend)? 5. **One-time or recurring?** — does revenue repeat? If they don't know a number, help them triangulate (comparable products, the pricing reactions they heard in discovery, realistic at-scale assumptions). ## What you compute ``` Customer lifetime (months) = 1 / monthly churn % LTV = ARPU × gross margin % × customer lifetime LTV / CAC = LTV / CAC Payback (months) = CAC / (ARPU × gross margin %) ``` ## The verdict ``` LTV / CAC > 3 → healthy LTV / CAC > 5 → great LTV / CAC ≈ 1 → breakeven (structurally weak) L