[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CTF3W97PSSWBAB5FDQAZHK":3,"skill-same:01M6CTF3W97PSSWBAB5FDQAZHK":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":6,"ownerDescription":42,"updatedAt":43,"install":44,"resources":56},"01M6CTF3W97PSSWBAB5FDQAZHK","pricing-unit-economics",null,"Analyzes pricing and unit economics: customer acquisition cost (CAC) versus lifetime value (LTV). Use when setting prices, changing them or checking financial health.","vibbs\u002Fcompany-os","vibbs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7379149?v=4","01M6CT6M03CAS1H7RA89F3965B","Vibbs Dod","01M6CT6M4MY60C9FFQ3AAR2RSK",6,"MIT","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fpricing-unit-economics\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27],"pricing","unit economics","pricing unit economics","customer","health","acquisition","financial health","use","cost","2026-11-10 10:12:30",false,"---\nname: pricing-unit-economics\ndescription: \"Analyzes pricing and unit economics: customer acquisition cost (CAC) versus lifetime value (LTV). Use when setting prices, changing them or checking financial health.\"\nruntimes:\n  claude:\n    user-invocable: true\n---\n\n# Pricing & Unit Economics\n\n## Reference\n- **ID**: S-RISK-05\n- **Category**: Ops & Risk\n- **Inputs**: revenue data, cost structure, acquisition spend, churn rates, customer segmentation\n- **Outputs**: unit economics report + financial forecast → artifacts\u002Ffinance\u002F\n- **Used by**: Ops & Risk Agent\n- **Tool scripts**: .\u002Ftools\u002Fartifact\u002Fvalidate.sh\n\n## Purpose\nAnalyzes customer acquisition cost (CAC), lifetime value (LTV), and related unit economics to validate that the pricing model is sustainable and identify levers for improving profitability.\n\n## Procedure\n\n### Step 0: Revenue Stage Check\n\nRead `company.stage` from `company.config.yaml`.\n\n**Pre-Revenue Mode** (idea\u002Fmvp, 0-10 customers):\n1. Value metric selection — what unit of value does the customer pay for?\n2. Willingness-to-pay hypothesis via customer conversations\n3. Competitive pricing teardown — 3-5 comparable products\n4. Initial price range (floor = cost x 3, ceiling = competitor median)\n5. Price sensitivity test script for first 10 sales conversations\n\nSkip CAC\u002FLTV\u002FNRR calculations until sufficient data exists. Proceed to full unit economics when monthly revenue exceeds $1K or customer count exceeds 20.\n\n1. Calculate **CAC**: total acquisition spend \u002F number of new customers acquired, by channel.\n2. Calculate **LTV**: average revenue per user (ARPU) * gross margin % * average customer lifetime.\n3. Compute the **LTV:CAC ratio** and assess health (target: 3:1 or higher).\n4. Calculate **CAC payback period**: CAC \u002F (ARPU * gross margin %).\n5. Segment the analysis by customer tier, plan, or cohort to find variation.\n6. Review the current pricing model: per-seat, usage-based, flat-rate, freemium.\n7. Stress-test pricing assumptions: what happens if churn increases 20%? If ARPU drops 15%?\n8. Identify pricing optimization opportunities: upsell paths, plan restructuring, value metric alignment.\n9. Produce recommendations with projected financial impact.\n10. **MRR\u002FARR Tracking Framework**:\n    - Define MRR components: new MRR, expansion MRR, contraction MRR, churned MRR, reactivation MRR.\n    - Produce cohort table template: signup month x months-since-signup, tracking retained revenue %.\n    - Calculate Net Revenue Retention (NRR): (Starting MRR + Expansion - Contraction - Churn) \u002F Starting MRR.\n    - Benchmark: NRR > 100% = healthy growth (expansion > churn), > 120% = excellent.\n11. **Financial Forecasting**:\n    - Build 3\u002F6\u002F12 month revenue projections using current MRR growth rate.\n    - Model three scenarios: Optimistic (1.5x current growth), Base (current growth), Pessimistic (0.5x current growth).\n    - Include key assumptions and sensitivity ranges.\n    - For each scenario: projected MRR, ARR, customer count, ARPU.\n12. **Runway Monitoring**:\n    - Calculate monthly burn rate: total monthly expenses (engineering, marketing, infrastructure, operations).\n    - Calculate months of runway: current cash \u002F monthly burn rate.\n    - Define trigger thresholds:\n      - Green: > 18 months runway.\n      - Yellow: 12-18 months (start exploring funding).\n      - Orange: 6-12 months (actively fundraise).\n      - Red: \u003C 6 months (emergency mode: cut costs or close round).\n    - Cash-out date projection based on current burn and revenue growth.\n13. **Budget Allocation Framework**:\n    - Define spending ratios by company stage:\n      - **idea\u002Fmvp**: 70% engineering, 15% marketing, 10% infra, 5% ops.\n      - **growth**: 50% engineering, 25% marketing, 15% infra, 10% ops.\n      - **scale**: 40% engineering, 30% marketing, 15% infra, 15% ops.\n    - Compare current allocation vs recommended ratios.\n    - Flag significant deviations with recommendations.\n14. **Investor Reporting Template**:\n    - Produce monthly investor update outline:\n      1. Key metrics (MRR, growth %, NRR, CAC, LTV:CAC, runway).\n      2. Product highlights (shipped features, user feedback themes).\n      3. Growth highlights (acquisition channels, activation rate).\n      4. Challenges & risks (what's not working, market shifts).\n      5. Asks (specific help needed from investors: intros, hiring, advice).\n    - Reference the template at `standards\u002Fops\u002Finvestor-reporting-template.md`.\n15. Save the unit economics report to `artifacts\u002Ffinance\u002F`.\n16. Validate the artifact using `.\u002Ftools\u002Fartifact\u002Fvalidate.sh`.\n\n## Quality Checklist\n- [ ] CAC is calculated by channel, not just blended\n- [ ] LTV calculation uses gross margin, not revenue\n- [ ] LTV:CAC ratio is computed and benchmarked\n- [ ] CAC payback period is calculated\n- [ ] Analysis is segmented by meaningful cohorts\n- [ ] Sensitivity analysis covers key risk scenarios\n- [ ] Pricing recommendations are tied to data\n- [ ] MRR decomposition (new, expansion, contraction, churn) is present\n- [ ] NRR is calculated and benchmarked\n- [ ] Financial forecast covers at least 3 scenarios\n- [ ] Runway is calculated with traffic-light classification\n- [ ] Budget allocation compared to stage-appropriate ratios\n- [ ] Investor update template is referenced\n- [ ] Artifact passes validation\n","# Pricing & Unit Economics\n\n## Reference\n- **ID**: S-RISK-05\n- **Category**: Ops & Risk\n- **Inputs**: revenue data, cost structure, acquisition spend, churn rates, customer segmentation\n- **Outputs**: unit economics report + financial forecast → artifacts\u002Ffinance\u002F\n- **Used by**: Ops & Risk Agent\n- **Tool scripts**: .\u002Ftools\u002Fartifact\u002Fvalidate.sh\n\n## Purpose\nAnalyzes customer acquisition cost (CAC), lifetime value (LTV), and related unit economics to validate that the pricing model is sustainable and identify levers for improving profitability.\n\n## Procedure\n\n### Step 0: Revenue Stage Check\n\nRead `company.stage` from `company.config.yaml`.\n\n**Pre-Revenue Mode** (idea\u002Fmvp, 0-10 customers):\n1. Value metric selection — what unit of value does the customer pay for?\n2. Willingness-to-pay hypothesis via customer conversations\n3. Competitive pricing teardown — 3-5 comparable products\n4. Initial price range (floor = cost x 3, ceiling = competitor median)\n5. Price sensitivity test script for first 10 sales conversations\n\nSkip CAC\u002FLTV\u002FNRR calculations until sufficient data exists. Proceed to full unit economics when monthly revenue exceeds $1K or customer count exceeds 20.\n\n1. Calculate **CAC**: total acquisition spend \u002F number of new customers acquired, by channel.\n2. Calculate **LTV**: average revenue per user (ARPU) * gross margin % * average customer lifetime.\n3. Compute the **LTV:CAC ratio** and assess health (target: 3:1 or higher).\n4. Calculate **CAC payback period**: CAC \u002F (ARPU * gross margin %).\n5. Segment the analysis by customer tier, plan, or cohort to find variation.\n6. Review the current pricing model: per-seat, usage-based, flat-rate, freemium.\n7. Stress-test pricing assumptions: what happens if churn increases 20%? If ARPU drops 15%?\n8. Identify pricing optimization opportunities: upsell paths, plan restructuring, value metric alignment.\n9. Produce recommendations with projected financial impact.\n10. **MRR\u002FARR Tracking Framework**:\n    - Define MRR components: new MRR, expansion MRR, contraction MRR, churned MRR, reactivation MRR.\n    - Produce cohort table template: signup month x months-since-signup, tracking retained revenue %.\n    - Calculate Net Revenue Retention (NRR): (Starting MRR + Expansion - Contraction - Churn) \u002F Starting MRR.\n    - Benchmark: NRR > 100% = healthy growth (expansion > churn), > 120% = excellent.\n11. **Financial Forecasting**:\n    - Build 3\u002F6\u002F12 month revenue projections using current MRR growth rate.\n    - Model three scenarios: Optimistic (1.5x current growth), Base (current growth), Pessimistic (0.5x current growth).\n    - Include key assumptions and sensitivity ranges.\n    - For each scenario: projected MRR, ARR, customer count, ARPU.\n12. **Runway Monitoring**:\n    - Calculate monthly burn rate: total monthly expenses (engineering, marketing, infrastructure, operations).\n    - Calculate months of runway: current cash \u002F monthly burn rate.\n    - Define trigger thresholds:\n      - Green: > 18 months runway.\n      - Yellow: 12-18 months (start exploring funding).\n      - Orange: 6-12 months (actively fundraise).\n      - Red: \u003C 6 months (emergency mode: cut costs or close round).\n    - Cash-out date projection based on current burn and revenue growth.\n13. **Budget Allocation Framework**:\n    - Define spending ratios by company stage:\n      - **idea\u002Fmvp**: 70% engineering, 15% marketing, 10% infra, 5% ops.\n      - **growth**: 50% engineering, 25% marketing, 15% infra, 10% ops.\n      - **scale**: 40% engineering, 30% marketing, 15% infra, 15% ops.\n    - Compare current allocation vs recommended ratios.\n    - Flag significant deviations with recommendations.\n14. **Investor Reporting Template**:\n    - Produce monthly investor update outline:\n      1. Key metrics (MRR, growth %, NRR, CAC, LTV:CAC, runway).\n      2. Product highlights (shipped features, user feedback themes).\n      3. Growth highlights (acquisition channels, activation rate).\n      4. Challenges & risks (what's not working, market shifts).\n      5. Asks (specific help needed from investors: intros, hiring, advice).\n    - Reference the template at `standards\u002Fops\u002Finvestor-reporting-template.md`.\n15. Save the unit economics report to `artifacts\u002Ffinance\u002F`.\n16. Validate the artifact using `.\u002Ftools\u002Fartifact\u002Fvalidate.sh`.\n\n## Quality Checklist\n- [ ] CAC is calculated by channel, not just blended\n- [ ] LTV calculation uses gross margin, not revenue\n- [ ] LTV:CAC ratio is computed and benchmarked\n- [ ] CAC payback period is calculated\n- [ ] Analysis is segmented by meaningful cohorts\n- [ ] Sensitivity analysis covers key risk scenarios\n- [ ] Pricing recommendations are tied to data\n- [ ] MRR decomposition (new, expansion, contraction, churn) is present\n- [ ] NRR is calculated and benchmarked\n- [ ] Financial forecast covers at least 3 scenarios\n- [ ] Runway is calculated with traffic-light classification\n- [ ] Budget allocation compared to stage-appropriate ratios\n- [ ] Investor update template is referenced\n- [ ] Artifact passes validation\n",{"name":5,"runtimes":33,"description":7},{"claude":34},{"user-invocable":35},true,"main","e842fb6d0e04360c47db78bc2e2e2987314d64d4","os\u002Fskills\u002Fpricing-unit-economics",2,"https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os","https:\u002F\u002Fgithub.com\u002Fvibbs","Principal Engineer · Applied AI · building ArcAI @ GrowthArc","2026-10-21 02:08:08",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":35},[46,49,52],{"tool":47,"command":48},"npx","npx skills add vibbs\u002Fcompany-os --skill pricing-unit-economics",{"tool":50,"command":51},"bunx","bunx skills add vibbs\u002Fcompany-os --skill pricing-unit-economics",{"tool":53,"command":54},"pnpm","pnpm dlx skills add vibbs\u002Fcompany-os --skill pricing-unit-economics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fpricing-unit-economics\u002FSKILL.md",[57],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"scripts\u002Fverify_ui.sh","SCRIPT","脚本",895,"https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Fandroid_ui_verification\u002Fscripts\u002Fverify_ui.sh",[64,73,81,91,107,125],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":28},"01M6CTHBW1E64ECYGD105N4S5E","typo-field","Fixture skill with a misspelled top-level field.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Ftypo-field\u002FSKILL.md",[],[71,72],"typo field","fixture skill",{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":28},"01M6CTHABTV8FKVDHFMMKPAV51","spaced-comments","Fixture skill with comments and spaces after block keys.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fspaced-comments\u002FSKILL.md",[],[80,72],"spaced comments",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":28},"01M6CTH8MHC14KB65ZDHYBJW1N","crlf-comments","Fixture skill with Windows line endings.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fcrlf-comments\u002FSKILL.md",[],[88,89,90,72],"crlf comments","CRLF","windows",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":28},"01M6CTH6TBKTDP9G8QB1Z2K0TY","claude-fields","Fixture skill using top-level fields Claude Code documents.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fclaude-fields\u002FSKILL.md",[],[98,99,100,101,102,103,72,104,105,106],"claude fields","explore","documents","src","grep","read","Bash","code","testing",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":118,"publishedAt":28},"01M6CTH46BGKXH80RWS876Y2CW","workflow-router","Maps an objective to the artifacts, stages and agents it needs. Use when deciding what happens next or which agents to involve.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fworkflow-router\u002FSKILL.md",[113],{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[119,120,121,122,123,26,124],"workflow","router","workflow router","next","maps","artifacts",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":28},"01M6CTH27653SRVP2FMEQN3J5B","weekly-review","Summarizes your week: what shipped, AI spend, support themes, security health and next priorities. Use at the end of each week.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[132,133,134,122,26,23,135,136,137],"weekly review","review","priorities","save","support","security"]