
At the start of a company the plan can be one line: build the product, launch the product. Almost everything else in a formal business plan is a prediction, and a new company has nothing to predict from. In our first two years we had no financial goal at all, and we started to decline when we set one.
Four lines on a napkin
About fourteen years ago I was talking with a mentor of mine, someone who had been through many businesses. He told me that the most complex plan he had ever made at the start of a company was one that could fit on a napkin. That was the peak of his planning for a new venture.
The reason is not laziness. A startup is a pile of unknowns, and it is nearly impossible to plan anything meaningful when the plan rests entirely on assumptions. The objectives, the executive summary and the financial modeling are almost useless at that stage. I have lived that lesson many times since, in our own companies and in others I have watched up close.
My napkin has four lines.
- What I am building, in one sentence.
- How much money I have, and how much of it I am willing to spend to validate the idea.
- The window of time that spending covers.
- The one thing I am watching to know whether it is working.
The second and third lines are the whole financial plan. I need to know how much money there is, how much will be spent and on what, with a rough timeline: over the next three months I can spend this much and I expect this much progress. A cash-flow model or a detailed profit-and-loss statement full of projections is not needed, least of all when there is very little money to invest.
A heavy financial plan is also dangerous, because its numbers are invented. A cash-flow projection for a company with no customers is fiction laid out as a spreadsheet. The risk is that I start to believe it, and then make decisions to defend the projection instead of decisions that serve the customer. The napkin is too small to pretend to know what it does not know.
Writing a long plan also feels like progress. It happens on the page, where every scenario resolves the way I imagined it. Launching is uncomfortable because reality answers back, and that answer is the feedback that matters. I write about it in Ship the prototype, then listen.
What happened when we set a financial goal?
In our first two years we never had a financial goal. When we started setting them, we started to decline.
That surprised me, because it contradicts what the courses teach. The revenue goal did not motivate us. It distracted us. Once the number was up on the wall, it became the thing we optimized. But revenue is a lagging shadow of the real work, which is building something people want and getting it in front of them. We stopped watching the product and the customer and watched the number. When we let the goal go and turned back to the product and the customer, the results came back.
I do not conclude from this that budgets are wrong. Large companies need financial objectives, budgets and financial organization. Inside a startup the same structure can do harm.
The model deserves the thinking the plan does not
What matters far more than the plan is the business model. The plan is a prediction about the future. The model describes how the company makes money: how the money comes in, how the work turns into value, how each part connects to the next. I think of it as a clock, in which every small gear turns so that the final result comes out. Because a model is about mechanism, it can be reasoned about, and at its core it fits on a single sheet of A4.
The model also determines whether results come quickly or slowly. That is where I spend my thinking.
Does planning get heavier once the business is stable?
Less than people expect. A complex plan can destabilize a stable business. Writing one pushes in one of two directions. Either everything gets overcomplicated, or the company loses focus, because on paper we write down far too many objectives and have no sense of how long any of them takes in reality.
Measurement stays small as well. For a single software product I do not need a hundred metrics. I can track monthly recurring revenue, what actually lands in the bank, and which customers are most committed over the long term. A metric is there to change a decision. A number that never changes one is decoration. I keep the two or three that would make me do something different and leave the rest until the company is large enough to afford watching them.


