Lean Canvas in 30 minutes: scope a product, not a thesis

In 2010, Ash Maurya looked at the Business Model Canvas and asked a simple question: why does a pre-revenue startup need blocks for “Key Partnerships” and “Key Resources” when it doesn’t know if anyone will pay for the product yet? [1]

He stripped out four blocks and replaced them with the four things startups actually need to figure out: the problem, the solution, the metrics that prove it’s working, and the unfair advantage that protects it. The result was the Lean Canvas — a one-page tool that forces clarity in 30 minutes.

The Lean Canvas doesn’t replace the Business Model Canvas. It precedes it. Fill the Lean Canvas to validate the idea. Switch to the BMC when you’re ready to scale the business.

The 9 blocks (in the order you fill them)

1. Customer Segments (3 minutes)

Who has this problem? Be specific. “Small businesses” is useless. “E-commerce store owners on Shopify doing $20K-$100K/month with 1-3 employees who manage inventory manually” — that you can build for.

Pick one primary segment. You’ll add more later. Right now, you need to solve one group’s problem so well that they’ll pay you before you have a brand, a sales team, or a second feature.

If you haven’t validated who this is, our product-market fit framework walks you through the validation process.

2. Problem (5 minutes)

List the top 3 problems your customer segment faces. Not the problems you think they have — the problems they’ll confirm they have when you ask them.

Good problems are specific and expensive:

• “I spend 6 hours/week reconciling inventory across Shopify, Amazon, and my warehouse spreadsheet”
• “I lost $12,000 in Q3 because stock-outs weren’t caught until customers complained”
• “I can’t afford a full-time operations person at my current revenue”

Bad problems are vague: “inventory is hard to manage.” That’s a category, not a problem.

List existing alternatives. How do they solve this today? Spreadsheets, manual processes, a competitor’s product, or “they don’t” — each answer tells you something about the opportunity.

3. Solution (5 minutes)

For each problem, write one feature. Three problems, three features. That’s your MVP scope.

Problem	Solution (feature)
6 hours/week reconciling	Auto-sync inventory across 3 channels
Stock-outs not caught	Low-stock alerts with configurable thresholds
Can’t afford ops hire	Dashboard showing inventory health at a glance

4. Unique Value Proposition (3 minutes)

One sentence. What makes you different AND why should the customer care?

Bad: “The best inventory management platform.” Good: “Sync inventory across Shopify, Amazon, and your warehouse in 10 minutes — not 6 hours.”

The value proposition isn’t a tagline for your landing page (though it might become one). It’s the reason someone switches from their current solution to yours. It must be specific, measurable, and obviously better.

This maps directly to the deeper Value Proposition Canvas exercise — which zooms into the customer’s jobs, pains, and gains to validate that your proposition actually resonates.

5. Channels (2 minutes)

How will your first 100 customers find you? Not your first million. Your first 100.

For most early-stage products: direct outreach (LinkedIn, email), communities (Reddit, Slack groups, forums), and content (SEO targeting the problem your product solves).

Don’t write “Facebook Ads” here unless you’ve already tested them. The Lean Canvas captures what you’ll actually do, not what sounds good. Your go-to-market strategy will formalize this later.

6. Revenue Streams (3 minutes)

How do they pay you? Monthly subscription, annual plan, per-transaction, usage-based? What’s the price?

Don’t overthink pricing at this stage. Start with: what would this be worth to the customer? If your tool saves 6 hours/week and the store owner values their time at $50/hour, that’s $300/week in savings. Charging $99/month gives them a 3:1 ROI. That’s defensible.

The software development cost of building the product informs your pricing floor — you need to charge enough to recover the build cost within a reasonable timeframe.

7. Cost Structure (3 minutes)

What does it cost to build and operate? Fixed costs (hosting, tools, salaries) and variable costs (per-customer infrastructure, support time).

For an early-stage SaaS: development cost ($8K-$30K for the MVP), infrastructure ($50-$200/month), and your time. Keep it simple. The goal is to know how many months of runway you have.

8. Key Metrics (3 minutes)

The 3-5 numbers that tell you if the business is working.

For a SaaS:

• Monthly signups (acquisition)
• Activation rate (% who complete onboarding)
• Monthly churn rate (retention)
• MRR (revenue)
• NPS or usage frequency (engagement)

If you’re not measuring these, you’re guessing. And you can’t iterate on guesses.

9. Unfair Advantage (3 minutes)

What do you have that can’t be easily copied? This is the hardest block. Most early-stage startups don’t have one — and that’s honest to write.

Real unfair advantages: proprietary data, network effects, unique domain expertise, existing customer relationships, regulatory moats, deep integrations that create switching costs.

Not unfair advantages: “we’re more passionate,” “our team is great,” “we move fast.” Everyone says that. It protects nothing.

From canvas to code

The Lean Canvas gives you:

• Customer Segment → who to interview and sell to
• Problem → what to validate
• Solution → what to build (your MVP feature set)
• Key Metrics → what to measure
• Revenue Streams → what to charge

That’s a product brief. Take the Solution block, turn each feature into user stories, estimate the build, and start. The canvas prevents the most common startup mistake: building features nobody asked for because they seemed like good ideas.

---

We help founders go from Lean Canvas to working software. Bring your canvas — we’ll scope the MVP, estimate the build, and ship it in 8-12 weeks. Start here.

References

[1] A. Maurya, Running Lean: Iterate from Plan A to a Plan That Works, 2012. O’Reilly Media.