Practical editorial guidance, not a promise of income or a hands-on product benchmark. Links are standard, non-affiliate links on this site. Read our editorial approach.

A working business plan is a set of decisions you can inspect. It should make it easier to act, notice what happens, and change course when your assumptions turn out to be wrong.

For an early idea, try a single page before building a long document. This is a practical planning format, not a substitute for formal documents a lender, investor, regulator, or other party may require.

1. Name the customer and the situation

Describe one type of person or business and the moment when the problem matters. “Busy founders” is broad. “A solo consultant receiving enquiries through three different inboxes” gives you something more concrete to investigate.

Add what you know from direct evidence and what you are assuming. Keep the distinction visible instead of filling every blank with a confident-sounding guess.

2. Write the problem in their language

What does the customer struggle to get done? How do they manage it today? Why would changing it be worth the effort? A useful problem statement is understandable without mentioning your preferred software.

Leave space for the exact words people use. They may describe the problem differently from you, or reveal that a different issue matters more.

3. Define the first offer

State the deliverable and the boundary. What does the buyer receive? What is not included? What input, access, approval, or participation do you need from them?

For example: “A map of one enquiry workflow and a prioritized implementation brief” is easier to scope than “AI transformation.” The point is not to make every offer small forever. It is to make the first one understandable and deliverable.

4. Describe how the first people will find it

Choose one realistic route to a relevant conversation: existing professional relationships, a specific partner, a useful article, or a community where participation is welcome. “Go viral” is an aspiration, not an acquisition process.

Write the first action, the intended audience, and the next step you want to offer. Avoid turning every interaction into an unsolicited pitch.

5. Map what delivery requires

List the actual work: preparation, production, review, changes, handover, and support. Name who is responsible. Include dependencies and things that could block completion.

Then ask which parts can be handled with tools you already have. A gap in your process is not automatically a reason to buy a subscription.

6. Record assumptions about money and time

For planning, distinguish your proposed price from money received, and the tool cost from the full effort of delivery. Record estimates as estimates. Do not convert a hopeful sales target into an established forecast.

This page is not personalized accounting, tax, or investment advice. Questions about business structure, obligations, and records need the appropriate qualified guidance for your circumstances.

7. Choose the next test

What uncertainty matters most before you invest more work? State one test, the observation you want to make, and when you will review it. A plan without a next action becomes another place to store the idea.

The point of the page is not to make the idea look finished. It is to make the next question clear.

Revisit the page after doing something real

After a customer conversation, a prototype test, or a pilot, update what changed. Keep a short decision log rather than erasing every previous assumption. It helps you see whether the plan is becoming better grounded or just more elaborate.

Your first version can be rough. It only needs to be clear enough to use.

Turn the read into a next step.

Use the free worksheet to put this into practice. No account or email required.

Get the worksheet

Need a little help applying this? Explore coaching and implementation.