Key Principle
The Product Plan is a versioned roadmap extending beyond the MVBP that charts feature expansion and adjacent-market entry along two axes: (1) functional capability per version and (2) new target markets each version unlocks. It translates the Follow-on Market TAM (Step 14) into concrete product versions, connecting ambition to execution (Step 24).
Why This Matters
Without a Product Plan, teams either stagnate in the beachhead or expand chaotically into markets their Core cannot serve. The beachhead becomes a ceiling rather than a launchpad. Competitors who planned ahead capture adjacent segments first. The Product Plan ensures expansion is considered and sequenced, not ad hoc (Step 24).
Two Expansion Axes
Axis 1 -- Capability expansion. Each product version adds features deferred during MVBP construction. Features are re-ranked based on real customer data from the feedback loop, not the founder's original vision. "Some originally prioritized features may prove less important than features not initially considered" (Step 24).
Axis 2 -- Market expansion. Each version unlocks adjacent markets. The next market's product may be (a) totally different, (b) significantly modified, (c) repackaged, or (d) unchanged -- determined entirely by the new Persona's needs (Step 24).
Beachhead Dominance Triggers
Two thresholds must be met before expanding to the next bowling pin (Step 24):
- Dominant market share -- generally 20% or more of the beachhead.
- Cash-flow positive status -- the beachhead sustains itself financially.
Moving before these thresholds splits focus and burns capital on a second front before the first is won. Each subsequent market requires a different Persona but must leverage the startup's Core (Step 24).
Feature Re-Prioritization from Real Data
The MVBP deliberately defers many features. After validation, the Product Plan selects which to reintroduce based on evolved understanding from customer feedback. Without this re-ranking, teams default to building the founder's original vision rather than what customers actually demonstrated they value (Step 24).
Quality-Release Protocol
New features require marketplace refinement. Prioritizing release speed over quality causes quality problems to compound. This is a cultural decision, not a technical one -- the protocol must be embedded in development culture, not bolted on after failures (Step 24).
Bowling Pin Sequencing
Adapted from Geoffrey Moore: the beachhead is the lead pin whose fall topples adjacent pins (Steps 2, 14, 24). Each adjacent pin can itself sprout upselling pins (Step 14). The causal chain:
- MVBP validated in the beachhead.
- Deferred features revisited and re-ranked by real Persona data.
- Product Plan versions built, each unlocking adjacent markets.
- TAM expands systematically along both axes.
The Planning Paradox
"Plans are nothing; planning is everything" (Eisenhower, cited Step 24). The Product Plan will change. Its value is in forcing consideration of possibilities, obstacles, and growth trajectory -- not in rigid adherence. Over-investing in future-market planning diverts execution capacity from proving the current product works. The explicit failure mode is running out of money before the beachhead is won (Step 24).
The Over-Planning Trap
The plan must stay lightweight. Real customer data from the beachhead will invalidate initial assumptions about which adjacent markets to target. The plan's value is ensuring expansion is considered, not that the specific path is correct. "Having no plan puts yourself in the hands of luck as opposed to your own methodical process" (Step 24).
SensAble Technologies Example
Two-axis expansion chart -- X: Form Types (Sculptural, Regular, Stylized); Y: Downstream Connection (Rapid Proto, NURBS, Polys) (Step 24):
- V1 (Beachhead): Toy/footwear; sculptural forms; .stl output.
- V2: Jewelry market; same Core, market-specific refinements.
- V3: Added geometric forms + NURBS export -- industrial design markets + CAD/CAM packages.
- V4: Added polygon format support -- DCC market (3D animation).
- V5: Ubiquity vision -- full coverage of all form types and connection formats.
Each version's coverage area grows along both axes, with target segments mapped as overlapping regions.
Scope Boundary
The 24-step framework delivers rock-solid product-market fit at initial launch. It does not cover culture, team building, sales execution, customer service, financials, fundraising, leadership, or governance. These are scaling competencies, not product-market fit competencies (Postlude).
Related References
- bowling-pin-strategy -- Beachhead-to-adjacent-market sequencing logic (Steps 2, 14).
- follow-on-tam -- Calculating expansion market size and the $1B trajectory test (Step 14).
- mvbp-design -- The MVBP that precedes and feeds the Product Plan (Step 22).
- core-competitive-position -- The Core that must be leveraged across all expansion markets (Steps 10-11).