Editorial content prepared for José’s review. General business information; not legal, tax or financial-product advice.
A small business plan earns its place when it helps you make a decision. It might explain a new idea, organise an established business or support a conversation with an external reader. Its usefulness depends less on length than on whether the customer, operating and financial assumptions fit together. Start by writing down the decision the plan needs to support.
1. Identify the reader and the purpose
A plan for your own team may prioritise responsibilities and immediate actions. A plan for an external reader may need different evidence and formatting. Ask what that reader needs before you invest time in presentation. The Australian Government’s business plan guidance recommends identifying the audience and keeping the plan under review. An external reader’s acceptance is never automatic.
Write a one-sentence purpose at the top of your working draft. For example: “Compare whether we should introduce an additional service using our existing capacity.” This gives every section a job and helps you decide what detail is unnecessary.
2. Explain the customer problem
Describe who is likely to buy, the problem they face and the alternatives they already use. Avoid “everyone” as a customer definition. A customer segment should be specific enough to research and reach. Explain what evidence you have, what it suggests and what it cannot prove.
Illustrative example — not a client result: a hypothetical repair business is considering scheduled maintenance for small offices. Its draft plan distinguishes owners who want predictable visits from customers who only buy emergency repairs. The owner still needs evidence about purchasing decisions and demand; a neat customer description does not establish a market.
3. Connect the offer to the operating model
Define what you will sell, what is included and how it reaches the customer. Then describe the work required to deliver it. Consider people, supplier availability, equipment, capacity, quality checks and handovers. A sales target that requires more work than the business can perform is an unresolved constraint, not a convincing forecast.
Record responsibilities as well as activities. If the same owner is expected to sell, deliver, invoice and manage every new customer, show that dependency explicitly. If an important permit, lease or contract remains unconfirmed, identify the need for appropriate specialist advice before commitment.
4. Make the numbers traceable
Financial assumptions should show their basis. Build revenue from plausible quantities and prices, then identify direct costs, regular overheads, one-off expenditure and the timing of receipts and payments. Separate existing records from estimates. State whether figures include or exclude GST and obtain accounting or tax guidance where needed.
Try a cautious operating scenario alongside the baseline. What happens if work starts later, a customer takes longer to pay or a supplier quote changes? The aim is to expose dependencies. Avoid adding detail merely to make uncertain estimates look precise.
5. Record risks and actions
A risk section should lead to something the owner can do. For each important uncertainty, record the evidence needed, the person responsible and the decision it affects. Some risks can be investigated; others need a contingency or an explicit limit on the resources you are willing to commit.
Turn the selected direction into a short action table. Include responsibilities, dependencies and a review point. Keep targets and forecasts distinct: a target expresses an ambition, while a forecast reflects current assumptions. Comparing actual progress with the forecast helps identify what needs updating.
6. Write the summary after the detail
Once the sections agree, write a concise summary of the business, intended customer, proposed offer, resources and next decision. Check that the summary does not promise more than the underlying analysis supports. Keep previous versions so you can see what changed and why.
At the next review, ask which assumptions proved useful, which were wrong and whether the plan still supports the decision. A plan does not need to be flawless to be useful; it needs to be honest about uncertainty and easy to update.