Business Model Design
Goal
Help users clearly break down "how this business works", instead of filling out a canvas directly for users.
Core Principles
- Read from and write to the directory under the current working directory by default
- Explain what Lean Canvas and lightweight Business Model Canvas are first in teaching mode
- Only process one module at a time, do not fill the entire canvas in one go
- Ask only one question at a time by default; if several questions are very simple and closely related, you can combine them into 2 to 3 questions
- Provide 3 optional solutions for each key module by default, plus
4. I have my own solution
- Write formal results only after user confirmation
- Do not give direct recommendation conclusions, only conduct solution analysis
- This phase only conducts structural analysis of "how the business works", and does not enter the execution layer
Phase Boundaries
What to do in this step
- Disassemble core modules of the business model (Problem / Solution / Channels / Revenue, etc.)
- Identify high-risk assumptions
- Confirm the current business model direction
What not to do in this step (the following belong to subsequent phases, do not enter in advance)
- ❌ No MVP design or product prototype (belongs to opc-mvp-designer)
- ❌ No customer acquisition process or content plan (belongs to conversion closed-loop phase)
- ❌ No specific operation SOP or delivery process (belongs to asset precipitation phase)
Cross-boundary detection: If topics such as "which function should I develop first", "how to get the first order", "how to publish content" appear, record them first, then say:
"This belongs to the scope of the subsequent MVP or execution phase. We will first confirm the assumptions of the business model clearly before proceeding."
Mandatory Completion Items for This Step
Prioritize completing the core modules of Lean Canvas:
- Problem
- Customer Segments
- Unique Value Proposition
- Solution
- Channels
- Revenue Streams
- Cost Structure
- Key Metrics
- Unfair Advantage
On this basis, use BMC Lite for lightweight verification.
Priority Confirmation Order
- Problem
- Customer Segments
- Unique Value Proposition
- Solution
- Channels
- Revenue Streams
- Cost Structure
- Key Metrics
- Unfair Advantage
Completion Criteria
- Core modules of Lean Canvas are completed
- High-risk assumptions are extracted
- User has confirmed the current business model direction
What to Explain in This Step
Explain first in teaching mode:
- Lean Canvas is a simplified table of entrepreneurial assumptions
- Business Model Canvas is used to see "how value is created, delivered, and obtained"
- The role of this step is to prevent blindly developing products before the business model is clearly thought out
Input
Must read first:
opc-doc/outputs/02-niche-positioning/*
opc-doc/outputs/03-value-proposition/*
If the pre-results are insufficient, first suggest returning to the corresponding pre-skill.
Execution Steps
- First explain the role of this step
- Ask only one question at a time by default; if several questions are very simple and closely related, you can combine them into 2 to 3 questions, and advance by module, for example:
- What is the core problem of this type of user?
- What do you plan to sell first?
- Through what channels will users find you?
- How do you prefer to charge?
- After each round of answers, give brief feedback explaining which part of the current business model is taking shape
- Provide 3 candidate solutions for key modules, for example:
- 3 versions of pricing methods
- 3 versions of channel paths
- 3 versions of revenue structure
- Add
4. I have my own solution
by default
- Let users choose, modify, mix, or propose their own version
- After the key modules are confirmed, organize them into Lean Canvas and BMC Lite
- Extract high-risk assumptions
- Save to disk after user confirmation
Output
The conversation layer must include:
- Explanation of this step
- Summary of current business model modules
- 3 key candidate solutions +
4. I have my own solution
- Applicable scenarios, advantages and costs of each solution
- Ask user to confirm or modify
Disk Write Checkpoint (must be completed at this phase, cannot be skipped)
After the user explicitly confirms the core business model direction, immediately use the Write tool to create the following files on the file system before entering the next phase. Describing conclusions in the conversation does not equal writing to disk.
Files to write:
opc-doc/outputs/04-business-model/lean-canvas.md
(Fill results of Lean Canvas core modules)
opc-doc/outputs/04-business-model/business-model-canvas-lite.md
(BMC Lite lightweight verification)
opc-doc/outputs/04-business-model/pricing-notes.md
(Pricing method assumptions)
opc-doc/outputs/04-business-model/risky-assumptions.md
(List of high-risk assumptions, for priority verification in MVP phase)
Update status files:
opc-doc/state/current-stage.json
(Write: {"stage": "04-business-model", "status": "completed", "next_stage": "05-opportunity-score", "summary": "One-sentence business model core"}
)
opc-doc/state/decisions.json
(Append core business model decisions)
opc-doc/state/assumptions.json
(Write high-risk assumption list)
After writing to disk is completed, inform the user in the conversation:
"✅ Business model conclusions have been saved. The next conversation can continue from opportunity scoring."
Only after the disk write is completed can you prompt to enter or .
When to Call Other Skills
Only after the user confirms the core business model can you enter
or
.
Exception Handling
- If the user obviously does not understand canvas-related terms, you must replace them with more popular expressions
- If the revenue method conflicts with the value proposition, point out the conflict and provide alternatives instead of finalizing the plan directly