Communitygithub.com

cbrock84/unit-economics

判断企业是否在每个客户或单位上盈利——涵盖边际贡献、获客成本、回收周期、客户生命周期价值,以及底层的人群队列行为。用于评估增长是否健康、分析渠道或细分市场、支持定价决策、判断企业能承受多快的增长速度,或诊断为何营收增长未能带来利润。

unit-economics 是什么?

该技能提供了一套系统性的单位经济分析框架,帮助创业公司、产品经理和财务分析师快速诊断业务盈利结构。它围绕五个核心指标展开:定义单位(客户/账户/订单等)、计算边际贡献(减去所有变动成本)、完全加载的获客成本(含人员薪资)、回收周期(获客成本/每月贡献)、以及基于实际留存数据的生命周期价值。技能特别强调了三个常见的致命错误:低估变动成本、忽略人员成本、以及用假设的流失率推导生命周期价值。同时,它提供了“诚实阅读”的指导原则——提醒用户比率可能掩盖约束、必须按细分市场而非混合平均值分析、使用队列数据而非总平均数、以及不要超出已有数据范围外推生命周期。该技能适用于所有主流AI Agent平台(如Claude Code、Cursor、Codex等),通过清晰的步骤和警示,帮助用户避免增长阶段常见的财务误判,将单位经济真正转化为决策依据。

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

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

单位经济

问题本身很简单,但通常没有答案:多一个客户是否让企业变得更好,以及需要多长时间才能实现?

按此顺序构建

  1. 定义单位。 客户、账户、席位、订单。明确说明,因为大多数关于单位经济的争论本质上是对单位定义的争论。
  2. 边际贡献 — 每单位收入减去与之相关的变动成本。包括所有实际变动的成本:支付处理、因使用量而产生的托管费用、客服成本、物流、第三方费用。低估变动成本是最常见的错误,它会美化所有下游指标。
  3. 获客成本 — 完全加载。所有销售和市场营销支出,包括薪资,除以同一时期内获取的客户数。排除人员成本是第二常见的错误,通常会低估一半或更多。
  4. 回收周期 — 获客成本除以月度边际贡献。这个数字决定了在无需外部融资的情况下,企业能多快增长。
  5. 生命周期价值 — 边际贡献 × 基于实际留存数据观察到的预期生命周期。而非基于一个为了得到良好比率而人为选择的流失率假设。

诚实解读

  • 比率隐藏了约束条件。 即使生命周期价值比率健康,但回收周期过长,仍然意味着增长消耗现金的速度快于现金产生的速度。回收周期决定了增速;比率决定了这件事是否值得做。
  • 在得出结论前先细分。 混合经济几乎总是掩盖了一个细分市场补贴另一个细分市场的事实。平均值是最没用的数字。
  • 使用队列数据,而非平均数。 留存率会随着时间推移改善或恶化,混合数据会掩盖这一趋势。如果早期队列的留存优于近期队列,说明业务在恶化,而平均值却看似稳定。
  • 不要超出数据范围外推生命周期。 一家成立12个月的公司无法观察到三年的生命周期,假设它存在正是让不盈利企业显得盈利的方法。

它应改变什么

好的单位经济(按细分市场)告诉你该在哪里花钱。差的单位经济告诉你应该在增长前修复模式——没有获客效率能挽救负的边际贡献,它只会更快地加速亏损。

切勿

  • 将获客成本与收入比较,而不是与边际贡献比较。
  • 报告生命周期价值时,不说明其背后的留存数据及观察窗口。
  • 在研究混合是否发生了偏移之前,就将比率的改善视为进步。

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.

相关技能