Model the Decision, Not the Year

Most founders build a financial model once. It happens in the two weeks before a raise, it covers twelve months, and it is never opened again once the round closes.

The model is not wrong. It is just answering a question nobody is asking. It says what the year is supposed to look like. What you actually need to know is narrower and far more useful: should I hire this person, should I raise this price, should I open this market, and what does it do to the number of months I have left.

That is a different exercise, and it is one you can run in an afternoon.

The budget habit and why it goes stale

A budget is a set of assumptions frozen at a point in time. You wrote it in January based on what you believed in January. By March you have signed a customer you did not expect, lost one you did, and pushed a hire back a quarter.

Every one of those events makes the budget less true, and none of them make it obviously false. It degrades quietly. So founders stop trusting it, then stop opening it, then go back to running the business off the bank balance and a feeling.

The bank balance is a rear-view number. It tells you where you have been. It cannot tell you what happens if you do the thing you are currently thinking about doing.

An initiative is a decision with its numbers attached

An initiative is a single action you are considering, modelled with everything it actually touches.

Not "sales and marketing spend goes up 20 percent." Instead: hire one account executive in Kuala Lumpur, starting September, on this salary, with a three month ramp before the first close, carrying this quota, generating deals at this average size with this expected win rate.

The difference matters. The first version is a spend line. The second is a mechanism. One tells you what leaves the bank account. The other tells you what comes back, when, and what has to be true for it to work.

How to build one

Take the next real decision on your desk and write down four things.

What it costs, and when. Full cost, not just salary. Employer contributions, tooling, the laptop, the recruiter fee if there is one. Put each cost in the month it actually lands, not spread evenly across the year. Timing is most of the answer.

What it produces, and when. Almost nothing produces revenue on day one. A salesperson ramps. A new market needs a first reference customer. A price change hits new contracts immediately but existing ones only at renewal. The lag between spending and earning is where founders get surprised, so model it explicitly.

What has to be true. Write the assumptions down as sentences, not just cells. "First close by November." "Average deal size holds at current levels." "Nobody churns because of the price move." These become the things you check monthly.

What it does to runway. Layer the initiative on top of your existing plan and read the month where cash gets tight. That single month is usually the whole decision.

What changes when you work this way

The answer stops being yes or no. It becomes conditional, which is how these decisions actually behave. "Yes, if the first two deals close by October, and here is the month it gets uncomfortable if they do not."

You also get a tripwire. Because you wrote the assumptions down, you know in November whether the initiative is tracking or not, and you still have time to act. Founders who model annually find out in March of the following year, which is not a decision point, it is a post mortem.

And when an investor asks what a new hire does to your runway, you are not estimating in the meeting. You have already run it.

Where founders get this wrong

Two failure modes come up repeatedly.

The first is building the initiative in isolation. A hire that looks affordable on its own can be unaffordable stacked on the two other things you already committed to. Initiatives have to sit on top of the same base plan, not in separate tabs.

The second is modelling only the upside case. If the only version you build is the one where the account executive hits quota, you have not modelled a decision, you have written a wish. Build the version where ramp takes five months instead of three. If that version still survives, you have a real answer.

Takeaway

You do not need a better annual budget. You need to be able to answer the specific question in front of you, with numbers, in an afternoon.

Model the decision, not the year. Write down what it costs and when, what it returns and when, what has to be true, and which month gets tight. Then go check it monthly against what actually happened.

That is not a finance exercise. It is how you find out what your business does before you ask it to do it.