The Business Model Canvas for Product Teams

The business model canvas is a one-page diagram of how an organization makes, delivers and earns from value. Its nine blocks trace back to Alexander Osterwalder's 2004 doctoral thesis on business model ontology, and the 2010 book Business Model Generation, written with Yves Pigneur, made it a standard workshop artifact.

It usually lives with founders and strategy teams. Product teams have a reason to read it too: most product changes move more than one of its nine blocks, and the canvas shows which ones.

The nine blocks

Each block answers one question. The third column lists where a product team would look for the answer.

Block	Question	Where the evidence is
Customer segments	Who are we creating value for?	Account data, personas built from research
Value propositions	What problem do we solve, or what need do we meet, for each segment?	Interview findings, reasons given at signup and cancellation
Channels	How do we reach those customers and deliver the product?	Acquisition reports, app store and marketplace listings
Customer relationships	What kind of relationship does each segment expect?	Support model, onboarding flow, account management
Revenue streams	What are customers paying for, and how?	Pricing page, billing data
Key resources	What assets does the model depend on?	Codebase, data, team skills, licenses
Key activities	What must we do well for the model to work?	Roadmap, on-call and operations load
Key partnerships	Who do we rely on outside the company?	Vendors, platforms, integrations, resellers
Cost structure	What are the biggest costs of running this model?	Infrastructure bills, headcount, payment fees

The canvas is published by Strategyzer under a Creative Commons license (CC BY-SA 3.0), so teams can print, copy and adapt it.

How the canvas is laid out

The blocks sit in a fixed arrangement. Value propositions is in the center. The four blocks on the right (segments, relationships, channels, revenue) describe the customer side. The four on the left (partnerships, activities, resources, costs) describe what the company has to run behind the scenes.

Read across, the layout says the left side exists to deliver the value proposition, and the right side carries it to someone who pays.

The blocks a product team changes

Features exist to make a value proposition true for a segment, so that block is the obvious one. Customer relationships is less obvious: onboarding, in-product help and self-serve settings decide what kind of relationship a customer has with the company, whether or not anyone on the team called it that.

Channels is the block product teams most often forget they own. A free trial, a share link or a listing in another tool's integration directory is distribution, and it was built by the product team. Key activities picks up whatever the product needs to keep working, like content moderation or data cleanup.

Revenue streams and cost structure are usually owned elsewhere, but product changes reach them: a usage-based feature changes what can be billed, and a feature that calls a paid API adds a variable cost per user.

Tracing one product change across the canvas

Take a hypothetical B2B scheduling tool sold to clinics through sales demos and annual contracts. The team is weighing a self-serve plan aimed at practices with one to three staff. Writing the current model and the proposed one side by side, block by block, shows how far the change reaches:

Block	Today	With a self-serve plan
Customer segments	Clinics with 10–50 staff	Adds practices with 1–3 staff
Value propositions	Fewer no-shows across many rooms and providers	Same, plus setup in an afternoon without IT
Channels	Outbound sales, demos	Website signup, search, templates gallery
Customer relationships	Named account manager	In-product onboarding, help center, email support
Revenue streams	Annual contract, invoiced	Monthly card billing
Key resources	Sales team, clinic integrations	Adds a working self-serve onboarding flow
Key activities	Running demos and implementations	Adds onboarding optimization, fraud and chargeback handling
Key partnerships	Practice-management software vendors	Adds a card payment processor
Cost structure	Sales salaries, hosting	Adds payment fees and higher support volume per dollar of revenue

Every row changes. A team that scoped this as "build a signup flow" would be working on the channels row, while revenue, partnerships, activities and costs all move with nobody assigned to them.

The riskiest line is the new promise in the value propositions row: setup in an afternoon without IT. Today a named account manager does that setup for each clinic. If small practices can't finish it alone, the relationships row has to add people back, and the cost row changes with it. A usability test of a prototype onboarding flow with a handful of small practices can check the promise before the plan is priced.

Common mistakes

Features in the value propositions block. "Calendar sync" is a feature. "Clinics stop double-booking providers across locations" is a value proposition. If the block reads like a release note, rewrite each line as the outcome for a named segment.

One canvas for several segments. A clinic group and a solo practice have different channels, relationships and willingness to pay, and one set of sticky notes blurs them. Color-code notes by segment, or draw a canvas per segment once they stop sharing channels.

Drawing only the current model. Two versions next to each other, as in the self-serve example, show a change better than one canvas covered in arrows.

Lean Canvas and the Value Proposition Canvas

The Lean Canvas, by Ash Maurya, keeps the nine-box shape for early-stage products. It swaps four blocks: key partnerships becomes problem, key activities becomes solution, key resources becomes key metrics, and customer relationships becomes unfair advantage. The swaps fit a team that has not proven its problem yet and has no partnerships worth listing.

The Value Proposition Canvas, also from Strategyzer, zooms into the fit between two blocks: customer segments and value propositions. One side profiles the customer's jobs, pains and gains; the other maps the product, pain relievers and gain creators. It sits close to day-to-day product work, and research such as user interviews feeds its customer side directly.

For a decision rather than a model, a SWOT analysis scoped to one product decision answers a different question: whether to go ahead, given what the team knows.

The product insights hub collects the other strategy and research frameworks on TYPENORM.

Frequently asked questions

What is a business model canvas?

A one-page template with nine blocks that together describe how an organization creates, delivers and captures value: customer segments, value propositions, channels, customer relationships, revenue streams, key resources, key activities, key partnerships and cost structure.

Who created the business model canvas?

Alexander Osterwalder, building on his 2004 doctoral thesis. It was popularized by Business Model Generation (2010), which he co-wrote with Yves Pigneur.

What are the 9 building blocks of the business model canvas?

Customer segments, value propositions, channels, customer relationships, revenue streams, key resources, key activities, key partnerships and cost structure.

What is the difference between the business model canvas and the Lean Canvas?

The Lean Canvas, by Ash Maurya, replaces four blocks to suit early-stage products: problem, solution, key metrics and unfair advantage take the places of key partnerships, key activities, key resources and customer relationships.

How do product managers use the business model canvas?

Mostly for changes that reach past the feature itself, like a new plan or a paid integration. Writing the before and after canvas shows the new channel, support load or variable cost that comes with it.

Is the business model canvas free to use?

Yes, under a Creative Commons Attribution-ShareAlike license. It can be copied and adapted with attribution, and an adapted version has to be shared under the same license, which matters for anyone selling a branded template.

Sources: Alexander Osterwalder and Yves Pigneur, Business Model Generation (2010) · Alexander Osterwalder et al., Value Proposition Design (2014) · Ash Maurya, Running Lean (2nd ed., 2012).