From Financial Model to Operating Decision

One company I co-founded rebuilt its financial model four times in a few months. None of them was "the right model." Each one answered a different question the team was asking that month, and once that question was answered, we let the model go.

For a long time I thought that was a sign of immaturity. Real companies, I assumed, had a model. One spreadsheet, maintained, the canonical source of truth, updated quarterly. The fact that we kept tearing ours down and starting over felt like we did not know what we were doing.

I had it backwards. Rebuilding the model that often was not the failure. Believing there was supposed to be one model was the failure.

A model is a decision instrument, not a forecast

The first model we built answered a single question: what does the core piece of equipment cost, and how do we amortize it. Say the equipment costs X up front and lasts some number of years. Do we treat it as a fixed cost smeared across every unit we produce, or as a capital bet we have to earn back before we call anything profitable? That sounds like accounting. It was not. It was a decision about how aggressively we would price and how patient we needed our capital to be. The model existed to force that one choice into the open.

The second model threw all of that out and asked something else: what are the unit economics of a single operator, before we had a single operator. No equipment schedule, no amortization debate. Just one hypothetical person running one hypothetical site, and whether the math on that person closed. If a single unit does not work, nothing downstream works, and no amount of scale fixes it.

Neither of those was a forecast. Neither one was trying to predict revenue in three years. Each was a tool built to resolve exactly one argument the team kept having. That is what a financial model actually is. It is not an input to a plan. It is an instrument you build to make one decision unavoidable.

The model you keep is the one that changes behavior

Here is the test I use now. A model has earned its place when it makes the team stop relitigating a question. Not when it is accurate - we never know if it is accurate until much later. When it changes what people do on Monday.

The runway model was the clearest example. It asked one thing: under a single bet, how long does the money last. It was crude. It ignored most of the real complexity of the business. But the day we finished it, the team stopped having a recurring, circular conversation about whether we could afford a particular move. The number was there. The argument was over. That is the only kind of accuracy that matters in the moment - did it move the decision forward.

The models that did not change behavior, no matter how detailed, were just expensive spreadsheets. Beautiful, internally consistent, and ignored. I have built plenty of those. The tell is always the same: nobody reaches for it when a real decision lands on the table.

Each model is a different story about the business

The reframe that finally made this click: a financial model is a narrative. It is a story we tell about how the business works, told in numbers because numbers force a kind of honesty that prose does not. The equipment model was one story - this is a capital-intensive operation that lives or dies on asset utilization. The single-operator model was a different story - this is a business that has to work at the smallest possible unit before anything else is true.

Both stories were correct. They were just answers to different questions. So now I treat models the way I treat any narrative artifact. I keep version history. I mark which one is canonical right now, and I write down the question it was built to answer. When we open a model, the first thing we read is not the numbers. It is the question.

The second-order benefit of this is bigger than the modeling itself, and it took me too long to see it. When the market does not match a model - and the market never matches the model - there is no blame cycle. Nobody was wrong. The model was right for the question it answered. The question simply changed. Reality moving away from your spreadsheet is not a forecasting failure. It is information. The old narrative described a business that no longer exists, which means it is time to write the next one.

Compare that to the team that maintains one sacred model. When reality diverges, somebody has to be at fault. The model was wrong, or the person who built it was wrong, or the assumptions were wrong, and now there is defensiveness baked into a tool that should be neutral. A single canonical model quietly turns every surprise into an accusation.

Build the toolkit, not the model

So I have stopped trying to build the model. There is no the model. There is a toolkit of small, sharp instruments, each built to resolve one specific choice, each kept around only as long as its question is live.

When a new question shows up - and in an early company a new one shows up roughly every month - I do not patch the old model to cover it. I build a new instrument, point it at the question, and let it change one decision. Then I file it next to the others, labeled with the question it answered and the date the answer stopped being current.

Four models in a few months is not thrashing. It is four decisions made cleanly, four arguments closed, four stories told and retired. The spreadsheet was never the deliverable. The decision was.

Field Notes from the Agentic Operator is a personal series. These are my own views, not those of my employer or any organization I work with, and nothing here relies on non-public information.