Lean canvas

By Allen Jay Bercero

A lean canvas is a one-page business-model template, divided into nine boxes, that forces you to capture the riskiest assumptions behind a product idea on a single sheet: the problem, who has it, your solution, how you’ll reach them, and how the money works. It’s the lean, fast alternative to a long business plan: minutes to sketch, easy to change, and built to be revisited as you learn.

It was created by Ash Maurya (2010), who adapted Alexander Osterwalder’s Business Model Canvas to focus on the things that actually kill early-stage products, chiefly building something nobody wants. It’s a core tool of the Lean Startup movement.

Also known as

Lean Canvas · one-page business model · (loosely) “the canvas”. But see the warning: that’s ambiguous

Don't confuse with

• Business Model Canvas (BMC): the parent it was adapted from (Osterwalder). Same nine-box, one-page idea, but four boxes differ. BMC leans toward established businesses (partners, activities, resources); Lean Canvas swaps those for startup risks (problem, solution, key metrics, unfair advantage). See the comparison below.
• Business plan: a long execution-and-funding document written after deciding to proceed. A lean canvas is a thinking tool for before and during. (You could say the lean canvas compresses the riskiest 80% of a business plan onto one page.)
• Feasibility study: a go/no-go assessment. The lean canvas is a model of the idea; teams often use it to frame what a lightweight feasibility check should test.

In plain English

Instead of a 40-page plan, you fill one page of nine sticky-note-sized boxes. It fits on a screen, takes 20 minutes, and you’re expected to rewrite it as you learn.

The nine boxes

The Lean Canvas is a single page divided into nine independent regions (plus three small sub-fields). This is Ash Maurya’s standard layout. The ”↳” cells are sub-fields, explained just below:

block-beta
  columns 5
  P["Problem"] S["Solution"] UVP["Unique Value Proposition"] UA["Unfair Advantage"] CS["Customer Segments"]
  EA["↳ Existing alternatives"] KM["Key Metrics"] HLC["↳ High-level concept"] CH["Channels"] EAd["↳ Early adopters"]
  COST["Cost Structure"]:3 REV["Revenue Streams"]:2

How to read this: it's a partition, not a hierarchy

The grid is just nine regions of one page arranged spatially. Vertical position does NOT mean containment. The boxes above Cost Structure and Revenue Streams do not “belong to” them. Those two are simply more boxes that run along the bottom edge. (Like rooms on a floor plan: the kitchen drawn below the living room isn’t “inside” it.)

• The nine real boxes: Problem, Customer Segments, Unique Value Proposition, Solution, Channels, Revenue Streams, Cost Structure, Key Metrics, Unfair Advantage.
• The three ”↳” cells (Existing alternatives, High-level concept, Early adopters) are sub-fields of the box directly above, the only real “belongs-to” links on the canvas. Key Metrics and Channels, despite sitting in that same middle row, are full boxes in their own right.
• Loose spatial grouping: left = product (problem/solution) · center = your promise (UVP) · right = market (customers/channels/advantage) · bottom band = the economics (money out / money in).

What goes in each:

#	Box	What it captures
1	Problem	The top 1–3 problems you’re solving, plus existing alternatives (how people cope today).
2	Customer Segments	Who has the problem, plus your early adopters (the narrow group you’ll win first).
3	Unique Value Proposition	One clear, compelling sentence on why you’re different and worth attention, plus a high-level concept (an “X for Y” analogy).
4	Solution	The top 1–3 features that address the problems. Kept deliberately small.
5	Channels	Your path to customers (referrals, ads, sales, app stores…).
6	Revenue Streams	How you make money (fees, subscriptions, etc.).
7	Cost Structure	What it costs to build and run (development, hosting, marketing, salaries).
8	Key Metrics	The few numbers that tell you whether it’s working.
9	Unfair Advantage	Something that can’t be easily copied or bought (network effects, insider knowledge, a brand). Often the hardest box (“none yet” is an honest answer early on).

Fill it in this order

Ash Maurya suggests: 1 Problem → 2 Customer Segments → 3 Unique Value Proposition → 4 Solution → 5 Channels → 6 Revenue Streams → 7 Cost Structure → 8 Key Metrics → 9 Unfair Advantage. Do it per customer segment; if you have two very different segments, use two canvases.

(Maurya actually groups a few as simultaneous steps, Problem with Customer Segments, and Revenue Streams with Cost Structure, but the relative order of all nine boxes is the same.)

Reading it as a story (how the boxes connect)

The grid shows where the boxes sit; this shows how they relate, the business logic the canvas is really capturing. Read it as a loop:

