startup-financial-modeling▌
wshobson/agents · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Build 3-5 year financial models with revenue projections, cost structures, and scenario planning for startups.
- ›Cohort-based revenue modeling with customer acquisition, retention, and ARPU inputs; supports SaaS, marketplace, e-commerce, and services business models
- ›Comprehensive cost structure breakdown across COGS, S&M, R&D, and G&A with fixed vs. variable categorization and scaling assumptions
- ›Cash flow analysis including monthly burn rate, runway calculation, and fun
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 × 12
Key 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 Expenses
Headcount 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-loaded
Step 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 Cash
Runway Calculation:
If Ending Cash < 0:
Funding Need = Negative Cash Balance
Runway = 0
Else:
Runway = Ending Cash / Average Monthly Burn
Step 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 Dec
Marketplace 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 revenue
E-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-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%)
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
How to use startup-financial-modeling on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add startup-financial-modeling
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches startup-financial-modeling from GitHub repository wshobson/agents and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate startup-financial-modeling. Access the skill through slash commands (e.g., /startup-financial-modeling) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★37 reviews- ★★★★★Sofia White· Dec 16, 2024
startup-financial-modeling reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Mateo Sharma· Dec 12, 2024
We added startup-financial-modeling from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Anika Agarwal· Nov 7, 2024
Registry listing for startup-financial-modeling matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Sakura Kim· Nov 7, 2024
startup-financial-modeling is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Hana Verma· Nov 3, 2024
Keeps context tight: startup-financial-modeling is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Nikhil Garcia· Oct 26, 2024
startup-financial-modeling fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Min Thompson· Oct 26, 2024
Useful defaults in startup-financial-modeling — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Soo Johnson· Oct 22, 2024
startup-financial-modeling has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Oshnikdeep· Sep 13, 2024
Keeps context tight: startup-financial-modeling is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Piyush G· Sep 9, 2024
startup-financial-modeling fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 37