Forecasting

Forecasting in SaaS sounds like CFO territory. It isn't. At indie scale forecasting is less about predicting the future and more about pressure-testing your decisions today — if you ship this pricing change, can you cover next quarter's hosting bill? If you hire that freelancer, when does the runway tip into the red? The articles in this category treat forecasting as a planning instrument, not a prediction game you try to win against the market.

The mistake we keep seeing: founders either don't forecast at all ("I'll know when I check Stripe next month") or build a thirty-tab spreadsheet that's impressive once and never updated. Both modes fail for the same reason — disconnection from the actual numbers. A useful forecast is two pages, has three or four inputs that auto-update from Stripe, and gets revisited on a fixed calendar (we recommend the first Monday of each month). Anything more elaborate gets out of date faster than it earns its keep.

Start with the SaaS forecast model for the conceptual frame — what variables actually matter when you're under €100K MRR and which ones are noise you can ignore. For runway specifically, the cash flow forecast template for SaaS gives you a working spreadsheet structure you can populate in an hour. And revenue forecast formula for SaaS zooms in on the revenue side specifically, including how to model expansion and churn without inventing numbers.

One thing we underline in every forecasting article: the forecast is wrong. That's not a bug. The point of forecasting at indie scale isn't accuracy — it's surfacing the assumptions you're betting on. If your forecast says €15K MRR by Q3 and you hit €11K, the question isn't "why was the model off." It's "which input was wrong, and what does that tell me about my growth model." The forecast is a hypothesis generator, not a prediction engine.