Business Model Canvas: fill it in 45 minutes, scope your MVP

The Business Model Canvas is one page. Nine boxes. It describes how your business creates value, delivers it, and captures money for it. Alexander Osterwalder designed it in 2010 [1], and it’s been used by everyone from Toyota to Y Combinator-backed startups since.

The problem: most founders fill it out once in a startup course, laminate it, and never look at it again. That’s useless. The canvas works when you use it as a decision tool — specifically, when you use it to decide what your MVP should include and what it shouldn’t.

Here’s how to fill it in 45 minutes and walk away with a product scope.

The 9 blocks — in the order you should fill them

Most guides list the blocks in Osterwalder’s original layout. That’s fine for a textbook. In practice, fill them in this order — each one informs the next.

1. Customer Segments (5 minutes)

Who pays you money? Not who uses your product. Who pays. If your product has multiple user types (buyers and sellers, managers and employees), list each one. But highlight the one that writes the check.

Bad: “SMBs.” Good: “E-commerce store owners doing $50K-$500K/month, 1-5 employees, using Shopify, spending $500-$2,000/month on tools.”

The more specific your segment, the better every subsequent box becomes. If you haven’t validated who your customer is yet, our product-market fit framework should come before this canvas.

2. Value Propositions (10 minutes)

What problem do you solve? What gain do you create? For each customer segment, write the specific outcome they get.

Bad: “We save businesses time.” Good: “Store owners reconcile inventory across 3 channels in 10 minutes instead of 2 hours.”

This is the box that connects to your value proposition canvas — a deeper tool for mapping customer pains to product features. If you can’t articulate the value in one sentence per segment, you don’t understand it well enough to build software for it.

3. Channels (3 minutes)

How do customers discover you and how do you deliver the product?

• Discovery: SEO, paid ads, referrals, partnerships, cold outreach
• Delivery: web app, mobile app, API, embedded widget

This block directly affects your go-to-market strategy. If your primary channel is organic search, you need content and SEO before you need a sales team. If it’s enterprise sales, you need a demo environment and sales collateral before you need a blog.

4. Customer Relationships (3 minutes)

How do you interact with each segment? Self-service? Personal account management? Automated onboarding? Community?

For most SaaS products: self-service signup → automated onboarding → email support → optional success management for high-value accounts. The relationship model determines what you build — a self-service product needs great UX and documentation. A high-touch product needs CRM integration and scheduling tools.

5. Revenue Streams (5 minutes)

How does each segment pay you?

Model	Example	Implication for product
Subscription (monthly)	$99/mo per account	Needs billing, account management, churn tracking
Subscription (usage)	$0.01 per API call	Needs metering, usage dashboards, alerts
One-time license	$5,000 per installation	Needs deployment tooling, update mechanism
Transaction fee	2.5% per transaction	Needs payment processing, reconciliation
Marketplace commission	15% of each sale	Needs escrow, dispute resolution, dual-sided flows

Your revenue model has massive product engineering implications. A usage-based model requires metering infrastructure. A marketplace requires payment splitting. Choose the model before you build — retrofitting is expensive.

6. Key Resources (3 minutes)

What assets make the business work? Intellectual property, data, technology, team expertise, brand.

For tech startups, this is usually: the product (codebase), the team (engineering + domain expertise), and the data (customer data, training data, market data).

7. Key Activities (3 minutes)

What must you do daily to deliver value? Product development, customer support, content creation, data processing, partner management.

This maps directly to your team structure and sprint priorities. If “content creation” is a key activity and you have zero writers, that’s a gap.

8. Key Partnerships (3 minutes)

Who do you depend on? Payment processors (Stripe), cloud providers (AWS, Cloudflare), data providers, integration partners, resellers.

Every partnership is a dependency. Dependencies are risks. List them. For each one, ask: what happens if this partner doubles their price or shuts down? If the answer is “we’re dead,” that’s worth noting.

9. Cost Structure (10 minutes)

What does it cost to operate?

Cost category	Typical range (early-stage SaaS)
Development team	$5,000-$30,000/mo
Infrastructure	$50-$500/mo
Marketing	$1,000-$10,000/mo
Tools & SaaS	$200-$1,000/mo
Support	$0-$3,000/mo (often founder-handled)

Add them up. That’s your monthly burn. Divide your funding (or savings) by this number. That’s your runway. If your runway is shorter than your time to revenue, something needs to change — your costs, your pricing, or your fundraising plan.

The full software development cost breakdown helps you estimate the build cost specifically.

From canvas to MVP scope

Here’s where the canvas becomes a product tool.

Step 1: Circle the revenue-critical path. Trace from Customer Segment → Value Proposition → Channel → Revenue Stream. This is the minimum viable business. Everything on this path must exist in your MVP. Everything not on this path is a maybe.

Step 2: List the features each block requires.

Your Value Proposition says “reconcile inventory across 3 channels in 10 minutes.” That requires: channel integrations (Shopify, Amazon, WooCommerce), reconciliation logic, and a dashboard. Three features. That’s your MVP scope.

Step 3: Cut everything else. Your canvas has 9 blocks. Your MVP addresses 4-5 of them. Key Partnerships, Key Activities, and Cost Structure are operational — they don’t need software features. Customer Relationships at MVP stage means “email support and a help page,” not a community platform.

Canvas vs. Lean Canvas — which to use

The Lean Canvas replaces four Business Model Canvas blocks (Key Partners, Key Activities, Key Resources, Customer Relationships) with startup-specific blocks (Problem, Solution, Key Metrics, Unfair Advantage).

Use the Business Model Canvas when: you have an established business model and want to document or refine it. Also useful for pitching — investors recognize the format from business school.

Use the Lean Canvas when: you’re pre-revenue, haven’t validated the problem, and need to move fast from idea to build. The Lean Canvas forces you to articulate the problem first, which prevents building solutions nobody asked for.

Use both: Fill the Lean Canvas first to validate the problem and solution. Then translate to the Business Model Canvas when you’re ready to scale and need to think about partnerships, resources, and operational structure.

---

We turn Business Model Canvases into product specs. Tell us what’s in your 9 blocks and we’ll tell you what to build first, how long it takes, and what it costs. Let’s scope your MVP.

References

[1] A. Osterwalder & Y. Pigneur, Business Model Generation, 2010. Wiley.