Why Your SaaS Team Needs a Budget - And a CFO to Build It

Most SaaS founders I work with did not have a proper budget until they were forced into one. Usually that forcing function is a board, an investor, or a cash scare. By then they have already wasted months of runway on hiring decisions made by gut feel and cost commitments nobody tracked.

A budget is not a spreadsheet exercise. It is the translation of your growth strategy into financial terms. It tells you how many people you can hire, when you can hire them, and what revenue you need to justify each head. Without one, you are flying blind.

Why most SaaS companies skip budgeting until Series A

Pre-seed and seed-stage founders tend to treat budgeting as a corporate exercise that does not apply to them. The logic goes: "We are moving fast, things change every month, a budget would be out of date in weeks."

That reasoning is wrong. A budget is not a rigid plan you cannot deviate from. It is a baseline you measure against. Without a baseline, you cannot answer basic questions: Are we spending more than planned? Is our hiring ahead of or behind schedule? Can we afford to bring forward that engineering hire by two months?

The companies that skip budgeting until Series A typically discover the same problems:

• Uncontrolled burn rate. Nobody noticed that monthly operating costs crept up by 15% over six months because nobody was comparing actual spend against a target.
• Hiring without revenue correlation. Team leaders hired when they felt they needed people, not when the revenue justified it.
• Surprise cash shortfalls. The founder checks the bank balance in month 8 and realises they have four months of runway left instead of seven.

A 12-month budget takes two to three weeks to build properly. That is a small investment to avoid running out of cash.

Top-down vs bottom-up: SaaS companies should use bottom-up

There are two approaches to budgeting:

Top-down starts with a revenue target and allocates costs as a percentage. "We want to hit £2M ARR, so we will spend 40% on sales and marketing, 30% on engineering, 20% on G&A, and keep 10% as margin." This approach is fast but dangerously imprecise. It tells you nothing about when costs land, which months are tight, or whether the hiring plan is realistic.

Bottom-up starts with the individual cost items - every person you plan to hire, every tool you plan to buy, every contract you plan to sign - and builds up to a total. This is the approach a fractional CFO uses because it produces a budget you can actually track against.

A bottom-up budget for a 20-person SaaS company typically has 60 to 80 line items. Each one has a start month, a monthly cost, and a category. When you roll those up, you get a month-by-month cost profile that shows exactly when your burn rate increases and by how much.

The budget timeline for SaaS companies

For companies with a January fiscal year-end, the budget process should start in October. For April year-end (common for UK companies), start in January. The timeline looks like this:

• Weeks 1-2: CFO reviews the prior year’s actuals, identifies trends, and prepares a budget template with baseline costs already populated.
• Week 3: CFO holds one-to-one calls with each team leader (engineering, sales, product, operations) to understand their hiring plans and cost requirements for the next 12 months.
• Week 4: CFO builds the first draft, cross-referencing hiring plans against revenue targets and cash runway.
• Week 5: Review with the founder or CEO. Challenge assumptions. Stress-test scenarios: what if revenue grows at 80% of target? What if a key hire is delayed by three months?
• Week 6: Final budget approved. Monthly tracking begins.

This process works whether you have 5 employees or 50. The difference is the number of team leader conversations, not the framework.

Revenue budget: linking MRR growth to the hiring plan

The revenue budget must start from your MRR schedule, not from an aspirational ARR target. Take your current MRR, apply realistic growth assumptions (new logos, expansion, churn), and build a month-by-month revenue forecast.

The critical link is between revenue and hiring. Every sales hire should have an expected ramp time and quota. If you are hiring a sales rep in March with a three-month ramp and a £30K monthly quota, your budget should not show incremental revenue from that hire until June. And even then, most reps do not hit full quota in their first producing month.

For engineering and product hires, the link to revenue is indirect but still real. A product engineer hired in April should be contributing to features that drive retention or expansion by Q3. If you cannot articulate that link, question whether the hire is needed this year.

How a fractional CFO runs the budget process

When I build a budget with a client, the most valuable part is not the spreadsheet. It is the conversations with team leaders.

A fractional CFO sits down (or gets on a call) with each department head and asks specific questions:

