View contents
Article
Startup Guide

How to Write a Product Roadmap in a Business Plan — Hypothesis · Milestone · Validation Metric Three-Layer Structure

2026.11.17·7 min·OPENSEED
MENTORING KNOWLEDGE FORProduct MentorChief Analyst

A product roadmap in a business plan should not be a list of features to be built — it should be written as a three-layer structure of hypothesis · milestone · validation metric that shows what you intend to validate at each stage. Listing features month by month produces a schedule with no answer to 'why that feature first?', erasing the logical rationale behind the plan. This three-layer structure comes from the Lean Startup's BML (Build-Measure-Learn) cycle, which ties a rationale and measurement criteria to each development stage.

Intro.

#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.

TIP
A hardware startup failure case study (Journal of Korea Venture Business Research, 2023) points out that when a startup fails to formulate its idea as a concrete customer value hypothesis in the early stages and fails at MVP experimentation, development continues without ever building a BML cycle.
02

#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.

ComponentQuestionRole in the Business Plan
HypothesisWhat customer behavior or business assumption does this feature validate?States the rationale for development priority
MilestoneWhat is the completion criteria for this stage and when is it achieved?Demonstrates schedule specificity and measurability
Validation MetricWhat 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.

03

#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.

  1. Pull out your existing feature list. 'What to build and when' is your starting point.
  2. Next to each feature, write 'What can't I learn if this feature doesn't exist?' This becomes the draft hypothesis.
  3. 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.
  4. 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.'
  5. 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.
  6. Place the completed items in a table format in the business plan.
04

#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.

StageHypothesisMilestone (Completion Criteria)Validation MetricTarget Date
Stage 1If we automate Task X that the core customer segment handles manually, weekly usage frequency will increaseDeploy Task X automation feature + complete onboarding of 20 beta companiesWeekly active user (WAU) rate of 60% or more within 30 daysMonth 4 from launch
Stage 2If WAU is stable, willingness to pay for a paid plan will emerge even without additional featuresPublish paid plan page + close first 5 paid contractsPaid conversion rate of 15% or more among beta usersMonth 7 from launch
Stage 3Referrals from paying customers can become the primary acquisition channelRun referral program + build tracking system for referral-driven new sign-upsReferral channel share of new acquisitions at 30% or moreMonth 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.

05

#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.

주의
The Pre-Startup Package targets prospective founders who are not yet registered as a business entity (sole proprietor or corporation) as of the announcement date. Commercialization funding is up to KRW 80 million, with differentiated stage-based funding through interim evaluations. For the 2026 announcement's detailed evaluation criteria and scoring, refer directly to the attachment in the official announcement.
Summary.

#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

Advertisement

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 →

관련 AI 피드백 서비스.

AI 피드백
사업계획서 AI 추천 →
AI 피드백
사업계획서 피드백 →
AI 피드백
예비창업패키지 점검 →
RELATED · Related pagesStartup Guide
Validating Startup Ideas — Confirming Demand with Customer Interviews and an MVP2026.06.25 · 8 minMicro-Business Support vs. Startup Track — How to Decide Which Channel Fits Your Business2026.10.05 · 7 minFirst 3 Months After Incorporating: Tax, Insurance & Corporate Account Admin Checklist2026.11.05 · 7 min4 Written Agreements Before Finding a Cofounder2026.10.30 · 6 minBusiness Plan BEP — Answer 'When Do We Break Even?' Not Just Show the Formula2026.10.21 · 6 min
← Back to Wiki