startup-business-analyst-financial-projections

sickn33/antigravity-awesome-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill startup-business-analyst-financial-projections
0 commentsdiscussion
summary

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.

skill.md

Financial Projections

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.

What This Command Does

This command builds a complete financial model including:

  1. Cohort-based revenue projections
  2. Detailed cost structure (COGS, S&M, R&D, G&A)
  3. Headcount planning by role
  4. Monthly cash flow analysis
  5. Key metrics (CAC, LTV, burn rate, runway)
  6. 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:

  1. New customers acquired
  2. Existing customers retained (apply churn)
  3. Revenue per cohort (customers × ARPU)
  4. Expansion revenue (upsells)

Formula:

MRR (Month N) = Σ across all cohorts:
  (Cohort Size × Retention Rate × ARPU) + Expansion

Project:

  • Monthly detail for Year 1-2
  • Quarterly detail for Year 3
  • Annual for Years 4-5

Step 4: Model Cost Structure

Break down operating expenses:

1. Cost of Goods Sold (COGS)

  • Hosting/infrastructure (% of revenue or fixed)
  • Payment processing (% of revenue)
  • Variable customer support
  • Third-party services

Target gross margin:

  • SaaS: 75-85%
  • Marketplace: 60-70%
  • E-commerce: 40-60%

2. Sales & Marketing (S&M)

  • Sales team compensation
  • Marketing programs
  • Tools and software
  • Target: 40-60% of revenue (early stage)

3. Research & Development (R&D)

  • Engineering team
  • Product management
  • Design
  • Target: 30-40% of revenue

4. General & Administrative (G&A)

  • Executive team
  • Finance, legal, HR
  • Office and facilities
  • Target: 15-25% of revenue

Step 5: Plan Headcount

Create role-by-role hiring plan:

Reference team-composition-analysis skill for:

  • Roles by stage
  • Compensation benchmarks
  • Hiring velocity assumptions

For each role:

  • Title and department
  • Start date (month/quarter)
  • Base salary
  • Fully-loaded cost (salary × 1.3-1.4)
  • Equity grant

Track departmental ratios:

  • Engineering: 40-50% of team
  • Sales & Marketing: 25-35%
  • G&A: 10-15%
  • Product/CS: 10-15%

Step 6: Calculate Cash Flow

Monthly cash flow projection:

Beginning Cash Balance
+ Cash Collected (revenue, consider payment terms)
- Operating Expenses
- CapEx
= Ending Cash Balance

Monthly Burn = Revenue - Expenses (if negative)
Runway = Cash Balance / Monthly Burn Rate

Include Funding Events:

  • Timing of raises
  • Amount raised
  • Use of proceeds
  • Impact on cash balance

Step 7: Compute Key Metrics

Calculate monthly/quarterly:

Unit Economics:

  • CAC (S&M spend / new customers)
  • LTV (ARPU × margin% / churn rate)
  • LTV:CAC ratio (target > 3.0)
  • CAC payback period (target < 18 months)

Efficiency Metrics:

  • Burn multiple (net burn / net new ARR) - target < 2.0
  • Magic number (net new ARR / S&M spend) - target > 0.5
  • Rule of 40 (growth% + margin%) - target > 40%

Cash Metrics:

  • Monthly burn rate
  • Runway in months
  • Cash efficiency

Step 8: Create Three Scenarios

Build conservative, base, and optimistic projections:

Conservative (P10):

  • New customers: -30% vs. base
  • Churn: +20% vs. base
  • Pricing: -15% vs. base
  • CAC: +25% vs. base

Base (P50):

  • Most likely assumptions
  • Primary planning scenario

Optimistic (P90):

  • New customers: +30% vs. base
  • Churn: -20% vs. base
  • Pricing: +15% vs. base
  • CAC: -25% vs. base

Step 9: Generate Financial Model Report

Create comprehensive markdown report with tables:

Section 1: Executive Summary

  • 3-5 year financial snapshot
  • Key metrics at scale
  • Funding requirements

Section 2: Model Assumptions

  • Revenue model and pricing
  • Growth assumptions
  • Cost structure assumptions
  • Headcount plan summary

Section 3: Revenue Projections Monthly/quarterly tables showing:

| Month | New Customers | Total Customers | MRR | ARR | Growth % |
|-------|---------------|-----------------|-----|-----|----------|

Section 4: Cost Breakdown

| Department | Year 1 | Year 2 | Year 3 | % Revenue |
|------------|--------|--------|--------|-----------|
| COGS       | $X     | $Y     | $Z     | XX%       |
| S&M        | $X     | $Y     | $Z     | XX%       |
| R&D        | $X     | $Y     | $Z     | XX%       |
| G&A        | $X     | $Y     | $Z     | XX%       |

Section 5: Headcount Plan

| Department | Current | Year 1 | Year 2 | Year 3 |
|------------|---------|--------|--------|--------|
| Engineering| X       | Y      | Z      | W      |

Section 6: Cash Flow Analysis

| Quarter | Revenue | Expenses | Net Burn | Cash Balance | Runway |
|---------|---------|----------|----------|--------------|--------|

Section 7: Key Metrics

| 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 |

Section 9: Funding Requirements

  • Amount needed
  • Use of proceeds breakdown
  • Milestones to achieve
  • Expected valuation impact

Section 10: Validation

  • Sanity checks performed
  • Benchmark comparisons
  • Risk factors
  • Assumptions to monitor

Step 10: Save Model

Offer to save as markdown file:

  • Suggest filename: financial-projections-YYYY-MM-DD.md
  • 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
how to use startup-business-analyst-financial-projections

How to use startup-business-analyst-financial-projections on Cursor

AI-first code editor with Composer

1

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-business-analyst-financial-projections
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill startup-business-analyst-financial-projections

The skills CLI fetches startup-business-analyst-financial-projections from GitHub repository sickn33/antigravity-awesome-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/startup-business-analyst-financial-projections

Reload or restart Cursor to activate startup-business-analyst-financial-projections. Access the skill through slash commands (e.g., /startup-business-analyst-financial-projections) 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

GET_STARTED →

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. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 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

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.550 reviews
  • Luis Huang· Dec 20, 2024

    We added startup-business-analyst-financial-projections from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Ishan Rahman· Dec 12, 2024

    startup-business-analyst-financial-projections reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Ren Kim· Dec 12, 2024

    Registry listing for startup-business-analyst-financial-projections matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Ren Huang· Dec 8, 2024

    startup-business-analyst-financial-projections has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Camila Farah· Nov 27, 2024

    startup-business-analyst-financial-projections reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Camila Khan· Nov 11, 2024

    startup-business-analyst-financial-projections fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Mei Sethi· Nov 3, 2024

    startup-business-analyst-financial-projections has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Tariq Johnson· Oct 22, 2024

    Useful defaults in startup-business-analyst-financial-projections — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Camila Liu· Oct 18, 2024

    I recommend startup-business-analyst-financial-projections for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Camila Zhang· Oct 2, 2024

    startup-business-analyst-financial-projections is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 50

1 / 5