Hiring and growth expectations. What positions are you hiring for in the next 12 months? What are the salary expectations? When do you need them to start, and what is the latest they could start without impacting delivery? This last question is critical - it gives you flexibility in the budget without the team leader feeling their plans are being cut.

Budget-to-hire correlation. For an accurate budget, the CFO must understand the link between each hire and the company’s growth targets. The right question is: "If we land 10 new customers this quarter instead of 15, does that change your hiring plan?" This forces team leaders to think about their resource needs as a function of the business, not as a wish list.

AI and automation. This is now a standard topic in budget discussions. A CFO needs to understand how each department is using AI tools and what the cost implications are. Some teams are spending £200 to £300 per person per month on AI subscriptions. That is £2,400 to £3,600 per employee per year - material enough to budget for explicitly. It may also mean you can defer a hire if AI tools increase individual productivity.

Non-staff costs. Beyond salaries, there are software subscriptions, contractor costs, training budgets, travel, events, and equipment. The best way to surface these is to pull the last 12 months of actual costs from your accounting system (Xero, QuickBooks), categorise them by department, and review them with each team leader. Invariably, you will find tools the company is paying for but nobody is using, and costs that were never budgeted because nobody asked.

Cost categories SaaS companies commonly miss

Every budget I review has gaps. The most common ones:

• Employer’s National Insurance. In the UK, employer’s NI is currently 15% on earnings above the secondary threshold. A £60,000 salary costs the company roughly £68,700 once you add employer’s NI and auto-enrolment pension contributions. Budget for the fully loaded cost, not the base salary.
• Recruitment costs. Agency fees are typically 15-20% of first-year salary. For a £60,000 hire, that is £9,000 to £12,000. If you are hiring four people, that is up to £48,000 in recruitment costs alone.
• VAT cash flow impact. If you are VAT-registered and billing annual contracts upfront, you collect 20% VAT on the full invoice amount but only pay it to HMRC quarterly. That creates a temporary cash benefit that reverses when the VAT return is due. Budget for the quarterly VAT payment, not just the annual net position.
• Corporation tax instalments. Companies with taxable profits above £1.5M must pay corporation tax in quarterly instalments starting in month 7 of the accounting period. Even below that threshold, your tax bill is due nine months and one day after your year-end. Budget for it.
• Software cost creep. SaaS companies tend to accumulate subscriptions. What starts as a £200/month tool becomes a £500/month tool when you add seats. Audit your subscriptions quarterly.

Variance analysis: tracking actual vs budget monthly

A budget without monthly tracking is a document, not a management tool. Every month, the CFO should produce a variance report comparing actual costs against budget, line by line.

The variance report answers three questions:

1. Where are we over budget, and why? A 10% overspend on hosting might be fine if it correlates with faster-than-expected customer growth. A 30% overspend on travel needs an explanation.
2. Where are we under budget, and why? Underspend is not always good news. If you budgeted for a Q2 hire and the role is still unfilled in Q3, you are under budget on staff costs but potentially behind on product delivery.
3. What does this mean for the full year? Reforecast quarterly. Take the actuals for the months completed, the budget for the months remaining, and adjust for anything that has changed. This gives you a realistic full-year outlook rather than a stale budget that stopped being accurate in month 3.

The discipline of monthly variance analysis creates accountability. Team leaders know their spend is being reviewed. Founders get early warning of problems. And when it comes time to raise your next round, you can show investors a track record of financial discipline - that you set a plan and managed to it.

The deliverables

A properly built SaaS budget should include:

• Month-by-month P&L budget with revenue, COGS, and operating expenses broken down by department
• Headcount plan showing each planned hire, start month, and fully loaded cost
• Cash flow forecast showing when cash comes in (from invoicing and collections) and when it goes out
• Scenario analysis with at least a base case and a downside case
• KPI targets tied to the budget: target MRR growth, burn multiple, and runway in months

If you do not have a 12-month budget, you are making financial decisions without a framework. That is how companies run out of runway.

If you want help building a budget that actually drives decisions, get in touch about our financial planning service or learn more about how a fractional CFO can support your SaaS company.