skills/unit-economics/SKILL.md
Model the unit economics of a business — CAC, LTV, payback, contribution margin — from real inputs. Use when asked to calculate unit economics, work out LTV:CAC, find the payback period, or check whether a business model is viable per customer. Produces a computed unit-economics summary (LTV, CAC, ratio, payback, contribution margin) with a verdict and the levers that move it most.
npx skillsauth add mohitagw15856/pm-claude-skills unit-economicsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
A business is only viable if each customer is worth more than it costs to acquire and serve. This skill computes the core unit economics — CAC, LTV, the LTV:CAC ratio, payback period, and contribution margin — from real numbers (not vibes), states a clear verdict against the rule-of-thumb benchmarks, and shows which lever moves the model most.
Ask for these only if they aren't already provided:
1. The numbers — computed, with the formula shown (use the helper script so they're consistent):
| Metric | Value | Benchmark | |---|---|---| | Lifetime (1/churn) | | | | LTV (ARPA × margin ÷ churn) | | | | CAC | | | | LTV : CAC | | ≥ 3:1 healthy | | Payback (months) | | < 12 healthy | | Contribution margin | | |
2. Verdict — healthy / borderline / underwater, in one line, against the benchmarks (LTV:CAC ≥ 3, payback < 12 months).
3. Biggest levers — which input, improved realistically, moves the model most (usually churn or CAC), with the rough effect.
4. Caveats — where the inputs are assumptions vs. measured, and what to validate before betting on this.
scripts/unit_econ.py (stdlib only) computes the model so the numbers are calculated, not estimated:
# in.json: {"arpa": 50, "gross_margin": 0.8, "monthly_churn": 0.03, "cac": 400}
python3 scripts/unit_econ.py in.json
python3 scripts/unit_econ.py in.json --json
SaaS unit-economics practice (David Skok / for Entrepreneurs) — margin-based LTV, LTV:CAC ≥ 3, payback < 12 months.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.