SaaS Financial Forecasting

🔮 How I Forecast Revenue If there’s one part of financial modeling that I obsess over — it’s revenue forecasting. And for good reason… Every company is different. Every forecast tells a unique story. But over the years, I’ve refined a framework that brings structure, clarity, and flexibility. Here’s how I do it: 📊 Step 1: Segmented Revenue Forecasting Break revenue down by product, region, or customer type. SaaS ≠ Services ≠ Hardware. Each needs its own assumptions. 🔁 Step 2: Existing Customers (E) I use cohort analysis to forecast retention, churn, and expansion. Key metrics: • Net Revenue Retention (NRR) • Monthly Recurring Revenue (MRR) • Gross Churn Rate 📥 Step 3: Pipeline Customers (P) Based on CRM data, I build a probability-weighted forecast. I apply stage-specific win rates and time-to-close to model revenue realistically. 🆕 Step 4: New Customers (N) — Powered by A•R•S•R: • Acquire → Leads by channel (organic, paid, referral, etc.) • Retain → Forecast customer lifetime • Sell → Estimate deal size & frequency • Record → Recognize revenue, deferred income, AR, and COGS 📈 Step 5: Growth Levers + Sensitivity Analysis I layer in assumptions (CAC, churn, ARPU) with toggle-based drivers for fast scenario shifts. 🎯 Step 6: Scenario Planning Especially for startups or enterprise deals, I use: • Best/Base/Worst cases • Monte Carlo simulations • Decision trees for high-stakes planning This method has helped my clients (and my own models) forecast with confidence — without overcomplicating things. #RevenueForecasting #FinancialModeling #FPandA #StartupFinance #BusinessStrategy #Consulting #CFOInsights #SaaSFinance #ARSR #EPNFramework

If I were leading FP&A at a high-growth SaaS company gearing up for a Series B, here’s the planning playbook I’d build before walking into investor meetings: Let’s define the baseline: -Usage-based pricing model -$11M ARR -Growing 60% YoY -73% gross margin -Burn of ~$650k/month -Forecasts are updated 1-2x/year -Headcount plan lives in Excel -CRM = Hubspot, forecasting done at pipeline stage level Here’s what we’re up against: Investors want clarity. They don’t want a pitch, they want conviction in the numbers, where risk lies, and what levers exist. But the current state? - Forecasts are built like art projects. - Headcount assumptions are scattered across tabs. - Usage scenarios live in someone’s brain. - Board reporting is a quarterly scramble. - Finance is a bottleneck, not a strategic partner. So let’s redesign it: The model: 1. Connect CRM (Hubspot) to planning = Pull real-time pipeline stage data = Create a dynamic bookings forecast with probabilities 2. Build usage scenarios = “What if usage drops 10% next quarter?” = “What’s our gross margin at 2x volume?” 3. Integrate headcount = Create future roles with start dates, comp, and org chart = See real cash impact by month Link all of it (revenue + headcount + margins+...) into one model that updates weekly. The output: - One model, built once, with live inputs. - Forecasts you can run on command. - Scenarios that reflect actual levers (not vibes). - A finance team that shows up with answers, not Excel files. And if we’re planning a raise? You have to be able to run: “What happens if we delay hiring by 90 days?” “What if our churn ticks up by 2%?” “How much runway do we buy if we freeze headcount post-Q3?” These aren’t slides - they’re survival questions. And answering them well is how you earn investor trust. Final thought: If you’re doing this prep DURING your fundraise, you’re already late. The best planning setup isn’t built for the board. It’s built for your team, so you’re never fundraising blind again. And the good news? You only have to build it once. IF you do it right.

The Forecast Loop: Why Your Numbers Never Match Reality 🧪 Ever notice how your forecasts miss the mark? You're not alone. Often times when I'm building forecasts for a fast-growing SaaS company, we'll spend weeks building models, only to watch it become irrelevant and stale after just a few months. The solution? Stop treating forecasting as a one-time project and start seeing it as an ongoing cycle of testing and improvement. ➡️ EXPERIMENT This is where the cycle begins. This requires structured testing, not random assumptions: Take a financial assumption and isolate it Change one pricing strategy at a time Adjust a specific operational factor The key is controlling your variables. When testing a price increase, don't simultaneously change your sales commission structure. Keep it clean! ➡️ MEASURE Now comes measurement. This means thorough tracking, well beyond a quarterly P&L review. I'm talking about tracking BOTH financial AND operational results: Revenue impact? Obviously. Customer acquisition cost changes? Critical. Renewal rates affected? You bet. Most companies fall short here - they watch revenue but miss the operational indicators that explain WHY the numbers changed. ➡️ LEARN Learning is comparing what you thought would happen with what actually happened. Launching a new product line? Trying a new acquisition channel? Landing a new partnership? These all involve assumption that require validation. But don't just note the difference - understand why it happened. Was your conversion rate overstated? Did it take longer to ramp up that partner? ➡️ UPDATE FORECAST Finally, update your forecast based on what you've learned. Most companies get this backward - they tweak forecasts to match historical results without updating the underlying assumptions. Instead: Adjust the actual input variables Refine how your model weighs different factors Document what you've learned so forecasts get smarter each cycle === The forecast loop focuses on continuous improvement rather than immediate perfection. What's the biggest gap you've seen between forecast and reality? How did you learn from it? Comment below 👇

