Work out your business plan before you write it up
Give each section of your plan its own branch, question the assumptions under it, and find what you still need to check before you write the document.
Start from a template
A business plan template you can clone. Describe your business in the root, then work through the sections one branch at a time.
How it works
Start with one sentence about the business and who it is for. Each section of the plan gets its own branch, and every question you ask under a section keeps that section and your description in context.
-
Lay out the sections. Ask for a business plan outline. The model proposes the usual sections: market, value proposition, business model, go-to-market, financials and team. Add a branch for each one you want to work on.
-
Work through one section. Under the business model branch, ask about unit economics, pricing or the cost of winning a customer. The model knows which business and which section you mean, because it reads every node above the one you are asking.
-
Question each assumption. Under any answer, ask “What if this is wrong?” A plan rests on a few bets, such as the price customers will pay, and each one gets its own branch you can come back to.
-
List what you still need to check. A vague answer usually marks a question you cannot settle from your desk. Add a note to that node saying how you will check it, such as a survey or a pilot.
Why a map before the document
A written plan buries each assumption in the middle of a section. On a map, each assumption sits under the section it belongs to, with its follow-ups underneath. You can fold the sections you have finished and keep working on the open ones.
When the thinking is done, export the map to Markdown and use it as the outline for the document.
Example
Say you and a co-founder are applying to an accelerator with an accounts payable product for mid-market companies. Under the revenue model branch you ask about three ways to charge: per transaction, per seat and as a share of invoice value. Per transaction grows with usage but makes revenue hard to forecast. Per seat is predictable but caps what one account can pay, and that trade-off becomes the pricing slide in your application.