financial-unit-economics
Analyzes profitability per customer, product, or transaction to determine business model viability and scalability. Covers CAC, LTV, contribution margin, cohort analysis, and growth-readiness assessment. Use when evaluating business model viability, validating startup metrics (CAC, LTV, payback period), making pricing decisions, comparing business models, or when user mentions unit economics, CAC/LTV ratio, contribution margin, customer profitability, or break-even analysis.
What this skill does
# Financial Unit Economics ## Table of Contents - [Workflow](#workflow) - [Common Patterns](#common-patterns) - [Guardrails](#guardrails) - [Quick Reference](#quick-reference) ## Example **Scenario**: SaaS startup, $100/month subscription - **CAC**: $20k spend / 100 customers = $200 - **Gross margin**: ($100 - $20 variable) / $100 = 80% - **Monthly churn**: 5% -> Average lifetime = 20 months - **LTV**: $100 x 20 months x 80% = $1,600 - **LTV/CAC**: 8:1 (healthy, >3:1), **Payback**: 2.5 months (good, <12 months) - **Interpretation**: Strong unit economics. Can profitably scale marketing spend. ## Workflow Copy this checklist and track your progress: ``` Unit Economics Analysis Progress: - [ ] Step 1: Define the unit - [ ] Step 2: Calculate CAC - [ ] Step 3: Calculate LTV - [ ] Step 4: Assess contribution margin - [ ] Step 5: Analyze cohorts - [ ] Step 6: Interpret and recommend ``` **Step 1: Define the unit** What is your unit of analysis? (Customer, product SKU, transaction, subscription). See [resources/template.md](resources/template.md#unit-definition-template). **Step 2: Calculate CAC** Total acquisition costs (sales + marketing) ÷ new units acquired. Break down by channel if applicable. See [resources/template.md](resources/template.md#cac-calculation-template) and [resources/methodology.md](resources/methodology.md#1-customer-acquisition-cost-cac). **Step 3: Calculate LTV** Revenue over unit lifetime minus variable costs. Use cohort data for retention/churn. See [resources/template.md](resources/template.md#ltv-calculation-template) and [resources/methodology.md](resources/methodology.md#2-lifetime-value-ltv). **Step 4: Assess contribution margin** (Revenue - Variable Costs) ÷ Revenue. Identify levers to improve margin. See [resources/template.md](resources/template.md#contribution-margin-template) and [resources/methodology.md](resources/methodology.md#3-contribution-margin-analysis). **Step 5: Analyze cohorts** Track retention, LTV, payback by customer cohort (acquisition month/channel/segment). See [resources/template.md](resources/template.md#cohort-analysis-template) and [resources/methodology.md](resources/methodology.md#4-cohort-analysis). **Step 6: Interpret and recommend** Assess LTV/CAC ratio, payback period, cash efficiency. Make recommendations (pricing, channels, growth). See [resources/template.md](resources/template.md#interpretation-template) and [resources/methodology.md](resources/methodology.md#5-interpreting-unit-economics). Validate using [resources/evaluators/rubric_financial_unit_economics.json](resources/evaluators/rubric_financial_unit_economics.json). **Minimum standard**: Average score ≥ 3.5. ## Common Patterns **Pattern 1: SaaS Subscription Model** - **Key metrics**: MRR, ARR, churn rate, LTV/CAC, payback period, CAC payback - **Calculation**: LTV = ARPU × Gross Margin % ÷ Churn Rate - **Benchmarks**: LTV/CAC ≥3:1, Payback <12 months, Churn <5% monthly (B2C) or <2% (B2B) - **Levers**: Reduce churn (increase LTV), upsell/cross-sell (increase ARPU), optimize channels (reduce CAC) - **When**: Subscription business, recurring revenue, retention critical **Pattern 2: E-commerce / Transactional** - **Key metrics**: AOV (Average Order Value), repeat purchase rate, contribution margin per order, CAC - **Calculation**: LTV = AOV × Purchase Frequency × Gross Margin % × Customer Lifetime (years) - **Benchmarks**: Contribution margin ≥40%, Repeat purchase rate ≥25%, LTV/CAC ≥2:1 - **Levers**: Increase AOV (bundling, upsells), drive repeat purchases (loyalty programs), reduce variable costs - **When**: Transactional business, e-commerce, retail **Pattern 3: Marketplace / Platform** - **Key metrics**: Take rate, GMV (Gross Merchandise Value), supply/demand CAC, liquidity - **Calculation**: LTV = GMV per user × Take Rate × Gross Margin % ÷ Churn Rate - **Benchmarks**: Take rate 10-30%, LTV/CAC ≥3:1 for both sides, network effects kicking in - **Levers**: Increase take rate (value-added services), improve matching (increase GMV), balance supply/demand - **When**: Two-sided marketplace, platform business **Pattern 4: Freemium / PLG (Product-Led Growth)** - **Key metrics**: Free-to-paid conversion rate, time to convert, paid user LTV, blended CAC - **Calculation**: Blended LTV = (Free users × Conversion % × Paid LTV) - (Free user costs) - **Benchmarks**: Conversion ≥2%, Time to convert <90 days, Paid LTV/CAC ≥4:1 - **Levers**: Increase conversion rate (improve product, optimize paywall), reduce time to value, lower CAC via virality - **When**: Product-led growth, freemium model, viral product **Pattern 5: Enterprise / High-Touch Sales** - **Key metrics**: CAC (including sales team costs), sales cycle length, NRR (Net Revenue Retention), LTV - **Calculation**: LTV = ACV (Annual Contract Value) × Gross Margin % × Average Customer Lifetime (years) - **Benchmarks**: LTV/CAC ≥3:1, Sales efficiency (ARR added ÷ S&M spend) ≥1.0, NRR ≥110% - **Levers**: Shorten sales cycle, increase ACV (upsell, premium tiers), improve retention (NRR) - **When**: Enterprise sales, high ACV, long sales cycles ## Guardrails 1. **Fully-loaded CAC**: Include all acquisition costs (sales salaries, marketing spend, tools, overhead allocation). Excluding sales team salaries is a common miss that inflates perceived economics. 2. **True variable costs**: Only include costs that scale with each unit (COGS, hosting per user, transaction fees). Exclude fixed costs (rent, core engineering). Accurate margins are essential for LTV. 3. **Cohort-based LTV**: Early cohorts are not the same as recent cohorts. Track retention curves by cohort. Base LTV on observed retention, not assumptions. 4. **Use conservative time horizons**: LTV is a prediction. For new products with limited data, weight recent cohorts more heavily and avoid projecting far beyond observed behavior. 5. **Optimize both payback and LTV/CAC**: High LTV/CAC but long payback (>18 months) strains cash. Fast payback (<6 months) allows rapid reinvestment. 6. **Analyze at channel level**: Blended metrics hide the truth. CAC and LTV vary by channel (paid search vs. referral vs. content). Break down separately to optimize spend. 7. **Retention drives LTV exponentially**: Improving monthly churn from 5% to 4% increases LTV by 25%. Retention improvements typically matter more than acquisition improvements. 8. **Gross margin floor**: SaaS needs >=60% gross margin, e-commerce >=40%, to be viable. Low margin means even high LTV/CAC ratios yield poor cash flow. **Common pitfalls:** - ❌ **Ignoring churn**: Assuming customers stay forever. Reality: churn compounds. Use cohort retention curves. - ❌ **Vanity LTV**: Using unrealistic retention (e.g., 5 year LTV with 1 month of data). Stick to observed behavior. - ❌ **Blended CAC**: Mixing profitable and unprofitable channels. Break down by channel, segment, cohort. - ❌ **Not updating**: Unit economics change as product, market, competition evolve. Re-calculate quarterly. - ❌ **Missing costs**: Forgetting support costs, payment processing fees, fraud losses, refunds. Track everything. - ❌ **Premature scaling**: Growing before unit economics work (LTV/CAC <2:1). "We'll make it up in volume" rarely works. ## Quick Reference **Key formulas:** ``` CAC = (Sales + Marketing Costs) ÷ New Customers Acquired LTV (subscription) = ARPU × Gross Margin % ÷ Monthly Churn Rate LTV (transactional) = AOV × Purchase Frequency × Gross Margin % × Lifetime (years) Contribution Margin % = (Revenue - Variable Costs) ÷ Revenue LTV/CAC Ratio = Lifetime Value ÷ Customer Acquisition Cost Payback Period (months) = CAC ÷ (Monthly Revenue × Gross Margin %) CAC Payback (months) = S&M Spend ÷ (New ARR × Gross Margin %) Gross Margin % = (Revenue - COGS) ÷ Revenue Customer Lifetime (months) = 1 ÷ Monthly Churn Rate MRR (Monthly Recurring Revenue) = Sum of all monthly subscriptions ARR (Annual Recurring Revenue) = MRR × 12 ARPU (Average Revenue Per User) = Total
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".