Budgeting, Forecasting & Building a Simple Financial Model

By Pritesh Yadav 9 min read

So far, most of business finance has been about looking back — what did we earn, what did we spend, what is the cash today. This section flips you around to look forward. You are going to learn how to make a plan for the future in numbers, check the plan against reality each month, and fix the plan when reality disagrees.

Do not be scared. A "financial model" sounds like something only a banker in a suit can build. It is really just a spreadsheet that says: "If these few things happen, here is the money that comes out." If you can multiply and add, you can build one.

Key takeaway: Looking back tells you if you are alive. Looking forward tells you if you will stay alive. A founder who plans the next 12 months in numbers is far less likely to run out of cash by surprise.

Three words people mix up: budget, forecast, and model

These three words get used as if they mean the same thing. They do not. Let me define each in plain English.

  • Budget — your plan for a period (usually one year). It is a promise to yourself: "We plan to make $40,000 a month and spend $30,000 a month." You set it once, usually at the start of the year, and you mostly leave it fixed so you can measure yourself against it.
  • Forecast — your best honest guess of where you are actually heading, updated as new facts arrive. The budget says "here is what we planned." The forecast says "here is where we are really going, based on what we now know."
  • Financial model — the machine (a spreadsheet) that produces both. You feed it assumptions (price, number of customers, costs), and it calculates revenue, profit, and cash. Change one assumption and every number downstream updates by itself.
Analogy: Think of a road trip. The budget is the plan you made at home: "We'll drive 500 miles a day and arrive Friday." The forecast is your GPS re-calculating arrival time after you hit traffic: "Now arriving Saturday morning." The model is the GPS app itself — the engine that turns your speed and distance into an arrival time.

Two ways to build a revenue plan: bottoms-up vs top-down

Before any model, you need a number for revenue (money coming in from sales). There are two directions to reach it. Smart founders use both and compare them.

Top-down: start big, shrink to your slice

You start with the total market and take a small share of it. TAM means Total Addressable Market — the total money everyone could spend on your kind of product.

Example (top-down): "The print-shop software market is worth $2 billion a year. If we capture just 0.1% of it, that's $2,000,000,000 × 0.001 = $2,000,000 a year." Easy to say… but where does "0.1%" come from? Usually thin air.

Bottoms-up: start with what you actually do

You build revenue from your real activities: how many customers, at what price, how often. This is slower but far more honest, because every number is something you can do something about.

Two common bottoms-up formulas:

Business typeRevenue formula
Subscription / B2BCustomers × Price per customer
E-commerce / storefrontTraffic × Conversion rate × Average Order Value (AOV)

Quick definitions: Traffic = visitors to your site. Conversion rate = the % of visitors who actually buy. AOV (Average Order Value) = the average dollars per order.

Example (bottoms-up, step by step): Your online store gets 100,000 visitors a month. 1% of them buy. Each order is worth $100.
Step 1 — buyers: 100,000 × 1% = 1,000 buyers.
Step 2 — revenue: 1,000 × $100 = $100,000 for the month.
Now you can see the levers: lift conversion to 1.2% and you earn $120,000 with the same traffic.
Top-downBottoms-up
Starts fromTotal market sizeYour own activities
Good forThe yearly big-picture, board slidesMonthly operating, knowing what to fix
RiskFantasy ("just 1% of a huge market")Can be too cautious
Editable levers?FewMany (price, conversion, traffic)
Best practice: Build bottoms-up as your real plan, then build a quick top-down as a sanity check. If your bottoms-up says you'll earn 5% of the entire world market, something is wrong. Industry data shows founders who compare both hit their goals more reliably than those using only one.

Driver-based modeling: make assumptions explicit and editable

A driver is an input number that "drives" the result — like price, customer count, or churn. An assumption is your guess for that driver before you have real data.

The golden rule: never type a final answer directly into a cell. Type the drivers, and let the spreadsheet calculate the answer. This is "driver-based modeling." If you write revenue as "$100,000" by hand, you've learned nothing. If you write traffic × conversion × AOV, you can change any driver and instantly see the effect.

Common mistake: Hard-coded numbers. Typing "Revenue = $50,000 growing 10% every month" hides the truth. What if you can't actually get those customers? A hard-coded number can't be argued with or improved. Always model the drivers underneath it.

Three scenarios: base, best, and worst case

