Chapter 6: Build Your Lean Canvas v0

Step 5: Put It All Together (The Lean Canvas)

You've done the hard work. You have a customer, a problem, and a value hypothesis. Now let's see if all the pieces actually fit together.

The Lean Canvas, created by Ash Maurya as an adaptation of Alex Osterwalder's Business Model Canvas, is a one-page business model designed specifically for startups operating under conditions of extreme uncertainty. It forces you to think about everything—not just the product, but how you'll reach customers, make money, and what happens when things go wrong. Traditional business plans run 30-50 pages and take weeks to write. The Lean Canvas takes 20 minutes—and it's more useful because it surfaces the critical assumptions you need to test.

This is your "v0"—version zero. It's entirely unvalidated. Think of it as a hypothesis about your business, not a plan. The distinction matters. A plan implies certainty: "This is what we'll do." A hypothesis implies learning: "This is what we believe, and here's how we'll find out if we're right." Every single box in your Lean Canvas contains assumptions that could be wrong. That's not a weakness—it's the point. The canvas makes those assumptions visible so you can systematically test them.

One of the Lean Canvas's greatest strengths is that it forces coherence. It's easy to have a great customer persona and a great value proposition that don't actually connect. When you put them on the same page alongside channels, revenue streams, and cost structure, misalignments become obvious. The customer you defined can't afford the price you imagined. The channel you planned doesn't reach the persona you described. These contradictions are much better discovered now than after you've spent months building.

The 9 Boxes (And What Goes In Each)

The Fill Order Matters

Ash Maurya recommends filling in the canvas in a specific order that maximizes insight:

1. Customer Segments first — Because everything flows from who you're serving
2. Problem second — What's the top pain for that segment?
3. Unique Value Proposition third — How do you solve it differently?
4. Solution fourth — Keep this deliberately vague. You'll refine it through validation.
5. Channels fifth — How will you actually reach these people?
6. Revenue Streams and Cost Structure together — Does the math work?
7. Key Metrics seventh — How will you know if you're succeeding?
8. Unfair Advantage last — This is often the last thing you discover, not the first.

Notice that Solution is fourth, not first. Most founders want to start with the solution—it's the most exciting part. But putting it fourth forces you to ground it in customer reality first. The solution should be a consequence of understanding the customer, not the starting point.

Find Your Hidden Assumptions (Before They Kill You)

Here's the uncomfortable truth: Your completed Lean Canvas is just a pile of guesses wearing a business suit. Every box contains assumptions you haven't validated. And the dangerous thing about assumptions is that they feel like facts. You've thought about your customer so much that you're convinced you understand them. You've analyzed the market so carefully that the opportunity feels obvious. But feeling certain and being right are very different things.

The goal of this section is to make every hidden assumption explicit and visible—because assumptions you can see are assumptions you can test. Assumptions you can't see are the ones that kill you six months from now when you realize the foundation your entire business was built on was wrong.

Go through each box of your Lean Canvas and ask: "What would have to be true for this box to be correct?" Write down every answer. You'll be surprised how many unproven beliefs are embedded in statements that felt like certainties.

The Three Types of Assumptions

How to Extract Assumptions from Each Box

Here's a practical guide to mining assumptions from your canvas:

• Customer Segments: "We assume this segment is large enough to sustain a business." "We assume they have budget authority." "We assume they're accessible through the channels we've identified."
• Problem: "We assume this problem is severe enough to pay for." "We assume the root cause we identified is actually the root cause." "We assume people aren't satisfied with existing solutions."
• Revenue Streams: "We assume customers will pay $X/month." "We assume a subscription model is preferred over one-time purchase." "We assume they'll pay this amount before experiencing the full product."
• Channels: "We assume we can reach customers through [channel]." "We assume the customer acquisition cost through this channel is less than the customer lifetime value."

A single Lean Canvas typically contains 15-30 hidden assumptions. That sounds overwhelming, but remember: you don't need to test all of them. You need to test the ones that matter most. That's where the risk matrix comes in.

The Risk Matrix: What to Test First

Not all assumptions are created equal. Some are just risky guesses. Others could sink your entire venture if wrong. Use this 2x2 matrix to prioritize what to test first:

The RAT Testing Sequence

Once you've identified your top 3-5 RATs, you need a plan to test each one. For each RAT, define:

This is where Playbook 01 (Ideation) connects directly to Playbook 02 (Validation). Your RATs become the testing agenda for your customer discovery process. You're not going into customer interviews blindly—you're going in with specific hypotheses to validate or invalidate.

What You Walk Away With

• A Lean Canvas v0: Your entire business model on one page. Messy, incomplete, and full of guesses—exactly as it should be at this stage. But now those guesses are organized and connected.
• A List of Assumptions: The hidden beliefs buried in every box of your canvas—typically 15-30 assumptions, now made explicit and visible.
• Ranked Risks: Your RATs—the high-impact, high-uncertainty assumptions you need to test first. Usually 3-5 critical assumptions that could make or break your business.
• A Testing Plan: For each RAT, a defined experiment and pre-set success criteria so you know exactly what you're looking for.
• A Clear Priority: You know what to validate before writing a single line of production code.

You now have a structured business hypothesis and a hit list of risks. Final step: Should you actually pursue this idea?