The Lean Canvas is a one-page strategic template that helps startup founders put their business assumptions on paper in 20 minutes. Ash Maurya created it in 2010, then described it in his book Running Lean, published by O'Reilly in 2012. It replaces the traditional business plan with 9 blocks, from the customer problem to key metrics, which you test and refine as you run customer interviews. According to CB Insights, 42% of startups fail because they build a product nobody needs. The Lean Canvas exists to prevent exactly that: it forces you to think through the problem before you code the solution. Below you'll find a blank template to copy, a method for filling it in, a completed example from a French startup, and the mistakes that leave most canvases stuck as theoretical exercises.
What is the Lean Canvas?
Definition and origin (Ash Maurya, 2010, Running Lean)
In 2010, an entrepreneur named Ash Maurya ran into a problem every founder knows: the 50-page business plan that nobody reads. Investors want a pitch deck, the team wants to know what to build, and the founder knows everything will change within three months anyway.
Maurya took Alexander Osterwalder's Business Model Canvas and reworked it to fit the reality of startups. He removed the blocks that apply to established companies (key partners, key activities, customer relationships, key resources) and replaced them with what matters when you're starting out: the problem, the solution, key metrics, and unfair advantage.
The result is a one-page tool you can fill in in 20 minutes, revise the next day, and throw away if your assumption doesn't hold up.
Lean Canvas vs Business Model Canvas: the differences
You'll often hear that the Lean Canvas and the Business Model Canvas are "more or less the same thing." In reality, they serve opposite goals.
Osterwalder designed the BMC to describe a business model that already works. It focuses on partners, resources, and customer relationships: in short, the infrastructure of an established company.
The Lean Canvas starts from a different premise: you don't know anything yet. You have assumptions, not certainties. Here are the 4 blocks it replaces:
| Business Model Canvas | Lean Canvas | Why |
|---|---|---|
| Key partners | Problem | A startup solves a problem before it forms partnerships |
| Key activities | Solution | What matters is how you answer the problem, far more than your internal processes |
| Customer relationships | Unfair advantage | You don't have customers yet, but you need to know what makes you unique |
| Key resources | Key metrics | Measuring progress is worth more than listing assets you don't have |
The other five blocks (customer segments, value proposition, channels, revenue streams, cost structure) appear in both canvases. Maurya still adjusted the grid in three places. The value proposition becomes "unique" and fits in a single sentence. The Segments block gets an early adopters sub-box, and the new Problem block gets an existing alternatives sub-box. These two additions force you to name real people and the solutions they already use.
Why startups should choose the Lean Canvas
If you're an early-stage founder, the BMC will waste your time on premature questions. Who are your key partners? You don't have any. What are your key resources? A laptop and some coffee.
The Lean Canvas has you answer the right questions at the right time: what problem are you solving? For whom? How will you know it's working? You validate instead of plan.
Blank Lean Canvas template
Copy this grid into a document, a spreadsheet, or onto a sheet of A4 paper turned landscape. It follows Ash Maurya's layout: five columns across the top, and two boxes along the bottom for the project's economics. Each box has a prompt line, and its number points to the detailed section further down.
| 1. Problem Your target's top 3 problems. Existing alternatives: what they use today to get by. |
4. Solution One minimal feature per problem. |
3. Unique value proposition One sentence your customer understands in 5 seconds: what you do differently. |
9. Unfair advantage What a competitor can neither copy nor buy. Leaving it empty is fine. |
2. Customer segments Who experiences the problem, described precisely enough to find them this week. Early adopters: the first people willing to try an imperfect version. |
|||||
| 8. Key metrics The 2 or 3 numbers that prove you're making progress. |
5. Channels The 1 or 2 channels where your early adopters already spend time. |
||||||||
| 7. Cost structure Fixed and variable costs, monthly burn rate, approximate break-even point. |
6. Revenue streams Revenue model, target price, and the reasoning behind the price. |
||||||||
The unique value proposition sits in the center. To its left, you describe the product (problem, solution, key metrics); to its right, the market (unfair advantage, channels, segments). Fill in the grid in pencil or on sticky notes: every box holds an assumption you'll revise after your first interviews.
The 9 Lean Canvas blocks explained
Each block answers a fundamental question. Here are all 9, in the order you should fill them in (which isn't left to right, more on that below).
1. Problem (+ existing alternatives)
List the top 3 problems your future customers face. Three is the right number: it forces you to prioritize without narrowing to a single bet. For each problem, ask yourself: "Is this painful enough that someone would pay to solve it?" If the answer is no, what you have is a mere inconvenience.
Below the block, write down the existing alternatives: how your future customers deal with the problem today. This is crucial. Your competitors include other startups, and also Excel, the intern, "we just live with it," or the accountant who bills €80 an hour to handle it. If nobody is actively trying to solve this problem, take a hard look at whether your market exists.
2. Customer segments (+ early adopters)
Who has this problem? Be specific. "French SMEs" is a statistical category from INSEE. "Micro-businesses with fewer than 10 employees that still invoice in Excel" is a segment. You can find them, call them, and understand their day-to-day.
Below that, identify your early adopters: the first customers willing to try an imperfect solution because their pain is strong enough. Early adopters are a small slice of your market, but they will make or break your launch. They tolerate bugs, give feedback, and recommend your product if you truly solve their problem.
3. Unique value proposition
One sentence, written plainly rather than as a marketing slogan. It explains why your solution differs from what already exists, phrased so your customer gets it in 5 seconds.
Steve Blank's formula works well: "We help [segment] [solve problem] with [differentiator]." So does Geoffrey Moore's: "For [target customer] who [need], our [product] provides [key benefit]." The exercise is harder than it looks. If your UVP sounds like your competitors', you don't have one yet.
4. Solution
For each problem you identified, describe the main feature that solves it. Three solutions for three problems, and that's it.
It's tempting to fill this block with a 200-line spec. Resist. At this stage, you don't even know whether the problem is real. There's no point designing the rocket before you've confirmed there's a destination. Describe the minimal features that prove your assumption holds, and save the ones you dream of for version 3.0.
5. Channels
How will customers discover your product? SEO, paid ads, word of mouth, partnerships, cold outreach, content, events?
Focus on 1 or 2 channels at the start. You have neither the budget nor the team to run more. The classic mistake is trying to be everywhere (LinkedIn, TikTok, Google Ads, trade shows, podcasts) and being effective nowhere. Pick the channel where your early adopters already spend time, test it seriously, and expand only once you've found a profitable acquisition cost.
6. Revenue streams
How you make money. Monthly subscription, per-transaction commission, one-time purchase, freemium, marketplace? Also note your target price and the reasoning behind it: cost-plus, competitive alignment, or perceived value.
If you don't know what to charge yet, that's a signal: you don't understand the perceived value of your solution well enough. Go ask 10 prospects: "How much do you pay today to solve this problem?" Their answer gives you your price anchor.
7. Cost structure
Your fixed costs (hosting, salaries, SaaS tools, rent) and variable costs (customer acquisition cost, support, infrastructure at scale). The goal here comes down to two numbers: your monthly burn rate and your approximate break-even point.
For an early-stage French startup, the main costs are usually development (developers or no-code), cloud hosting, and acquisition. Be honest about these numbers: underestimating your burn rate is one of the fastest routes to shutting down.
8. Key metrics (AARRR)
The metrics that prove your startup is moving in the right direction. Skip LinkedIn likes and blog traffic, and track the indicators that measure the real value you create.
The AARRR (Pirate Metrics) framework, created by Dave McClure in 2007, provides a proven structure: Acquisition (how users arrive), Activation (their first "aha moment"), Retention (do they come back?), Referral (do they tell others?), and Revenue (do they pay?). Early on, focus on Activation and Retention: if people try your product and don't come back, no marketing budget will save you.
9. Unfair advantage
What your competitors can't easily copy. A patent, a network of experts, proprietary data, domain expertise, an active community, regulatory access. Ash Maurya calls it an "unfair advantage": something you have that can't be bought.
A word of caution: "our team" or "our technology" are not lasting competitive advantages, since anyone can hire the same people or build the same thing. If you don't have one yet, leave this block empty. Honesty beats illusion. Your unfair advantage often builds over time, as you accumulate data, users, and expertise.
How to fill in your Lean Canvas in 20 minutes
The optimal fill-in order (it's non-linear)
Don't fill in the canvas from left to right. Maurya recommends starting with the problem/customer segment pair, because everything else flows from it. Here's the optimal order:
- Problem and Customer segments (both at once: a problem only exists if someone experiences it)
- Unique value proposition (your answer in one sentence)
- Solution (the minimal features)
- Channels (how to reach your early adopters)
- Revenue streams and Cost structure (the business model)
- Key metrics (how to measure success)
- Unfair advantage (often last, and that's normal)
This order has you validate the "why" before the "how." If your problem isn't real, your solution is useless, however polished your value proposition looks.
Full example: a French SaaS startup
Let's take Factolib, a fictional but realistic startup: invoicing software for French micro-businesses. We made this example up, so its prices and costs are for illustration only. Here's its canvas in the same grid as the blank template.
| Problem 1. Micro-businesses invoice in Excel/Word (errors, wasted time). 2. The 2026 e-invoicing compliance deadline stresses them out. 3. Payment tracking is manual. Existing alternatives: Excel, an accountant who handles everything, overly complex tools (Sage). |
Solution 1. Create an invoice in 3 clicks. 2. Automatic e-invoicing compliance. 3. Automated payment reminders. |
Unique value proposition "Send compliant invoices in 30 seconds, no training needed" |
Unfair advantage Native integration with the Chorus Pro portal (French compliance) |
Customer segments French micro-businesses with 1-10 employees, tradespeople and independent professionals. Early adopters: tech freelancers invoicing 5 or more clients a month. |
|||||
| Key metrics Activation (first invoice created), M3 retention > 60%, MRR |
Channels SEO ("logiciel facturation TPE"), partnerships with accounting firms |
||||||||
| Cost structure Hosting (€200/month), developer (€4,000/month), acquisition (€500/month) |
Revenue streams Freemium (5 free invoices/month) + €19/month subscription |
||||||||
This canvas took 15 minutes. We left it imperfect on purpose.
Notice what's missing: Factolib doesn't have any real data yet. The €19/month is an assumption, not a validated price. M3 retention above 60% is still a target. The unfair advantage (Chorus Pro) only matters if micro-businesses know what it is. Each of these boxes is a sticky note to verify in the field.
You can see your blind spots on a single page. A 50-page business plan would have buried these uncertainties under 5-year financial projections. The canvas puts them front and center.
Fatal Lean Canvas mistakes
Confusing the problem with the solution
This is the most common mistake, and the most damaging. You write "Micro-businesses need invoicing software" in the Problem block. That's your solution disguised as a problem.
The problem is: "Micro-businesses lose 3 hours a week invoicing by hand and risk penalties under the 2026 e-invoicing mandate." The problem describes a pain. The solution describes a remedy. They belong in different blocks.
If you mix them up, you never test the problem. You go straight to building a product on the assumption that the pain exists. That's exactly how a startup ends up discovering nobody wanted what it built, the top reason for failure identified by CB Insights.
Targeting "everyone" as your segment
"Our target? Every company in France." Congratulations, you're targeting no one.
A segment has to be precise enough that you could find your first 10 customers this week. "Construction micro-businesses with fewer than 5 employees in the Paris region" is a segment. You can find them on LinkedIn, call them, ask them questions, and learn whether your problem really exists. "Companies" is an abstraction that gives you no direction for action.
The fear behind a broad segment is "closing doors." In reality, it works the other way around: a narrow segment lets you say no to everything else and concentrate your resources where they count. You'll expand later, once you've proven it works for the first group.
Never updating it
A Lean Canvas filled in once and shoved in a drawer is as useful as a 50-page business plan nobody reads.
This document needs to evolve after every customer interview, every test, every pivot. Maurya recommends reviewing it at least every two weeks during the validation phase. Some founders in accelerators update it weekly, noting what changed and why.
Think of the canvas as a logbook of what you've learned, written for yourself rather than for a jury. If your March canvas looks exactly like your January one, either you found product-market fit on the first try (unlikely), or you learned nothing in two months.
From Lean Canvas to MVP: what comes next
Validate the critical assumptions first
Your Lean Canvas contains assumptions, not truths. The next step is to identify the riskiest assumption and test it before building anything.
Ask yourself: "If this assumption is wrong, does the whole project collapse?" If so, test that one first. Start with the riskiest assumption, even when an easier one is tempting.
For Factolib, the critical assumption would be: "Micro-businesses are willing to pay €19/month for an invoicing tool when they currently use Excel for free." Before writing a line of code, go ask 20 micro-businesses whether they'd pay for it. Asking "Would this interest you?" gets you polite yeses from everyone. Ask instead: "Here's the pre-signup link, it's €19/month, will you sign up?"
Successful founders often share this one reflex: testing the risky assumption before building. In Startup Genome's report on premature scaling (building before validating), this mistake ranks among the leading causes of failure in the startups studied.
From canvas to experimentation (the Lean Startup link)
The Lean Canvas is the starting point of Eric Ries's Lean Startup loop: Build, Measure, Learn. Your canvas identifies the assumptions. The MVP tests them. The results update the canvas. And the cycle starts again.
In practice, once your canvas is done:
- Identify your riskiest assumption
- Design the simplest experiment to test it (landing page, interviews, clickable prototype)
- Define the success criterion in advance ("if 5 out of 20 people pre-order, we keep going")
- Run it, measure, decide: pivot or persevere
For the full process around the canvas, including customer interviews and the MVP, read the first chapter of the swanbase guide, Trouver le bon problème.
Each iteration brings you closer to product-market fit or convinces you to pivot. Finding out your assumption is wrong after 3 weeks of testing costs €0. Finding out after 6 months of development costs you your runway.
If you're looking for a cofounder to run this process with, the Lean Canvas also works well as an alignment tool: each of you fills one in separately, then you compare. The differences will surface your disagreements before they turn into conflicts. A canvas that says "we disagree on the problem" is far better than a startup that blows up 6 months later because the founders never shared the same vision.
FAQ
What is the Lean Canvas in one sentence?
The Lean Canvas is a one-page strategic template, created by Ash Maurya in 2010, that structures a startup's 9 key assumptions (from the customer problem to the unfair advantage) so you can test them quickly.
Lean Canvas or Business Model Canvas: which should you choose?
If you're creating a company or validating an idea, use the Lean Canvas: it focuses on the problem, the solution, and the risks. If you run an established company and want to optimize your model, Osterwalder's Business Model Canvas is a better fit: it covers partnerships, resources, and customer relationships.
How long does it take to fill in a Lean Canvas?
Between 15 and 20 minutes for a first version. That first version is only the starting point, though. Plan to update it after every meaningful customer interaction, ideally every two weeks during the validation phase.
Can you use the Lean Canvas for an existing company?
Yes, especially to test a new product, explore a new market segment, or evaluate a pivot. The Lean Canvas works whenever you're facing uncertainty, whether your company is 6 months or 6 years old.
Where can you find a free Lean Canvas template?
The blank template in this article is free: copy the grid into a document, a spreadsheet, or onto a sheet of A4 paper turned landscape. If you prefer an online tool, LEANSTACK, Ash Maurya's company, offers a free Lean Canvas editor, LEANSpark, available from leanstack.com.
Which Lean Canvas example should you follow?
Start from an example close to your own business model, then replace each box with your own assumptions. The Factolib example in this article, a fictional invoicing tool for micro-businesses, shows a complete SaaS canvas with its existing alternatives, early adopters, and key metrics. Reuse its structure and fill in each box with what your customer interviews have taught you.