The future is unknown, so don't pretend you know it exactly. Build three versions by changing your key drivers:

  • Base case — what you genuinely expect (your honest middle bet).
  • Best case — things go well (higher conversion, faster growth).
  • Worst case — things go badly (slow sales, higher costs). This one matters most — it tells you when you'd run out of cash.
Example: Base case: 1.0% conversion → $100,000/month. Best: 1.4% → $140,000. Worst: 0.6% → $60,000. If your costs are $80,000/month, the worst case loses $20,000 a month — now you know exactly how much cash buffer you need before you start.
Best practice: Because you built drivers, all three scenarios should come from changing two or three assumption cells — not rebuilding the whole sheet.

Rolling forecast vs annual budget

An annual budget is set once a year and frozen, so you can measure yourself against it. A rolling forecast is updated every month and always looks the same distance ahead — as one month finishes, you add a new month at the far end, so you always see roughly 12 months forward.

Analogy: The annual budget is a printed map you bought in January. The rolling forecast is live GPS — it re-routes every time the road changes.

You don't have to pick one. The strongest setup keeps both: the frozen budget gives you accountability (did we hit the plan?), and the rolling forecast gives you agility (where are we really heading now?).

Variance analysis: plan vs actual, then act

Variance just means the difference between what you planned and what really happened. Variance analysis is the monthly habit of putting plan and actual side by side and asking why they differ — then doing something about it.

Example (with arithmetic):
Planned revenue: $100,000. Actual revenue: $85,000.
Variance = $85,000 − $100,000 = −$15,000 (a $15,000 shortfall).
As a %: −$15,000 ÷ $100,000 = −15%.
Now the real work — why? Because you built drivers, you can see traffic was on target, AOV was fine, but conversion fell from 1.0% to 0.85%. The problem is on your website, not your marketing. That is the power of variance analysis: it points you at the exact thing to fix.
Best practice: Investigate variances bigger than a set threshold — many teams use roughly 5–10%. Tiny wiggles are just noise; chasing them wastes your day.

A simple month-by-month model layout

Here is a clean layout. Months across the top, line items down the side. Every revenue number is calculated from the drivers above it — nothing is typed in by hand except the assumptions.

LineJanFebMar
Traffic (driver)100,000110,000121,000
Conversion (driver)1.0%1.0%1.1%
AOV (driver)$100$100$100
Revenue (calc)$100,000$110,000$133,100
Costs (driver)$80,000$82,000$85,000
Profit (calc)$20,000$28,000$48,100
Cash at end (calc)$120,000$148,000$196,100

How the flow works, top to bottom:

  Drivers (you type these)
  traffic  conversion  AOV  costs
        \      |       /     |
         v     v      v      |
        REVENUE = T x CR x AOV
                  |          |
                  v          v
              REVENUE  -  COSTS  = PROFIT
                                    |
                                    v
            CASH(last month) + PROFIT = CASH(now)

Best practices that separate good models from junk

  • One assumptions tab. Keep every driver (price, conversion, churn, salaries) in one place, clearly labeled. The rest of the sheet only does math on those cells. To test a new idea, you change one tab — not 200 scattered cells.
  • Don't fake precision. Writing "$1,284,447.18" for next year is silly — you don't know it to the penny. Round numbers ($1.3M) are more honest and easier to trust.
  • Update monthly. The best model is the one you actually keep current. A simple sheet you refresh every month beats a fancy one nobody has touched in three months.
  • Color-code inputs. Make typed-in driver cells one color (say blue) and calculated cells another. Then you instantly see what's a guess and what's math.
Common mistake — the hockey-stick fantasy: A chart that's flat for six months, then suddenly rockets up to huge growth "by month 12" — with no reason given for why month 6 is magic. Investors have seen a thousand of these and trust none of them. If your line bends sharply upward, you must point to the exact driver that changes (a new channel, a price rise, a big partner) and defend it.
Key takeaway: A good financial model is not a crystal ball that predicts the future perfectly. It's a thinking tool — explicit drivers on one tab, three honest scenarios, and a monthly habit of comparing plan to actual and acting on the gap. Built that way, it stops cash surprises before they kill you.

Sources: Forecastio, Finro, 8020 Consulting, Onetribe Advisory, PrometAI, Inflection CFO, Polaris Growth.

Continue reading