How to Write a One-Page Business Plan (Free Template)

Why 40-Page Business Plans Are Dead

Traditional business plans are a relic from a time when starting a company required a bank loan and a five-year forecast. The bank needed to see that you'd thought about every scenario. Fair enough.

But startups don't work that way. In the early days, everything is uncertain. Your customer might change. Your business model will almost certainly change. Your product will change. Writing a 40-page plan for something that's going to change in three months is a waste of your most precious resource: time.

What you need instead is a forcing function for clarity. Something that makes you answer the hardest questions about your business in the simplest possible language. If you can't explain it simply, you don't understand it well enough.

That's where the one-page business plan comes in. It's not a document for investors - it's a thinking tool for you. It strips away the fluff and forces you to confront what you actually know (and don't know) about your business.

The One-Page Framework - Five Questions

Your one-page business plan answers five questions. That's it. If you can answer these clearly, you understand your business better than 90% of early-stage founders.

1. What is the ONE problem you're solving?

Not three problems. Not "a suite of challenges." One problem. The most common mistake I see in applications is founders trying to solve too many things at once. They think a broader scope makes them more attractive. It doesn't. Specificity is a superpower. Pick the one problem that's most painful for your target customer and own it completely.

Bad: "We help small businesses with their operations." Good: "Australian SaaS founders with 5-20 employees waste 6+ hours a week on manual invoicing and payment chasing."

See the difference? The second version tells me exactly who has the problem, what the problem is, and how big it is. The first version tells me nothing.

2. Who is your customer?

Be brutally specific. "Small business owners" is not a customer - it's a demographic. You need to describe a person you can picture sitting across from you.

Great customer definitions include: what they do for work, how many people are in their company, what tools they currently use, what their day looks like, and why they're underserved by existing solutions.

The tighter your customer definition, the easier everything else becomes - your marketing, your product, your pricing, your go-to-market. You can always expand later. Start narrow.

3. What makes your solution 10x better than what exists?

This is where most founders lead, and it's a trap. Your solution should emerge from your deep understanding of the problem, not the other way around.

That said, you need a clear answer to this question. If your solution isn't 10x better than the current alternative, people won't switch. Switching costs are real - the new thing has to be dramatically better, not just marginally better.

And "what exists" includes doing nothing. For many problems, the current solution is spreadsheets, manual processes, or just living with the pain. Your 10x has to beat that inertia.

4. What does the product roadmap look like?

Keep this simple. Three time horizons: - Next 3 months: What are you building right now? What's the MVP? - Next 6 months: What does the product look like with your first 50 customers? - Next 12 months: What's the vision for the product once you've found product-market fit?

This isn't a commitment. It's a signal that you've thought beyond the first release. Investors and advisors want to see that you have a direction, even if the specifics change.

5. How will you make money?

This is simpler than people make it. Pick a business model: subscription, transaction fee, marketplace commission, usage-based, one-time purchase. Then put rough numbers on it.

How many customers do you need at what price point to hit a meaningful revenue milestone? If the maths doesn't work - if you need a million users at $1/month to be viable - that's important to know now, not after you've built the product.

Common Mistakes - And How to Avoid Them

Mistake 1: Solution-first thinking. Most founders start with "I'm building an app that does X" and work backwards to the problem. Flip it. Start with the problem, validate it obsessively, and let the solution emerge from what you learn. The solution is the least interesting part of your business plan.

Mistake 2: Vague customer definition. "Everyone" is not a target customer. Neither is "millennials" or "small businesses." If you can't describe your ideal customer in a single sentence with specific details, you don't know them well enough. Go talk to more people.

Mistake 3: Solving multiple problems. Every additional problem you try to solve dilutes your focus and complicates your product. The most successful startups I've seen started by solving one problem exceptionally well. They expanded later, from a position of strength.

Mistake 4: Ignoring the business model. "We'll figure out monetisation later" is a red flag. You don't need a perfect model on day one, but you need a hypothesis. If you can't articulate how your business makes money, you don't have a business - you have a hobby.

Mistake 5: Writing it alone. Your one-page plan should be a conversation starter, not a private document. Show it to five people - potential customers, advisors, other founders. Their reactions and questions will teach you more than a week of desk research.

What to Do After You've Written It

Your one-page business plan isn't a static document. It's a living hypothesis that you test and update constantly.

Week 1-2: Show it to 10 potential customers. Don't pitch them - just show them the plan and ask: "Does this resonate? Is this how you'd describe the problem?" Their feedback will sharpen every section.

Week 3-4: Based on customer feedback, update the plan. Your problem statement might change. Your customer definition will almost certainly get more specific. Your solution might need to shift entirely. That's the whole point.

Month 2-3: Start building your MVP while continuing customer conversations. Your one-page plan becomes the north star that keeps you focused. Every feature decision, every marketing decision, every hiring decision should trace back to this document.

Every month after that: Revisit and update. As you learn more, the plan evolves. The problem gets clearer. The customer gets more specific. The business model gets sharper. A one-page plan from month six should look noticeably different from month one - and that's a sign you're learning.

The goal is never to write the perfect plan. The goal is to think clearly about your business. The one-page format forces that clarity in a way that a 40-page document never will.