Symptom: Problem block reads like a feature list.
Cause: Solution leakage: problem notes mention your app or solution.
Fix: Rewrite problems as customer pains only. No 'they need an app'; use 'they struggle to X'.
Title, meta description, canonical, OG, Twitter, BreadcrumbList, FAQPage, WebApplication schema.
This is Ash Maurya's Lean Canvas (9 blocks). Not the Business Model Canvas. Create a testable one-page plan with quality checks, riskiest assumptions, and next-step experiments.
No login. Autosave in browser. Shareable URL.
Step 1
Choose Wizard mode for a guided 15-minute pass block by block, or Canvas mode to edit the full 9-block board. Add notes with title, details, Top 3, and Assumption/Validated plus evidence.
Step 2
Use the Quality checks panel to fix solution leakage in Problem, weak UVP, unlinked solutions, vanity metrics, and economics. Use the Assumptions panel to tag risks and get suggested next tests.
Step 3
Save History snapshots, export CSV/Markdown/JSON/PNG/PDF, share a URL, or import from CSV. Revisit and validate as you learn.
The Lean Canvas is Ash Maurya's one-page business model for early-stage startups. It has 9 blocks: Problem, Solution, Unique Value Proposition, Unfair Advantage, Customer Segments, Key Metrics, Channels, Cost Structure, and Revenue Streams. Use it when you are hypothesis-driven and pre or early product: to force clarity on problems, solution fit, and economics. It works best before you scale execution, so you can test riskiest assumptions and update the canvas as you learn.
Solution-first: Filling Problem with your product idea instead of customer pains. Vanity metrics: Focusing on followers or pageviews instead of activation and revenue. Fake unfair advantage: Saying "hard work" or "first mover" without a defensible asset. Channel-segment mismatch: Enterprise segment with only social channels. Use the Quality panel to catch these and fix before you scale.
Tag assumptions (desirability, viability, feasibility). Run customer interviews for desirability; landing page or smoke tests for problem interest. Run pricing or willingness-to-pay for viability. Run technical spikes or prototype tests for feasibility. Move notes to Validated when you have evidence. Revisit the canvas weekly and update Top 3 and links as you learn.
Symptom: Problem block reads like a feature list.
Cause: Solution leakage: problem notes mention your app or solution.
Fix: Rewrite problems as customer pains only. No 'they need an app'; use 'they struggle to X'.
Symptom: UVP is long and generic.
Cause: Trying to say everything; no segment or outcome.
Fix: One sentence, under 140 chars. Include segment, need, and outcome. Test with: 'So what?'
Symptom: Solution notes don't map to problems.
Cause: Filling blocks in isolation.
Fix: Link each solution to at least one problem. Use Quality panel to find unlinked problems.
Symptom: Key metrics are vanity metrics.
Cause: Choosing metrics that look good but don't predict success.
Fix: Prefer activation, retention, revenue, conversion. Justify if you keep a vanity metric.
Symptom: Channels don't fit the segment.
Cause: Copying others' channels (e.g. TikTok for B2B).
Fix: Match channel to how your segment discovers and buys. Enterprise: sales, events, LinkedIn.
Symptom: Unfair advantage is 'we work hard'.
Cause: No defensible asset.
Fix: Use data, IP, exclusive access, community, or expertise that others can't easily replicate.
Symptom: Revenue filled, costs empty (or vice versa).
Cause: Avoiding economics.
Fix: Fill both. Stress-test: can you be profitable at the scale you're targeting?
Symptom: Canvas never validated.
Cause: Treating the canvas as a one-time doc.
Fix: Tag assumptions, run interviews and tests, move notes to Validated with evidence. Revisit weekly.
This is Ash Maurya's Lean Canvas: the 9-block one-page plan for startups (Problem, Solution, UVP, Unfair Advantage, Customer Segments, Key Metrics, Channels, Cost Structure, Revenue Streams). It is not the Business Model Canvas, which has different blocks and a broader focus. The Lean Canvas is designed for early-stage, hypothesis-driven validation.
Use it when you are validating a new product or pivot: before or right after building. It forces you to name problems, link solutions, and stress-test economics. It works best in the first 15 minutes with Wizard mode, then refine in Canvas mode. Revisit when you have new evidence from interviews or experiments.
The Quality panel flags: missing Top 3 for Problem (and Segment, Metrics); solution-language in the Problem block; UVP too long or too generic; top problems with no solution linked; vanity metrics; channel-segment mismatch; weak unfair advantage; and revenue without costs or costs without revenue. Each warning includes a fix suggestion.
All notes marked Assumption are collected and ordered by block priority (problem, UVP, metrics, channels, etc.). You can tag each as desirability, viability, or feasibility risk. The tool then suggests next tests: desirability (interviews, landing page), viability (pricing, pre-orders), feasibility (spike, prototype). Rule-based, no AI required.
Yes. Export CSV (notes + metadata), Markdown (stakeholder-ready with blocks, assumptions, next tests), JSON (full state), and PNG. Print or save as PDF via the browser. Import from a CSV with headers: block, title, details, priority, status, evidence, links_to. A template is available for download.
History lets you save snapshots of your canvas with a short note and timestamp. You can restore a previous snapshot to compare or roll back. Snapshots are stored locally in your browser and are not sent to our servers. They are not included in the share URL to keep it small.
Yes. The tool is free, runs in your browser, and requires no login. You can use Wizard and Canvas modes, load examples, run quality checks, export and share, and save history. Autosave uses local storage; we do not store your canvas on our servers.
Wizard walks you through the blocks in a recommended order: Customer Segments and Early Adopters, then Problem and Alternatives, then UVP and High-level concept, Solution, Channels, Key Metrics, Revenue and Cost, Unfair Advantage. Each step has a short explanation, two examples, and one common-mistake warning. At the end you see quality summary, riskiest assumptions, and suggested next tests.
Yes. In Canvas mode you can link solution notes to problem notes. The Quality panel checks that each Top 3 problem has at least one solution linked. Linking is used for the solution-mapping check and for exports (CSV links_to, Markdown).
Use the Value Proposition Canvas for customer-job and value-map fit; the Problem Statement Generator for a concise problem frame; the JTBD Statement Generator for job stories; and the Interview Script Generator for discovery. The Lean Canvas ties problem, solution, and business model in one place. Feed interview insights into Problem and Customer Segments, then validate with next tests.
Use CraftUp to connect discovery, validation, and execution.
Last updated: 2026-03-05