The Business Plan Has a Branding Problem
In the startup world, the business plan has developed a reputation problem.
In the startup world, the business plan has developed a reputation problem.
For the past fifteen years the dominant advice has been some version of: build first, figure the rest out later. Move fast. Ship product. Iterate. The pitch deck replaced the business plan, and founders were told that traction was the only thing that mattered.
To be fair, this shift corrected a real problem. Traditional business plans were often elaborate works of fiction. Forty pages of immaculate formatting, optimistic charts, and revenue projections that had very little connection to reality. They created the comforting feeling of preparedness without requiring much real thinking.
But somewhere along the way we threw out the wrong thing.
Not the document itself. The discipline behind it.
A good business plan is not about predicting the future. It is about forcing the uncomfortable conversations early—before reality forces them for you.
Lately I have been meeting with a number of startups, many of them led by extremely capable founders. Brilliant, even. They understand their product. They understand the market. They can explain convincingly how the idea will make money and why the timing is right.
In the first fifteen minutes, everything sounds promising.
Then you ask a few more questions.
What does the company actually look like when revenue is ten times larger? Who gets hired first? Where does capital actually go? What systems will finance run on? What happens if customer acquisition becomes more expensive than expected? What breaks first?
That is usually where the conversation slows down.
Not because the founders are not smart. Because much of the company still exists as instinct. The product is real. The business, however, is still partially a thought experiment.
A business plan is where that thought experiment becomes architecture.
Right now I am involved in a real estate venture, and the first thing I did was write a business plan. I do not think there would really be a business without it. There would be conversations, enthusiasm, maybe even some early deals. But the act of writing the plan forces a kind of clarity that informal thinking rarely produces. It turns a concept into something you can interrogate.
You start asking practical questions. What are the economics? How does this scale? What does the capital stack look like? What kind of organization actually needs to exist for this to work beyond the first few projects?
Those questions are not glamorous, but they are foundational.
I saw this dynamic clearly in two conversations this week.
One friend of mine—let’s call him Jarvis—has built one of the most impressive AI tools I have seen in a long time. It is the kind of product that makes you pause and recalibrate what is possible. He already has a couple of term sheets floating around.
On paper, that sounds like the startup story investors love: brilliant founder, breakthrough technology, early capital interest.
But Jarvis is still, practically speaking, a one-man company. The product exists. The company around it is still forming. He has a plan, but much of it lives in his head. That is normal for a founder at this stage. But there is a meaningful difference between a brilliant product and a structured business, and the bridge between the two is usually built in the process of writing things down.
Another friend—let’s call him Cami—has the opposite situation. He has a SaaS business with traction, real customers, and meaningful ones at that. There is ARR. The product works. By most startup metrics, things are going well.
But once you look under the hood, the structure is thinner than you would expect. There is no real P&L. The organizational model is still fuzzy. Finance, marketing, PR, HR—the parts of a company that determine whether it can scale—are still treated as afterthoughts.
Cami has a business that works commercially.
What he does not yet have is a fully formed company.
This is where business plans become surprisingly practical. They force founders to confront the operational questions that momentum allows them to postpone.
What should compensation look like? What salary philosophy makes sense for the stage of the company? When do you hire senior talent versus cheaper generalists? What systems will the company run on? Where does finance live? What CRM powers sales? How does reporting work when the company doubles in size?
These questions rarely feel urgent early on. But they quietly determine whether a startup becomes a durable company or simply a successful product that eventually collapses under its own improvisation.
A business plan does not solve those problems.
It simply forces them into the open.
There is also an important nuance here. Early-stage business plans should not be overly financial. At the beginning, the numbers are mostly educated guesses anyway. Founders sometimes obsess over detailed five-year projections as if the spreadsheet itself were the strategy.
It rarely is.
At that stage the finances are inevitably a bit “pie in the sky.” What matters far more is the foundation behind them. What is the business trying to become? How does it make money in principle? What capabilities need to exist for it to scale? What kind of organization must be built around the product?
The plan is less about predicting exact outcomes and more about defining the architecture of the company.
And here is the funny part: it has never been easier to build one.
Twenty years ago writing a business plan felt like a chore. It required spreadsheets, consultants, and a large block of uninterrupted time. Today you can build the first version conversationally. With Claude, ChatGPT, or Gemini, a founder can outline a real business plan while walking the dog or sitting in traffic.
You can ask the model to challenge your hiring plan, sketch organizational structures, propose software stacks, build early financial models, or pressure-test assumptions. In other words, you can take the vague version of the company that exists in your head and quickly turn it into something concrete enough to argue with.
AI does not write the business plan for you in any meaningful sense.
It simply removes the friction.
The founder still has to think. If anything, the process just makes it easier to see the holes.
Startup culture often treats planning and speed as opposites. The assumption is that you either move quickly or you sit around thinking. In reality, the best founders do both. They build quickly, but they also spend time modeling what the business becomes if it actually works.
Because scaling introduces entirely new problems. Hiring complexity. Capital planning. Operational systems. Distribution strategy. Brand positioning. Organizational structure.
None of those appear magically when the product succeeds.
They have to be designed.
The business plan is simply where that design begins.
It is not glamorous. It will never trend on LinkedIn. It does not photograph well next to a laptop and a cappuccino. But it quietly does one of the most important things a founder can do: it forces the company to exist outside the founder’s head.
Startups love to talk about disruption. But the companies that survive are usually built on something much quieter: the discipline of thinking the business through.