How to Build (and Overachieve) an Annual Financial Plan for SaaS Companies

For SaaS companies scaling between $3M–$30M in revenue, the plan should show which growth commitments preserve your cash floor and pass the pre-agreed scenario tests. Annual planning maps how the year could unfold and agrees in advance what would change hiring or spending. Keep the approved budget fixed while updating the outlook against it.

• Connect software revenue and earned transaction fees to direct costs, collections, hiring, and available cash.
• Delay a planned hire if lower payment volume or slower customer launches push forecast cash below the minimum.
• Review actuals and update the forecast monthly, with a deeper review each quarter.

What should an annual plan include?

An annual plan starts with the growth priorities you can fund and the minimum cash balance you will protect. Set those guardrails before asking departments for budgets. Otherwise, each budget request rests on a different assumption about how much the company can spend.

Build one monthly model that connects operating decisions to the income statement, balance sheet, and cash flow. Forecast contracted software revenue separately from usage and earned transaction fees. Sales capacity and implementation timing determine when new customers begin paying, while retention and customer activity shape later revenue. For each stream, subtract its direct costs to see the contribution margin available to support headcount and other spending.

Finally, map earned revenue to cash collections. A customer may process more payments this month without increasing cash on hand at the same pace. Department budgets should fit the resulting cash plan, not set it.

Illustrative company used throughout: A vertical SaaS platform for home services (HVAC, plumbing, and electrical businesses) has a historical run rate of $12 million in annual revenue from subscriptions and payment processing. The plan covers the next quarter and is built from forecast cash receipts, which are not the same as that run rate. Its 40 live customers are forecast to process $90 million this quarter. It starts with $2 million of available cash, excluding customer funds held in settlement. Forecast cash receipts for the quarter are $2.65 million: $1.9 million software, $300,000 usage, and $450,000 net payment fees after processor costs. Planned cash spending is $2.95 million, for a $300,000 net outflow before any new hire. The cash floor is $1.5 million.

What cash floor and burn guardrails should a SaaS company set?

Set a cash floor before departments submit budgets. For the illustrative platform, the $1.5 million floor is a management choice informed by payroll, unavoidable vendor payments, and settlement exposure; the example does not supply a cost breakdown to derive it further. Its $60,000 implementation hire is conditional: planned quarter-end cash of $1.70 million becomes $1.64 million after hiring. A separate burn-multiple limit, if used, must be calculated from actual net operating burn and net new contracted software ARR. SaaS Capital's 2026 survey supplies peer context, not a target for this company's floor.

Test each scenario against available cash after customer funds and reserves. The bear case leaves $1.53 million before the hire and $1.47 million after it. Defer the hire because the $60,000 commitment would breach the $1.5 million floor; do not treat an illustrative $1.65 million cushion as a policy the company adopted.

How do you build the baseline for an annual SaaS plan?

Start with the trajectory your company already has before you add growth targets. Give each input a named owner and due date so you can review one baseline before departments propose new spending.

Build the baseline before setting targets

Start with the latest closed month and project the business you already have across the next 12 months. Use signed contracts and renewal dates for software revenue. Project usage and earned transaction fees separately so a spike in payment volume does not inflate the software run rate.

Carry forward direct costs by revenue stream to estimate contribution margin. Then add current payroll and approved hires at their expected start dates. Check the projection against recent actuals, and mark unusual months rather than treating them as normal. Once you have that baseline, you can see which proposed targets depend on additional sales, faster launches, or new spending.

Illustrative quarterly baseline. The platform begins with $2.00 million in available cash. Planned receipts are $1.90 million from software, $300,000 from usage, and $450,000 from net payment fees; planned spending is $2.95 million, all before the proposed implementation hire. The $90 million of eligible processed volume is a driver of the $450,000 fee line at a 0.50% net take rate, not company revenue. The supplied figures support this quarterly cash bridge; they do not establish monthly direct costs, payroll, or a 12-month forecast.

The bridge is $2.00 million + $2.65 million receipts − $2.95 million spending = $1.70 million. To extend it across 12 months, finance must supply monthly receipts, direct costs, payroll, working-capital changes, and settlement timing rather than repeat this quarter mechanically.

