Lean Canvas: The 1-Page Business Plan Template (2026)

The traditional 30-page business plan was invented in 1942 by the Harvard Business School to help WWII suppliers raise capital from banks. Eighty years later, founders are still writing them. For a $50,000 product test that should take 14 days.

You spend three weeks researching market size. You write executive summaries. You build five-year revenue projections from numbers you invented. By the time you finish, your idea has either died of boredom or someone else has shipped it.

Ash Maurya solved this in 2012 in Running Lean. The lean canvas is one page, takes 30 minutes, and tests every assumption that actually matters. This guide explains all 9 boxes with real founder examples from Airbnb, Dropbox, and Slack, shows you the exact order to fill them in (which is not the order printed on the canvas), and gives you a free template at the end.

What Is a Lean Canvas?

A lean canvas is a one-page business plan divided into 9 boxes that capture every assumption your business depends on. It replaces the traditional written business plan with something a founder can fill in 30 minutes and rewrite every week as they learn.

The canvas was created by Ash Maurya in 2010 and formalised in his 2012 book Running Lean, which has since sold over 200,000 copies and become required reading at Y Combinator, Techstars, and 500 Global. Maurya built the lean canvas as a startup-specific adaptation of Alex Osterwalder's Business Model Canvas, which was originally designed for established companies, not pre-product-market-fit founders.

The core philosophy that makes the lean canvas different: it is a learning tool, not a planning document. You fill it in pencil. You expect to be wrong. You test the boxes that scare you most. You rewrite what was wrong, then test again. After six weeks of this loop, the canvas stops being theoretical and starts reflecting what you actually know.

This is the part most founders skip. They write the canvas, file it, and never touch it again. That is not how it works. The canvas only has value if you update it.

Lean Canvas vs Business Model Canvas

The two canvases look almost identical at first glance. Same one-page format, same 9-box grid. Look closer and four of the boxes are completely different.

Alex Osterwalder published the Business Model Canvas in 2010 in Business Model Generation. It was designed for executives at established companies who needed a shared visual language for strategy meetings. Customer relationships, key partners, key resources, and key activities all assume you have an operating business.

Ash Maurya saw founders trying to use the Business Model Canvas pre-launch and noticed they kept skipping or faking those boxes. Pre-product-market-fit founders do not have key partners. They do not have key activities. They are still figuring out what the product even is. So Maurya swapped four boxes for the ones that actually matter early on.

Business Model Canvas (Osterwalder)	Lean Canvas (Maurya)	Why the change
Key Partners	Problem	Pre-PMF founders have no partners yet. They need to nail the problem.
Key Activities	Solution	"Activities" is too vague at day zero. "Solution" forces 3 concrete features.
Key Resources	Key Metrics	Founders need to know what to measure, not what they own.
Customer Relationships	Unfair Advantage	Relationships matter for retention. New founders need to know what cannot be copied.

Which one should you use? If your business is pre-launch, pre-revenue, or in its first year, use the lean canvas. The boxes match where your real risks are. If you are running an established operation thinking about expansion or pivots, use the Business Model Canvas. The boxes match the questions you are actually asking.

For most readers of this guide, that means lean canvas. Moving on.

The 9 Boxes Explained (With Real Founder Examples)

Here is every box, what it means, what to write, what NOT to write, and what a real founder would have filled in before their company was famous. The examples are constructed from public interviews, founder essays, and YC application archives. They reflect what these companies looked like before product-market fit, when they were still hypotheses.

Box 1: Problem (top-left)

The top 3 problems your customer has, ranked by pain. Plus a note on what they currently do to solve them (the alternative).

What to write: three specific, observable pain points. Each one should be a sentence a real customer would say out loud.

What NOT to write: "there is no easy way to..." (vague). "Users want a better experience..." (untestable). "The market needs..." (this is not a problem, this is your guess).

Airbnb 2008 example: "Hotels in conference cities sell out months in advance. Spare rooms in those cities sit empty. Business travellers want a more local experience than chain hotels offer."

Box 2: Customer Segments (top-right)

Who specifically. Not "small business owners" or "millennials." Specific enough that you could put a face to it.

What to write: the smallest, most testable segment first. You can expand later. Add an "Early Adopters" line for the slice you will reach first.

What NOT to write: "everyone," "consumers," "the general public." If your segment is broader than 5,000 people, narrow it.

Dropbox 2007 example: "Tech-savvy professionals working across 2 or more devices (laptop plus home computer). Early adopters: Hacker News readers."

Box 3: Unique Value Proposition (centre)

One sentence. The single most important promise your product makes to your customer. If you cannot fit it in one sentence, you do not understand it yet.

What to write: a sentence with a specific outcome and a specific reason it works. Bonus: a "high-concept pitch" underneath (e.g., "X for Y": "Stripe for podcasts").

What NOT to write: "the best...", "the leading...", "the easiest..." (every founder thinks this; nobody believes it).

Slack 2013 example: "Be less busy. Slack replaces internal email with searchable team chat."

Box 4: Solution (middle-left, under Problem)

The top 3 features that solve the top 3 problems. Not all features. Three.

What to write: one bullet per problem. Each one should be a thing you can build in under 4 weeks.

What NOT to write: a feature list. The lean canvas is not your product roadmap. If you have 12 features here, you are building a product, not testing a hypothesis. Read our guide to building an MVP for what to cut.

Airbnb 2008 example: "List a room with photos and price. Book a room with a credit card. Hosts and guests both leave reviews."

