Create a comprehensive 3-5 year financial model with revenue projections, cost structure, headcount planning, cash flow analysis, and three-scenario modeling (conservative, base, optimistic) for startup financial planning and fundraising.
Use this skill when
Working on financial projections tasks or workflows
Needing guidance, best practices, or checklists for financial projections
Do not use this skill when
The task is unrelated to financial projections
You need a different domain or tool outside this scope
Instructions
Clarify goals, constraints, and required inputs.
Apply relevant best practices and validate outcomes.
Provide actionable steps and verification.
If detailed examples are required, open resources/implementation-playbook.md.
関連 Skill
What This Command Does
This command builds a complete financial model including:
Cohort-based revenue projections
Detailed cost structure (COGS, S&M, R&D, G&A)
Headcount planning by role
Monthly cash flow analysis
Key metrics (CAC, LTV, burn rate, runway)
Three-scenario analysis
Instructions for Claude
When this command is invoked, follow these steps:
Step 1: Gather Model Inputs
Ask the user for essential information:
Business Model:
Revenue model (SaaS, marketplace, transaction, etc.)
Pricing structure (tiers, average price)
Target customer segments
Starting Point:
Current MRR/ARR (if any)
Current customer count
Current team size
Current cash balance
Growth Assumptions:
Expected monthly customer acquisition
Customer retention/churn rate
Average contract value (ACV)
Sales cycle length
Cost Assumptions:
Gross margin or COGS %
S&M budget or CAC target
Current burn rate (if applicable)
Funding:
Planned fundraising (amount, timing)
Pre/post-money valuation
Step 2: Activate startup-financial-modeling Skill
The startup-financial-modeling skill provides frameworks. Reference it for:
Revenue modeling approaches
Cost structure templates
Headcount planning guidance
Scenario analysis methods
Step 3: Build Revenue Model
Use Cohort-Based Approach:
For each month, track:
New customers acquired
Existing customers retained (apply churn)
Revenue per cohort (customers × ARPU)
Expansion revenue (upsells)
Formula:
MRR (Month N) = Σ across all cohorts:
(Cohort Size × Retention Rate × ARPU) + Expansion
| Metric | Year 1 | Year 2 | Year 3 | Target |
|--------|--------|--------|--------|--------|
| CAC | $X | $Y | $Z | <$A |
| LTV | $X | $Y | $Z | >$B |
| Burn Multiple | X | Y | Z | <2.0 |
Section 8: Scenario Analysis
| Scenario | Year 3 ARR | Customers | Burn | Runway |
|----------|------------|-----------|------|--------|
| Conservative | $Xم | Y | $Z | W mo |
| Base | $X | Y | $Z | W mo |
| Optimistic | $X | Y | $Z | W mo |
Include note that user can convert to Excel/Sheets
Provide formulas for key calculations
Financial Model Best Practices
Do:
Use cohort-based revenue model
Include 3 scenarios
Show monthly detail (Year 1-2)
Calculate key metrics
Validate against benchmarks
Document all assumptions
Show cash flow and runway
Include fundraising milestones
Don't:
Be overly optimistic on growth
Underestimate costs
Forget fully-loaded compensation
Ignore cash timing
Skip scenario analysis
Use static headcount
Forget to validate
Integration with Other Commands
Pairs well with:
/market-opportunity - Use SOM for revenue ceiling
/business-case - Include projections in business case
Example Usage
User: /financial-projections
Claude: I'll create a comprehensive financial model for your startup. Let me gather the key inputs.
What's your business model?
→ "B2B SaaS, subscription-based"
Current state?
→ "$50K MRR, 100 customers, 5-person team, $500K cash"
Growth assumptions?
→ "Expect 15% MoM growth, 10% monthly churn, $500 ACV"
[Claude builds complete model with all sections]
Notes
Model building takes 45-90 minutes
Results in comprehensive planning tool
Update monthly to track vs. actuals
Share with investors and board
Use for fundraising decks
Basis for budget and hiring decisions
Limitations
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.