How to Write a Business Plan That Wins: 5 Principles From 15 Years of Building Pitch Documents

You included the market analysis, the product description, the revenue forecast and the execution plan, and the plan still didn't get through. A consultant who has structured business plans, proposals and pitch decks for 15 years argues the problem usually isn't missing content. Putting everything your company knows into a document is different from structuring it so an evaluator can make a decision. The core of how to write a business plan is whether claims, evidence and execution conditions connect in one line of reasoning.

Problem → Customer → Solution → Market & competition → Evidence → Revenue model → Execution plan → Resources → Risks & responses

1. Show the problem before the product

The evaluator's first question is "Why does this business need to exist?" Instead of listing features, follow customer → recurring problem → limits of current solutions → what's needed → your product.

Start with decision questions, not a table of contents

• Who will read this document?
• What do they need to decide?
• What must the document answer?
• Where will they have doubts?

Write each page's conclusion in one sentence first. It clarifies which evidence you need and what to cut.

2. Give evidence, not just potential

"Strong market potential" and "a competitive edge" don't let reviewers reach your conclusion on their own. Use verifiable evidence: addressable customer counts, interviews, inbound inquiries, test sales, signed or pending contracts. Show competitiveness on comparable criteria such as price, performance, lead time, scope and adoption requirements.

• Keep claim → evidence → judgment close together.
• Separate verified facts from assumptions, and attach calculation logic and a validation date to each assumption.
• For market-size figures, state the source, base year, scope and whether it's the total or the reachable market.

3. Connect revenue to execution

If your target is 1 billion won in annual revenue, how you get there matters more than the number.

• Customers × average contract value × purchase frequency = revenue target
• Prospects × conversion rate × average price = revenue target

That math has to match the execution plan: the sales activity needed, the people to do it, development time and cost, and, for public-sector buyers, procurement timelines. Market → customers → sales → contracts → revenue → headcount → cost → timeline should read as one story.

4. Charts must prove a conclusion

Before adding a chart, ask: "If I delete this, is my conclusion harder to prove?" If not, it's decoration. Structure each page as conclusion → key evidence → supporting numbers or visuals, and move detailed stats and raw data to an appendix.

5. Review with counter-questions

Check for gaps and contradictions before typos and design.

• Is there another explanation for this conclusion?
• What if customer acquisition is slower than planned?
• Can a reader recalculate the revenue from what's in the document?
• How does a development delay affect the revenue plan?
• Are achieved results clearly separated from future targets?

Ask a colleague reading it for the first time to explain why the business can work, and write a one-sentence "what did I learn" for each page. Rather than hiding weaknesses, state what's confirmed, when the rest will be confirmed and how you'll respond if results differ.

Why this matters beyond business plans

The same logic applies to grant applications, investor decks and B2B proposals. Agency pitches, too, land faster when they move from the client's problem to evidence, execution, cost and expected results.

If you're using AI to generate customer evidence, read Can AI Synthetic Respondents Replace Market Research? first. For how B2B buyers evaluate vendors before the first meeting, see B2B Buyers Start Researching 124 Days Before Talking to Sales.