Box 5: Channels (right, under Customer Segments)

How you reach your customers. Be honest. "We will run ads" is rarely the right answer for early stage. The right answer is usually "we will manually go talk to 100 of them."

What to write: the specific channel and the unit economics if you know them. "Reddit r/entrepreneur, free." "Cold email to LinkedIn lead list, $0.50 per contact."

What NOT to write: "social media," "content marketing," "viral growth" (none of these are channels, they are wishes).

Dropbox 2007 example: "Demo video on Hacker News for early access waitlist. Referral programme rewarding users with extra storage."

Box 6: Revenue Streams (bottom-right)

How does money move from customer to you? Pricing model, price point, lifetime value if you can estimate it.

What to write: the model (one-time, subscription, freemium, transactional), the price, and the unit (per user per month, per transaction, etc.).

What NOT to write: "TBD" (decide). "Free for now, paid later" (this is the most common way founders lie to themselves).

Slack 2013 example: "Freemium. Free tier with 10,000 message history limit. Paid tier $6.67 per user per month for unlimited history plus integrations."

Box 7: Cost Structure (bottom-left)

The major costs to get to launch and to run for the first 6 months. Not a P&L. Just the big buckets.

What to write: 3 to 5 line items. Hosting, salaries, customer acquisition cost estimate, any contractor fees. Add total monthly burn at the bottom.

What NOT to write: a 12-line accounting breakdown. This is the back-of-napkin version. The detailed version belongs in a spreadsheet.

Airbnb 2008 example: "Hosting: $800/mo. Two founder salaries: $6,000/mo (delayed). Cereal box manufacturing for fundraising stunt: $500. Total monthly burn: $7,300."

Box 8: Key Metrics (centre, below UVP)

The 1 to 3 numbers that matter most right now. Not a metrics dashboard. The single most predictive numbers for your stage.

What to write: activation rate, retention rate, time-to-first-value, weekly active users, paying customer count. Pick the ones that prove your assumption is right or wrong.

What NOT to write: "revenue" (too late a signal), "page views" (vanity), "sign-ups" (also vanity unless tied to activation).

Slack 2013 example: "Daily active users per team (target: 80%+). Messages sent per week per active user. Conversion from free to paid (target: 30%)."

Box 9: Unfair Advantage (centre-right)

Something that cannot be copied or bought. Patents, exclusive deals, insider domain knowledge, personal credibility in your niche, an audience you built first.

What to write: the genuine moat. If you do not have one yet, write "none yet." That is honest and useful. Most founders do not have one at day one.

What NOT to write: "first-mover advantage" (rarely real), "we are passionate" (everyone is), "our team is great" (so is everyone else's).

Airbnb 2008 example: "Direct relationships with first 200 hosts photographed personally by founders. None yet on tech defensibility."

How to Fill Out a Lean Canvas in 30 Minutes (Step-by-Step)

Here is the part most guides skip. The canvas prints in one visual order (Problem in box 1, Customer Segments in box 2), but founders should fill it in a different strategic order. Trying to write the Problem box before you know your customer is how you end up with vague answers.

Maurya himself recommends starting with Customer Segments, then jumping around. Here is the optimal 9-step sequence based on his guidance plus what tends to work in practice.

Total: 30 minutes. If you spent 45, you are overthinking it. The canvas is supposed to be your best guess, not your final answer. The point is to start testing.

3 Real Lean Canvases (Airbnb, Dropbox, Slack)

Here is what these canvases would have looked like before product-market fit. We reconstructed them from public founder interviews, Y Combinator application archives, and early product screenshots. They are illustrative, not exact, but they show how the boxes get filled at day zero.

Notice what is true across all three. The problem is concrete, not abstract. The customer segment is small and specific. The UVP is one sentence. The solution is 3 things, not 30. And in all three cases, the "unfair advantage" box was almost empty at the start. That did not stop them from launching.

5 Lean Canvas Mistakes to Avoid

I have watched founders fill the canvas perfectly, then make every one of these mistakes. The canvas only works if you treat it the way Maurya intended. Here are the five most common ways founders break it.

What to Do After You Fill the Canvas

This is where most founders stop and most teachers gloss over. The canvas is filled. What now?

The answer is the entire reason Maurya built the canvas in the first place. Each box is a hypothesis. The boxes you are least certain about are your riskiest assumptions. Those are what you test next.

Walk through the canvas and rate each box on a 1-to-5 scale: how confident are you that this is right? The boxes you rated 1 or 2 are where you spend the next two weeks. Not building. Testing.

• Low confidence on Problem? Run 15 customer interviews. Read our guide to customer interviews for the question framework.
• Low confidence on UVP? Build a landing page test. Run $50 of ads. Measure click-through and waitlist conversion.
• Low confidence on Solution? Build an MVP that tests the riskiest feature. Two weeks max.
• Low confidence on Channels? Run a 7-day experiment on one channel. Cold outreach to 50 prospects beats a "marketing strategy" every time.
• Low confidence on Pricing? Quote 10 customers different prices. See where they flinch.

The canvas tells you what to test. The validation process shows you how. After two weeks, you come back to the canvas, update the boxes that changed, and run the loop again. After 6 weeks of this you will know if your idea is real. After 12 weeks you might have product-market fit. The canvas is the map. The testing is the journey.

Free Lean Canvas Template

Download a free PDF version of the lean canvas you can print or fill on your screen. Both formats include the 9 boxes in their visual layout plus the strategic fill-order numbers from this guide.

Frequently Asked Questions