project finance model for fintech law firm

You are a senior FP&A analyst with extensive technical knowledge in valuation. You write clear, precise, and implementation-ready content.

Build a comprehensive project finance model for a fintech law firm.

**Purpose:** Financial analysis and decision-making
**Audience:** solopreneurs
**Complexity level:** Intermediate to advanced

## Model Overview
- Purpose and use cases for this project finance model
- Key assumptions and inputs required
- Output metrics and decision criteria
- Model limitations and caveats

## Input Assumptions
Define and justify each key assumption:
- Revenue assumptions (growth rate, pricing, volume)
- Cost structure (fixed vs. variable, COGS, operating expenses)
- Working capital assumptions (DSO, DPO, DIO)
- Capital expenditure projections
- Tax rate and depreciation schedule
- Discount rate / WACC calculation

## Model Structure
### Tab 1: Assumptions & Inputs
- Input cells clearly formatted (blue font, yellow background convention)
- Toggle switches for scenario selection
- Data validation on key inputs

### Tab 2: project finance model Core
- Step-by-step calculation flow
- All formulas written out (Excel/Sheets compatible)
- Error checking formulas
- Circular reference handling (if applicable)

### Tab 3: Output Dashboard
- Key metrics summary: revenue growth and supporting ratios
- Sensitivity tables (2-variable data tables)
- Charts: revenue waterfall, margin trends, returns analysis
- Executive summary section

## Scenario Analysis
- Base case assumptions and results
- Bull case (20% upside) assumptions and results
- Bear case (20% downside) assumptions and results
- Breakeven analysis

## Sensitivity Analysis
Create 2-variable sensitivity tables for:
- Revenue growth vs. operating margin → revenue growth
- Discount rate vs. terminal growth rate → valuation
- Price vs. volume → revenue impact

## Quality Checks
- Balance sheet balances (Assets = Liabilities + Equity)
- Cash flow reconciliation
- Growth rate reasonableness tests
- Ratio trend analysis for anomalies

Present as numbered steps. Each step should have: a clear action title, detailed instructions, expected outcome, and common pitfalls to avoid.
- Use precise technical terminology appropriate for the audience
- Include code examples, configurations, or specifications where relevant
- Document assumptions, prerequisites, and dependencies
- Provide error handling and edge case considerations