Set a planning calendar with named owners

Set planning deadlines backward from the fiscal-year start, and name an owner for every input. Six weeks before the new year, sales should submit expected contract start dates, while customer success submits renewal assumptions.

Four weeks before the new year, department leads should submit hiring and vendor requests against the cash guardrails already set. Finance can then combine the inputs in one monthly model, return conflicting assumptions to their owners, and circulate a draft for approval before the fiscal year begins. Without owners and handoff dates, one late input can delay the entire plan.

How do you forecast SaaS revenue by stream?

Forecast contracted software, usage, and earned transaction fees separately because each responds to different operating decisions. For software, start with active contracts and renewals, then add new sales based on sales capacity and expected implementation dates. If billing begins at launch, a deal signed in January with an April launch contributes no software revenue before April.

Forecast usage by customer cohort, using observed activity, seasonality, and retention to estimate what existing customers will consume. For transaction fees, project eligible processed volume and apply the fee terms you expect to earn. Customer mix matters because two customers with the same payment volume may generate different fees. Gross payment volume is not company revenue. Only the earned transaction fee counts.

Carry each stream into the base and downside cases. A slower launch changes software revenue timing, while lower payment volume reduces expected fees and may delay a hire if projected cash falls below your guardrail. For the calculation mechanics, see the stream-by-stream forecasting walkthrough.

How do payment flows affect usable cash?

For one illustrative Stripe Connect separate-charges-and-transfers arrangement, the flow has four steps:

1. The payer's charge sits in the processor and platform pending balance.
2. The platform transfers the customer's share to the connected customer account.
3. The connected customer account pays out to the customer.
4. The platform keeps its earned fee, which becomes available operating cash once it settles.

Stripe documents that this charge type initially puts the charge on the platform and requires a separate transfer; Stripe fees, refunds, and chargebacks can debit the platform. The diagram is an example, not a universal payment flow. Exclude funds owed to customers, pending balances, and processor reserves from usable cash. Check the contract to identify who bears refunds, fraud, disputes, negative balances, and reserves. A change in processor pricing, reserves, or access changes both margin and cash availability.

If $40,000 of this quarter's earned fees settle next quarter, this quarter's available cash falls from $1.70 million to $1.66 million before hiring, assuming no other timing offset. The $40,000 becomes a receivable until collected. Do not count it as operating cash or add it to the next period twice.

How do you stress-test an annual plan against downside scenarios?

Test the annual plan against specific misses before you approve conditional spending. If you earn transaction fees, lower payment volume reduces them, while slower launches delay software revenue and collections. Weaker retention can reduce both. Model each change against the cash floor rather than cutting every revenue line by the same percentage.

Illustrative, not a Bridges client result. Start with the platform's $2.0 million available cash, $2.65 million planned receipts, and $2.95 million planned spending. The $60,000 all-in cost of one implementation specialist is excluded from the $2.95 million. Compare a normal quarter with an early spring and a bear case in which seasonal demand, payment mix, launch timing, collections, and reserves move together. Cash figures below are quarter-end balances before that hire unless stated otherwise.

Apply the same cash-floor test if launches slip or retention falls below plan.

The bull case brings spring HVAC work forward. Volume reaches about $97 million, 8% above plan, while two launches move earlier. Fees add $35,000 and earlier software billing adds $40,000; $15,000 of extra support, commissions, and processor costs leaves $60,000 more cash. The bear case starts with a mild winter and weak volume at two large customers. Higher-margin card volume drops faster than bank transfers: $75 million × 0.48% net take rate = $360,000 of fees, $90,000 below plan. A six-week launch slip removes $30,000 of quarter cash, late invoices remove $15,000, and a bank reserve holds back $35,000. Together, those effects cut available cash by $170,000 to $1.53 million. Do not count spending cuts until executed.

Funding overlay, not a fourth operating scenario. If $400,000 is received by June 30, base cash would be $2.10 million before the hire ($2.04 million after), and bear cash $1.93 million before ($1.87 million after). If funding slips past quarter-end, the operating outcomes stay $1.70 million and $1.53 million before hiring. Never release funding-dependent commitments against an unsigned or unreceived amount.

