#Why a Feature List Doesn't Work as a Business Plan Roadmap
Many business plan development roadmaps take the form of listing 'Feature A → Feature B → Feature C' in chronological order. The fundamental problem with this structure is that it shows 'what to build' but does not explain 'why in that order' or 'what assumptions support that timeline.'
Lean Startup research distinguishes business model hypotheses into value hypotheses (does this product create value for the customer?) and growth hypotheses (is that value scalable?), and holds that these two hypotheses determine the fate of the company. Because a feature-list roadmap states neither the value hypothesis nor the growth hypothesis, readers are left to guess the logical rationale behind each development stage.
#What the Hypothesis · Milestone · Validation Metric Three-Layer Structure Means
The core of the BML cycle is building a Build-Measure-Learn feedback loop. Translating this loop into a business plan roadmap means answering three questions for each development stage.
| Component | Question | Role in the Business Plan |
|---|---|---|
| Hypothesis | What customer behavior or business assumption does this feature validate? | States the rationale for development priority |
| Milestone | What is the completion criteria for this stage and when is it achieved? | Demonstrates schedule specificity and measurability |
| Validation Metric | What number confirms whether the hypothesis is right or wrong? | Pre-defines the decision criteria, increasing the credibility of the plan |
A Lean Startup case study on Cardoc (Journal of Korea Venture Business Research, 2016) explicitly states that you must first find the value hypothesis, validate it with an MVP, and then scale rapidly once product-market fit is confirmed. This sequence directly connects to the logic of stage ordering in the roadmap.
#The Process for Converting a Feature List into a Three-Layer Structure
When converting an existing feature list into a three-layer structure, following the steps below naturally reveals the rationale for each stage.
- Pull out your existing feature list. 'What to build and when' is your starting point.
- Next to each feature, write 'What can't I learn if this feature doesn't exist?' This becomes the draft hypothesis.
- Re-order the features according to the sequence in which the hypotheses need to be answered. The correct stage order is one where a downstream hypothesis becomes meaningless if the upstream hypothesis hasn't been validated first.
- Write the completion time and completion criteria for each stage as a concrete number. Write it in a measurable way — not 'development complete' but 'the week when a specific user count or number of actions is recorded.'
- Choose 1–2 key metrics that confirm or disprove the hypothesis at each stage. Selecting key metrics for effective measurement is an essential element of the BML cycle.
- Place the completed items in a table format in the business plan.
#Example of Writing a Completed Roadmap Entry
Below is an example of the first three stages of a B2B SaaS service written in the three-layer structure. The three columns — hypothesis, milestone, and validation metric — connect logically within a single row.
| Stage | Hypothesis | Milestone (Completion Criteria) | Validation Metric | Target Date |
|---|---|---|---|---|
| Stage 1 | If we automate Task X that the core customer segment handles manually, weekly usage frequency will increase | Deploy Task X automation feature + complete onboarding of 20 beta companies | Weekly active user (WAU) rate of 60% or more within 30 days | Month 4 from launch |
| Stage 2 | If WAU is stable, willingness to pay for a paid plan will emerge even without additional features | Publish paid plan page + close first 5 paid contracts | Paid conversion rate of 15% or more among beta users | Month 7 from launch |
| Stage 3 | Referrals from paying customers can become the primary acquisition channel | Run referral program + build tracking system for referral-driven new sign-ups | Referral channel share of new acquisitions at 30% or more | Month 11 from launch |
In this structure, Stage 2 only becomes meaningful once Stage 1's hypothesis (stable WAU) has been validated first. The key point is that the stage order reflects the dependency relationships between hypotheses.
#How to Use the Three-Layer Structure in the Pre-Startup Package Format
The Korea Startup Promotion Agency's Pre-Startup Package is a program that supports prospective founders with innovative tech startup ideas during their pre-launch preparation phase, providing differentiated funding through interim evaluations at each stage. This structure itself aligns closely with stage-by-stage hypothesis validation.
In the 'commercialization plan' or 'development schedule' section of the business plan, you can place the three-layer structure table directly instead of listing features. However, the completion criteria for each milestone must be linked to the interim evaluation schedule. If the business plan specifies in advance what each pre-evaluation stage was trying to validate and by which metric it will be judged, the execution rationale for the plan becomes clear.
#Points Easy to Miss When Writing a Roadmap with AI Tools
Text generation tools can restructure a feature list into plausible-sounding sentences, but they cannot reliably maintain the dependency relationships between stage hypotheses across the entire document. Even if a generated roadmap formally follows the three-layer structure, you need to verify directly that each stage's hypothesis genuinely depends on the validation results of the preceding stage.
OpenSeed is not a tool that writes your business plan for you — it is a feedback tool that lets you check, before submission, where the weaknesses in your rationale, numbers, and logic are, and what to fix first, from multiple reviewer perspectives. When a roadmap has weaknesses in its stage order or hypothesis dependency chain, that is the context where this tool is most useful.
Sources
- Applying the Lean Startup Methodology: A Case Study of South Korea's 'Cardoc' — Asia-Pacific Journal of Business Venturing and Entrepreneurship, Korea Venture Business Association (Vol. 11, No. 5, No. 47, pp.29-43), 2016-10 (retrieved: 2026-11-17)
- Journal of Korea Venture Business Research Vol. 18, No. 5 (No. 89) — Lean Startup Application Case Study of a Hardware Startup — Asia-Pacific Journal of Business Venturing and Entrepreneurship, Korea Venture Business Association (Vol. 18, No. 5, No. 89), 2023 (retrieved: 2026-11-17)
- Korea Startup Promotion Agency — Pre-Startup Package Program Guide — Korea Startup Promotion Agency (KISED), Not verified (retrieved: 2026-11-17)
Check the Hypothesis-Milestone Links in Your Roadmap
Paste your roadmap into your business plan and check from multiple reviewer perspectives where the weaknesses in your rationale, numbers, and logic are.
Pre-submission business-plan review with clear service limitations
Start OpenSeed Review →