The Lean Canvas sums up a product idea in nine blocks: problem, customer segments, unique value proposition, solution, channels, revenue streams, cost structure, key metrics and hard-to-copy advantage. It is built for those who still have more assumptions than certainties: instead of a long business plan, one page that shows what must be true for the business to work and what to test first.
How to use
- Name the product and describe the customer segments and, if you know them, the early adopters.
- List up to three top problems and how the customer solves them today.
- Write the unique value proposition as one short sentence and the smallest solution for each problem.
- Fill in channels, revenue, costs, key metrics and, if there is one already, the hard-to-copy advantage.
- Read the warnings and the list of assumptions, and export as PNG, PDF, Markdown or CSV.
What each field asks for
| Field | What to enter |
|---|---|
| Product or idea | A working name is enough. |
| Customer segments | Who it is for. Separate who uses from who pays, if they differ. |
| Early adopters | Optional. Who feels the problem most and would use it first. |
| Top problems | Up to three is ideal, from most to least severe. |
| Existing alternatives | Optional. How the customer solves it today, even badly. |
| Unique value proposition | One sentence that says why you are different and worth attention. |
| Solution | The minimum features that tackle each problem. |
| Channels | How you reach customers. |
| Revenue streams | How the product makes money. |
| Cost structure | What it costs to run and grow. |
| Key metrics | The numbers that show whether the model works. Favour rates and behaviours. |
| Hard-to-copy advantage | Optional. What a competitor cannot buy or copy quickly. Empty is normal early on. |
Example
A fictional booking product for independent restaurants lists three problems, with no-shows first, and two existing alternatives (a booking notebook and commission-based platforms). The unique value proposition has 16 words and passes the check. Of the three key metrics, "app downloads" gets the possible vanity metric warning; the no-show rate and the tables filled from the waiting list pass. The tool lists five assumptions to test, starting with "the problem of diners who book and do not show up happens often and hurts enough to look for another solution".
When to use
- At the start of an idea, to put the business assumptions on one page before building.
- To compare two or three versions of the same business (different segments or revenue) side by side.
- Before a conversation with investors or the board, to show what has been validated and what is missing.
- In the periodic product review, to update what changed after the tests.
Frequently asked questions
What is the Lean Canvas?
It is an adaptation, created in the late 2000s for start-ups, of the nine-block business model board. It swaps blocks aimed at established companies (partners, activities and resources) for problem, solution, key metrics and hard-to-copy advantage. This tool uses its own layout.
How is it different from the traditional business model board?
The traditional one describes a company that already works, with partners, resources and activities. The Lean Canvas starts from uncertainty: it begins with the problem and the customer and highlights what needs testing. Many teams use the Lean Canvas during discovery and the traditional one once the business settles.
Where should I start?
With customer segments and problems, together: a problem only exists for someone. Then the unique value proposition, and only then the solution. Revenue, costs and metrics complete the board.
What is a vanity metric?
It is a number that only goes up and makes the product look good without helping you decide, such as cumulative downloads or followers. Favour rates and recurring behaviours, such as conversion, retention or weekly use. The tool warns you when a metric looks like vanity.
What if I have no hard-to-copy advantage?
That is normal at the start. A hard-to-copy advantage usually comes with time: accumulated data, community, network effects, specialist knowledge. Leave the block empty and come back to it once the product has usage.
How often should I update it?
After every testing cycle. When an assumption is confirmed or disproved, the matching block changes. Keeping the versions helps tell the story of how the business evolved.
Does it work for a product inside a large company?
Yes. Swap "investor" for "whoever approves the budget" and use the board to show the problem, the segment and the metrics that will prove the value. Internal costs, such as team hours, go into the cost structure.