When can a SaaS company afford its next hire or vendor commitment?

Approve a hire or vendor contract now only if its full cost keeps projected cash above your minimum cash floor in the downside case. Put other commitments on hold until the revenue signals in your scenario table support them. If payment volume falls or customer launches slip, delay those commitments rather than following the original hiring date.

Budget the full cost of each hire

Budget a hire at its full monthly cash cost, not the salary on the offer letter. Add payroll taxes, benefits, recruiting and onboarding costs, software, and any commission. Include the manager time needed to train the person, even if that time does not create a new cash expense.

A new salesperson may take months to build a pipeline, and a new implementation hire may start before customer launches generate fees. Put those costs into the months when you expect to pay them, then test the hire against your cash guardrails under both the base and downside cases. If the downside case breaches the cash floor, keep the role conditional rather than treating its start date as approved.

Make vendor commitments respond to the business

New vendor contracts should cost less when revenue or launches fall short of plan. A fixed annual minimum can keep cash outflows high even when revenue falls below forecast. Before signing, ask for a shorter term, a lower minimum, or usage tiers that follow actual activity.

A longer contract may earn a discount, so compare its savings against the cash you would still owe in the downside case. Keep the fixed term only if available cash stays above your agreed floor after those payments. Otherwise, defer the purchase or pay more for flexibility.

Connect the plan to cash runway

Approve a hire or vendor contract only if available cash stays above your minimum floor after the full commitment. Revenue earned and cash collected can arrive in different months; if you earn transaction fees, settlement lag can widen the gap. Forecast fee revenue when earned, then place the related cash in the month you expect to collect it.

In the illustrative bear quarter, the implementation specialist's $60,000 quarter cost takes available cash from $1.53 million to $1.47 million, below the $1.5 million floor. Defer the hire and hold inflexible vendor commitments; do not credit a proposed cost reduction until it is executed. Recheck the commitments when collections and the forecast clear the floor, including any settlement lag.

How should a monthly forecast track against plan scenarios?

Compare each month's actual results with the base and downside cases, then update the forecast for the remaining months. A shortfall in payment volume may point toward the downside case before it appears in cash collections. The revised forecast shows whether the company can still make a conditional hire without breaching its cash guardrail.

Which KPIs should support the plan?

Track KPIs that test the assumptions behind each hiring decision. Sales and finance should own annual recurring revenue, or ARR, as contracted recurring software revenue. Exclude variable usage so a payment-volume spike cannot make the software pipeline look stronger than it is. Customer success and finance should track gross and net revenue retention for each customer cohort. Gross retention excludes expansion, while net retention includes it. A sustained drop in either can trigger a review of planned sales hires.

Finance should track realized take rate, calculated as earned transaction fees divided by eligible processed volume. If volume falls or the take rate slips, finance should update the fee forecast before releasing conditional spending. Finance should also track contribution margin by revenue stream, subtracting direct stream costs from earned revenue. Finally, compare cash available after expected collections and settlement timing with the plan's minimum cash floor before approving a hire.

How often should a SaaS company re-forecast, and what triggers an early update?

Update the rolling forecast after each monthly close, then review its assumptions more deeply each quarter. Compare actual launches, payment volume, earned fees, and cash collections with the base and downside cases before changing the outlook.

Re-forecast sooner when evidence crosses a threshold agreed during planning. For example, a launch slipping by 30 days or payment volume running 10% below plan for two consecutive weeks could trigger an update. A projected breach of the minimum cash floor should trigger one immediately. Use the revised cash outlook to decide whether a conditional hire or vendor commitment can proceed. Keep the approved annual budget fixed so you can still measure how actual decisions and results compare with the original plan.

What does a good annual plan tell you about when to spend?

A good annual plan gives you a rule for deciding when to spend and when to wait. If slower launches or lower earned transaction fees push projected cash below your floor, delay the next hire. Keep the approved budget fixed, and use each monthly forecast to test whether your commitments still fit the cash available.