flowchart TD
  CS["Customer Segments"] -->|feel a| PR["Problem"]
  PR -->|you build a| SOL["Solution"]
  SOL -->|summed up as your| UVP["Unique Value Proposition"]
  UVP -->|carried to customers via| CH["Channels"]
  CH -->|reach the| CS
  UA["Unfair Advantage"] -.->|defends it| UVP
  KM["Key Metrics"] -.->|measures| SOL
  SOL -->|drives| COST["Cost Structure (money out)"]
  CS -->|drives| REV["Revenue Streams (money in)"]

The solid loop is the value story: a customer segment feels a problem, you build a solution, you distil it into your unique value proposition, and you deliver that through channels back to those customers. The dotted lines are the two supports: unfair advantage defends the promise, and key metrics tell you whether it’s working (a common set is AARRR, the “pirate metrics”). At the bottom, Revenue Streams − Cost Structure = whether the model makes money; everything above it explains why customers would pay.

This is the view most people find clicks. The grid is just the standard way it’s drawn, not the way it’s reasoned about.

Lean Canvas vs Business Model Canvas

Maurya kept five boxes from Osterwalder’s BMC and replaced four to make it startup-focused:

Business Model Canvas box	its grid slot became →	Lean Canvas box	Why
Key Partners	→	Problem	Startups’ #1 risk is building something nobody needs. Lead with the problem.
Key Activities	→	Solution	Keep the focus on what you’ll build to solve it.
Key Resources	→	Key Metrics	Early on, knowing what to measure matters more than resource planning.
Customer Relationships	→	Unfair Advantage	Force the founder to confront what actually protects the business.

(Kept unchanged: Customer Segments, Value Proposition, Channels, Cost Structure, Revenue Streams.)

It's a positional swap, not an equivalence

Maurya removed those four BMC boxes and added these four in the grid positions they left behind. He is not claiming that “Problem” is a kind of “Key Partners.” The arrows above mean “took that box’s slot,” not “means the same thing.”

A worked example: a lending-marketplace app

The same idea a business plan would spell out over 40 pages, compressed to one canvas

• Problem: Borrowers waste hours traveling to lending offices; small lenders can’t afford their own app and struggle to judge borrower risk. Existing alternatives: web-only lenders, in-person microfinance.
• Customer Segments: local microfinance firms (primary), their borrowers (secondary). Early adopters: small firms with no app of their own.
• Unique Value Proposition: “Lending made mobile: apply, receive, and repay loans without leaving home.” High-level concept: “Shopify for microlenders.”
• Solution: in-app loan application; auto bank deposit & repayment; shared borrower credit database.
• Channels: partner firms recommend it to clients; referrals & word-of-mouth; targeted social ads.
• Revenue Streams: small per-transaction fee; featured-listing subscription for firms.
• Cost Structure: app development, hosting/maintenance, marketing, salaries.
• Key Metrics: active borrowers transacting per day; transactions per month; partner firms onboarded.
• Unfair Advantage: first mover in the local market; a shared credit-rating network that gets more valuable as more firms join (a network effect).

Notice how much of a full business plan’s marketing plan, operations, and financial projections collapses into Channels, Cost Structure, and Revenue Streams, and how the lean canvas forces the two questions a business plan can bury: what problem, and what’s your unfair advantage?

When to use it

• Very early, to pressure-test an idea before investing in it (a lightweight stand-in for parts of a Feasibility study).
• As a living document: update it every time an experiment, prototype, or MVP teaches you something.
• It pairs with the Lean Startup build–measure–learn loop: the canvas states your assumptions; the MVP tests them; you revise the canvas.

See also

• Feasibility study: the heavier, plan-driven relative
• Prototype: the MVP / proof-of-concept that tests a canvas’s assumptions
• Software development process: lean/agile approaches favor canvases over big up-front documents
• AARRR: a ready-made set of metrics for the Key Metrics box
• Adoption: what the Channels box and the Early-adopters sub-field are ultimately driving

References

• A. Maurya, Running Lean: Iterate from Plan A to a Plan That Works (2nd ed., O’Reilly, 2012). Details the Lean Canvas (which Maurya first introduced on his blog in 2010). https://openlibrary.org/books/OL25288569M/Running_lean
• A. Maurya, “Why Lean Canvas vs Business Model Canvas?” (2012). The four-box adaptation and its rationale. https://medium.com/lean-stack/why-lean-canvas-vs-business-model-canvas-af62c0f250f0
• A. Osterwalder & Y. Pigneur, Business Model Generation (Wiley, 2010). The Business Model Canvas that Lean Canvas adapts. https://www.strategyzer.com/library/the-business-model-canvas
• E. Ries, The Lean Startup (Crown Business, 2011). The lean startup movement the canvas serves. https://theleanstartup.com/