Building an Early-Stage SaaS Financial Model That Stays Useful

Keep it to five tabs, with assumptions on their own page so nothing is hard-coded elsewhere:

• Assumptions: every input in one place, such as leads, conversion rates, average contract value, churn, expansion, salary bands, benefits load and hosting cost per customer.
• Revenue build: beginning ARR, new, expansion, contraction, churn and ending ARR, month by month.
• Headcount: a named roster and open roles with start dates, salaries and burden by department.
• Operating expenses: hosting, software, contractors, marketing programs, legal and accounting, travel and other non-payroll costs.
• Summary and cash: income statement, cash balance, net burn and runway, and the KPIs you report to investors.

When you're ready for a full three-statement version, add a balance sheet and cash flow statement built from the same drivers. A chart of accounts template for SaaS helps you map the model to the accounts your books already use.

The ARR schedule is a roll-forward: beginning ARR plus new plus expansion minus contraction minus churn equals ending ARR. Each line comes from a driver, not a typed number.

For example, say your quarter starts with $600,000 of ARR. Say new customers add $90,000, existing customers expand by $15,000, downgrades remove $5,000 and cancellations remove $25,000. Say ending ARR then comes to $675,000. New ARR itself should come from a driver such as leads times conversion times average contract value, so when you change the sales plan the revenue moves with it.

Model churn as a monthly percentage of beginning ARR, not a fixed dollar amount, so losses grow as the base does. If you have annual contracts, model the timing: churn shows up at renewal, not evenly across the year. And separate bookings, billings and revenue if you invoice annually in advance, since cash arrives when you bill, not when you recognize revenue.

Payroll is usually the largest cost in an early SaaS company, so treat it as a schedule, not a percentage. Follow these steps:

1. List every current employee and contractor with start date, salary and department.
2. Add planned hires with realistic start dates. Recruiting takes months, and a role you plan for January may not start until spring.
3. Apply a burden for payroll taxes and benefits, using the rate your payroll provider quotes.
4. Include ramp for sales roles, since a new rep won't produce at full quota immediately.
5. Tie non-payroll costs to drivers where you can, for example hosting cost per customer or software cost per employee.

Cash burn is operating cash flow after payroll, expenses and any timing differences. Runway is cash divided by burn, but recompute it each month, since burn changes as hiring and revenue change. If you model debt, tie interest to a reference rate: the Federal Reserve's H.15 series put the bank prime rate at 6.75 percent in 2026¹, which is a useful starting point for a line of credit, though your lender's spread and terms will differ.

Run these checks, because investors will:

• Growth. Compare the growth your model implies with benchmarks. SaaS Capital reported a median ARR growth rate of 25 percent for private B2B SaaS companies in 2024², so a plan far above that needs a clear reason, such as sales capacity you've already funded.
• Unit economics. Check that your implied customer acquisition cost and payback are believable, using the approach in unit economics for CAC and LTV.
• Cash. Confirm cash never goes negative in the base case, and see when it would in a downside case.
• Ties. Make sure totals on the summary tab equal the detail tabs.
• Hard-codes. Scan for typed numbers inside formulas.
• Actuals. Compare last quarter's model output to what really happened and note the gaps.

Keep a downside scenario with lower new ARR and higher churn, and show the runway under it.

A spreadsheet works while the model has one owner and a few dozen drivers. Look at a planning tool when several people edit it, you're reforecasting monthly against actuals from your accounting system, or your board wants scenarios on demand. Tools such as Jirav and Cube can pull actuals from accounting software and hold driver-based plans; compare them, along with Mosaic, in Jirav vs Cube vs Mosaic and the B2B SaaS comparison of Cube and Mosaic.

Before you buy, ask in a demo how the tool handles your billing setup, how driver logic is built and who on your team will maintain it. As the team grows, the finance team structure guide covers who should own the model. Whatever you use, keep your assumptions documented so anyone can trace a number back to its source.