startup-financial-modeling
Skill2 starsChanged 8 months agoMITView on GitHub
This skill should be used when the user asks to "create financial projections", "build a financial model", "forecast revenue", "calculate burn rate", "estimate runway", "model cash flow", or requests 3-5 year financial planning for a startup.
11 other projects use a version of this, 10 of them edited.
Adopted by
Most recently taken up by
- joaoguirunas/team-osedited, first seen Oct 21, 2026
- MaxMiksa/Autonomous-Companyedited, first seen Oct 15, 2026
- xfstudio/skillsedited, first seen Oct 13, 2026
- Samueladewole/claude-skillsedited, first seen Oct 13, 2026
- Tgoldi/claude-skillsword for word, first seen Oct 13, 2026
- MaxMiksa/Auto-Companyedited, first seen Oct 2, 2026
Used with
Projects with it also use community-led-growth, ph-community-outreach and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
nicepkgSkillcommunity-led-growth
Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.
Also in 5 projects that use this
nicepkgSkillph-community-outreach
Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.
Also in 5 projects that use this
mastepanoskiSkillux-audit-rethink
Comprehensive UX audit using IxDF's 7 factors, 5 usability characteristics, and 5 interaction dimensions. Holistic evaluation with redesign proposals based on user-centered design principles.
Also in 5 projects that use this
ncklrsSkillseo-content-strategist
Expert SEO content strategy for SaaS and B2B sites. Use when doing keyword research, planning content clusters, creating pillar pages, optimizing on-page SEO, fixing technical SEO issues, building links, refreshing content, implementing programmatic SEO, mapping search intent, optimizing for SERP features, or measuring content performance. Use for SEO audits, content gap analysis, and organic growth strategy.
Also in 5 projects that use this
hieutrtrSkillcode-review-security
Security-focused code review checklist and automated scanning patterns. Use when reviewing pull requests for security issues, auditing authentication/authorization code, checking for OWASP Top 10 vulnerabilities, or validating input sanitization. Covers SQL injection prevention, XSS protection, CSRF tokens, authentication flow review, secrets detection, dependency vulnerability scanning, and secure coding patterns for Python (FastAPI) and React. Does NOT cover deployment security (use docker-best-practices) or incident handling (use incident-response).
Also in 5 projects that use this
YYH211Skilldeep-reading-analyst
Comprehensive framework for deep analysis of articles, papers, and long-form content using 10+ thinking models (SCQA, 5W2H, critical thinking, inversion, mental models, first principles, systems thinking, six thinking hats). Use when users want to: (1) deeply understand complex articles/content, (2) analyze arguments and identify logical flaws, (3) extract actionable insights from reading materials, (4) create study notes or learning summaries, (5) compare multiple sources, (6) transform knowledge into practical applications, or (7) apply specific thinking frameworks. Triggered by phrases like 'analyze this article,' 'help me understand,' 'deep dive into,' 'extract insights from,' 'use [framework name],' or when users provide URLs/long-form content for analysis.
Also in 5 projects that use this
- +6 more from nicepkg
Other versions11 projects use a version of this.
Word for word · 1
- Tgoldi/claude-skills★ 0100% same
Edited · 10
- MaxMiksa/Auto-Company★ 3.2k92% same
- MaxMiksa/Autonomous-Company★ 3.2k92% same
- nicepkg/auto-company★ 18893% same
- NikitaDmitrieff/auto-co-meta★ 4393% same
- xfstudio/skills★ 988% same
- joaoguirunas/team-os★ 688% same
- ai4brands-design/claude-skills★ 288% same
- ZeroTokenClaw/agents-skills★ 193% same
- DrifterXXX/auto-company★ 093% same
- Samueladewole/claude-skills★ 093% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository239 other files it gives its agents.
- claude-code-docs/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- claude-code-docs/llms.txtllms.txt
- agent-native-architectureSkill
- claude-apiSkill
- embedding-strategiesSkill
- fal-ai-mediaSkill
- gemini-imagegenSkill
- hybrid-search-implementationSkill
- langchain-architectureSkill
- llm-evaluationSkill
- ml-pipeline-workflowSkill
- prompt-engineering-patternsSkill
- rag-implementationSkill
- similarity-search-patternsSkill
- vector-index-tuningSkill
- api-design-principlesSkill
- api-designSkill
- architecture-patternsSkill
- cqrs-implementationSkill
- event-store-designSkill
- fastapi-templatesSkill
- microservices-patternsSkill
- openapi-spec-generationSkill
- projection-patternsSkill
- saga-orchestrationSkill
- api-conventionsSkill
- andrew-kane-gem-writerSkill
- angular-migrationSkill
- auth-implementation-patternsSkill
- backend-patternsSkill
- bazel-build-optimizationSkill
- coding-standardsSkill
- database-migrationSkill
- debugging-strategiesSkill
- dependency-upgradeSkill
- dhh-rails-styleSkill
- dotnet-backend-patternsSkill
- dspy-rubySkill
- error-handling-patternsSkill
- monorepo-managementSkill
- nodejs-backend-patternsSkill
- nx-workspace-patternsSkill
- react-modernizationSkill
- temporal-python-testingSkill
- turborepo-cachingSkill
- workflow-orchestration-patternsSkill
- defi-protocol-templatesSkill
- nft-standardsSkill
- solidity-securitySkill
- web3-testingSkill
- backtesting-frameworksSkill
- billing-automationSkill
- competitive-landscapeSkill
- data-storytellingSkill
- employment-contract-templatesSkill
- investor-materialsSkill
- investor-outreachSkill
- kpi-dashboard-designSkill
- market-sizing-analysisSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. 6 are common, 0 are distinctive, and 0 are very specific to this project.
6
Common
Most of the 10 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 169
Use cohort-based methodology for accuracy.
- Common: line 277
Create three scenarios with different assumptions.
- Common: line 411
Ensure runway to achieve next milestone + 6 months buffer.
- Common: line 418
Use conservative customer acquisition assumptions
- Common: line 423
Add 20% buffer to expense estimates
- Common: line 442
Always model conservative case
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Startup Financial Modeling
Build comprehensive 3-5 year financial models with revenue projections, cost structures, cash flow analysis, and scenario planning for early-stage startups.
Overview
Financial modeling provides the quantitative foundation for startup strategy, fundraising, and operational planning. Create realistic projections using cohort-based revenue modeling, detailed cost structures, and scenario analysis to support decision-making and investor presentations.
Core Components
Revenue Model
Cohort-Based Projections: Build revenue from customer acquisition and retention by cohort.
Formula:
MRR = Σ (Cohort Size × Retention Rate × ARPU)
ARR = MRR × 12Key Inputs:
- Monthly new customer acquisitions
- Customer retention rates by month
- Average revenue per user (ARPU)
- Pricing and packaging assumptions
- Expansion revenue (upsells, cross-sells)
Cost Structure
Operating Expenses Categories:
- Cost of Goods Sold (COGS)
- Hosting and infrastructure
- Payment processing fees
- Customer support (variable portion)
- Third-party services per customer
- Sales & Marketing (S&M)
- Customer acquisition cost (CAC)
- Marketing programs and advertising
- Sales team compensation
- Marketing tools and software
- Research & Development (R&D)
- Engineering team compensation
- Product management
- Design and UX
- Development tools and infrastructure
- General & Administrative (G&A)
- Executive team
- Finance, legal, HR
- Office and facilities
- Insurance and compliance
Cash Flow Analysis
Components:
- Beginning cash balance
- Cash inflows (revenue, fundraising)
- Cash outflows (operating expenses, CapEx)
- Ending cash balance
- Monthly burn rate
- Runway (months of cash remaining)
Formula:
Runway = Current Cash Balance / Monthly Burn Rate
Monthly Burn = Monthly Revenue - Monthly ExpensesHeadcount Planning
Role-Based Hiring Plan: Track headcount by department and role.
Key Metrics:
- Fully-loaded cost per employee
- Revenue per employee
- Headcount by department (% of total)
Typical Ratios (Early-Stage SaaS):
- Engineering: 40-50%
- Sales & Marketing: 25-35%
- G&A: 10-15%
- Customer Success: 5-10%
Financial Model Structure
Three-Scenario Framework
Conservative Scenario (P10):
- Slower customer acquisition
- Lower pricing or conversion
- Higher churn rates
- Extended sales cycles
- Used for cash management
Base Scenario (P50):
- Most likely outcomes
- Realistic assumptions
- Primary planning scenario
- Used for board reporting
Optimistic Scenario (P90):
- Faster growth
- Better unit economics
- Lower churn
- Used for upside planning
Time Horizon
Detailed Projections: 3 Years
- Monthly detail for Year 1
- Monthly detail for Year 2
- Quarterly detail for Year 3
High-Level Projections: Years 4-5
- Annual projections
- Key metrics only
- Support long-term planning
Step-by-Step Process
Step 1: Define Business Model
Clarify revenue model and pricing.
SaaS Model:
- Subscription pricing tiers
- Annual vs. monthly contracts
- Free trial or freemium approach
- Expansion revenue strategy
Marketplace Model:
- GMV projections
- Take rate (% of transactions)
- Buyer and seller economics
- Transaction frequency
Transactional Model:
- Transaction volume
- Revenue per transaction
- Frequency and seasonality
Step 2: Build Revenue Projections
Use cohort-based methodology for accuracy.
Monthly Customer Acquisition: Define new customers acquired each month.
Retention Curve: Model customer retention over time.
Typical SaaS Retention:
- Month 1: 100%
- Month 3: 90%
- Month 6: 85%
- Month 12: 75%
- Month 24: 70%
Revenue Calculation: For each cohort, calculate retained customers × ARPU for each month.
Step 3: Model Cost Structure
Break down costs by category and behavior.
Fixed vs. Variable:
- Fixed: Salaries, software, rent
- Variable: Hosting, payment processing, support
Scaling Assumptions:
- COGS as % of revenue
- S&M as % of revenue (CAC payback)
- R&D growth rate
- G&A as % of total expenses
Step 4: Create Hiring Plan
Model headcount growth by role and department.
Inputs:
- Starting headcount
- Hiring velocity by role
- Fully-loaded compensation by role
- Benefits and taxes (typically 1.3-1.4x salary)
Example:
Engineer: $150K salary × 1.35 = $202K fully-loaded
Sales Rep: $100K OTE × 1.30 = $130K fully-loadedStep 5: Project Cash Flow
Calculate monthly cash position and runway.
Monthly Cash Flow:
Beginning Cash
+ Revenue Collected (consider payment terms)
- Operating Expenses Paid
- CapEx
= Ending CashRunway Calculation:
If Ending Cash < 0:
Funding Need = Negative Cash Balance
Runway = 0
Else:
Runway = Ending Cash / Average Monthly BurnStep 6: Calculate Key Metrics
Track metrics that matter for stage.
Revenue Metrics:
- MRR / ARR
- Growth rate (MoM, YoY)
- Revenue by segment or cohort
Unit Economics:
- CAC (Customer Acquisition Cost)
- LTV (Lifetime Value)
- CAC Payback Period
- LTV / CAC Ratio
Efficiency Metrics:
- Burn multiple (Net Burn / Net New ARR)
- Magic number (Net New ARR / S&M Spend)
- Rule of 40 (Growth % + Profit Margin %)
Cash Metrics:
- Monthly burn rate
- Runway (months)
- Cash efficiency
Step 7: Scenario Analysis
Create three scenarios with different assumptions.
Variable Assumptions:
- Customer acquisition rate (±30%)
- Churn rate (±20%)
- Average contract value (±15%)
- CAC (±25%)
Fixed Assumptions:
- Pricing structure
- Core operating expenses
- Hiring plan (adjust timing, not roles)
Business Model Templates
SaaS Financial Model
Revenue Drivers:
- New MRR (customers × ARPU)
- Expansion MRR (upsells)
- Contraction MRR (downgrades)
- Churned MRR (lost customers)
Key Ratios:
- Gross margin: 75-85%
- S&M as % revenue: 40-60% (early stage)
- CAC payback: < 12 months
- Net retention: 100-120%
Example Projection:
Year 1: $500K ARR, 50 customers, $100K MRR by Dec
Year 2: $2.5M ARR, 200 customers, $208K MRR by Dec
Year 3: $8M ARR, 600 customers, $667K MRR by DecMarketplace Financial Model
Revenue Drivers:
- GMV (Gross Merchandise Value)
- Take rate (% of GMV)
- Net revenue = GMV × Take rate
Key Ratios:
- Take rate: 10-30% depending on category
- CAC for buyers vs. sellers
- Contribution margin: 60-70%
Example Projection:
Year 1: $5M GMV, 15% take rate = $750K revenue
Year 2: $20M GMV, 15% take rate = $3M revenue
Year 3: $60M GMV, 15% take rate = $9M revenueE-Commerce Financial Model
Revenue Drivers:
- Traffic (visitors)
- Conversion rate
- Average order value (AOV)
- Purchase frequency
Key Ratios:
- Gross margin: 40-60%
- Contribution margin: 20-35%
- CAC payback: 3-6 months
Services / Agency Financial Model
Revenue Drivers:
- Billable hours or projects
- Hourly rate or project fee
- Utilization rate
- Team capacity
Key Ratios:
- Gross margin: 50-70%
- Utilization: 70-85%
- Revenue per employee
Fundraising Integration
Funding Scenario Modeling
Pre-Money Valuation: Based on metrics and comparables.
Dilution:
Post-Money = Pre-Money + Investment
Dilution % = Investment / Post-MoneyUse of Funds: Allocate funding to extend runway and achieve milestones.
Example:
Raise: $5M at $20M pre-money
Post-Money: $25M
Dilution: 20%
Use of Funds:
- Product Development: $2M (40%)
- Sales & Marketing: $2M (40%)
- G&A and Operations: $0.5M (10%)
- Working Capital: $0.5M (10%)Milestone-Based Planning
Identify Key Milestones:
- Product launch
- First $1M ARR
- Break-even on CAC
- Series A fundraise
Funding Amount: Ensure runway to achieve next milestone + 6 months buffer.
Common Pitfalls
Pitfall 1: Overly Optimistic Revenue
- New startups rarely hit aggressive projections
- Use conservative customer acquisition assumptions
- Model realistic churn rates
Pitfall 2: Underestimating Costs
- Add 20% buffer to expense estimates
- Include fully-loaded compensation
- Account for software and tools
Pitfall 3: Ignoring Cash Flow Timing
- Revenue ≠ cash (payment terms)
- Expenses paid before revenue collected
- Model cash conversion carefully
Pitfall 4: Static Headcount
- Hiring takes time (3-6 months to fill roles)
- Ramp time for productivity (3-6 months)
- Account for attrition (10-15% annually)
Pitfall 5: Not Scenario Planning
- Single scenario is never accurate
- Always model conservative case
- Plan for what you'll do if base case fails
Model Validation
Sanity Checks:
- Revenue growth rate is achievable (3x in Year 2, 2x in Year 3)
- Unit economics are realistic (LTV/CAC > 3, payback < 18 months)
- Burn multiple is reasonable (< 2.0 in Year 2-3)
- Headcount scales with revenue (revenue per employee growing)
- Gross margin is appropriate for business model
- S&M spending aligns with CAC and growth targets
Benchmark Against Peers: Compare key metrics to similar companies at similar stage.
Investor Feedback: Share model with advisors or investors for feedback on assumptions.
Quick Start
To create a startup financial model:
- Define business model - Revenue drivers and pricing
- Project revenue - Cohort-based with retention
- Model costs - COGS, S&M, R&D, G&A by month
- Plan headcount - Hiring by role and department
- Calculate cash flow - Revenue - expenses = burn/runway
- Compute metrics - CAC, LTV, burn multiple, runway
- Create scenarios - Conservative, base, optimistic
- Validate assumptions - Sanity check and benchmark
- Integrate fundraising - Model funding rounds and milestones
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

