Skip to main content
Back to Frameworks
Foundation · Startup

Lean Canvas

The Lean Canvas, created by Ash Maurya as a startup-friendly adaptation of the Business Model Canvas, helps founders capture their business model on a single page. It replaces 'key partners' and 'key activities' with 'problem' and 'unfair advantage' — what matters most in the early stages. It's designed to be filled in quickly (under 20 minutes), iterated often, and shared easily with co-founders and advisors.

When to use this framework

  • →You're launching a new product or startup and need to crystallise your model
  • →You need to pitch your business in a structured, one-page format
  • →You want to compare multiple business model hypotheses quickly
  • →You're pivoting and need to map the new direction
  • →Product and marketing teams need alignment on who you serve and why
Related:Value Proposition Canvas Jobs To Be Done (JTBD) Positioning Statement Template

Sign in to unlock full access

You're browsing as a visitor. Create a free account to fill in worksheets, download PDFs, and save your progress.

Get startedSign in
Sign in to download
Worked Example

Notion (early stage, ~2016)

1. Problem

List the top 1-3 problems your customer segment faces. Be specific — vague problems lead to vague solutions.

1. Teams use too many tools (Docs, Wikis, Spreadsheets, Project Management, Notes) — each with its own login, data silo, and learning curve. 2. Existing tools are rigid — you can't customize them to match how your team actually works. 3. Information is scattered — finding the right document means searching across 5+ different apps.

How are customers solving these problems today? Include direct competitors, workarounds, and doing nothing.

Google Docs + Confluence + Trello + Evernote + Airtable (used together but poorly integrated). Microsoft Office 365 (powerful but bloated and not designed for modern workflows). Individual point solutions (Asana for projects, Notion/wiki for docs). Some teams resort to shared folders and naming conventions.

2. Customer Segments

Who has the problem most acutely? Be as specific as possible. Early adopters first — who will buy before the product is perfect?

Small-to-medium tech teams (5-50 people) who are tool-fatigued. Product teams, engineering teams, and design teams who need flexible documentation and project tracking. Teams that value customisation over rigid workflows.

Who will be your first customers? These are people who feel the problem so strongly they'll tolerate an imperfect solution.

Startup founders and heads of product at companies with 5-20 people who are setting up their stack for the first time. Power users who currently use Markdown, are frustrated with Confluence, and want a tool they can shape to their workflow.

3. Unique Value Proposition

A single, clear, compelling message that states why you are different and worth paying attention to. Focus on the outcome, not the mechanism.

All-in-one workspace that replaces your docs, wikis, project management, and databases — and lets you build custom tools without code.

An analogy that makes your UVP instantly understandable. 'YouTube for education' or 'Airbnb for office space.'

Lego blocks for productivity tools

4. Solution

Sketch the simplest possible solution for each problem listed above. Don't over-engineer — what's the minimum feature set?

Problem 1 → A single app with modular 'blocks' (text, tables, kanban boards, calendars, databases) that can be combined on any page. Problem 2 → Completely flexible — templates for common use cases, but everything is customisable down to the block level. Problem 3 → Powerful search across all content, plus a sidebar navigation that mirrors your team's mental model.

5. Channels

How will you reach your customer segments? Consider both free and paid channels. Focus on channels where your early adopters already spend time.

1. Product-led growth (free tier → team adoption → paid conversion) 2. Content marketing (templates gallery, use case guides, YouTube tutorials) 3. Community (template creators, power user community, Reddit) 4. Word of mouth / referral (natural virality — invite teammates) 5. Influencer / creator partnerships (productivity YouTubers, Twitter thought leaders)

6. Revenue Streams

How will you make money? Subscription, transaction fee, licensing, advertising, freemium conversion? Be specific about pricing.

Freemium: Free for individuals (limited blocks per page early on, later unlimited). Team plan at $8/user/month. Business plan at $15/user/month with advanced permissions, audit log, and SSO. Enterprise with custom pricing.

Estimated revenue per customer over their lifetime. Even a rough estimate helps validate the model.

1440

7. Cost Structure

What are your fixed and variable costs? Customer acquisition cost, hosting, team, marketing spend. Focus on the biggest costs.

Infrastructure (AWS hosting, CDN). Engineering team (largest cost — complex product). Content and community management. Limited paid marketing (primarily organic growth). Customer support and success for paid teams.

How much does it cost to acquire one customer? Include marketing, sales, and onboarding costs.

120

Calculated from LTV and CAC above. A ratio of 3:1 or higher is generally considered healthy for a sustainable business.

—

8. Key Metrics

What are the 3-5 numbers that tell you if your business is working? Activation rate, retention, revenue per user, referral rate, etc.

1. Weekly Active Users (engagement, not just signups) 2. Pages created per user per week (activation metric) 3. Team invite rate (virality / network effects) 4. Free-to-paid conversion rate 5. Net Revenue Retention (expansion revenue from seat growth)

9. Unfair Advantage

Something that cannot be easily copied or bought by competitors. This might be empty at first — that's okay. It could be: insider information, unique expertise, existing audience, network effects, community, or a dream team.

1. Block-based architecture — once teams build their workflows in Notion, switching cost is extremely high (data lock-in + workflow lock-in). 2. Community flywheel — thousands of templates created by users, making the product better without engineering effort. 3. Network effects — the more team members use it, the more valuable it becomes (shared knowledge base). 4. Engineering team with deep expertise in real-time collaboration and block-based editors (hard to replicate).
Your Worksheet

Fill in for your brand

Sign in to use this worksheet

Create a free account to fill in frameworks with your own brand details, download completed worksheets, and save your progress.

Create free accountAlready have an account? Sign in

Take this framework offline

Download a blank PDF to fill in by hand, use it in workshops, or pin it to your wall. If you've filled in the worksheet above, you can download your completed version too.

Create free account to downloadAlready have an account? Sign in