Forecasting cloud costs is inherently hard because of unpredictable usage patterns, complex cloud pricing, speed of innovation, and non-linear scaling. Cloud budgets blow up when forecasts start with “last year’s bill x growth %”. A better play is to lock each workload to a stable unit cost and let business metrics drive the math: - In SaaS, tie it to cost per customer, cost per user, cost per licensed feature per customer.  - In consumer businesses, tie it to cost per transaction or order. Why it works: - Forecast ties directly to revenue drivers (seats, orders, API calls). - Variance tells a clear story—either usage outpaced sales, or unit cost inflated. - Pricing & architecture decisions surface early - if something is pushing the unit cost up, you can either optimize or take a business decision on feature/pricing. Cloud forecasting doesn’t need to be perfect; it needs to be predictable, and help support the budget commitments. Unit economics provides that predictability, so Finance trusts the budget and Engineering spots problems while they’re still cheap.

While most of the SaaS companies have challenge knowing what exactly their ARR is, it is even more difficult for usage based companies considering the fluctuating nature of actual revenue. Tracking and forecasting ARR for usage-based SaaS companies comes with its unique set of challenges: 1. Complex Usage Metrics: Usage-based companies often have complex usage metrics that vary from customer to customer. Tracking and consolidating this data can be challenging, especially when there are multiple pricing tiers, feature add-ons, or usage-based billing models. 2. Granularity of Data: Usage-based companies need to collect granular data on customer usage to accurately calculate revenue. This requires robust data collection systems and integration with the product or service to capture usage details at a fine-grained level. Handling and analyzing vast amounts of usage data can be daunting. 3. Data Synchronization: The data required to calculate ARR often resides in different systems such as usage tracking tools, billing platforms, and CRM systems. Ensuring data synchronization and accuracy across these systems can be a significant challenge for finance teams. 4. Billing and Revenue Recognition: Usage-based billing introduces complexities in revenue recognition, as revenue is recognized based on actual customer usage. Finance teams must navigate the intricacies of recognizing revenue correctly based on usage patterns, contractual commitments, and billing cycles. 5. Forecasting Accuracy: Forecasting ARR becomes more challenging with usage-based models due to the inherent variability in customer usage. Predicting future usage patterns and accurately forecasting revenue requires sophisticated algorithms, statistical modeling, and a deep understanding of customer behavior. 6. Data Analysis and Insights: Finance teams must analyze usage data alongside billing and contract data to derive meaningful insights about customer behavior, revenue drivers, and trends. This requires advanced analytics capabilities and cross-functional collaboration between finance, product, and sales teams. Overall, successful tracking and forecasting of ARR for usage-based SaaS companies require a combination of robust systems, data integration, accurate revenue recognition methodologies, advanced analytics capabilities, and cross-functional collaboration to navigate the complexities of the usage-based business model effectively. As usage based business model becomes the majority for SaaS companies, more and more companies will face the issue of being able to derive the right ARR at the right time. I would love to hear how you are tackling this problem at your company today. P.S.: FP&A tools like Mantys help companies keep a track of their usage data, revenue and help forecast based on past trends and future possibilities. #saas #usagebased #arr

Your MRR Waterfall 📊 Is the Swiss Army Knife of SaaS Data Too many SaaS companies don't have their MRR waterfall (aka snowball, roll-forward) data dialed in. You're flying blind if you’re not breaking down your monthly recurring revenue into new, expansion, contraction, and churn. And by product line, revenue type, etc. Your MRR Waterfall is more than a nice chart—it’s the heartbeat of your recurring revenue engine. It reveals what’s really driving growth. Here’s how I use the MRR Waterfall: ✅ Analyze net MRR movement to understand true revenue performance 🔍 Spot retention and churn trends early—before they get out of hand 📈 Track the impact of product and pricing changes on expansion revenue 🧮 Reconcile ARR forecasts with actual subscription performance 📋 Support Board decks, budget variance analysis, and investor reporting ⚠️ The heart of an accurate revenue forecast And it’s not just for internal use. Potential investors will ask for this. If you can’t show retention and expansion dynamics at a glance, you’re at a disadvantage—especially during due diligence. 📊 The pic below is from my SaaS forecast model. I've iterated on this model over the past 10+ years. If you'd like a copy, just let me know. #SaaS

I just built myself a CFO! 🤯 For years, our financial planning lived in Excel. It worked, but it was static. So, I decided to take a leap and rebuild our entire financial stack using Claude Co-Work as an interactive HTML dashboard. The result? A fully automated, real-time financial brain. 🧠 Here is everything we now have running under the hood: ➡️ The Core: Management KPIs, Total Revenue, P&L, and Cashflow ➡️ The Models: Snowball, Assumptions, Waterfall, and Scenario Planners ➡️ The Magic: It is all seamlessly connected to Candis and our live accounting data for a true, real-time forecast. But the absolute game-changer is the "Smart CFO" layer. Instead of just looking at numbers, I now get proactive alerts, strategic recommendations, and instant updates on whether our KPIs are on or off track. No more waiting for end-of-month reports to know where we stand. The future of finance isn't some distant reality. We are actually living in it right now. 🚀 Has anyone else started moving their financial models out of Excel and into AI-driven workspaces? #Finance #AI #Startups #FinancialPlanning #FutureOfWork #SaaS