TL;DR: A budget vs. actuals framework compares what you planned to spend and earn against what actually happened. Most SaaS companies build budgets once annually and never look at them again. Smart companies review budget vs. actuals monthly, investigate variances over 10%, and adjust forecasts based on what they learn. This transforms budgeting from an academic exercise into an operational tool that improves decision-making and catches problems early. Build your framework around revenue, expenses by department, and cash, with clear variance explanations required for anything materially off plan.
We see two types of SaaS companies. The first builds an annual budget in December, presents it to the board, then ignores it for 12 months. The second builds the same budget but reviews actuals against it every month and adjusts plans based on what they learn.
The second company spots problems faster, makes better resource allocation decisions, and hits their goals more consistently. The difference is discipline around variance analysis.
Here’s what monthly budget vs. actuals review catches:
A marketing channel that’s running 40% over budget with no incremental customers. Without monthly review, you burn an extra $50K before anyone notices.
Engineering costs coming in 15% under budget because two planned hires fell through. You can reallocate that budget to other priorities or banking the savings.
Revenue tracking 8% behind plan for two consecutive months. This is a trend that requires immediate attention, not something you discover in month six when you’ve missed quarterly targets.
Sales rep productivity 25% below modeled assumptions. Your hiring plan assumed reps would produce $60K in monthly bookings after ramp. Actual is $45K. This affects your whole revenue forecast and hiring strategy.
The point isn’t catching variances for their own sake. The point is using variances as information to improve decisions. Budget vs. actuals tells you where your assumptions were wrong so you can fix them going forward.
Most SaaS budgets are organized wrong for variance analysis. They have 100 line items in the P&L and no clear ownership. Nobody knows who’s responsible for “software subscriptions” or “consulting fees.”
Build your budget structure around decision makers:
Revenue by channel: Organic, paid search, content, inside sales, field sales. Each channel has an owner who’s accountable for hitting targets.
Cost of goods sold: Hosting, support, implementation. These roll up to different teams (engineering for hosting, support for customer success, services for implementation).
Sales and marketing by function: Sales compensation, marketing programs, marketing operations, sales operations. Each has a budget owner.
Research and development: Engineering, product management, design. Usually one owner (VP Engineering or CTO).
General and administrative: Finance, HR, legal, facilities. Usually rolls up to CFO or COO.
This structure maps budget to organizational accountability. When marketing programs run over budget, the marketing leader owns the explanation. When engineering runs under budget, the CTO explains why.
Within each category, separate fixed costs from variable costs. Sales compensation is variable (scales with bookings). Software subscriptions are fixed. When revenue varies from plan, variable costs should vary predictably while fixed costs stay constant. If they don’t, investigate why.
Create a monthly budget vs. actuals review process that actually gets completed:
By day five of each month: Close the prior month’s books. This means finalizing revenue, expenses, cash balance, and key metrics.
By day seven: Finance produces budget vs. actuals report showing plan, actual, variance in dollars and percentage for each budget category.
By day ten: Budget owners review their variances and provide explanations for anything over 10% off plan.
By day twelve: Leadership team reviews consolidated budget vs. actuals with explanations, discusses trends, and decides on forecast adjustments.
This timeline forces discipline. Some companies let variance analysis slip to day 25, by which time you’re nearly into the next month and the information is stale.
The variance report should show:
Budget: What you planned for the month
Actual: What actually happened
Variance: Actual minus budget (positive is favorable for revenue, negative is favorable for expenses)
Variance percentage: Variance divided by budget
Explanation: Written explanation for variances over threshold
Year-to-date columns: Budget, actual, and variance for the year so far
Include both monthly and year-to-date views because patterns emerge over time that single months hide. A category that’s 5% over budget three months in a row is a trend. A category that’s 20% over in one month but within budget year-to-date is probably timing.
Set clear thresholds for what requires explanation:
Revenue: Any variance over 5%. Revenue is your most important number and should be predictable.
Major expense categories (sales, marketing, engineering): Any variance over 10% or $25K, whichever is less.
Minor expense categories: Any variance over 15% or $10K, whichever is less.
These thresholds focus attention on what matters. Don’t waste time explaining why office supplies were $200 over budget. Do explain why hosting costs were $15K over budget.
Favorable variances (better than plan) require explanation just like unfavorable variances. If sales compensation is 20% under budget, that’s probably because bookings are below plan, which is a problem. If engineering is 15% under budget, maybe you’re not hiring fast enough and will bottleneck product development.
The explanation should include:
– What caused the variance (specific driver)
– Whether it’s temporary or permanent
– What you’re doing about it
– Whether budget needs to be adjusted going forward
“Marketing was over budget because we increased paid search spend” isn’t enough. “Marketing was $25K over budget because we increased paid search by $30K to test higher-intent keywords. Results show 20% better conversion so we’re requesting permanent budget reallocation from other channels” is what you need.
The purpose of variance analysis is improving forecasts. When actuals diverge from budget, update your forecast to reflect new reality.
If revenue is running 10% below plan for three months straight, your annual forecast needs to decrease unless you can articulate specific reasons growth will accelerate.
If CAC is running 25% higher than budgeted, update your customer acquisition forecast to reflect actual CAC and adjust hiring plans accordingly.
If churn is 3% monthly instead of budgeted 2%, your revenue forecast for the rest of the year needs to account for higher erosion.
We worked with a company that budgeted $10M in annual revenue based on 25% quarterly growth. After Q1 showed 18% growth (not 25%), they stuck with the original forecast anyway. Q2 also hit 18%. They finally revised the forecast in Q3 and had to cut 20% of staff because burn was unsustainable at the lower revenue level.
If they’d updated the forecast after Q1, they could have adjusted spending gradually instead of panic cuts in Q3.
Build a rolling forecast that updates monthly. Keep your annual budget as a baseline for comparison, but maintain a separate current forecast that incorporates actual results and updated assumptions.
Show both in your management reporting:
– Original budget (what you planned)
– Current forecast (updated based on actuals)
– Actual results
This shows what you planned, what you now expect, and what’s happening. The gaps between these three numbers tell the story of how your business is evolving versus expectations.
Some variance explanations show up repeatedly. Here’s what they actually mean:
“Timing difference”: Revenue or expense will hit in a different month than planned but the full-year impact is unchanged. This is fine if true, but watch for “timing differences” that never reverse. That’s not timing, that’s a broken forecast.
“One-time expense”: An unplanned expense that won’t repeat. Fine occasionally, but if you have three “one-time” expenses in Q1, you’re not budgeting correctly for operational reality.
“Customer payment delayed”: Revenue recognition pushed to next month because customer hasn’t paid or contract hasn’t started. Red flag if this happens repeatedly. Either collections are breaking down or your revenue forecasting doesn’t account for implementation delays.
“Open headcount”: You budgeted for someone to start in March but hired them in April. Common early in the year, concerning if it’s happening across many roles or late in the year. Means you’re not hitting hiring targets.
“Lower than expected volume”: Revenue or variable costs are under budget because customer acquisition or usage was lower than planned. This is the most important variance to investigate because it signals the business model isn’t performing as expected.
Create dashboards that make variance analysis visual and easy:
Revenue dashboard: Shows actual vs. budget by channel, by month, with year-to-date totals. Include variance percentages. Color code red for over 10% below budget, green for on track.
Expense dashboard by department: Shows actual vs. budget for each major cost center. Include headcount actuals vs. plan since people costs drive most SaaS expenses.
Cash dashboard: Shows actual cash balance vs. budgeted cash balance. Include burn rate actuals vs. plan. This is your early warning system for runway problems.
Key metrics dashboard: Shows metrics like CAC, LTV, churn, and NRR against targets. These often explain financial variances.
Update these dashboards monthly as part of your close process. Review them in leadership meetings. Make them accessible to department heads so they can self-serve rather than waiting for finance to produce custom reports.
The visual format matters. A spreadsheet with 50 rows of numbers is hard to interpret. A dashboard with clear charts showing budget vs. actual trends tells the story instantly.
Sometimes variance analysis uncovers issues that require strategic response:
Persistent revenue shortfalls: Three months of revenue 15% below budget suggests the market opportunity is smaller than you thought, competition is fiercer, or your sales motion isn’t working. This might require rethinking your go-to-market strategy, not just adjusting the forecast.
Ballooning customer acquisition costs: CAC running 40% over budget for two quarters means your unit economics are worse than modeled. You might need to pivot acquisition channels, improve conversion rates, or revisit your ICP.
Gross margin compression: If COGS is running 25% over budget and gross margin is dropping, you have a structural problem. Either your infrastructure isn’t scaling efficiently, support costs are out of control, or your pricing is wrong.
Operating leverage not materializing: You budgeted for operating expenses to grow slower than revenue as you scaled. Instead, they’re growing in line with revenue. This means you’re not getting the leverage that makes SaaS valuable. You need to find where automation and efficiency should be happening but isn’t.
These problems won’t fix themselves. Variance analysis that reveals them early gives you time to respond strategically instead of reactively when you run out of cash.
Budget vs. actuals only works if the organization takes it seriously:
CEO must care: If the CEO doesn’t review variance reports and ask tough questions, nobody else will either.
Consequences for missing budget without explanation: If people consistently miss budget and face no consequences, budget becomes fiction. Either the budget is wrong (fix it) or execution is wrong (fix that).
Rewards for beating budget: Teams that consistently deliver results better than budget should be recognized. This creates positive reinforcement for the process.
Transparency: Share budget vs. actuals broadly (at least with leadership team, potentially with all managers). When people can see results, they care about them.
No punishment for honest variance explanations: If people get punished for explaining why they missed budget, they’ll stop providing honest explanations. Separate variance analysis (learning tool) from performance management (accountability tool).
Regular process: Make budget vs. actuals review a standing monthly meeting. Same time, same format, every month. Consistency builds discipline.
—
Q: How detailed should our budget vs. actuals tracking be?
Detailed enough to drive decisions but not so detailed you drown in data. At minimum, track revenue by major channel and expenses by department with 5-10 line items per department. For a $5M ARR company, this means 20-30 total budget lines. For a $50M ARR company, maybe 50-75 lines. If you have more than 100 budget lines, you’re probably too granular. The test is: would knowing this specific variance change a decision? If not, roll it up into a broader category.
Q: What if we consistently miss our budget by large margins?
This means either your budget is unrealistic (too aggressive) or your execution is poor. If you’re missing by 20%+ for multiple quarters, the budget is wrong. Rebuild it with more conservative assumptions grounded in actual historical performance. If you’re missing by 10-15%, execution might be the issue. Dig into why. Are there resourcing problems, process problems, or market problems? The key is being honest about which it is. Many companies keep building aggressive budgets year after year and missing them rather than admitting their assumptions are wrong.
Q: Should we reforecast monthly or stick with the annual budget?
Maintain both. Keep the annual budget as approved by the board as your baseline for comparison. But build a rolling forecast that updates monthly based on actuals and revised assumptions. Report both in your variance analysis. This shows what you originally planned (budget), what you now expect (forecast), and what’s happening (actuals). The gap between budget and forecast shows how your assumptions evolved. The gap between forecast and actuals shows your current predictive accuracy. Both are valuable information.