Sign in

Blog · Forecast and pipeline · Software

SaaS financial projections: revenue, costs and cash

Build SaaS financial projections from customer movements, pricing, delivery costs and hiring assumptions. Follow a monthly spreadsheet example, reconcile cash and receivables, and compare the projection with actual performance.

The short answerSaaS financial projections translate customer counts, churn, pricing, delivery costs, hiring and payment timing into future revenue, profit and cash. Start from a reconciled actual month, document each assumption, and roll customer and cash balances forward monthly. Keep recognized revenue separate from billings and collections, then compare actual results with the saved projection.

SaaS financial projections turn customer growth, churn, pricing and hiring assumptions into revenue, costs and cash. Start from a closed actual month, project each driver explicitly, and keep collections separate from revenue. Save the projection before comparing it with actual results.

Start with the exports and assumptions

Bring a customer activity export, revenue report, payroll or hiring schedule, operating expense ledger, receivables aging and bank-reconciled cash balance. Use a consistent customer identifier and effective dates. The wider SaaS financial management review covers how these schedules support recurring operating decisions.

Build monthly columns with assumptions separated from calculated rows. The SBA's business planning guidance calls for projected income statements, balance sheets, cash flow statements and capital budgets, with more detail in the initial year. A monthly operating schedule makes the links between them visible.

This illustrative US SaaS business has one monthly subscription price, no expansion revenue, no annual prepayments and no bad debts. January opens with 1,000 customers, receivables of $10,000 and cash of $500,000. December recognized revenue was $200,000. All figures below are USD unless labeled otherwise.

Roll customers into recognized revenue

Assume monthly customer churn of 2.0%, a monthly price of $200 and evenly timed customer movements. Customer losses are rounded to whole customers before the ending balance is calculated. In Excel, the ROUND function uses zero decimal places to round to an integer.

Spreadsheet row Driver or result January February March
2 Beginning customers 1,000 1,080 1,178
3 Churn assumption 2.0% 2.0% 2.0%
4 Customers lost 20 22 24
5 New customers 100 120 140
6 Ending customers 1,080 1,178 1,294
7 Average active customers 1,040 1,129 1,236
8 Monthly revenue per customer (USD) 200 200 200
9 Recognized revenue (USD) 208,000 225,800 247,200

With January in column B, enter these formulas and copy across. February's beginning customers use January's ending balance.

B4 =ROUND(B2*B3,0)
B6 =B2-B4+B5
B7 =(B2+B6)/2
B9 =B7*B8
C2 =B6

Average customers approximate service delivered during each month. Use effective service dates when customer movements are uneven. An ending customer count multiplied by price would overstate revenue when many additions arrive late.

Add delivery costs and hiring

Assume delivery costs equal 20.0% of revenue, with other operating expenses of $40,000 monthly. Paid headcount is 10, 11 and 12, and fully loaded monthly payroll is $10,000 per employee. Each hire starts on the first day of the applicable month; all expenses are paid in the same month. The gross profit margin guide explains the delivery-cost boundary.

Spreadsheet row Income statement line (USD) January February March
10 Delivery costs 41,600 45,160 49,440
11 Payroll 100,000 110,000 120,000
12 Other operating expenses 40,000 40,000 40,000
13 Operating income 26,400 30,640 37,760
B10 =B9*20%
B11 =10*10000
C11 =11*10000
D11 =12*10000
B13 =B9-SUM(B10:B12)

Keep hiring dates and compensation assumptions in a separate input schedule in a larger workbook. Include employer taxes and benefits in the loaded cost. Add interest, taxes and noncash expenses when the business has them; this simplified illustration assumes none.

Build collections and prove cash

Assume 95.0% of each month's revenue is collected that month and the remaining 5.0% the next month. Capital spending is $10,000 monthly, with no financing flows. This timing assumption fits the example's monthly billing; it does not fit annual prepayments. The SEC's revenue guidance specifically identifies accelerating ratable revenue to the billing date as a potentially misleading non-GAAP adjustment.

Spreadsheet row Cash or receivables line (USD) January February March
14 Collections 207,600 224,910 246,130
15 Operating payments 181,600 195,160 209,440
16 Operating cash flow 26,000 29,750 36,690
17 Capital spending 10,000 10,000 10,000
18 Beginning cash 500,000 516,000 535,750
19 Ending cash 516,000 535,750 562,440
20 Ending receivables 10,400 11,290 12,360
B14 =B9*95%+200000*5%
C14 =C9*95%+B9*5%
B15 =SUM(B10:B12)
B16 =B14-B15
B19 =B18+B16-B17
C18 =B19
B20 =10000+B9-B14
C20 =B20+C9-C14

January's receivables check is 10,000 + 208,000 - 207,600 = 10,400. Its cash check is 500,000 + 26,000 - 10,000 = 516,000. Repeat both checks monthly and tie the starting balances to the closed accounts.

Compare the saved projection with actuals

For an illustrative January actual, new customers are 80 and losses are 30, giving 1,050 ending and 1,025 average customers. Price remains $200; delivery cost becomes 21.0% of revenue, payroll remains $100,000 and other operating expenses become $42,000.

January result (USD) Projection Actual Actual minus projection
Revenue 208,000 205,000 -3,000
Delivery costs 41,600 43,050 1,450
Payroll 100,000 100,000 0
Other operating expenses 40,000 42,000 2,000
Operating income 26,400 19,950 -6,450

Use =Actual-Projection for each variance. The profit check is -3,000 - 1,450 - 0 - 2,000 = -6,450. Review complete periods; the month-to-date reporting guide explains comparisons before close.

Where it goes wrong

  • Churn uses the wrong base. Apply customer churn to beginning customers and distinguish it from revenue churn.
  • Billings become revenue. Annual contracts need separate recognition and collection schedules.
  • Hiring is undated. A start date changes both payroll and cash timing.
  • Revisions erase the baseline. Preserve the original projection and label each updated version.

Covirage is not affiliated with Microsoft.

Compare your SaaS projection file in Covirage

Bring your prepared projections and actuals workbook or Google Sheet; Covirage maps the columns, and its tools compute and check the comparisons. The external AI model explains the variances with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data.

See Covirage for SaaS teams for the industry context.

Questions people ask

What should SaaS financial projections include?

Include customer movements, revenue assumptions, delivery costs, payroll, other operating expenses, capital spending and cash collection timing. Carry forward receivables and cash balances. An operating review also needs an actuals column and a saved forecast version so revisions do not erase the original comparison.

Should SaaS revenue use beginning or ending customer counts?

Use the customer exposure that matches when service is delivered. An average of beginning and ending customers is a simplified approximation when additions and losses occur evenly. If changes cluster near month-end, calculate revenue from actual service dates or a more detailed cohort schedule.

How do annual prepayments affect SaaS projections?

Annual prepayments can bring cash in before the related service revenue is recognized. Build separate billing, collection and revenue recognition schedules. Carry the resulting contract liability forward and reconcile it; applying the same percentage collection assumption to revenue will not describe that billing pattern.

How often should a SaaS finance team update projections?

Use a schedule aligned with the operating review, commonly after each monthly close, and revise sooner when a material assumption changes. Keep the prior version available. Updating assumptions should produce a new outlook while preserving the evidence needed to explain the original forecast variance.