Communitygithub.com

cbrock84/unit-economics

Establishes whether the business makes money on each customer or unit — contribution margin, acquisition cost, payback period, lifetime value, and the cohort behavior underneath. Use this to assess whether growth is profitable, evaluate a channel or segment, support a pricing decision, judge how fast the business can afford to grow, or diagnose why revenue growth is not producing profit.

What is unit-economics?

unit-economics is a Claude Code agent skill that establishes whether the business makes money on each customer or unit — contribution margin, acquisition cost, payback period, lifetime value, and the cohort behavior underneath. Use this to assess whether growth is profitable, evaluate a channel or segment, support a pricing decision, judge how fast the business can afford to grow, or diagnose why revenue growth is not producing profit.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/cbrock84/headcount/tree/main/plugins/finance/skills/unit-economics

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Unit economics

The question is simple and usually unanswered: does one more customer make the business better off, and how long does that take?

Build it in this order

  1. Define the unit. A customer, an account, a seat, an order. State it, because most disagreements about unit economics are disagreements about the unit.
  2. Contribution margin — revenue per unit minus the costs that vary with it. Include everything that actually varies: payment processing, hosting attributable to usage, support load, delivery, third-party fees. Understating variable cost is the single most common error and it flatters everything downstream.
  3. Acquisition cost — fully loaded. All sales and marketing spend, including salaries, divided by customers acquired in the same period. Excluding people costs is the second most common error and typically understates by half or more.
  4. Payback period — acquisition cost divided by monthly contribution. This is the number that governs how fast you can grow without financing it.
  5. Lifetime value — contribution × expected lifetime, from observed retention. Not from a churn-rate assumption chosen because it produces a good ratio.

Read it honestly

  • Ratios hide the constraint. A healthy lifetime-value ratio with a long payback still means growth consumes cash faster than it produces it. Payback governs the growth rate; the ratio governs whether it is worth doing at all.
  • Segment before concluding. Blended economics almost always conceal one segment subsidizing another. The average is the least useful number.
  • Use cohorts, not averages. Retention improves or decays over time, and blended figures mask which. If early cohorts retain better than recent ones, the business is deteriorating while the average looks stable.
  • Do not extrapolate lifetime beyond your data. A twelve-month-old company cannot observe a three-year lifetime, and assuming one is how unprofitable businesses appear profitable.

What it should change

Good unit economics by segment tell you where to spend. Bad ones tell you to fix the model before scaling — no acquisition efficiency rescues a negative contribution margin, it only reaches the loss faster.

Never

  • Compare acquisition cost against revenue rather than contribution.
  • Report lifetime value without stating the retention data behind it and its observation window.
  • Treat improving ratios as progress without checking whether the mix simply shifted.

Individual skills in this repo

This repo contains 11 individual skills — each has its own dedicated page.

cbrock84/interface-craft

Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered product from a generic one. Use this when a screen works but looks unfinished or default, when a layout feels crowded or arbitrary, when a page has no clear focal point, or when an interface needs to feel trustworthy rather than merely functional.

cbrock84/org-design

Designs how an organization is structured — reporting lines, team boundaries, spans and layers, role definition, and workforce planning against the strategy. Use this to structure a new team, restructure an existing one, resolve unclear ownership between teams, plan headcount, or diagnose why a team underperforms for structural rather than individual reasons.

cbrock84/portfolio-governance

Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things. Use this to set up intake and prioritization, run a stage gate, decide between competing initiatives, resolve resource contention across projects, or work out why everything is in flight and nothing is finishing.

cbrock84/product-launch

Takes something built and gets it into the market — tiering the launch to match what it actually warrants, sequencing internal readiness before external announcement, preparing sales and support to answer the questions it creates, choosing the date for a reason, and measuring adoption rather than announcement reach. Use this to plan a launch, right-size one that is consuming more than it deserves, work out why a released feature nobody uses was launched loudly, or run the weeks after launch day.

cbrock84/program-management

Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving. Use this to run a multi-team initiative, recover a program that is slipping, build a delivery plan with dependencies, structure status reporting, or diagnose why cross-team work keeps missing dates.

cbrock84/project-delivery

Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips. Use this to plan a project, build or challenge a schedule, estimate credibly, track progress meaningfully, or recover a project that is late.

cbrock84/retention

Diagnoses and reduces churn — cancellation flows, save offers, failed-payment recovery, at-risk detection, and the product and service causes underneath. Use this when churn is rising or unexplained, to design a cancellation or win-back flow, to recover involuntary churn, to identify at-risk accounts before they leave, or to decide whether a retention problem is a product problem.

cbrock84/sales-enablement

Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies. Use this to create or fix sales collateral, prepare for a competitive deal, build a demo flow, document objection responses, or diagnose why a pitch is not converting.

cbrock84/tax

Structures the tax questions a growing business faces — corporate income, sales and use, payroll, nexus, and the obligations created by hiring or selling somewhere new. Use this to work out what a new state or country obligates you to, prepare for a tax filing or audit, understand sales tax on your product, or check what a remote hire or new market triggers.

cbrock84/video-content

Plans and scripts short-form and long-form video, and designs the packaging — titles, thumbnails, and openings — that determines whether it gets watched. Use this to script a video, plan a series, fix retention or click-through problems, design thumbnail and title concepts, or turn written content into video. For a YouTube channel specifically — idea selection, retention teardowns, and channel-level strategy — use `youtube-producer`.

cbrock84/visual-content

Designs and directs the visual assets that carry content — carousels, infographics, quote graphics, diagrams, and social imagery — including the generation prompts where they are AI-produced. Use this to turn a written piece into a visual format, design a carousel or infographic, create social graphics, or fix visuals that are not stopping the scroll.

Related Skills