heyparsadev/claude-venture-plugin / venture/skills/model
model
VerifiedThis skill should be used when the user asks about business models, unit economics, lean canvas, pricing math, CAC/LTV, break-even, or financial projections — e.g. "build a lean canvas", "calculate unit economics", "does the math work", "CAC LTV payback", "revenue projection", "مدل کسبوکار", "اقتصاد واحد", "بیزینس مدل", "حساب کن این بیزینس میصرفه یا نه", "پیشبینی درآمد". Produces a lean canvas, unit economics workbook, and scenario projections in the venture workspace.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.1 KB |
| references/lean-canvas.md | markdown | 1.6 KB |
| references/unit-economics-guide.md | markdown | 2.9 KB |
references/unit-economics-guide.md
View on GitHub# Unit Economics Guide — Formulas & Health Checks
Every output shows formula + inputs + result. Inputs labeled `measured / sourced / assumption (confidence)`.
## Core formulas
```
ARPU = revenue / active customers (per month)
Gross margin % = (revenue − COGS) / revenue
COGS: hosting/API per user, payment fees, support cost per user,
delivery/fulfillment — NOT founder salary or marketing
Monthly churn % = customers lost in month / customers at month start
Lifetime (mo) = 1 / monthly churn (simple; fine early)
LTV = ARPU × gross margin × lifetime
= (ARPU × gross margin) / monthly churn
CAC = total sales+marketing spend / new customers acquired (same period)
blended AND per-channel where data allows; founder time priced in at
a stated hourly rate (ignoring it flatters services badly)
LTV : CAC = LTV / CAC
CAC payback = CAC / (ARPU × gross margin) → months
Contribution = price − variable cost per unit (per order/booking for non-subscription)
Break-even = fixed costs / contribution per customer → # customers; map to month via projection
```
## Health thresholds (rules of thumb — cite as such)
| Metric | Trouble | OK | Healthy |
|---|---|---|---|
| LTV:CAC | <1.5 | ~2 | ≥3 (>>5 = likely under-spending on growth) |
| CAC payback | >18 mo | 12–18 | ≤12 (B2B) / ≤6 (consumer) |
| Gross margin | <40% (software) | 40–70% | >70% software · >20–30% e-commerce/services |
| Monthly churn | >7% B2B / >12% B2C | 4–7% / 8–12% | <3% B2B / <6% B2C |
## Type-specific notes
- **Marketplace:** unit = transaction. Take-rate revenue only (GMV is not revenue). Compute CAC per *side*; LTV on the constrained side.
- **Service/agency:** unit = client or engagement. Capacity ceiling is part of the model (hours available). Utilization % drives everything.
- **E-commerce:** unit = order, then customer. First-order contribution after CAC is the survival number; LTV needs repeat-rate evidence, not hope.
- **Freemium:** model free users as COGS; conversion % free→paid is the assumption to stress hardest.
## Scenario discipline
Pessimistic / base / optimistic varying the 2–3 lowest-confidence inputs. Base case uses uncomfortable defaults: early churn high, CAC rising with scale, conversion below hope. Then one **sensitivity line**: "result is most sensitive to <variable>: ±20% moves payback by <X> months → validate that variable next."
## High-inflation / local-currency contexts (e.g. Iran)
- State the inflation and FX assumption; show money columns in local currency AND a hard-currency reference.
- Annual prepay (common locally) changes payback math — model the cash timing, not just accrual.
- Repricing cadence is part of the model: if costs are USD-linked and prices are local, margin erodes monthly — show it.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |