portfolio-canvas

To convert a Lean Canvas into structured portfolio data, provide your canvas markdown file to map sections like Customer Segments and Revenue Streams into structured portfolio entities, storing original context in portfolio.json.

Canvas-to-portfolio translation maps Lean Canvas or Business Model Canvas sections such as Customer Segments and Revenue Streams into Markets, Products, and Features, enabling teams to bootstrap without manual re-entry.

Yes, you can use incomplete canvases. The translation process handles incomplete canvases gracefully with schema-like relationship enforcement and fallbacks, supporting both numbered and named section formats.

Yes, portfolio mapping preserves original context. It stores the original canvas context in portfolio.json to keep hypotheses, UVP, and assumptions visible for future validation workflows.

The best way to generate portfolio entities from a hypothesis document is canvas-to-portfolio translation, which automatically maps canvas sections to markets, products, and features while enforcing schema-like relationships.

When translating a Business Model Canvas, unmapped sections or incomplete data are handled with graceful fallbacks to ensure the portfolio setup workflow continues without failing.