What is a Business Model Canvas?
The Business Model Canvas is a one-page framework for describing how a business creates, delivers, and captures value. It was developed by Alex Osterwalder and Yves Pigneur and is associated with Strategyzer. Its nine blocks connect the customer-facing offer with the activities, resources, partners, revenues, and costs needed to support it.
Strategyzer presents the canvas as something to challenge and revise as evidence arrives. Filling every box does not establish that people want the product or that delivery is economically sustainable. Date the version and distinguish observed facts from assumptions so another person can see what would need to change the model.
This guide walks through an original fictional SaaS model. Use the linked official canvas if you want the creators’ visual template. Our download is a supplemental evidence worksheet with original prompts and examples; it does not replace or rebrand the official template.
The nine blocks through a completed SaaS example
BriefBoard is a fictional client-brief tool for small design studios. In this teaching model, a studio buys one workspace subscription, clients provide project inputs through a shared route, and the founder supports a narrow workflow. These are proposed choices, not customer findings or a description of an existing listed product.
Read across the blocks instead of treating them as independent lists. If the target customer changes from a two-person studio to an enterprise agency, the required support, procurement, access controls, distribution, and price may all change. A familiar product category does not guarantee that the rest of the model still fits.
| Block | Example assumption | Evidence still needed |
|---|---|---|
| Customer segments | Small studios preparing recurring client briefs | Recent examples of the job and who can buy |
| Value propositions | See brief inputs and missing information before kickoff | Observed completion of a representative brief |
| Channels | Founder conversations, relevant guides, and referrals | Qualified introductions and attributable trials |
| Customer relationships | Founder-assisted first setup, then self-service repeat use | Actual setup and support effort |
| Revenue streams | A hypothetical $40 monthly workspace subscription | Willingness to pay under stated terms |
| Key resources | Application, reliable storage, documentation, and founder time | Capacity, permissions, and maintenance needs |
| Key activities | Run the service, help setup, resolve failures, maintain the workflow | Time and cost of repeated delivery |
| Key partners | Infrastructure and payment providers | Availability, terms, and switching requirements |
| Cost structure | Delivery usage, shared tools, support, and acquisition effort | Observed cost by account and period |
Start with the customer job and the value exchange
Choose one model and customer situation for the first version. BriefBoard’s example concerns studios that repeatedly prepare briefs and can ask clients to use a shared input route. The person entering information may be a client, while the studio owner buys the subscription. Record that difference so you do not confuse a user’s task with a buyer’s decision.
Connect the value proposition to the outcome the studio wants. Then identify how the buyer can discover, evaluate, start, and continue the workflow. A channel is a proposed route to that exchange; an article view or referral mention does not by itself establish a repeatable acquisition channel.
Keep the first canvas narrow enough to investigate. If you include freelancers, agencies, enterprises, and consumers in one segment box, you may hide incompatible requirements. You can draft separate model versions and compare their assumptions before combining them.
Connect delivery work to a transparent cost scenario
The left side of the model needs enough detail to make delivery credible. Who handles failed submissions, restores an account, keeps providers configured, and updates documentation? Founder time is a resource with a real capacity limit even when it does not appear as an immediate cash payment.
Use an original fictional scenario with ten paying workspaces at $40 per month. Modeled recurring revenue is $400. If direct delivery cost is assumed to be $10 per workspace, that cost is $100 and gross profit under this definition is $300. Subtracting an assumed $60 of shared tools leaves $240 before other costs.
The $240 is not net profit. This simplified exercise leaves out founder compensation, acquisition, taxes, additional overhead, refunds, and cash timing. It holds usage and delivery costs constant. Record omitted costs and replace estimates with observations before using the model to make a spending decision.
| Item | Calculation | Amount |
|---|---|---|
| Recurring revenue | 10 workspaces × $40 | $400 |
| Assumed direct delivery costs | 10 × $10 | $100 |
| Gross profit under this cost definition | $400 − $100 | $300 |
| Assumed shared tools | One monthly estimate | $60 |
| Remainder before omitted costs | $300 − $60 | $240 |
Check the dependencies between blocks
Imagine that the model changes to larger client files with longer storage. That could increase delivery cost, alter the price needed to sustain the service, and add support work. A revenue assumption that looked reasonable under a small-file workflow may no longer fit. Review the connected blocks rather than changing only the cost box.
A second change might be founder-assisted onboarding for every account. It could help initial setup while limiting the number of accounts one person can serve. Write the time assumption per new account and ask what happens when several arrive together. Do not assume that a self-service interface removes all service work.
In the narrow cash scenario above, two workspaces contribute $60 after the assumed per-workspace delivery cost, covering the $60 shared-tool estimate. That is only coverage of those listed costs, not a complete business break-even calculation. The pricing guide and LTV guide help examine the additional definitions and assumptions.
Use the canvas to choose the next evidence to collect
Mark each assumption by its current evidence: untested, supported by an observed task, supported by a transaction, contradicted, or still unclear. Choose the most consequential uncertain link. If studios do not repeatedly need the job, refining infrastructure costs will not fix the customer-side model.
For the fictional example, a bounded next investigation could observe a studio preparing a real permitted brief, record support work, and ask whether the proposed offer fits the buying process. Keep those findings separate from the hypothetical ten-workspace arithmetic. A test plan is not a completed validation result.
The go-to-market guide turns an audience and offer into a coordinated launch plan. The canvas addresses the broader business model, including delivery and economics. Use the documents together and update their shared assumptions when evidence changes, rather than maintaining two contradictory versions of the offer.
Download the business model assumptions worksheet
Our original worksheet records model versions, the fictional financial scenario, dependencies, evidence status, and the next decision. For the visual nine-block canvas, use Strategyzer’s official template linked above. Sources were checked on October 27, 2026.