A lean canvas is a way of describing a business idea on one page, in nine boxes: from the customer's problem to what competitors can't copy. It was created by Ash Maurya, who adapted Alexander Osterwalder's well-known Business Model Canvas to the needs of new products. Instead of dozens of pages of business plan you get one page that you can fill in within an hour and change after every conversation with a customer.
A lean canvas isn't an end in itself. Its job is to show which assumptions are the riskiest, so you know what to test first.
The nine boxes of a lean canvas
| Box | The question it answers |
|---|---|
| 1. Problem | What 1–3 problems does the customer have? How do they cope with them today? |
| 2. Customer segments | Who has this problem? Who are the first customers (early adopters)? |
| 3. Unique value proposition | One sentence: why is this different and worth attention? |
| 4. Solution | The simplest solution to each problem. |
| 5. Channels | How will you reach customers? |
| 6. Revenue streams | What does the customer pay for, and how much? |
| 7. Cost structure | What does it cost to build and run the product and to acquire a customer? |
| 8. Key metrics | How will you know it's going well? |
| 9. Unfair advantage | What can't easily be copied or bought? |
Compared with the Business Model Canvas, Maurya replaced the boxes about partners, key resources, activities and customer relationships with boxes about the problem, the solution, metrics and the advantage. A new product doesn't have partners or processes yet. What it has is a lot of uncertainty about the problem and the customer.
In what order to fill it in
The numbers in the table aren't accidental. Start with the customer and the problem, not with the solution.
1–2. Problem and customers together. These boxes depend on each other. List the most important problems of one specific group and how they solve them today (a spreadsheet, the phone, a competing programme, nothing). The current workaround is your real competition.
3. Value proposition. One sentence that someone from this group will understand. Not "an innovative AI-based platform", but "appointment reminders that send themselves, with no need to phone patients".
4. Solution. Deliberately only in fourth place and brief. At this stage three bullet points are enough. The details will change after the first conversations.
5. Channels. Where these people already are: search, industry groups, trade shows, referrals, direct sales. Think about which channel will bring the first 10 customers, not a thousand.
6–7. Revenue and costs. Enter numbers, even rough ones: the price, the cost of building the first version, the cost of running it, how much you'll spend to acquire one customer. If these two boxes don't add up, it's better to know now.
8. Key metrics. One or two numbers that really say something about progress: for example, the number of clinics that still use the reminders after a month. More on what to measure in the topic on the lean startup methodology.
9. Unfair advantage. The hardest box. Often it stays empty at the start, and that's fine. "A good team" or "first-mover advantage" usually isn't an advantage. An advantage can be access to data, a community, industry knowledge that can't be quickly acquired.
Example: a reminder app for clinics
An idea made up for the sake of the example.
| Box | Content |
|---|---|
| Problem | Patients forget about appointments. The front desk wastes time phoning with reminders. Empty slots are lost revenue. |
| Current workaround | Manual calls and texts from a private phone, notes in a calendar. |
| Customer segments | Small clinics (1–3 treatment rooms) without an extensive system. First customers: clinics that already complain about no-shows. |
| Value proposition | Appointment reminders send themselves, and the patient confirms or reschedules with one click. |
| Solution | Calendar import, automatic SMS and email, a link to confirm or change the appointment. |
| Channels | Industry groups, search ("SMS reminders for a clinic"), referrals between clinics. |
| Revenue | A monthly subscription depending on the number of treatment rooms. |
| Costs | Building the first version, the cost of SMS, hosting, time to acquire the first customers. |
| Key metrics | Share of clinics still active after 30 days, drop in no-shows among customers. |
| Unfair advantage | None for now. A candidate: integrations with popular clinic software. |
The riskiest assumption in this example: will clinics pay monthly for reminders, given that some clinic management software includes them in the package. That is exactly what has to be tested first, for example with conversations and a pricing page, before an MVP is built.
The most common mistakes
Filling it in for everyone at once. "Companies" or "young people" isn't a segment. If you have several groups, make a separate canvas for each.
Starting with the solution. Then the problem gets written in to fit a ready-made idea. Problem first, even if you already have an app in your head.
Empty numbers in revenue and costs. An estimate to the right order of magnitude is better than "to be determined". This is where it most often becomes visible that an idea doesn't add up.
A canvas filled in once and put away. It's a working document. Update it after every test and conversation, and keep the old versions so you can see what you've learned.
No marked risks. After filling it in, mark 1–2 boxes where you are least sure. That's your list of things to check in the first turn of the loop.
Tools
A sheet of paper, a whiteboard or a spreadsheet with nine boxes is enough. There are also free templates online. The tool doesn't matter: what matters is that the canvas is short, specific and changed often.
Once you know which assumption to test and you need a working app for it, see how I build an MVP: a fixed price, 2–6 weeks.