Communitygithub.com

cbrock84/unit-economics

評估企業是否在每個客戶或單位上獲利——包含貢獻利潤、獲取成本、回收期、終身價值及背後的群組行為。可用於判斷成長是否健康、評估通路或區塊、支援定價決策、判斷企業可承受的成長速度,或診斷為何營收成長未帶來利潤。

unit-economics 是什麼?

這是一個專門分析單位經濟學的 AI 代理技能,旨在幫助開發者與企業人士深入評估每個客戶或單位是否真正為企業帶來利潤。它涵蓋貢獻利潤、獲取成本、回收期、終身價值以及群組行為等關鍵指標,並提供一套嚴謹的建構順序與解讀原則,避免常見的計算錯誤與誤導性比率。本技能適用於 Claude Code、Cursor、Codex 等支援工具檔案的開發者平台,主要透過 SKILL.md 文件引導使用者逐步定義單位、計算貢獻利潤與獲取成本、推算回收期與終身價值,並強調使用群組資料而非平均值來避免偏誤。核心價值在於協助使用者判斷成長是否健康、評估不同通路或客戶區塊的表現、支援定價決策,以及診斷為何營收成長未能轉化為利潤。最終目的是讓使用者根據單位經濟學的結果調整策略:良好數據指引資源配置方向,壞數據則提醒應先修正商業模式再擴大規模。

相容平台~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. 終身價值 — 貢獻 × 預期壽命,根據觀察到的留存率計算,而非根據一個為了產生良好比率而選擇的流失率假設。

誠實解讀

  • 比率會隱藏限制。 一個健康的終身價值比率若伴隨著長回收期,仍意味著成長消耗現金的速度快於產生現金的速度。回收期決定成長速度;比率則決定是否值得做。
  • 在得出結論前先區分區塊。 混合的經濟學幾乎總是隱藏著一個區塊補貼另一個區塊的事實。平均值是最沒用的數字。
  • 使用群組,而非平均值。 留存率會隨著時間改善或惡化,混合數字會掩蓋哪一種情況。如果早期群組的留存率優於近期群組,則企業正在惡化,而平均值看起來仍穩定。
  • 不要將壽命推斷超出你的數據範圍。 一家成立十二個月的公司無法觀察到三年的壽命,而假設一個正是虧損企業顯得有利可圖的方式。

應該改變什麼

按區塊劃分的良好單位經濟學告訴你該在哪裡投入。糟糕的單位經濟學告訴你應在擴大規模前修正商業模式——任何獲取效率都無法挽救負的貢獻利潤,它只會更快地達到虧損。

絕不

  • 將獲取成本與營收而非貢獻比較。
  • 在未說明背後留存數據及其觀察窗口的情況下報告終身價值。
  • 在未檢查是否只是組合發生了轉移的情況下,將改善的比率視為進展。

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.

相關技能