mcpbeat Sign in

Biz Unit Economics Agent Skill

Analyze unit economics to evaluate per-unit profitability and business model scalability. Use this skill when the user needs to assess whether each transaction, customer, or product unit is profitable, evaluate startup viability, or optimize contribution margins — even if they say 'does our business model work', 'what's our margin per order', or 'can we scale profitably'.

3k tokens
context cost
the whole folder, loaded on every use
3
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
223
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/asgard-ai-platform/skills --skill biz-unit-economics

What comes with it

7 580 bytes besides the instruction
examples/sample_input.json
scripts/unit_economics.py

The instruction itself

12 sections, as written by the author

Unit Economics

Overview

Unit economics measures profitability at the single-unit level — per customer, per transaction, or per product. If unit economics are negative, scaling makes losses worse, not better. Positive unit economics are the prerequisite for sustainable growth.

Framework

IRON LAW: If Unit Economics Are Negative, Growth = Faster Death

Scaling a business with negative unit economics means losing more money
faster. "We'll make it up in volume" only works if variable costs per unit
decrease with scale (economies of scale). If they don't, more volume = more losses.

Prove unit economics are positive BEFORE investing in growth.

Key Metrics by Business Model

Subscription/SaaS:

| Metric | Formula |

|--------|---------|

| CAC | Total acquisition spend / New customers |

| LTV | ARPU × Gross Margin × (1/Churn Rate) |

| LTV:CAC | Must be > 3:1 |

| Payback Period | CAC / (Monthly ARPU × Gross Margin) |

| Net Revenue Retention | (Starting MRR + Expansion - Contraction - Churn) / Starting MRR |

E-commerce/Marketplace:

| Metric | Formula |

|--------|---------|

| AOV | Total Revenue / Number of Orders |

| Contribution Margin per Order | AOV - COGS - Shipping - Payment fees - Returns |

| Repeat Rate | Returning customers / Total customers |

| Fully-loaded CAC | Total marketing / New customers |

On-demand/Delivery:

| Metric | Formula |

|--------|---------|

| Revenue per Trip | Order value × Take rate |

| Cost per Trip | Driver pay + Support + Insurance + Incentives |

| Contribution per Trip | Revenue - Cost per Trip |

| Orders per Day per Driver | Utilization metric |

Analysis Steps

  • Define the unit: What is one "unit"? (customer, order, trip, seat)
  • Calculate revenue per unit: What does each unit generate?
  • Calculate variable cost per unit: What does each unit cost?
  • Calculate contribution margin: Revenue - Variable cost
  • Layer fixed costs: At what volume do you cover fixed costs? (→ break-even)
  • Assess scalability: Do unit economics improve or degrade at 10x volume?

Output Format

# Unit Economics: {Business}

## Unit Definition
- Unit: {customer / order / trip}
- Time period: {monthly / per-transaction}

## Per-Unit Economics
| Metric | Value |
|--------|-------|
| Revenue per unit | ${X} |
| Variable cost per unit | ${X} |
| Contribution margin | ${X} ({X%}) |

## Scalability Assessment
| Volume | Unit Revenue | Unit Cost | CM | Notes |
|--------|-------------|-----------|-----|-------|
| Current ({N}) | ${X} | ${X} | {X%} | baseline |
| 3x ({N}) | ${X} | ${X} | {X%} | {economies of scale?} |
| 10x ({N}) | ${X} | ${X} | {X%} | {what changes?} |

## Verdict
{Positive/negative unit economics, scalability assessment, key lever to improve}

Examples

Correct Application

Scenario: Unit economics for a Taiwan food delivery startup

  • Revenue per order: NT$350 × 30% take rate = NT$105
  • Variable costs: Driver pay NT$65 + Payment fee NT$10 + Support NT$5 = NT$80
  • Contribution margin: NT$25/order (23.8%) ✓
  • At 10x scale: Driver pay drops to NT$55 (better routing), CM improves to NT$35 (33%)
  • Verdict: Marginally positive, scale-dependent — needs volume for viability

Incorrect Application

  • "Revenue per customer is NT$500, cost per customer is NT$200, so we make NT$300 per customer" — but excluded customer support (NT$150) and payment processing (NT$50). True margin is NT$100. Must include ALL variable costs per unit.

Gotchas

  • "We'll achieve economies of scale": Maybe. Identify WHICH costs decrease with scale and by how much. Delivery driver pay may not decrease. Server costs for SaaS typically do.
  • Contribution margin ≠ profit: CM covers variable costs only. You still need enough total CM to cover fixed costs (see Break-Even Analysis).
  • Blended vs cohort: Blended unit economics across all customers hides that early customers (organic) may be profitable while recent customers (paid acquisition) are not.
  • Negative unit economics can be strategic: Temporarily, in land-grab markets with network effects (ride-sharing, marketplaces). But the path to positive must be explicit.

Scripts

| Script | Description | Usage |

|--------|-------------|-------|

| scripts/unit_economics.py | Compute SaaS unit economics (NRR, GRR, LTV, CAC payback, magic number, burn multiple) | python scripts/unit_economics.py --help |

Run python scripts/unit_economics.py --verify to execute built-in sanity tests.

References

  • For CAC-LTV deep dive, see the biz-cac-ltv skill
  • For break-even analysis, see the biz-breakeven skill

Other skills for the same job

different authors, same section of the catalogue
Protocolsio Integration
by christophacham
×4

Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.

16k tokens
Tailored Resume Generator
by frostant
×4

Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances

3k tokens
Excalidraw Diagram Generator
by github
vendor ×3

Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.

36k tokens scripts
Expo Dev Client
by openai
vendor ×3

Build and distribute Expo development clients locally or via TestFlight

961 tokens
Executing Plans
by ZhanlinCui
×3

Use when you have a written implementation plan to execute in a separate session with review checkpoints

542 tokens
Anndata
by christophacham
×3

Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.

16k tokens
Benchling Integration
by christophacham
×3

Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.

14k tokens
Biopython
by christophacham
×3

Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.

24k tokens

How to use it

Copy the folder

Take asgard-ai-platform/biz-unit-economics from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.