Installs into .claude/skills of the current project.
Are you the author of Unit Economics?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/oyi77-unit-economics)
---
name: unit-economics
description: Use when calculate CAC, LTV, margins, payback period, and cohort analysis.
Use when evaluating business model sustainability or optimizing growth efficiency.
domain: mindset
author: oyi77
license: Apache-2.0
subdomain: mindset
tags:
- economics
- mindset
- personal-development
- soft-skills
- unit
version: 1.0.0
category: mindset
---
# Unit Economics
## Overview
Mindset skill for unit economics. Builds capability through deliberate practice and structured frameworks.
## Anti-Rationalization Table
| Rationalization | Reality |
|---|---|
| "I'll figure it out as I go" | A structured approach saves time and reduces errors. Follow the workflow in this skill rather than improvising. |
| "I already know this topic" | Familiarity breeds shortcuts. Use the checklist to verify you haven't missed critical steps. |
| "This doesn't apply to my situation" | The patterns here generalize across contexts. Adapt, don't skip — the underlying principles hold. |
| "One more tool will fix it" | Adding complexity rarely solves process gaps. Master the core workflow first. |
## When to Use
**Trigger phrases:**
- "unit economics"
- "Evaluating business model sustainability"
- "Deciding whether to scale go-to-market"
- "Optimizing pricing, retention, or acquisition"
- Evaluating business model sustainability
- Deciding whether to scale go-to-market
- Optimizing pricing, retention, or acquisition
- Investor diligence or board reporting
- **When NOT to use**: Pre-revenue (focus on PMF first), or non-profit models
## When NOT to Use
- When the situation requires professional counseling or therapy
- For high-stakes decisions that need expert judgment
- When the skill conflicts with cultural or personal values
## Core Principles
- **Start small** — Begin with manageable unit economics practices and build incrementally
- **Be consistent** — Daily practice beats occasional intense effort
- **Track progress** — Measure improvement to maintain motivation
- **Reflect regularly** — Review what's working and adjust your approach
## Daily Practice
1. **Morning intention** — Set a specific unit economics goal for the day
2. **Active practice** — Apply unit economics techniques during real situations
3. **Evening reflection** — Review the day's unit economics moments and lessons learned
4. **Journal entry** — Record insights, wins, and areas for improvement
## Frameworks
- **OODA Loop** — Observe, Orient, Decide, Act — for rapid unit economics decision cycles
- **PDCA Cycle** — Plan, Do, Check, Act — for iterative unit economics improvement
- **After-Action Review** — What happened? Why? What to improve?
- **Deliberate Practice** — Focused effort on specific unit economics weaknesses
## Common Pitfalls
- **Perfectionism** — Waiting for ideal conditions instead of starting now
- **Inconsistency** — Practicing sporadically instead of building a routine
- **Isolation** — Not seeking feedback or accountability partners
- **Overwhelm** — Trying to improve everything at once instead of focusing
## Resources
- Keep a unit economics journal for tracking progress
- Find an accountability partner or mentor
- Set weekly unit economics challenges with measurable outcomes
- Review and adjust your approach monthly
```markdown
# Daily Practice Template
## Morning (5 min)
- Set intention for the day
- Review top 3 priorities
## During the day
- Practice the skill in real situations
- Note moments of success and struggle
## Evening (5 min)
- Reflect: What worked? What did not?
- Log one lesson learned
```
## Process
1. **Prepare** — Gather requirements, verify prerequisites, set up environment
1. **Execute** — Run unit economics workflow with configured parameters
1. **Verify** — Validate output meets requirements, document results
## Verification
- [ ] All steps executed successfully
- [ ] Results validated against acceptance criteria
- [ ] Error handling tested with edge cases
- [ ] Documentation updated with findings