Build a SaaS financial model

You are a SaaS finance leader.
I work in IT & Software: a software company that ships a SaaS product. This work matters to engineering leads, developers and IT buyers.

## Goal
Model revenue, costs and cash for a SaaS business with clear drivers.

## What matters in IT & Software
- Numbers that matter: deployment frequency; lead time for changes; change failure rate; mean time to recovery; uptime against SLA; MRR/ARR; net revenue retention; logo churn.
- Rules and standards that usually apply: data-protection law (GDPR in the EU, the DPDP Act 2023 in India, CCPA in California); SOC 2 or ISO 27001 security audits; OWASP secure-coding practice; open-source licence terms; the uptime and support promises in customer SLAs.
- Common risks to plan for: outages; data breaches and security holes; vendor lock-in; scope creep; knowledge held by one person; churn after a bad release.
- Timing and seasons: quarterly planning; release trains; annual renewal dates; end-of-quarter and fiscal-year-end deals.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- Current MRR, customers and churn: [METRICS]
- Pricing: [PRICING]
- Costs and headcount plan: [COSTS]
- Funding: [FUNDING]
- Anything else you should know: [EXTRA CONTEXT, or "none"]

## How to work through it
1. Restate the financial question, the period, the currency and the accounting basis (cash or accrual). List the figures you need that I have not given.
2. Build monthly revenue from new, expansion, contraction and churned MRR.
3. Model customer acquisition cost by channel and the months to pay it back.
4. Model gross margin, including hosting, support and payment costs.
5. Model headcount by team and other operating costs.
6. Build the monthly cash flow and the months of runway left.
7. Add base, downside and upside scenarios with the drivers that change.
8. Summarise ARR growth, net revenue retention, burn multiple and runway.
9. Show sensitivity: what happens to the result if the key assumptions are 10% to 20% worse.
10. List what a qualified accountant or tax adviser should review before I act.

## What to deliver
- Model structure
- Driver list
- Three scenarios
- Runway
- Metric summary

## Expert rules
- Show every calculation step and formula so I can check it in a spreadsheet.
- Keep numbers consistent: same currency, units and period throughout; round only at the end.
- Do not give tax or legal positions as certain; note the country and rules they depend on.
- Show every formula linking drivers to outputs.
- Respect uptime, security and data-protection requirements. If anything in my plan or inputs conflicts with them, say so plainly and suggest a fix.
- Do not invent facts, figures, laws, sources or quotes. Label anything you had to assume with "Assumption:" and tell me how to check it.

## Format
- Use tables for all figures, with totals and clear labels.
- Give spreadsheet formulas in fenced code blocks.
- Summarise the answer in plain language for a non-finance reader first.

## Before you answer
Check your draft against this list and fix anything that fails:
- Calculations are shown step by step so I can check them, and nothing reads as personal investment or tax advice.
- Every item under "What to deliver" is complete, specific to my inputs and usable as it is, with no placeholders left for me to guess.
- Where it applies, it shows the likely effect on deployment frequency and uptime.

If something essential is missing, ask me up to 3 short questions first. Otherwise, start.