[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F73XEVFQ4RGTY7R6JEYEE2":3,"skill-same:01M7F73XEVFQ4RGTY7R6JEYEE2":62},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":14,"repositoryHtmlUrl":45,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M7F73XEVFQ4RGTY7R6JEYEE2","building-driver-based-models",null,"Constructs driver-based financial models with operational metric linkage and sensitivity analysis. Use when building driver-based forecasts, linking operational and financial metrics, or modeling business drivers.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffinance\u002Fbuilding-driver-based-models\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: building-driver-based-models\nlanguage: en\ndescription: Constructs driver-based financial models with operational metric linkage and sensitivity analysis. Use when building driver-based forecasts, linking operational and financial metrics, or modeling business drivers.\ntags:\n  - modeling\n  - financial-planning-and-analysis\nmetadata:\n  author: casemark\n  practice_areas:\n    - FP&A\n    - Management Accounting\n    - Business Intelligence\n  document_types:\n    - Model\n  skill_modes:\n    - Modeling\nsource: \"https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills\"\nsource_repository: \"CaseMark\u002Fskills\"\nsource_path: \"skills\u002Ffinance\u002Fbuilding-driver-based-models\u002FSKILL.md\"\nlicense: \"Apache-2.0\"\nimported_at: \"2026-09-20\"\n---\n# Building Driver Based Models\n\n## When To Use\n\n- Building a forecast model that ties operational metrics (headcount, units sold, utilization rates) to financial outcomes (revenue, COGS, operating expenses)\n- Replacing static spreadsheet budgets with dynamic models where changing one driver cascades through the P&L, balance sheet, or cash flow\n- Preparing scenario analyses for board presentations, fundraising narratives, or strategic planning cycles\n- Linking departmental KPIs to consolidated financial statements for management reporting\n\n## Inputs To Gather\n\n- **Business context**: industry, business model (SaaS, manufacturing, services, retail), revenue streams, and cost structure\n- **Historical data**: 12-36 months of actuals for revenue, expenses, headcount, and unit economics; identify which periods are representative vs. anomalous\n- **Operational drivers to model**: e.g., leads → conversion rate → customers → ARPU → revenue; or units produced → materials cost per unit → direct labor hours → COGS\n- **Assumptions and constraints**: growth targets, hiring plans, pricing changes, capacity limits, capital expenditure schedules\n- **Granularity requirements**: monthly vs. quarterly cadence, department-level vs. consolidated, single entity vs. multi-entity\n- **Sensitivity parameters**: which 2-5 drivers are most uncertain and should be toggled in scenario analysis\n\n## Workflow\n\n1. **Map the driver tree**\n   - Identify 3-7 primary drivers per revenue stream and major cost category\n   - Build a driver hierarchy: top-level financial line items → intermediate metrics → base operational inputs\n   - Example revenue tree: website visits → lead conversion % → qualified leads → close rate → new customers → average contract value → new ARR\n   - Example cost tree: headcount by department → fully loaded cost per head → total personnel expense; or units shipped → packaging cost\u002Funit → freight cost\u002Funit → total fulfillment cost\n\n2. **Structure the model layout**\n   - **Assumptions tab**: all tunable inputs in one place — growth rates, pricing, conversion rates, cost-per-unit figures, hiring timeline\n   - **Driver calculations tab**: intermediate computations linking assumptions to financial outputs\n   - **Output tabs**: P&L, cash flow, and balance sheet (or whichever statements are in scope)\n   - **Scenarios tab**: base, upside, and downside cases toggled by changing assumption sets\n   - Use named ranges or clear cell references; never hardcode numbers inside formulas\n\n3. **Build driver-to-output linkages**\n   - Wire each financial line item to its driver chain — no line item should be a flat manual entry unless truly fixed\n   - For revenue: connect volume drivers × price drivers, accounting for churn\u002Fretention where applicable\n   - For variable costs: tie to the volume driver they scale with (e.g., COGS scales with units sold, hosting costs scale with active users)\n   - For semi-variable costs: model the fixed base plus the variable component (e.g., customer support = base team + 1 FTE per 500 incremental accounts)\n   - For fixed costs: link to timing assumptions (lease start dates, SaaS contract renewals) rather than flat monthly amounts where possible\n   - [VERIFY] Tax rate assumptions, depreciation methods, and capitalization thresholds against the entity's jurisdiction and accounting policy\n\n4. **Run sensitivity and scenario analysis**\n   - Select the 3-5 highest-impact, highest-uncertainty drivers\n   - Build a data table or scenario toggle showing how changes in each driver affect EBITDA, cash runway, or the target metric\n   - Construct at minimum: base case (management plan), downside (stress test on demand or pricing), upside (accelerated growth or margin expansion)\n   - Document what \"downside\" and \"upside\" mean quantitatively (e.g., \"downside = 20% lower conversion rate and 10% higher CAC\")\n\n5. **Validate and stress-test**\n   - Check that the model balances: assets = liabilities + equity on every period; cash flow reconciles to balance sheet cash movement\n   - Compare model outputs against historical actuals — if the model cannot replicate last year's results with last year's inputs, the driver structure is wrong\n   - Test extreme inputs: what happens if a key driver goes to zero or doubles? The model should degrade gracefully, not produce errors or nonsensical outputs\n   - Verify unit economics implied by the model (e.g., LTV:CAC ratio, gross margin %) are within plausible industry ranges [VERIFY]\n\n## Output\n\n- **Driver map diagram**: visual showing the hierarchy from operational inputs → intermediate metrics → financial line items\n- **Assumptions summary**: table of all input assumptions with source\u002Fbasis noted (historical average, management target, industry benchmark)\n- **Linked financial model**: P&L (and optionally balance sheet\u002Fcash flow) with every line item traceable to its driver chain\n- **Scenario comparison table**: base\u002Fupside\u002Fdownside side-by-side with key metrics (revenue, EBITDA, cash balance, burn rate)\n- **Sensitivity matrix**: tornado chart or data table showing which drivers move the target metric most\n\n## Quality Checks\n\n- Every financial line item traces back to at least one operational driver — no orphan rows with hardcoded values\n- Changing any single assumption in the assumptions tab correctly cascades through all dependent calculations\n- Model reproduces historical actuals within 5% tolerance when fed historical driver values\n- Scenario outputs are internally consistent (e.g., headcount in downside case still supports the revenue volume assumed)\n- All external benchmarks, tax rates, and regulatory thresholds are marked [VERIFY] with source noted\n- Assumptions tab clearly distinguishes between data-backed inputs and management estimates\n","# Building Driver Based Models\n\n## When To Use\n\n- Building a forecast model that ties operational metrics (headcount, units sold, utilization rates) to financial outcomes (revenue, COGS, operating expenses)\n- Replacing static spreadsheet budgets with dynamic models where changing one driver cascades through the P&L, balance sheet, or cash flow\n- Preparing scenario analyses for board presentations, fundraising narratives, or strategic planning cycles\n- Linking departmental KPIs to consolidated financial statements for management reporting\n\n## Inputs To Gather\n\n- **Business context**: industry, business model (SaaS, manufacturing, services, retail), revenue streams, and cost structure\n- **Historical data**: 12-36 months of actuals for revenue, expenses, headcount, and unit economics; identify which periods are representative vs. anomalous\n- **Operational drivers to model**: e.g., leads → conversion rate → customers → ARPU → revenue; or units produced → materials cost per unit → direct labor hours → COGS\n- **Assumptions and constraints**: growth targets, hiring plans, pricing changes, capacity limits, capital expenditure schedules\n- **Granularity requirements**: monthly vs. quarterly cadence, department-level vs. consolidated, single entity vs. multi-entity\n- **Sensitivity parameters**: which 2-5 drivers are most uncertain and should be toggled in scenario analysis\n\n## Workflow\n\n1. **Map the driver tree**\n   - Identify 3-7 primary drivers per revenue stream and major cost category\n   - Build a driver hierarchy: top-level financial line items → intermediate metrics → base operational inputs\n   - Example revenue tree: website visits → lead conversion % → qualified leads → close rate → new customers → average contract value → new ARR\n   - Example cost tree: headcount by department → fully loaded cost per head → total personnel expense; or units shipped → packaging cost\u002Funit → freight cost\u002Funit → total fulfillment cost\n\n2. **Structure the model layout**\n   - **Assumptions tab**: all tunable inputs in one place — growth rates, pricing, conversion rates, cost-per-unit figures, hiring timeline\n   - **Driver calculations tab**: intermediate computations linking assumptions to financial outputs\n   - **Output tabs**: P&L, cash flow, and balance sheet (or whichever statements are in scope)\n   - **Scenarios tab**: base, upside, and downside cases toggled by changing assumption sets\n   - Use named ranges or clear cell references; never hardcode numbers inside formulas\n\n3. **Build driver-to-output linkages**\n   - Wire each financial line item to its driver chain — no line item should be a flat manual entry unless truly fixed\n   - For revenue: connect volume drivers × price drivers, accounting for churn\u002Fretention where applicable\n   - For variable costs: tie to the volume driver they scale with (e.g., COGS scales with units sold, hosting costs scale with active users)\n   - For semi-variable costs: model the fixed base plus the variable component (e.g., customer support = base team + 1 FTE per 500 incremental accounts)\n   - For fixed costs: link to timing assumptions (lease start dates, SaaS contract renewals) rather than flat monthly amounts where possible\n   - [VERIFY] Tax rate assumptions, depreciation methods, and capitalization thresholds against the entity's jurisdiction and accounting policy\n\n4. **Run sensitivity and scenario analysis**\n   - Select the 3-5 highest-impact, highest-uncertainty drivers\n   - Build a data table or scenario toggle showing how changes in each driver affect EBITDA, cash runway, or the target metric\n   - Construct at minimum: base case (management plan), downside (stress test on demand or pricing), upside (accelerated growth or margin expansion)\n   - Document what \"downside\" and \"upside\" mean quantitatively (e.g., \"downside = 20% lower conversion rate and 10% higher CAC\")\n\n5. **Validate and stress-test**\n   - Check that the model balances: assets = liabilities + equity on every period; cash flow reconciles to balance sheet cash movement\n   - Compare model outputs against historical actuals — if the model cannot replicate last year's results with last year's inputs, the driver structure is wrong\n   - Test extreme inputs: what happens if a key driver goes to zero or doubles? The model should degrade gracefully, not produce errors or nonsensical outputs\n   - Verify unit economics implied by the model (e.g., LTV:CAC ratio, gross margin %) are within plausible industry ranges [VERIFY]\n\n## Output\n\n- **Driver map diagram**: visual showing the hierarchy from operational inputs → intermediate metrics → financial line items\n- **Assumptions summary**: table of all input assumptions with source\u002Fbasis noted (historical average, management target, industry benchmark)\n- **Linked financial model**: P&L (and optionally balance sheet\u002Fcash flow) with every line item traceable to its driver chain\n- **Scenario comparison table**: base\u002Fupside\u002Fdownside side-by-side with key metrics (revenue, EBITDA, cash balance, burn rate)\n- **Sensitivity matrix**: tornado chart or data table showing which drivers move the target metric most\n\n## Quality Checks\n\n- Every financial line item traces back to at least one operational driver — no orphan rows with hardcoded values\n- Changing any single assumption in the assumptions tab correctly cascades through all dependent calculations\n- Model reproduces historical actuals within 5% tolerance when fed historical driver values\n- Scenario outputs are internally consistent (e.g., headcount in downside case still supports the revenue volume assumed)\n- All external benchmarks, tax rates, and regulatory thresholds are marked [VERIFY] with source noted\n- Assumptions tab clearly distinguishes between data-backed inputs and management estimates\n",{"name":5,"tags":24,"source":27,"license":15,"language":28,"metadata":29,"description":7,"imported_at":39,"source_path":40,"source_repository":41},[25,26],"modeling","financial-planning-and-analysis","https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills","en",{"author":30,"skill_modes":31,"document_types":33,"practice_areas":35},"casemark",[32],"Modeling",[34],"Model",[36,37,38],"FP&A","Management Accounting","Business Intelligence","2026-09-20","skills\u002Ffinance\u002Fbuilding-driver-based-models\u002FSKILL.md","CaseMark\u002Fskills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Ffinance\u002Fbuilding-driver-based-models","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill building-driver-based-models",{"tool":54,"command":55},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill building-driver-based-models",{"tool":57,"command":58},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill building-driver-based-models","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffinance\u002Fbuilding-driver-based-models\u002FSKILL.md",true,[],[63,71,78,85,92,99],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]