skills/wshobson/startup-financial-modeling/SKILL.md
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.
npx skillsauth add aiskillstore/marketplace startup-financial-modelingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Build comprehensive 3-5 year financial models with revenue projections, cost structures, cash flow analysis, and scenario planning for early-stage startups.
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.
Cohort-Based Projections: Build revenue from customer acquisition and retention by cohort.
Formula:
MRR = Σ (Cohort Size × Retention Rate × ARPU)
ARR = MRR × 12
Key Inputs:
Operating Expenses Categories:
Cost of Goods Sold (COGS)
Sales & Marketing (S&M)
Research & Development (R&D)
General & Administrative (G&A)
Components:
Formula:
Runway = Current Cash Balance / Monthly Burn Rate
Monthly Burn = Monthly Revenue - Monthly Expenses
Role-Based Hiring Plan: Track headcount by department and role.
Key Metrics:
Typical Ratios (Early-Stage SaaS):
Conservative Scenario (P10):
Base Scenario (P50):
Optimistic Scenario (P90):
Detailed Projections: 3 Years
High-Level Projections: Years 4-5
Clarify revenue model and pricing.
SaaS Model:
Marketplace Model:
Transactional Model:
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:
Revenue Calculation: For each cohort, calculate retained customers × ARPU for each month.
Break down costs by category and behavior.
Fixed vs. Variable:
Scaling Assumptions:
Model headcount growth by role and department.
Inputs:
Example:
Engineer: $150K salary × 1.35 = $202K fully-loaded
Sales Rep: $100K OTE × 1.30 = $130K fully-loaded
Calculate monthly cash position and runway.
Monthly Cash Flow:
Beginning Cash
+ Revenue Collected (consider payment terms)
- Operating Expenses Paid
- CapEx
= Ending Cash
Runway Calculation:
If Ending Cash < 0:
Funding Need = Negative Cash Balance
Runway = 0
Else:
Runway = Ending Cash / Average Monthly Burn
Track metrics that matter for stage.
Revenue Metrics:
Unit Economics:
Efficiency Metrics:
Cash Metrics:
Create three scenarios with different assumptions.
Variable Assumptions:
Fixed Assumptions:
Revenue Drivers:
Key Ratios:
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 Dec
Revenue Drivers:
Key Ratios:
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 revenue
Revenue Drivers:
Key Ratios:
Revenue Drivers:
Key Ratios:
Pre-Money Valuation: Based on metrics and comparables.
Dilution:
Post-Money = Pre-Money + Investment
Dilution % = Investment / Post-Money
Use 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%)
Identify Key Milestones:
Funding Amount: Ensure runway to achieve next milestone + 6 months buffer.
Pitfall 1: Overly Optimistic Revenue
Pitfall 2: Underestimating Costs
Pitfall 3: Ignoring Cash Flow Timing
Pitfall 4: Static Headcount
Pitfall 5: Not Scenario Planning
Sanity Checks:
Benchmark Against Peers: Compare key metrics to similar companies at similar stage.
Investor Feedback: Share model with advisors or investors for feedback on assumptions.
For detailed model structures and advanced techniques:
references/model-templates.md - Complete financial model templates by business modelreferences/unit-economics.md - Deep dive on CAC, LTV, payback, and efficiency metricsreferences/fundraising-scenarios.md - Modeling funding rounds and dilutionWorking financial models with formulas:
examples/saas-financial-model.md - Complete 3-year SaaS model with cohort analysisexamples/marketplace-model.md - Marketplace GMV and take rate projectionsexamples/scenario-analysis.md - Three-scenario framework with sensitivitiesTo create a startup financial model:
For complete templates and formulas, reference the references/ and examples/ files.
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.